On thing to do is to try to save as much memory as possible. The tendency seems to be that if a variable can be used, it will be used. For example, the property isChild in dynobject is not needed at all. The information is already in the parent property. isChild==(parent!=null). The other thing to do is to try to save some code. Or to modularize it a bit. One thing that could be used more extensively, is the dynamic extension of objects. The ideal situation could be of course that if you dont need to support netscape, just leave the netscape module out. Currently all that kind of code is just inside if else loops in dynobject. Just a couple of ideas, Tuomas Huhtanen _______________________________________________ Dynapi-Help mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/dynapi-help
- RE: [Dynapi-Help] Splitting the API Pascal Bestebroer
- Re: [Dynapi-Help] Splitting the API bob basques
- Re: [Dynapi-Help] Splitting the API bob basques
- Re: [Dynapi-Help] Splitting the API Stephan Tolksdorf
- RE: [Dynapi-Help] Splitting the API Digital Strider
- Re: [Dynapi-Help] Splitting the API Doug Melvin
- RE: [Dynapi-Help] Splitting the API Digital Strider
- Re: [Dynapi-Help] Splitting the API Michael Pemberton
- Re: [Dynapi-Help] Splitting the API Nick Pelling
- Re: [Dynapi-Help] Splitting the API Doug Melvin
- Re: [Dynapi-Help] Splitting the API Tuomas Huhtanen
- Re: [Dynapi-Help] Splitting the API Richard Bennett
- Re: [Dynapi-Help] Splitting the API Doug Melvin
- Re: [Dynapi-Help] Splitting the API Marc van Leeuwen
- RE: [Dynapi-Help] Splitting the API Tuomas Huhtanen
- Re: [Dynapi-Help] Splitting the API Richard Bennett
- Re: [Dynapi-Help] Splitting the API Marc van Leeuwen
- Re[2]: [Dynapi-Help] Splitting the API Robert Rainwater
- Re[2]: [Dynapi-Help] Splitting the API Marc van Leeuwen