I think you have something there, if the list widget for IE5 could be more efficient by using DOM, Ns4 can use the current model, because it has less problems with memory leaks. I'm also piddling around with the 1k dhtml API, which works somewhat like DynAPI1, I think it's going to be interesting to use it to manipulate Div's nested inside DynLayers, basically use it for the simple commands, if you don't need all the power of a DynLayer. And it doesn't create an actual object, it simply manipulates an existing Div, so it shouldn't give as many problems with memory leaks. This might also be an option for a leaner list widget. Richard. ----- Original Message ----- From: "Eytan Heidingsfeld" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Saturday, April 21, 2001 9:33 PM Subject: RE: [Dynapi-Dev] Bye, bye > I must say that there is something in what Pascal is saying. When I wrote > that DOM table it took me about 15 minutes because of how simple it is. > I think that we should divide the DynAPI Core (.api, .evnt) in to DOM and > NON-DOM. Development will be so much easier and everything will work faster. > It will mean that some widgets will only have DOM support but that is the > future anyway. IE 4 and NN4 together have around 15% of the market. I'm not > saying lets drop all support of non-DOM browsers. I'm saying let's split > development. DOM and Non DOM. All these problems with list widget is because > of creating hundreds of layers. I think that the avg. amount of Layers per > site should be 20. I know this is inviting the rocks but what do you think? > > 8an > > > _______________________________________________ > Dynapi-Dev mailing list > [EMAIL PROTECTED] > http://lists.sourceforge.net/lists/listinfo/dynapi-dev > _______________________________________________ Dynapi-Dev mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/dynapi-dev
