AS many people have said sometimes a dir is better sometimes a file is better, either way if you end up with a dir it will have more then one class per file. therfore I propose this

1- quickstart will stay as if
2- <insert name here>, this one will ask
you want a controllers package? [default: no]
you want a model package? [default: no]
3- <expand> a quickstart
>>>migrating controller.py to ./controllers/controller.py
>>>migrating model.py to ./models/model.py

If you think of it a little bit the changes in quickstart code are small
check the input, create the dir change to that dir.

and since we have to import if it's on a package or not there is nothing else for TG to do.

ohh yea and create the __init__.py file which is trivial.

On 3/7/06, Kevin Dangoor <[EMAIL PROTECTED]> wrote:

The project created by quickstart is intentionally very simple.
Clearly, though, as a project grows you might need more than just
model.py and are very likely to need more than controllers.py.

Through the import statement, it's very easy to add more modules and
get those names into the "standard" namespaces if you want them there.
Given the near inevitability that you'll probably need more than just
a single controllers module, would people prefer to have a controllers
package set up by quickstart instead? How about the model? Do you find
yourself outgrowing a single file there?

Kevin

--
Kevin Dangoor
Author of the Zesty News RSS newsreader

email: [EMAIL PROTECTED]
company:



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

Reply via email to