On Fri, 2006-12-29 at 22:54 +0000, Ben Sizer wrote:
Christopher Arndt wrote:
> Let's put our energy in implementing missing features and documentation 
instead
> of arguing why it's a bad thing that this and that feature/documentation is
> missing!

Unfortunately some of us are stuck in the void where you don't know
enough about the system to either use it or write about it. I'm sure it
is possible to get some use out of the code, if you have many hours
free to browse the source and experiment. I don't have that sort of
time. I like clear, well-organised documentation.

Documentation should be done as you go along, not left to the end for
whoever is willing to give it a go. I will politely keep drilling this
into the heads of developers until they listen. :) Until then, at least
I can hopefully make it very clear which documentation are missing,
because sometimes the experts who no longer need the docs have no idea
what the rest of us need.
Just by way of consolation/observation - I'm learning ROR at same time
as learning TG -(and learning both ruby and python simultaneously). TG
was my framework of choice, but have landed 2 ROR paying gigs, so whats
a struggling developer to do!! ;-).   Any how, point being you think TG
has documentation issues - at least I can go to SO website, or kid
website and get more or less what I need to know  - rails OTH... OMG
lets just say i've never had to use TG source code as a substitue for
documentation! But speaking as one stuck in the void you mention, i
share your pain, but just thought id mention the 'competition' are in
the same boat - I think what you  suggest is as necessary as it is
impossible.
glenn



--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"TurboGears" 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/turbogears?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to