"milde" <[EMAIL PROTECTED]> writes:
> Well my main gripes were that it uses one controller module, instead of
> a controllers package. I tried "subtemplating" TGBig, but I wasn't able
So you haven't used the big template. You can ask quickstart to use it with
something like "-tbig" (I don't know the correct option since I don't use
it).
> to figure out how to have my template actually subclass the TGBig class
> itself, so I could inherit all of the controllers.py handling. I
> suppose in retrospect I could've done something like "from
> turbogears.commands.quickstart import TGBig". This might be better than
> just Paste's inheritance, because then you can do something like "class
> MyStart(TurboGearsTemplate)" and then call inherited methods or ignore
> them as you like. It might be even better to allow more granularity, so
> a subclass can choose exactly which options it supports or doesn't
> support.
But how would you generate the final templates and keep on using the mechanism
there is implemented now? Or you're proposing a complete rewrite?
> The only other differences really is that Kid is set to output
> xhtml-strict by default, the start script supports FastCGI, SCGI,
> mod_python, and PyChecker, and the default kid templates are more
> barebones. You can pass options to the start script through environment
> variables, though I didn't have much luck with that through mod_python.
For mod_python you have to use the setenv directive:
SetEnv OPTION value
> I might make some wrapper function for the os.environ.get() calls that
> substitutes it with mod_python's req.get_options() if it's available.
This is something related to your project... I am actually interested on the
difference for the existing template... Having a customized template for some
kind of applications is fine...
> If any of you are curious, this is how I have my apache configuration
> set up to use the test application. The application is deployed to
> site-packages.
>
> <VirtualHost [...]:80>
> <Location /mytgtest>
> SetHandler python-program
> PythonOption cfg /[...]/mytgtest.cfg
> PythonOption wsgi.application cherrypy._cpwsgi::wsgiApp
> PythonHandler modpython_gateway::handler
> PythonFixupHandler mytgtest.start::start_mod_python
> PythonDebug On
> </Location>
> </VirtualHost>
So you can try using the SetEnv directive I talked above to pass your
environment variables to your scripts.
> Also, this ticket really needs handling:
> http://trac.turbogears.org/turbogears/ticket/1014 . I ran into the same
> problem at first.
These were removed, actually. Don't ask me why, but I believe there were some
problems with widgets code or something like that.
--
Jorge Godoy <[EMAIL PROTECTED]>
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
