I think ZDNet hold the copyright, and the author , Rick Scott. I guess we'd need permission from ZDNet to host the tutorials on our server, and from Rick Scott to update the content, but I'm not sure. Probably the easiest is to send him a mail and see what he says.
ZDNet have a terrible searchengine, it doesn't return any results for Dynapi, while they have 6 articles on it there! part1 http://www.zdnet.com/devhead/stories/articles/0,4413,2688979,00.html part2 http://www.zdnet.com/devhead/stories/articles/0,4413,2695172,00.html part3 http://www.zdnet.com/devhead/stories/articles/0,4413,2703838,00.html part4 http://www.zdnet.com/devhead/stories/articles/0,4413,2712462,00.html part5 http://www.zdnet.com/devhead/stories/articles/0,4413,2712462,00.html part6 http://www.zdnet.com/devhead/stories/articles/0,4413,2771447,00.html his frequent references to "The DynAPI Four" are funny, I imagine them galloping away into the sunset, or singing songs from under their sombreros :o) Richard. ----- Original Message ----- From: "Doug Melvin" <[EMAIL PROTECTED]> To: "Richard Bennett" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Tuesday, November 13, 2001 9:58 PM Subject: Re: [Dynapi-Dev] wish list > Who owns the one's on ZDnet and What's the location (URL please)? > > ----- Original Message ----- > From: "Richard Bennett" <[EMAIL PROTECTED]> > To: "Doug Melvin" <[EMAIL PROTECTED]>; > <[EMAIL PROTECTED]> > Sent: Tuesday, November 13, 2001 2:47 PM > Subject: Re: [Dynapi-Dev] wish list > > > > Yeah, the documentation would be a good thing. > > I think what we are missing doc-wise is a starter tutorial. Pascal's > > tutorials should also be checked, to see if they are still up to date, but > > we are missing something that explains the basics, like the directory > > structure, why you shouldn't use doctypes, why you can't get inner html > from > > inline layers, why we use simple, and normal eventlisteners, and when > etc... > > Or otherwise a walk-through tutorial, showing how to create, for instance, > a > > dynapi powered chat interface, or something. > > Another thing, the tutorials on ZDNet contain lots of errors, and are not > on > > our servers, if we get permission, (if needed) we could correct them, and > > add them to the docs. > > > > just some ideas... > > Richard. > > > > > > > > > > ----- Original Message ----- > > From: "Doug Melvin" <[EMAIL PROTECTED]> > > To: <[EMAIL PROTECTED]> > > Sent: Tuesday, November 13, 2001 5:03 PM > > Subject: Re: [Dynapi-Dev] wish list > > > > > > > Well, that's one vote for DynAPI Documentation.. > > > I gues that makes two votes total and pushes it to the top of the list. > > > > > > Da List: > > > > > > 1)DynAPI Documentation: Take what exists and modify it to mach the > current > > > state of the API > > > > > > 2)Advanced DynAPI tutorial: There is a lot of unharnessed power in the > API > > > that I believe should be documented > > > > > > 3)Expansion Pack CVS branch and download page/link > > > > > > By the way, it would be "...will hesitate to move from... > > > > > > ----- Original Message ----- > > > From: "Jordi Ministral" <[EMAIL PROTECTED]> > > > To: <[EMAIL PROTECTED]> > > > Sent: Tuesday, November 13, 2001 10:52 AM > > > Subject: Re: [Dynapi-Dev] wish list > > > > > > > > > > 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/ > > > > > > > > > _______________________________________________ > > > Dynapi-Dev mailing list > > > [EMAIL PROTECTED] > > > http://www.mail-archive.com/dynapi-dev@lists.sourceforge.net/ > > > > > > > > _______________________________________________ > Dynapi-Dev mailing list > [EMAIL PROTECTED] > http://www.mail-archive.com/dynapi-dev@lists.sourceforge.net/ > _______________________________________________ Dynapi-Dev mailing list [EMAIL PROTECTED] http://www.mail-archive.com/dynapi-dev@lists.sourceforge.net/
