#1655: Create some kind of "component" archetecture for TG2
------------------------+---------------------------------------------------
Reporter: mramm | Owner: plewis
Type: defect | Status: assigned
Priority: normal | Milestone: 2.1
Component: TurboGears | Version: trunk
Severity: normal | Resolution:
Keywords: |
------------------------+---------------------------------------------------
Comment (by lszyba1):
So how will tg-registration look in this scenario...what tg-registration
did was to put its code under one of the folders. User then changed
configuration files and we were ready to go.
Rum has a nice entry points, where you load the app, add one configuration
file and it takes over the master template look. I think the biggest
problem for me at this point is how to create an application that can be
loaded by another tgapp? I think simple tutorial on how to create tg2 app
that can be called by another tg2app,and get its master template, db
connection, authentication.
Thanks,
Lucas
--
Ticket URL: <http://trac.turbogears.org/ticket/1655#comment:12>
TurboGears <http://www.turbogears.org/>
TurboGears front-to-back web development
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google
Groups "TurboGears Tickets" group.
This group is read-only. No posting by normal members allowed.
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/turbogears-tickets?hl=en?hl=en
-~----------~----~----~----~------~----~------~--~---
