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.

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
June 24, 2011 at 8:22 AM
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
June 24, 2011 at 8:23 AM
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.
June 24, 2011 at 10:23 AM
Post a Comment

Popular posts from this blog

The iPhora Journey - Part I - Reimagining Domino

Domino, which is currently owned by HCL Technologies, is one of the most enduring application platforms ever built. It owes its existence to Ray Ozzie, who was heavily influenced by his use of the PLATO system, a pioneering interactive/educational network at the University of Illinois. The first version of Domino (then called Lotus Notes) was released in 1989, and Domino applications from 1989 can still run on the newest version (12.01). You can build Domino applications for deployment on the Notes clients, mobile devices, or Web browsers, and for programming and customization, you can use Nodejs, Java, LotusScript, and Formula language, or any combination of them. Regardless of which programming languages are used, a typical application is usually represented by a single Domino database. However, the IT landscape has changed significantly since Domino was a dominant player in the market. The migration to web and mobile applications using cloud-based solutions has led to the steep decl
Read more

Creating Composite Applications for Classic Lotus Notes Clients – Part 2

Image
This is part 2 of my creating composite application for classic Lotus Notes clients. In part 2, I will cover how a new event in Lotus Notes 8 can used to simplify the process of creating a composite application. You can download the demo code from the sidebar or download it from here. This new event is "onSelect" and is found in Notes View. This event works not only for regular views but also for embedded views and even embedded views within a dialog box. This event is triggered whenever a document is selected in a view. It hold true even when the view is display for the first time. As a Notes developer, I feel this one single event is more than enough reason to upgrade to at least the Lotus Notes 8 Basic client. It makes a number of UI issues simply go away. Just like in the previous Lotus Notes clients we need to create a launch document in our composite application that will be used to trigger the population of the frames in the composite application. However, rather than
Read more

The iPhora Journey - Part 5 - Dammit Jim, I'm a LotusScripter not a JavaScripter

Image
As often said by Dr. McCoy in the original Star Trek series, he is a doctor, not a ____________ .  However, just like Dr. McCoy, you may sometimes need to work on things that seem very alien to your experience.  One of those things, might be JSON. LotusScript, which was derived from Visual Basic, was written long before JSON existed, and therefore, LotusScript had no built-in capabilities for handling JSON objects. As we mentioned in Part 4, JSON plays a critical role in iPhora.  All data are stored as JSON, and JSON serves as the primary data and communication format between modules, functions and services.  All core components operate using JSON-based configurations.  Therefore, it was extremely important that we are able to fluidity create, read and process JSON.   Creating a JSON string is relatively easy in any programming language. You can create it even using Commodore 64 Basic, and if built sequentially, one line at a time, it is possible to create JSON representations of ve
Read more