----- Original Message ----- From: "Laszlo Teglas" <[EMAIL PROTECTED]>
> If you want you can be in charge of the css. All I ask is that you keep my > class definitions. Feel free to change anything inside the curly brackets. > Also try to stick to the browser friendly color palate. Ok, we'll see how that turns out, I like your flexible approach though. > But as of yesterday, one fundamental issue may change the structure of the > documents. "To Widget, Or Not To Widget" That is the question. It seems that > most of you are eager to get rid of the widgets as part of the official > distro, while others want to keep them for testing purposes, still others > want to keep them and expand on them as fundamental building blocks. If we > will scrap the widgets, there is no point in documenting them. And if all of > you are just going to sit around and wait for Dan to release his new set of > widgets, than also there is no point in documenting our current widget set. > Because our own widgets will never be maintained after Dan's release. It is > not fair to expect one person to do all the work, and I can see why Dan > would want to charge for it. I just don't see how Dan will protect his hard > work, by creating generic widgets that could look very similar to others who > had the same idea, but that is for Dan to worry about. We as a community > need to decide: > > Do we want widgets with our distro??? Well, yes, the current modest widgets should be kept, and improved upon as needed, so we can keep testing our code is working as it should, and as an example to others. The reason they have never been changed is, I got the impression they were "hands-off". Any changes ever suggested on the list, like extra functionality for imageanim, replacements for loadpanel, or new widgets, were always skill-fully ignored, so I got the impression that these widgets were Dan's work, and shouldn't be messed with. Now that Dan clearly stated that he had expected the widgets to have been overhauled long ago, I think that has been cleared up, and we can start to look at which widgets are in there, which we need, and what's wrong with the ones we have. I would recommend that the DynAPI widgets be real simple - more building-blocks than anything else, but that they work well, in all browsers. I would suggest leaving things like treevieuws, and lists for the widget-packs, and sticking with loadpanels, scrollpanes, buttons, image-loader, scrollbar etc. Trying to keep the widgets light-weight, and cross-browser. Cheers, Richard. _______________________________________________ Dynapi-Dev mailing list [EMAIL PROTECTED] http://www.mail-archive.com/[email protected]/
