I had previously considered your suggestion about the Torque and Velocity documentation. My conclusion was to include the basics of each so as to get new user's started without having to scour several websites and user-lists. This is particularly true with Torque, which has quite poor documentation. In retrospect, without the TDK I never would have been able to learn the Torque concepts.
Right.
I also supposed it would be helpful if the information came heavily from the Turbine perspective, which is something that would be missing with links to the official Torque and Velocity documentation. "Okay, so I can do a #foreach now, but how does that relate to my Screen class and the List that I need to display?".
That's a really good point. I agree. :)
Still, as developers we decouple code, and we should likewise decouple documentation.
What about a combination of the two...contribute lacking documentation to the other projects, link to it, then write an concept-adaptor to bring the concept back into Turbine?
Sounds great.
I have an idea. I think some of the documentation that already exists gets overlooked by newcomers because it's organized poorly. As an example, the TDK how-to has some important basics about developing an app with Turbine, yet people don't read it because it's under TDK on the site. I'm waiting for a response from Michael C. Starkie regarding the thread "newbie create new table" to verify this.
I suggest we reorganize the docs, although I don't have a specific recommendation.
What do you think?
Eric
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
