If we leave them in the XWiki space we should postfix them with Macro. So it is either:
Macros.Map or XWiki.MapMacro I'm +1 for Macros.Map. I remember that we have XWiki.LudovicDubost instead of Users.LudovicDubost and that it's bad and hard to change now. I'm +1 with what's necessary in XE to have this happen. Ludovic Vincent Massol a écrit : > On Nov 23, 2009, at 10:09 AM, Ludovic Dubost wrote: > > >> Vincent Massol a écrit : >> >>> On Nov 20, 2009, at 9:53 AM, Ludovic Dubost wrote: >>> >>> >>> >>>> Hi, >>>> >>>> Before we start doing a wide range of Macros, I would like to >>>> suggest that unless a Macro is part of a bigger application we store >>>> it in the Macros space. >>>> >>>> Macros.GoogleCalendar >>>> Macros.Map >>>> >>>> WDYT ? >>>> >>>> >>> +1 especially since it's the current strategy. Are there some that >>> are >>> in apps when they should be in Macros? >>> >>> >> Ah I did not know this was the current strategy. >> Anyway I'm not sure it's actually happening. I've been doing the TODO >> macro in the XWiki space, like jerome has been doing the Map Macro in >> http://code.xwiki.org/xwiki/bin/view/Macros/MapMacro >> >> Or Asiri that put it in the "Macro" space >> >> http://code.xwiki.org/xwiki/bin/view/Macros/MBoxMacro >> >> Si I think it would be good if we enforced the "Macros" space and we >> controled it a bit for the macros published on code.xwiki.org >> > > ok I wrongly understood your proposal. I thought you were talking > about the category on code.xwiki.org. > > If we want to "reserve" the "Macros" space for wiki macros (and also > velocity macros?) then we need to package a Macros.WebHome page in the > default XE that would: > - explain what the space is about (and explain the different types of > macros) > - list all found wiki macros in the wiki (currently Asiri has put the > wikimacro-bridge app page listing all macros in the XWiki space) > - The Macros.WebHome page should be located in wikimacro-bridge > application > > Then there's another problem: this Macros space would not be hidden by > default which means simple users will get to see it in the Dashboard. > I don't think this is right. Only advanced users should see it IMO. > > Thus I'd also propose to hide this space as we do for other spaces > (i.e. blacklist it). > > If we had nested spaces I'd have preferred macros to be located in > XWiki/Macros instead (or even better Applications/Macros). > > +0 for: > - putting macros in the Macros space by default > - modifying the wikimacro bridge application accordingly > - blacklisting the Macros space (and hoping nobody is already using it > for other purpose...) > > I'd also be ok to put them in the XWiki space (while waiting for > nested space support). Advantages are: > - no need to reserve a new space name to blacklist (it's already > blacklisted) > - it's clearly marked as for non simple users since it's in the > technical XWiki space > > Thanks > -Vincent > > >> However, I don't think macros should go in the Macros space if they >> come >> with a large app. In this case I believe they should stay in the App >> code space if there is one >> >> Ludovic >> >> >>> Note my earlier email about code.xwiki.org where I was suggesting >>> categories implemented as tags: >>> >>> <quote> >>> Another idea would be to succeed in having the same XClass for all >>> extensions (if possible - I wanted to do that initially but found >>> there were different, maybe we can try again) and then use tags for >>> categorize extensions (and the tag cloud feature of the livetable on >>> the home page). >>> </quote> >>> >>> Thanks >>> -Vincent >>> > _______________________________________________ > devs mailing list > [email protected] > http://lists.xwiki.org/mailman/listinfo/devs > > -- Ludovic Dubost Blog: http://blog.ludovic.org/ XWiki: http://www.xwiki.com Skype: ldubost GTalk: ldubost _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
