AlexT
Thank you for your investigation.

We have tried to implement js gzip + js minifying in Dolphin 7.0.3, but have implemented js gzip only.
Because of the following:

1) js syntax accept code lines ending with semicolon (;) and without it, but minifying scripts require that all lines are ended with semicolon. Dolphin has a lot of js files with both variants - this is a lot of code to change and we postpone it for the future versions.

2) there are already some minified scripts (like jQuery) see more in Dolphin and it can be some problems with minyfying one file where non-minified and minified js scrips are mixed. There is no solution for it right now, after 1) is resolved - I hope some solution will be found.

Now js gzip is implemented and it saves more bandwidth than js minifying. Of cause it is better if both variants are implemented.
DosDawg
AlexT,
if you looked at the source code issues that were pointed out from the evaluation, this amounts to poor and lazy coding. Why would you not use one coding convention, so that you are not creating these performance problems? This was not just about the semi-colon (;), its about much more. There are non-declared variables, against convention. There are variables that are used before they are declared, against coding convention, there is syntax that is just incorrect.

Yes it is a lot of work, see more and just by you saying that, you should realize that selling this product for the amount that it is sold for, is totally ludicrous. The code for the most part can be cleaned up, one coding convention should be used, strict adherence to the coding convention standard should be followed and enforced. Yes there is a lot of javascript within the dolphin application, and that is even more a reason that it should be cleaned and optimized.

The ability to compress the jscript is important for performance, not just bandwidth. JS gzip may as you state save bandwidth, js-minify, increases overall performance, and that is what is being sought after here is a performance increase.

The solution AlexT, is code convention standards, that would resolve the issue with the javascript. Yes its a lot of work, work that should have been done from the onset, and not released and sold as a functional product.

I will point out one issue that was annoying to me, the jscript for IE 5.5 and 6, now honestly, why is that source code still being used, do you know of one soul who is using Dolphin 7 and IE 5.5 or IE 6, doubtful.

at any rate Alex, time-consuming or not, these issues need to be fixed, else, the product should not have been released to the public if its not ready for public consumption.

Regards,
DosDawg
DosDawg
one other thing to note here, is there a valid reason why this post is not showing up on the blogs on IE?
 
 
Below is the legacy version of the Boonex site, maintained for Dolphin.Pro 7.x support.
The new Dolphin solution is powered by UNA Community Management System.
PET:0.040459871292114