Thursday, June 23, 2011

How to destroy a nice application? Have it run on IE

Damn IE. I have been working for months on an application that uses a lot of Dojo. It is a fairly complex application with the user interface sitting all on one page with 5 dialog box, data grids, lots of xhrPosts and xhrGets, and many other visual affects. Of course everything works on Chrome and Firefox, but it crashes on IE during testing yesterday. Now I have to spend an enormous amount of time debugging why it crashes in IE. I suspect it is the datagrid which is very sensitive.

3 comments:

nick wall said...

Richard,

We have a system in production that uses dojo 1.5 and another using dojo 1.6. We use dialog boxes, loads of grids, TimeTextBoxes, Panels, xhr, layout regions, charts...laods. Our application gets used continuously by users for hours on end. We had many, many issues with memory issues with dojo. Check you do not bind to DOM and dijit, we ended up actively destroying lots of our objects. We need to make use of the dodjo tool to do a custom build, I found it reduced the size of overall dojo files passed down (to 1 file), but it was still pretty big!...but better than 180 odd individual files it is sending down to client (once client has them cached it is OK, but coming in for first time...ooof!). Our app is cross browser, and works well, but we always tested for IE first, then the others for the reasons you are bumping into. We went with dojo since it is "integrated" with Domino, but in hindsite, I prefer the look of ExtJs.

Good luck.

Nick

nick wall said...

Richard,

We have a system in production that uses dojo 1.5 and another using dojo 1.6. We use dialog boxes, loads of grids, TimeTextBoxes, Panels, xhr, layout regions, charts...laods. Our application gets used continuously by users for hours on end. We had many, many issues with memory issues with dojo. Check you do not bind to DOM and dijit, we ended up actively destroying lots of our objects. We need to make use of the dodjo tool to do a custom build, I found it reduced the size of overall dojo files passed down (to 1 file), but it was still pretty big!...but better than 180 odd individual files it is sending down to client (once client has them cached it is OK, but coming in for first time...ooof!). Our app is cross browser, and works well, but we always tested for IE first, then the others for the reasons you are bumping into. We went with dojo since it is "integrated" with Domino, but in hindsite, I prefer the look of ExtJs.

Good luck.

Nick

Domino Interface said...

Nick,

Thanks for your comments. I was able to locate the problem and fix the datagrid issue that was being created. I am not familiar with ExtJs, but I do like Dojo and how it structure. For a public facing sites, I use the CDN from Google or AOL. An example is our mwlug.com site. It is much faster especially, Domino 8.52, which is so slow in loading dojo. For internal site I have stuck with 8.51 which loads so much faster.