> -----Original Message----- > From: Nathan Strutz [mailto:[EMAIL PROTECTED] > Sent: Tuesday, December 07, 2004 1:31 PM > To: CF-Talk > Subject: Re: SOT: Browser Stats (stirring the pot) > > Jim Davis wrote: > > That depends on where your logic lies. > > > > In our HTA applications, for example, the presentation is completely > > decoupled from the middle-ware, but is still IE specific (as only IE > > supports HTA). > > Yes, a HTA application would have more than a couple problems running in > Firefox. That's too bad, and one day, I assume, this app would have to > be ported to a longer-term architecture. > > Personally, I hold the belief that using HTAs as a base for a business > application is flawed from the start. Interesting concept though. I > think HTA is perfect for, oh, say, the "IE7" project, that script that > promises to make IE6 render with web standards.
For what it's worth, aside from the use of COM object within the HTA almost all the actual web code in (at least my) HTAs runs fairly well in FireFox. Object-oriented JavaScript is almost completely ignored by the community at large, but is insanely useful in abstracting interfaces and segmenting browser-specific code. HTA's allow us to make highly maintainable interfaces in very short periods of time. If I had my druthers we'd actually be using Flash for this, but the company doesn't want to commit to it. For example, the project I'm building now is a tool allowing a small group (around 5 people) to view and modify mainframe-based (DB2) data for the purposes of data purification and cleanup. The original version of the program was in PowerBuilder, but built very badly. The HTA version works client-side with a WebSphere middleware engine which talks to DB2. The HTA is distributed online (offering instant updates) but has full client-application privileges (registry access, file system access, etc). The HTA application makes extensive use of JavaScript objects for abstraction and portability. It makes structured POSTs to Beans in WebSphere which returns only XML data. In this way the Middleware is completely decoupled from the interface (and interface logic). Because of time constraints we're requiring IE 6 (we need to save money on end-to-end testing and the user base is exceedingly small), but so far the app is working in 5 and 5.5 as well. There are definite issues, but so far it's amazing how much better our applications can be using the technology. Jim Davis ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Special thanks to the CF Community Suite Silver Sponsor - CFDynamics http://www.cfdynamics.com Message: http://www.houseoffusion.com/lists.cfm/link=i:4:186598 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
