Personally I have never considered the widgets part of the DynAPI. I've always been reluctant to include the widgets as part of the core distribution because I found it to be a wrong approach, but as people wanted them includes, I kept them.
I've used the dynapi in many projects, yet I have always used my own widgets instead of the 'default' ones which, as a user, I don't like. From the very begining (I'm speaking YEARS) everybody has been encouraged to write its own widgets using the dynapi. A few have been written, some of them contributed back. The strength of the API is the platform it gives you to develop more complex things on top of it, not the label widget. I know it is easier to expect Dan to create, document and mantain his widgets for free, as it would be a waaaay better world if we had thousands of DynAPI widget packs around to choose from for free, as in the PERL community, but this is not the case. Dan selling widgets is ok, because he owns them, as Doug pointed out. Mine are free ( which reminds me that I should get my website up again ) but because I decide so, it has nothing to do with the DynAPI. If you downloaded a Java class from any author you wouldn't expect direct support from Sun nor would you blame them if the author wanted you to pay for that class, would you ? Just ranting, nice work with the docs :) I wouldn't want to 'rock' you too hard after all the effort you're putting in this. We're low on contributors. _______________________________________________ Dynapi-Dev mailing list [EMAIL PROTECTED] http://www.mail-archive.com/dynapi-dev@lists.sourceforge.net/
