>
> but you didn't answer my question about precreation of
> document children.
Precreation code made the DynAPI alot faster (when used correctly in
widgets) and it
also seems to have made the NS4 version more stable when creating many
layers/child layers.
You simply can't compare those two things. The one is a feature used by only
a few people
the other one is created to make the dynapi faster and more stable.
> as this is currenlty not shown to be in use anywhere. it is
> not also a feature
> that can be left alone until we get the rest of the code working.
It IS used, every child layer added before the creation of the parent it
using the
precreate.. it will write a div string instead of creating a new object (in
NS this might
also save some memory problems)
> I'm all for getting the bugs out first. but if the code has
> no room for errors,
> I see no point in stopping it's inclusion.
please read my other reply to Eythan's mail.
> we need to have a series of docs written that outlines
> EXACTLY how a method is
> expected to work. This will allow for simple comparison
> between the various
> versions.
the problem is this: post this as a seperate mail, requesting EVERYONE to
spawn there ideas on methods and stuff.. there won't be many people helping
you out
(I remember some talk about DynAPI-next-gen a while ago.. what ever
happened!? disillusioned rock-throwers!?)
So writing outlines is a waste of time (at least for me) because nothing is
ever accomplished.
damn.. I'm in a bad mood :)
Pascal Bestebroer ([EMAIL PROTECTED])
Software ontwikkelaar
Oberon Informatiesystemen b.v.
http://www.oibv.com
_______________________________________________
Dynapi-Dev mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/dynapi-dev
