On Nov 30, 2010, at 5:24 PM, Guillaume Lerouge wrote: > Hi, > > On Tue, Nov 30, 2010 at 17:12, Vincent Massol <[email protected]> wrote: > >> Hi, >> >> I think we should provide default template providers in default XE. This >> thread is about deciding which ones to have by default. >> > > +1 for the concept. See my comments below. > > >> Candidates: >> ========== >> >> 1- Wiki Macro >> 2- Blog Post >> 3- Scheduler Job >> 4- Class (same result as creating a class from the class wizard) >> 5- Color Theme >> 6- Panel >> 7- Skin >> > > We might also want to have a "user" template, if that's doable with the > current mechanism.
I hesitated adding it to the list since I don't think it' a good thing to have. I think that when we have specialized UI it's better to not have a template provider, or maybe better to redirect to the specialized UI. >> For some of these we have home pages to create them (For example: Blog, >> Scheduler, Class, Color Theme, Panel) so we need to decide if it's ok to >> provide 2 locations from where to create them. >> > > Yes, I think it's ok to have 2 locations, the same way we have more than one > way to create new pages (links to non-existent pages, "create" button...). > > In addition some of the candidates above are technical things and they >> shouldn't be displayed to simple users IMO: Wiki Macro, Scheduler Job, >> Class, Color Theme, Panel, Skin. >> >> Thus I'd also like to discuss having a mechanism for a Template Provider to >> say to whom it's addressed. Could be done by adding an "Audience" field to >> the Template Provider class. >> > > That's not necessarily needed. There are already 2 mechanisms that can be > leveraged in order to handle this use case: > > - The ability to restrict a template to a given space -> the ColorTheme > template could be provided only in the ColorThemes space for instance That makes a colortheme template provider quite useless since there's already a way to create color themes from the color theme space... ok it allows a user to create a new theme when viewing another theme, sure, but that use case is not the main one IMO and it's covered by the create color theme feature of the color them webhome. > - The $blacklistedSpaces variable -> it's already used to hide technical > spaces. Coupled with the above mechanism, it could be sufficient See previous comment. Template providers are not really useful when restricted to a space IMO. Thanks -Vincent > > Thus I'm not sure that we need an additional field. Let's first use (and if > needed improve) the existing mechanisms. > > Guillaume > > >> WDYT? >> >> Thanks >> -Vincent _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
