21 Sep
2010
21 Sep
'10
3:11 p.m.
Hi Denis,
On 09/21/2010 09:37 AM, Denis Gervalle wrote:
On Mon, Sep 20, 2010 at 18:50, Anca
Luca<lucaa(a)xwiki.com> wrote:
Well no, if we want parameters for the inner groups, then every group
needs to define its own parameters.
Another option would be to use ((( ))) groups for when there are no
params, and when we start needing parameters, we add an alternative
syntax based on a macro. This way both should work, in the case of a
group with no params ((( and {{{group}}} being equivalent.
On 09/20/2010 06:16 PM, Jerome Velociter wrote:
I am not sure I get your idea.
Either we do not have parameters on the inner macro, and using ((( )))
groups are the best. This means that parameters for groups are provided on
the container macro. Is this really nice, do you like html colgroups ? On Mon, Sep 20, 2010 at 5:40 PM, Anca
Luca<lucaa(a)xwiki.com> wrote:
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.
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'}}" ?
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?
Or we need parameter on the inner macro, and...
Mainly because the inner macros don't do anything (at all) by themselves
they're just markers for the outer macro to know how to deal with that
group of content. Which is why we had the idea of using ((( ))) groups,
to avoid having a macros that do nothing in the list of macros.
The more macros that do nothing we plan, the worse (column, panel,
gridbox, or who knows what other things we might want inside).
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
My +1 for c).
WDYT? in general about this limitation and in particular about the name
of the macro to use.
... why should we use a single name ?
The container macro (I would prefer "layout" like Jerome) may just be a
container for multiple different group, and one of them could then be called
"column", why not ?
Have I missed some important issue related to the WYSIWYG or the macro
implementation that prevent that ?
multiple macros inside? no, it's very possible. However wysiwyg doesn'r
yet allow editing macro in macro.
If yes, I would even prefer to keep a specific
columns/column macro, this
would be clearer, even if this macro became an alias for something more
generic latter.
in my view columns column is a little bad because they can be easily
confused, but that's a different story.
I think it's not such a good idea to add things that we know will
disappear, because it's hard to make them disappear, and we're gonna
endup with a bloated list of macros, from which half are aliases of the
other half.
Moreover, I am not sure that the generic aspect of the implementation should
be really shown externally, macro usage should not be reserve to programmers
only (even if the WYSIWYG is a great tool), and the way of thinking of
programmers is not a good example of the human way of thinking :)
While I agree with the fact that users would prefer more a macro which
is called columns instead of a macro called container with a layout
parameter that says columns, I don't think it's that bad and difficult
to use.
What do others think about these?
Thanks,
Anca
WDYT ?
Denis
Still one could use group parameters as a
replacement,
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
but you cannot achieve exactly the same (from the
WYSIWYG interaction
perspective for example).
The wysiwyg cannot handle nested macros in any case, 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
> devs(a)xwiki.org
> http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs