30 Nov
2010
30 Nov
'10
5:43 p.m.
On Nov 30, 2010, at 5:38 PM, Jean-Vincent Drean wrote:
On Tue, Nov 30, 2010 at 5:12 PM, Vincent Massol
<vincent(a)massol.net> wrote:
I don't like it. The point of this Add menu is to make it extra *simple* to create new
pages. If I have to navigate first to the right space, we fail this goal and we don't
need template providers at all since we can offer buttons to create objects from the
space's webhomes.
IMO we really need a way to create new pages with objects from anywhere else in the wiki.
Thanks
-Vincent
Hi,
I think we should provide default template providers in default XE. This thread is about
deciding which ones to have by default.
I agree, however we need to find a way to translate the name of the
provided templates, for the moment this name is stored in a simple
string property. I haven't commited templates by default since I was
reluctant to put velocity in those fields.
Candidates:
==========
I think all those candidates should be present only in specific
spaces, this way most of them would be (almost) invisible to simple
users. 1- Wiki Macro
XWiki.
2- Blog Post
Blog.
3- Scheduler Job
Scheduler.
4- Class (same result as creating a class from
the class wizard)
XWiki.
5- Color Theme
ColorThemes.
6- Panel
Panels.
7- Skin
XWiki.
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.
I think it's ok to have multiple locations allowing to create them, a
macro would be cool.
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.
I'm 0 on this, I'm not a fan of relying on this prop but space
restriction might not be enough.
Thanks,
JV.