Mailserver was down yesterday, so I don't know if this got through... --------------------
Bfff there are so many thinks I'd like to comment that I don't know where to start. Whereas the concept is nice from a Software Engineering point of view, I'm not sure it is the best way to go IN THIS PROJECT and IN THIS MEDIA, where size does matter and speed does matter. I've had to rewrite my own widgets in the past and Its a pain in the ass, but sometimes I've also had to strip down the files of the DYNAPI because either the size or the performance of the whole project were unbearable. Honestly, I haven't been able to build an opinion yet. If some of you want to discuss and develop a widget spec that works over the DynLayer structure and grows from there, great. I'll stay a little bit below you, doing the dirty DHTML stuff which needs to be done regardless of what you build on top of it. Sourceforge allows to have several release blocks. What if I we totally split the widgets and the core files in two different release blocks ? Then it would be easier for some of us to keep with the core as well as some others build widget packs and mantain those. They could be released separately, and each widget pack release would specify in which DynAPI core release is it supposed to work. I think this solution would allow for "8an-thinking" developers to start implementing their ideas as well as providing space for the new branch Dan is preparing, which could be released appart. What do you think ? Regards, Jordi "thereIsSpaceForEverybody" Ministral _______________________________________________ Dynapi-Dev mailing list [EMAIL PROTECTED] http://www.mail-archive.com/[email protected]/
