[Grok-dev] Grok & the lack of good documentation
battlefox at gmail.com
Fri Sep 11 02:31:32 EDT 2009
Jep, the right balance between simplicity and complexity is not found yet in
Maybe because ppl still think that increasing the complexity will result in
a complicated tutorial. In fact, that's not true: It's rather a question of
the writers skills in making explanations if the tutorial is easy to
understand or not.
Sebastian Ware wrote:
> I agree that a more complex example for the official tutorial is
> better. The problem when it is too simple is that it doesn't help much
> since you'll never use grok for such simple apps. I think also it
> might give the illusion that Grok is simpler than it is, and thus
> cause frustration.
> Grok is a Formula 1 car, you can't just jump in and start driving, but
> once you've done your first laps without crashing you will never want
> to drive anything else (ok, I haven't driven a F1 car, but...). It
> just isn't a framework for everybody.
> Mvh Sebastian
> On 9 sep 2009, at 17.28, Martijn Faassen wrote:
>> grokomobil wrote:
>>> The tutorial might need a more complex example, I think. People
>>> read that
>>> tutorial and say: "Well thats easy! And what do i have to do to make
>>> something different than a list of mammoths with it?"
>>> See my point?
>> Yes, a more complex example that's detailed would be good to have. The
>> tutorial itself was aimed to really build up things step by step,
>> however, so jumping to a more complex example might be too big of a
>> leap. But perhaps a change of pace would be useful.
>> Grok-dev mailing list
>> Grok-dev at zope.org
> Grok-dev mailing list
> Grok-dev at zope.org
View this message in context: http://www.nabble.com/Grok---the-lack-of-good-documentation-tp25259107p25395730.html
Sent from the Grok mailing list archive at Nabble.com.
More information about the Grok-dev