On 10/22/07, Alberto Valverde <[EMAIL PROTECTED]> wrote: > > - hard to use (basically no docs) > > Fair enough. This is something I would really have liked to solve long > ago but seems like some sort of mental blockade of mine. I've tried my > best to personally give support in TW's mailing list to anyone needing > help (secretly hoping users would fill the docs gap :) but experience > has shown it's no substitute for real documentation. I hope to have time > to change this soon.
The lack of documentation has been the main reason I haven't stepped into the the ToscaWidgets learning curve yet. If you know me, you know that documentation is my forte, so I'll be writing at least a Pylons-ToscaWidgets howto and a FormEncode-ToscaWidgets comparision once I know enough to do it. Alberto, is the ToscaWidgets trunk kept reasonably stable? Meaning, Cheetah has a rule that all changes have to pass the unittests before being checked in, and backward compatibility is generally maintained, so that the trunk is almost always more usable and less buggy than the last release. Pylons, SQLAlchemy, and Supervisor seem to have a similar attitude because I've had good luck with their trunks. Does ToscaWidgets keep a clean trunk too? Is it safe enough for application development, knowing that we may have to change our API calls occasionally? Are there any anticipated changes which will change the API? -- Mike Orr <[EMAIL PROTECTED]> --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
