IMHO: the main reason for the lack of docs is that when people where interested in doing docs, the DynAPI group was spending 99% of our time arguing over the future of the DynAPI.. There where questions as to weather the API would be branched, or replaced, or re-worked. At the time, anyone who DID want to do docs would have been rather discouraged by the API itself changin for minute-to-minute..
All that asside tho, I agree that now that the API has reached some stability (Implementation-wise) Documentation should be a priority. Assuming that I am not loaded down with work when I get home from work (full-time job Plus Startup company) I will start on a tutorial. I know, we need API documentation, but I feel like doing a tutorial.. :-) Obviously, I'll build it on top of what exists. Later, Doug Melvin aka: Crazy Programming Doug (CPD) ----- Original Message ----- From: "David Corbin" <[EMAIL PROTECTED]> To: "Jordi Ministral" <[EMAIL PROTECTED]>; "Dynapi (E-mail)" <[EMAIL PROTECTED]> Sent: Monday, October 22, 2001 5:05 PM Subject: Re: [Dynapi-Help] Re: Documentation (was: Dynapi-Help digest, Vol 1 #698 - 7 msgs) > I know I like to code better than write documentation. But consider the > long-term ramifications. Write better documentation. The community grows. > More coders start contributing code. Everyone is happier :) > > Just a thought. > David Corbin > > ----- Original Message ----- > From: "Jordi Ministral" <[EMAIL PROTECTED]> > To: "Dynapi (E-mail)" <[EMAIL PROTECTED]> > Sent: Monday, October 22, 2001 5:36 AM > Subject: Re: [Dynapi-Help] Re: Dynapi-Help digest, Vol 1 #698 - 7 msgs > > > > I'm the first one to admit that the documentation is a lot to wish for, > > and it is outdated. However, as I have stated lots of times, we don't > > have the time to do both the coding and the documenting. In fact, we > > barely have the time to do the coding. There's a documentation center > > where everybody can contribute. Either someone joins in or I'm afraid > > the docs are going to continue being a bit of a disapointment. > > > > > > Hansen Jakob Veje wrote: > > > > > Hi > > > > > > Although I agree that you should have working knowledge of javascript > and > > > browsers in general - ie. already be a web developer, to use the API, I > > > don't see that as an excuse for invalid documentation that confuses more > > > than it helps. I too had a lot of trouble figuring out how to write a > > > widget. The documentation didn't work or was inaccurate, so I ended up > > > looking at sources of existing widgets instead. > > > > > > I'd gladly give the widget source-code (although undocumented) to anyone > > > interested. It's a clickable vertical listmenu that probably works with > N > > > nested submenus. I've only tested it thouroughly with 2 levels for now. > > > > > > I'm not flaming here, only agreeing that the documentation has a lot to > wish > > > for. I think the DynAPI is a tremendous help in creating crossbrowser > DHTML, > > > and wouldn't live without it. I really appreciate the work that has been > > > done by the contributors, and do realize that it's unpayed pioneer work. > > > > > > Kind regards, > > > > > >>--- > > >>Jakob Veje Hansen - mailto:[EMAIL PROTECTED] > > >>WM-data eSolutions > > >>Tel: +45 8744 4619 - Mobil: +45 2169 0361 > > >>http://www.wmdata.dk > > >> > > > > > > _______________________________________________ > > > Dynapi-Help mailing list > > > [EMAIL PROTECTED] > > > https://lists.sourceforge.net/lists/listinfo/dynapi-help > > > > > > > > > > > > > > _______________________________________________ > > Dynapi-Help mailing list > > [EMAIL PROTECTED] > > https://lists.sourceforge.net/lists/listinfo/dynapi-help > > > > > > > _______________________________________________ > Dynapi-Help mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/dynapi-help _______________________________________________ Dynapi-Help mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dynapi-help
