Re: do we need plone.app.customerize? was: [Plone-Users] Insufficient privileges on folder_contents
"David Glick (Plone)" <david.glick-z4DKO/[email protected]>
| Newsgroups | gmane.comp.web.zope.plone.devel |
|---|---|
| Message-ID | <[email protected]> |
On 12/11/13, 7:35 AM, Martin Aspeli wrote: > Hi, > > +1 - I've tried restricting myself to doing a site theme within a zip > file before, and being able to include per-type themes in the zip file > would have been incredibly handy, verging on essential. So something > like:- > > site.theme/views/Folder/my_magical_listing.pt > <http://my_magical_listing.pt> > > Registering a @@my_magical_listing for Folder portal types. > They're part > of the theme, so definitely a job for plone.app.theming. As you say no > need to be able to override views, since you can do any overriding > within Diazo. It's mostly about making sure the data is there for > Diazo > to chew on. > > I thought plone.app.themingplugins was going to save me but apparently > only works with a theme on the filesystem (not necessarily it's own > package IIRC). If it works for zip files then I guess it'd also be TTW > using the ACE editor. Not convinced a builder UI is worth it, versus > copy-and-pastable examples on developer.plone.org > <http://developer.plone.org> / stackoverflow you > can then tweak. > > > The p.a.themingplugins implementation uses startup hooks to register > views by looking at files on the filesystem. That was easy, because > it's basically done at the same time as ZCML directives register > components. Doing it TTW requires something a bit different. I am not > particularly a fan of persistent component registrations because they > are opaque and difficult to manage. Instead, I was toying with ideas > for having a custom component registry in the chain (between the > global, transient one and the site-specific, persistent one) that > could dynamically provide components (view registrations) based on > template objects in content space or some such. > I think we're overly afraid of persistent view registrations. plone.app.customerize does it, and it's problems have overwhelmingly been not to do with that but with the effects of suddenly executing in restricted Python. Using a base registry of the portal's component registry sounds like an interesting idea, though we'd want to make sure it doesn't affect the speed of global lookups too much. David ------------------------------------------------------------------------------ Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk _______________________________________________ Plone-developers mailing list Plone-developers-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org https://lists.sourceforge.net/lists/listinfo/plone-developers