Hi, Want to sum up the discussion, so I could start writing my application.
There is idea of pluggable application, which should be designed. To understand how should it work tgextpages is started. There are several Component Architectures (Zope, RUM, etc) which can be used. As a result this becomes a eature of the TurboGears 2.1 I have some questions according tgextpages. * Which version of TG I must use to be able to start a project with tgextpages? Trunk of TG or TG2.0rc1? * How are pluggable elements implemented now? -- Dima On Mar 24, 11:59 am, Mark Ramm <[email protected]> wrote: > Wow, that is really nice! > > One other worth looking at in general when thinking about plugable > components is the Component Architecture from the zope project, which > seems way worse than it actually is. > > I think they overuse it in many places, and it creates some issues > because of that, but it's a solid component framework that's been > tested in years and years of production use, which says something. > > --Mark Ramm > > On Tue, Mar 24, 2009 at 2:39 AM, Michael Brickenstein > > > > <[email protected]> wrote: > > > Hi! > > Regarding components: > > > You should have a look at components in RUM: > > I don't know, if that matches your concept of a component, but > > it's completely pluggable. > > >http://docs.python-rum.org/developer/modules/component.html#module-ru... > > > Most things in rum are components: > > > wsgiapp.py: controllerfactory = Component('rum.controllerfactory', > > default='default') > > wsgiapp.py: repositoryfactory = Component("rum.repositoryfactory", > > default='default') > > wsgiapp.py: viewfactory = Component('rum.viewfactory', > > default='default') > > wsgiapp.py: router = Component('rum.router', default='default') > > wsgiapp.py: policy = Component('rum.policy', default='default') > > wsgiapp.py: jsonencoder = Component('rum.jsonencoder', > > default='default') > > wsgiapp.py: translator = Component('rum.translator', > > default='default') > > > At the moment this is tied to rum apps, but it shouldn't be a problem > > to make it fit into different settings. > > > Another point, which might be interesting for you, is that the next > > version of RUM will contain a security policy: Alberto's latest > > marvel. > > >http://hg.python-rum.org/TgRumDemo/file/688e9ea77be2/tgrumdemo/policy... > > > This might also fit into your CMS. > > > Michael > > -- > Mark Ramm-Christensen > email: mark at compoundthinking dot com > blog:www.compoundthinking.com/blog --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
