Ticket #2275 (closed task: wontfix)
loosely component architecture
| Reported by: | jorge.vargas | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | 2.1rc1 |
| Component: | TurboGears | Version: | trunk |
| Severity: | normal | Keywords: | |
| Cc: |
Description (last modified by jorge.vargas) (diff)
This is a meta-ticket to hold all aspects of component reuse for TG2
I strongly believe we should have lossy components instead of the approach proposed in #1655, that is the project should import and call the library. And we should have tools to query the library for things we are interested in. Ideally the library should hint in an obvious way similar to how all works for modules and application works for wsgi.
Ideally a component should provide one of more of the following
Potential tools
- model collector, will display/query all installed options
- model updater (#2239)
- default data collector, extension to setup-app/websetup.py
- controller collector, will display/query all installed options
- config collector, will display/query all app_cfg.py/base_conf
Change History
Note: See
TracTickets for help on using
tickets.