+1 for the controllers/ and models/ subdirectory hierarchy. Every time
I create a new TG project, the first thing I do is create a
controllers/ subdirectory. I've only had one project that was small
enough that I stayed within the single controllers.py file.
On a tangent: another thing I always do is modify the setup.py's
find_package_data to (where='.', package=''). The reason being that I
have a "shared" directory that I link in to every TG project at the top
level of the project, and I want it to get picked up when I build the
egg. I suppose my other option is to build and release my shared
library as an egg and set the version number dependency in my setup.py?
Another tangent: another thing I always do is move the app version out
of the setup.py and put it in my projectdir/__init__.py so I can do
this in myproject-start.py:
def add_custom_variables(variables):
variables['app_version'] = myproject.__version__
turbogears.view.variableProviders.append(add_custom_variables)
I do this because I want my application's version number available to
my templates for appending at the end of each .js and .css inclusion.
Jeff Marshall
[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
-~----------~----~----~----~------~----~------~--~---
