If you can write the documentation that would be more than enought to get into the most praised contributors around. Most people that contacts here asks for help and directions on how to use the DynAPI or solve the most common problems ( I wish I had an euro for each time I've been asked about forms inside layers ) rather than requesting new stuff.
I would be nice to have a central page were all external resources are kept but to me documenting is the most important think now. Ok we don't know what's going to happen with the code Dan's working on, but since it is going to be significantly different, there will be lots of people that will hesitate from ( is that correct, hesitate from, or is it hesitate to or what ? ) moving from the current branch and hence they will need some documentation. ---- I'm about to release a very big website we've been doing for a Spanish company, were I've used DynAPI and almost every DHTML trick I know and faced all problems you can think of. When it is released I plan to write an extense doc where I explain how it works, the problems I found and how they were solved, as well as several weird issues I've discovered. I hope that if I share the experiences I've gone through with this project I can help developers in other ways than just pure code help. Regards, Doug Melvin wrote: > I have an offer to the users and developers of DynAPI. > In a couple of weeks I will be taking a week's vacation, > now I know that I'm not supposed to work on a vacation but, > I don't consider DynAPI work.. :-) > > So.. I intend to spend much of that time making up for > not having any real impact on the DynAPI for many moons. > > What I want from you guys is a wish list. > Items that I can do over my vacation. > > If you guys wanbt to play then you should submit your wishes soon so that we > my determine priorities.. and so that I can tell you all flat out what I > will and will not take on.. > > I'lll start the list. These items are in order of my preferences but I am > open to suggestions. > > -Advanced DynAPI tutorial: There is a lot of unharnessed power in the API > that I believe should be documented > > -DynAPI Documentation: Take what exists and modify it to mach the current > state of the API > > -Expansion Pack CVS branch and download page/link > > > > > _______________________________________________ > Dynapi-Help mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/dynapi-help > > _______________________________________________ Dynapi-Dev mailing list [EMAIL PROTECTED] http://www.mail-archive.com/dynapi-dev@lists.sourceforge.net/
