The Arcive of Official vBulletin Modifications Site.It is not a VB3 engine, just a parsed copy! |
|
#11
|
||||
|
||||
One idea for the JavaScript issues:
Before applying the compression replace all instances of <script> ... </script> with $script[x]. Afterwards run a special compression on the script-snippets (which should just ignore <!-- and -->, or maybe strip them but not the text within), then run the compression on the template (as there are no <!-- or // within JavaScripts now there should be no problems) and finally re-substitue the $script[x] with the script(s). |
#12
|
||||
|
||||
is it really so nessary with how vB3 is done?
|
#13
|
|||
|
|||
You can get information here:
http://leknor.com/code/gziped.php Simply enable it on your forum then enter your forum's url and you can see what benefit you're getting |
#14
|
||||
|
||||
faranth,
yes, it does make a difference ... especially in the long run. Less bytes = Less bandwidth / faster rendering (client side) / also, makes it harder to read source code (client side) It's similar to putting entire source code (client side) in one line. I like KirbyDE's idea - about doing the compression before hand.:up: cirisme, two different end results ... not the same thing |
#15
|
||||
|
||||
Quote:
|
#16
|
||||
|
||||
all you have to do is look at the source code here and you will see a lot of
S P A C E It's really a personal choice. However, as a web professional, I make sure my customers/friends get maximum results for their money. |
#17
|
|||
|
|||
Quote:
|
#18
|
|||
|
|||
I used the vb2 version and it worked straight up for me. I have been using it for about a two weeks now with no problems. Then again im running a ported version of the vb2 microstats hack that i brought over a while back.
|
|
|
X vBulletin 3.8.12 by vBS Debug Information | |
---|---|
|
|
More Information | |
Template Usage:
Phrase Groups Available:
|
Included Files:
Hooks Called:
|