On Mon, Sep 20, 2010 at 6:50 PM, Anca Luca <[email protected]> wrote: > > > On 09/20/2010 06:16 PM, Jerome Velociter wrote: > > On Mon, Sep 20, 2010 at 5:40 PM, Anca Luca<[email protected]> wrote: > > > >> Hi devs, > >> > >> actually after a discussion I had with Vincent about naming, we thought > >> of the following approach, for a more general purpose: > >> > >> 1/ section turns into ** container ** and it gets a parameter called > >> **layoutStyle** to specify the type of layout for its contents. One of > >> the possible values of this param would be "columns" and it would be the > >> only one implemented for the moment. > >> > >> 2/ the content of this container macro would be a **list of groups**, > >> wiki syntax groups, like ((( ... ))). There's no point of having a macro > >> that does nothing else but specify that some items should be grouped > >> together. > >> > >> With these, the syntax of columned content would now be: > >> > >> {{container layoutStyle="columns"}} > >> ((( some wiki content ))) > >> ((( some other wiki content))) > >> {{/container}} > >> > > > > > > I don't like too much "container", it's not very explicit its use is > > "layouting". Do you see there are other uses? Why not "{{layout > > style='columns'}}" ? > > For example you could use it to also provide borders, and size, > eventually ending up implementing the box as a special case of container > macro. > > > > > Also, if you abandon the column macro, you abandon the possibility to its > > potential parameters. > > This is a very good argument actually, particularly if we think about > the simple case of columns that take percents of the page width, the > percent should be passable as a parameter of the column macro, I don't > like the idea of specially parsing the group parameters. > > WDYT? > > Also if we think about a border layout (a la Swing), we'd need a group > to specify its position. > > In this case, a new vote would be for the name of the inner macro, which > needs to have a suggestive name. Proposals: > > a) content > b) item > c) group > d) widget > e) part > f) element > g) entity > > I like "item"
could be containerItem, containerElement ? "group" is too technical IMHO. > My +1 for c). > > WDYT? in general about this limitation and in particular about the name > of the macro to use. > > > Still one could use group parameters as a replacement, > > but you cannot achieve exactly the same (from the WYSIWYG interaction > > perspective for example). > > The wysiwyg cannot handle nested macros in any case, I know, but I dare to hope they be supported at some point :) Jerome. > at least not for > the moment and I don't think it's really that much envisaged. > > Thanks, > Anca > > > > > +0 anyway > > > > Jerome. > > > > > >> The dashboard macro would then just delegate to a container macro with > >> columns layout style. > >> > >> I like this approach, +1. > >> > >> WDYT? > >> > >> Once I get your votes, I will commit this in the platform. > >> > >> Thanks, > >> Anca > >> > >> On 09/17/2010 03:56 PM, Anca Luca wrote: > >>> Hi devs, > >>> > >>> wdyt about committing the section& macro columns from the contrib > >>> ( > >> > https://svn.xwiki.org/svnroot/xwiki/contrib/projects/xwiki-macro-column/) > >>> in the platform macros, along with a first, very simple implementation > >>> of the dashboard macro (which for the moment only delegates to the > >>> section macro)? > >>> > >>> This would be the first step towards the implementation of the > >>> dashboard, and the plan is to be done before 2.5M2. > >>> > >>> Here's my +1. > >>> > >>> WDYT? > >>> Anca > >>> _______________________________________________ > >>> devs mailing list > >>> [email protected] > >>> http://lists.xwiki.org/mailman/listinfo/devs > >> _______________________________________________ > >> devs mailing list > >> [email protected] > >> http://lists.xwiki.org/mailman/listinfo/devs > >> > > _______________________________________________ > > devs mailing list > > [email protected] > > http://lists.xwiki.org/mailman/listinfo/devs > _______________________________________________ > devs mailing list > [email protected] > http://lists.xwiki.org/mailman/listinfo/devs > _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
