On Sun, Feb 22, 2009 at 5:42 PM, a.fowler <[email protected]> wrote:
>
>
>> This is a fairly common request, in fact even seasoned tg devs aren't
>> sure what to delete and what not to delete. The main problem is that
>> the current quickstart has two contradicting goals.
>>
>> 1- provide an introduction/explanation to new people
>> 2- provide a basic package structure for every turbogears project.
>>
>> The issue here is that our current tool to work this (paster template)
>> has some limitation that will not allow us to provide it in two
>> stages. Sadly changing this at this point will break too many apps.
>> Therefore it's a goal for 2.1http://trac.turbogears.org/ticket/2159
>>
>> As for what could break and what will not break sadly the answer is
>> delete it and figure it out :) but most stuff in templates (except
>> master and siebars) and controllers (except root and error) can be
>> deleted.
>>
>
> Haveing a "quickstart", "quickstart-verbose", and "quickstart-minimal"
> options in 2.1 or later sounds like a good idea.
>
yea it is.

> Since this is the first stable 2.x release (plus are trying to grow
> the user base), between now and whenever 2.1 is released, you will
> have far more "new TG2.x users" than "seasoned TG2.x users".
>
agreed.

> Thus, I think that quickstart should err on the side of more
> verbosity.  (many verbose inline-comments, docstrings, etc.)

I'll invite you to look at the quickstart code and add as much stuff
as you want, if you come to IRC right now we can do that. But as I'm a
"seasoned dev" I really think it's way too bloated and it should be
trimmed to like 1/3 of it's current size.

--~--~---------~--~----~------------~-------~--~----~
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