On 10/13/06, Kevin Horn <[EMAIL PROTECTED]> wrote: > -1 > - also why not put json.py in view.py too, since that's a view component.
replying to the 3 of you. about having flexible project remenber TG is totally like that, other then the setuptools layout you can move everything to anywhere... well expect for the model.py that you have to do some acrobatics to get tg-admin sql * to work, but that's another story. also remenber We are talking about "quickstart" default which in most cases will be used by new people trying out TG. and they will say model.py controller.py and templates?!? > For several reasons: > a) I don't think it will be used for the same things from project to > project, so it's better to let each project grow its own way. of course each project is different. but as you said each project will grow it's own way. > b) Too vague...as Lee said. I don't see why it's vague. "here you put all your view related code", is as vague as controller.py > c) Lots of docs would probably have to be changed not really, only the widgets and json related, from which the only one that's written is the json stuff. > d) I just don't like it...personal preference. > > I _do_ think, however, that some docs related to project structuring would > be helpful, with tips on how to split things into a seperate package, etc. > TG is attracting a lot of Python newbies, it seems, and a lot of those > people will not know how to do this right off. > yes I agree there should be something in the getting started that explains what all those files are. http://docs.turbogears.org/1.0/RoughDocs/DocumentationWishList > Kevin H > > > On 10/13/06, Lee McFadden <[EMAIL PROTECTED]> wrote: > > > > -1 from me. view.py is so ambiguous it'll be difficult to explain to > > people what should go in there and why. > > > > If anything it should be widgets.py or something, but even then if a > > developer has so many widgets and helper functions that they need a > > separate file they will probably know a) how to do it and import > > everything and b) what they want the name of the file to be. > > > > Every one's brain works slightly differently and it would be better > > not to foist arbitrary names on people for the sake of an empty file > > (which it will be when it is quickstarted). > > > > Just my $0.02. > > > > On 10/13/06, Max Ischenko <[EMAIL PROTECTED]> wrote: > > > > > > +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? > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > Lee McFadden > > > > blog: http://www.splee.co.uk > > work: http://fireflisystems.com > > > > > > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
