Standard and Optimized versions are NOT the same

23 July, 2008 - 14:47 — risala

We are under the impression that the optimized version of client framework is what we should be deploying in production but, evidently what is released in non optimized version (ie. standard) is not identical to optimized. Here's my evidence.

For a menuPopUpItem if it is disabled, the standard version correctly adds .btl-disabled same menuPopUpItem if used with the optimized files will not add the class and menu does not appear disabled.

Since we cannot trust the optimized version and we are not going to test both versions, we have to now use the non optimized version in production. Kind of defeats the purpose of purchasing the license instead of using the "free" edition.

So now what?

Hi, the Standard and

23 July, 2008 - 15:12 — Sjoerd

Hi, the Standard and Optimized versions should code-wise be the same, the only difference between them is that the bindings are optimized (e.g. the white-spaces and comments are removed). And that the engine has less debug information (and misses the debugger).

We always test both versions in our automated testing, and both report the same result.

Testing the Menu in the Backbase Explorer (http://demo.backbase.com/explorer/#|examples/menuBarDisabled.xml) which runs the optimized 4.2.1 version doesnt show me the problem, can you provide a testcase maybe?

Use Case

23 July, 2008 - 18:01 — risala

The only thing different I see in demo vs what I am doing is that my popUpMenuItems have behavior assigned to them.

<b:popUpMenuItem id="mnuSave" e:behavior="ssd:saveMenu" disabled="true"/>

During various activities in the page I execute command as

bb.document.getElementById('mnuSave').setAttribute('disabled','false');

I use firebug to detect the difference in class attribute of TR, optimized version (at least the one I have) does not add btl-disabled and standard version does.
Please check with the optimized version that is available for download so we are talking the same source.

Further Evidence

31 July, 2008 - 01:38 — risala

In Optimized version, btl/loadingMessage folder is empty and there is another folder called btl/loadingM
In debug version loadingMessage/Chameleo folder has the content and Chameleon folder is empty

Your download package must

4 August, 2008 - 08:13 — Sjoerd

Your download package must be corrupted then, the bindings are not renamed in my package. Please try to download an other copy.

I used WinRAR to unzip, what program do you use?

Unzip

4 August, 2008 - 17:58 — risala

I originally used easyzip. After your comment I downloaded the package again and unzipped using 7-Zip and the folders are correct. So it looks like either the download or unzip was corrupted. Yikes..

Client Framework