+0 on this.
There are lot of ways to structure the project source code and there are alot of factors that come into play. I am not very happy with the default TG layout but I don't think it's a problem - any non-trivial project will twisted it to suit there needs.
That's why it's hard for me to judge usefuleness of the proposal. In smaller projects I usually have forms.py which is similar to your view.py; in larger project I found that splitting based on functionality makes more sense ( e.g. stats.py, billing.py, dashboard.py, etc.).
On 10/13/06, Jorge Vargas <[EMAIL PROTECTED]> wrote:
This morning I was thinking about widgets and where to put then and I
remenber the discussion that was raised about @view vrs @template,
then I realize why don't we have a view.py file?
- in view.py there will be all the python code related to the view,
that is all the project widgets, and probably some helper functions
for example one that takes a variable and creates a link (a tag), and
any code related directly to the view.
- This will help clarify the issue that people new to the framework
will say well this is MVC we have model.py, controller.py and
templates?!?!
- for now view.py is totally optional, and will have a big comment on
top saying what the intention of it is.
what do you think?
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
