That is indeed a good idea.. so good in fact.. we already thought of it..
:-) hehe.. I don't know i this was actually inplemented in DynAPI3 but I sure as hell hope it has.. asking the same "if" for each layer of a 300 node tree would seem a little redundant to me.. (hint hint) And yes.. I am actually using DynAPI for a tree that floats from 300 to 500 hundred node depending on the latest inventory.. ( NS 4.x only) http://www.figure8.net/fakeFrames2.html?page=catalog/catalog.html ----- Original Message ----- From: "Joy Ride" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Sunday, February 09, 2003 11:42 PM Subject: [Dynapi-Dev] Some ideas for DynAPI3 > Hello, > > We have few ideas for DynAPI3. Since we haven't involved in to DynAPI3 > development earlier it may be that these ideas have been taken in to DynAPI3 > allready :-) > > The number one issue in our mind are posibility to have alternate browser > JS-modules ("browser transforms"). We believe that this would improve the > compability and speed of DynAPI. > > The basic idea goes like this: > > 1) There is one set of js-files, which is called DOM or Basic set > 2) Then there is browser / platform family set of JS-files ("browser > transforms") as well as browser version related set of JS-files ("sub > transforms"), which will replace or add certain things in to basic set ... I > call these browser transforms > 3) Browser detection is in one JS-file and there is browser description JS > file, which anounces the JS-files to be loaded with each browser ... all the > other JS-files do not call or contain browser detection of anykind. > > This approach would allow users to write their own browser transforms > (extensible support for any browser available). It would make the browsers > optimization for speed and compability easier. This would enable easier > browser by browser bugfixing, and it would make the compability tests and > problem isolation easier (some times fix will cause incompability with other > browser). This approach will reduce the amount of code to be downloaded each > time (only the code needed for certain browser would be downloaded). Placing > the browser detection only in to one place would propably speed up the > excecution speed of DynAPI quite much also. > > The transforms could be used also when only a limited set of features would > be needed --> light version of JS-files. > > > > - Juho Risku / Visualway Design Oy > > > _________________________________________________________________ > Add photos to your messages with MSN 8. Get 2 months FREE*. > http://join.msn.com/?page=features/featuredemail > > > > ------------------------------------------------------- > This SF.NET email is sponsored by: > SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! > http://www.vasoftware.com > _______________________________________________ > Dynapi-Dev mailing list > [EMAIL PROTECTED] > http://www.mail-archive.com/[email protected]/ > ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ Dynapi-Dev mailing list [EMAIL PROTECTED] http://www.mail-archive.com/[email protected]/
