On 2/1/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
>
> First, we should decide a way to 'list available quickstart templates'
> for future version
> #1073: No way to discover available quickstart templates
>
> Actually we could use paste command to list all paste templates
>
> # paster create --list-templates
>   Available templates:
>     basic_package:  A basic setuptools-enabled package
>     paste_deploy:   A web application deployed through paste.deploy
>     tgbase:         tg base template
>     tgbig:          For more complex projects
>     tgwidget:       TurboGears widget projects
>     turbogears:     web framework
>
> 'turbogears'(kid-based) template is the default for quickstart
> template.
>
> Is it ok to point out the usage in doc, or implemented as a wrapper
> around that as jorge.vargas suggestion in trac?
>
> I prefer the prior one as we discussed about the nosetests wrapper.
>
>
> > > - I could wrap the genshi-default template as an optional choices.
> >
> > That's a good compromise. 1.1 could start offering better Genshi
> > integration and optional choices (like --future is doing now) and
> > mention that to use widgets in genshi page templates it's best to
> > switch to TW.
> >
>
> Second, I've wraped the genshi-default template as an optional
> extension, the usage is with the command:
>
> $ tg-admin quickstart [-t tggenshi] [project name]
>
> To make current tg templates looks more meaningful, I'd like to change
> the default (kid-based) quickstart template name as 'tgkid' instead of
> 'turbogears'.
>
> ....
> tgkid:            web framework with kid
> tggenshi:       web framework with genshi

I have already done this.
http://groups.google.com/group/turbogears-trunk/browse_thread/thread/c52de71231cf03f1/6ddfebb34b6b509a?lnk=gst&q=quickstart&rnum=10#6ddfebb34b6b509a
but got no reply back then so it was something to be done post1.0
here is the dirrect link
http://docs.turbogears.org/1.0/RoughDocs/quickstartInternals

Third, should we separate all quickstart templates as extensions?


I don't think so at much it should be one package with all the templates.

Forth, if we think so, what is the preferable way to organize the
> increasing projects in trac?
>
>
> --
> Fred
>
>
> >
>

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

Reply via email to