I suggest to add a command "addController " to replace the tgbig
template.
[Usage]
$ tg-admin addController
Enter controller name:Magic
Enter entry name [magic]:
(addController command is the alias for "$tg-admin quickstart -t
addController")
[Command Behavior]
add /controllers/__init__.py (if not exist)
add /controllers/+entry+ (magic)
append
from +package+.controllers.+entry+ import +controller+ (from
demo.controllers.magic import Magic)
+entry+ = +controller +() ("magic=Magic()")
[Reason]
Does anyone use tgbig template?
The current tgbig template is derived from tg basic template , and
will:
remove controllers.py
add controllers/__init__.py
add controllers/root.py
I find when I use tgbig template.
It confused me that "controllers.py" is moved in "controllers" folder
and is renamed to "root.py",
it breaks my experience to handle controllers.
(also, in controllers folder we also have to use full template
path....bla...bla... that's a lot to acclimatise),
"root.py" in controllers is not as obvious as "controllers.py" in top
heirachy.
And the 'contollers' folder is not such useful because I still need to
figure out what should I do to add another controllers. So why not make
it implicit?
I think "Fast Track style" structure is pretty reasonable.
keep controllers.py, append entry to RootController
add /controllers/__init__.py
add /controllers/custom controller
Now it looks more helpfull :)
Is this possible?
--
Fred
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
