Thats good. Btw: If I were you I would set the Netscape bar to version 7 (or any mozilla version above 1). Netscrap 6 is based on a pre-1 version of Mozilla, and has a couple of very nasty bugs that can make trying to do certain DHTML things an absolute nightmare. (Such as not submitting values for controls that are under hidden nodes, etc...)
The other thing to keep in mind is that JavaScript widgets always seem to take far longer to implement than you think they will! - So the simpler you can keep things the better, and as with all languages using good programming techniques in JavaScript will pay off when it comes to maintenance and enhancement. Its very easy when coding JavaScript DHML stuff to just anyhow try and bang together something that runs but where the code is very ugly. Ive learnt the hard way that it quickly becomes a nightmare to maintain! (and yet I keep doing it. garrgh! (99.9% of the freely downloadable JS widgets to be found on the net on various DHTML sites are nasty like this. Its often actually easier to roll your own than to try and find a suitable widget out there and modify it for your needs (tree components being a prime example)) So even if its just a simple widget like the two box selector thinghy, sitting down to design it properly , and make it modular and reusable (for example writing a custom tag to encapsulate it in a way that seems transparent to the page designer), will pay dividends! If your not totally familiar with the subtle details of JavaScript (how objects work, prototyping, implicit type casting etc...), spending a day studying the language in detail (ie: actually making notes like you did back in college) will be a day well spent! (it will save you at least a week debugging!) hth Andrew -----Original Message----- From: Wendy Smoak [mailto:[EMAIL PROTECTED] Sent: Friday, 19 December 2003 22:36 To: Struts Users Mailing List Subject: RE: OT: Examples of HTML-based user interfaces? > From: Andrew Hill [mailto:[EMAIL PROTECTED] > Still, if you are in a position to limit your audience (such as with > intranet apps) to just the more common modern browsers (IE5+, > Mozilla) there is indeed a lot you can do with DHTML. I should have said that up front-- it is intranet and we can (and do) refuse to support browsers which won't play nicely. All I officially have to support is a reasonably recent IE & Netscape. And they can't disable javascript, or they won't get very far. :) I don't go out of my way to break stuff on other browsers (and I test from home on Mozilla/Konqueror) but if it gets to be too much trouble, I don't have to mess with it. Thanks for the tips! -- Wendy Smoak Application Systems Analyst, Sr. ASU IA Information Resources Management --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
