"Tim Lesher" <[EMAIL PROTECTED]> writes: > The big issues I can see right now are: > > 1. What's the recommendation for structuring model, controllers, and > templates for reusable components? > 2. What's the recommendation for dealing with the different supported > ORMs and template engines?
>From what I see that will be done and somewhat easy you'll have to split reusable parts in different applications and then "cherrypy.tree.mount" them. The big thing will be being able to reuse master.kid, sitetemplate, etc. since you can alreay mount other applications today... As separate applications, you'll be able to manage them independently. Some structures will have to be shared, duplicated or something like that (such as user, group and permission tables for identity and visit). > /myproject/myproject/ > controllers.py (as usual; user has to import reg's controller and > add an entry point by hand) Here he'd mount the controllers tree... The result would be almost the same, but there would be no reg_* in your code. > In the ideal, post-1.0 world, should this all live in an installed > .egg for that particular component, outside the current project's > directory? That's one option. Yes... > If so, that makes customizing or interactions (like the way > registration depends on Identity) problematic. I'm also unsure > whether SQLObject will have problems with model objects outside the > current class path (for tg-admin sql create and such). What are you thinking? It should use your app.cfg's identity configurations... Of course it would expect the basic and standard identity stuff to be available (but you can change that since you have the code). > If not, it seems that the choice is whether to separate things 1) by > component (a la Django) or 2) by component type (the way we do now > with templates, and the way the "big" quickstart template does for > controllers). Could you elaborate? -- Jorge Godoy <[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 -~----------~----~----~----~------~----~------~--~---
