I have 2 cents to spend: Many things are crucial in dynamic content - one important one is performance (otherwise it's not very dynamic to the eye, I would say). I have done some heavy lifting, with JS and DHTML - namely a project management application with full waterfall (read:dependency) Gantt charts, drag and drop, spreadsheet-like grid data entry, etc.
I have also done some DHTML and XMLHTTP work (basically the same methods AJAX uses) with an application that supports IE aswell as FF. IE and FF use different event models, and rendering DHTML is always different: you know one pixel here, one pixel there, margins inside, margins outside, etc. pp. If you have gone down this road, you know... So AJAX packages (DOJO, ATLAS,..) are basically putting a layer between you (your application) and the different browsers. This means it's basically a translator for your code... unfortunately, this also means a loss in performance. Also, with AJAX your apps will perform differently on different browsers - just as strong as the translation of code and more relevant the rendering of DHTML (a big one). If you use FLASH, its going to be as fast or slow as FLASH is - fast in most cases ;-) Plus you can trust that if an app runs on one platform it will run on pretty much any other that supports Flash - with the same look and feel - I shoudl add. Now add to this, all the nice effects, transistions, moves, etc. for DYNAMIC experience... I think you sould rephrase into "CAN AJAX compete with FLEX" ;-) Sorry, but it had to be said... --- In flexcoders@yahoogroups.com, "thetexaspsycho2003" <[EMAIL PROTECTED]> wrote: > > I mean, creating something as simple as a dynamic ID is crucial in > creating truly dynamic content. >
