IWETHEY v. 0.3.0 | TODO
1,095 registered users | 0 active users | 0 LpH | Statistics
Login | Create New User
IWETHEY Banner

Welcome to IWETHEY!

New I disagree.
The DOM in IE 5.5 is actually pretty stable. You can do a lot by sticking to the W3C DOM, though the IE5.5 extensions are convenient. I know this because I (currently) build intranet web pages for a living; mostly with PHP but for client-side stuff, JavaScript is the only option. We currently target IE 5.5, but we'd like better cross-browser compatibility. In our sights next is IE 5.1/Mac, then IE 5.0/Win32, then NetScape 6 (probably 6.2). Opera is further down the list than it should be because they're actually behind everyone else with their DOM implementation. And Netscape 4 had already been ruled out.

Wade.

"All around me are nothing but fakes
Come with me on the biggest fake of all!"

New consistent bugs
(* The DOM in IE 5.5 is actually pretty stable. *)

Meaning that the bugs are consistent? I found at least 2 repeatable, and significant bugs in IE 6. Sure, there are probably workarounds, but if every feature is nothing but a workaround, then you have a mess to maintain. You end up practically micromanaging each pixel. It makes assembler look easy.

It is very painful to make it act like a "desktop" GUI. JS+DOM+HTML *are* optimized for e-brochures and NOT business forms. You have to jump thru hoops for some of the otherwise simplest things (from a VB/Delphi perspective).

Something that would take 10 lines in VB/Delphi could end up being several hundred in JSDOMHTML.


________________
oop.ismad.com
New Haven't tried IE6.
But it does sound like you're trying to make JS+DOM do something it isn't suitable for.

Wade.

"All around me are nothing but fakes
Come with me on the biggest fake of all!"

     Flashback - (drewk) - (32)
         DOM is a lost cause - (tablizer) - (31)
             I disagree. - (static) - (2)
                 consistent bugs - (tablizer) - (1)
                     Haven't tried IE6. - (static)
             Perhaps you should read this: - (pwhysall) - (27)
                 event driven - (tablizer) - (26)
                     Quoting - (ChrisR) - (6)
                         WYSIWYG - (tablizer) - (5)
                             Use blockquote. - (pwhysall) - (4)
                                 still not WYSIWYG - (tablizer) - (3)
                                     Get over yourself - (pwhysall) - (2)
                                         whatever - (tablizer) - (1)
                                             Mistyped HTML... - (admin)
                     GUIs over HTTP. - (pwhysall) - (8)
                         Java applets == fat client (-nt) - (tablizer) - (7)
                             Er, no. - (pwhysall) - (6)
                                 Obese - (tablizer) - (5)
                                     Still wrong. - (pwhysall) - (1)
                                         You are missing the point. - (tablizer)
                                     I've got a better example. - (static) - (2)
                                         Exception to the rule - (tablizer) - (1)
                                             Huh? - (imric)
                     Re: event driven -> ASP.NET - (altmann) - (9)
                         Real GUI's or bust - (tablizer) - (8)
                             I realize... - (altmann) - (2)
                                 question, and Master Image - (tablizer) - (1)
                                     Similar to .NET - (altmann)
                             I find CGI approach wonderfully limiting - (tseliot) - (4)
                                 Agree for the most part... - (ChrisR)
                                 Spank-A-Matic ? - (tablizer) - (2)
                                     Sorry, I misunderstood. - (tseliot) - (1)
                                         The pudding is not even in alpha - (tablizer)

Out of respect for Apple's good name, this LRPDism has been censored.
57 ms