9 Dec
2010
9 Dec
'10
12:33 p.m.
On Dec 9, 2010, at 12:15 PM, Ecaterina Moraru (Valica) wrote:
Never used the Container macro, while the Box macro
IMO is more highly used
(specially on xwiki.org) in combination with "floatinginfobox" class.
Yes that's the proposal: to replace it since the container macro does what the box
macro already does and more.
I'm +1 to deprecate the box macro and replace it with the more generic container
macro.
We need to find a way for the info, warning and error macros to be implemented using the
container macro and still have icons.
Thanks
-Vincent
Thanks,
Caty
On Wed, Dec 8, 2010 at 19:46, Anca Luca <lucaa(a)xwiki.com> wrote:
> Hi devs,
>
> There is obviously some overlapping between the purposes of the box
> macro (http://extensions.xwiki.org/xwiki/bin/view/Extension/Box+Macro)
> and the container macro
> (http://extensions.xwiki.org/xwiki/bin/view/Extension/Container+Macro),
> namely that the box macro is just a very specific type of container.
>
> How do you feel about moving all or some of the box macros
> functionalities to the container macro and either implement the box
> macro as a particular type of container, or deprecate it completely?
>
> The way I see it is that the container macro would have parameters to
> allow to:
> * fix its size
> * render a border around
> * use a background color
> * title (to be discussed, I am not 100% convinced that it's generic enough)
> * image (to be discussed, same)
> * layout it inside text (float it to the left or right)
> * other decorations we could find useful for the users (note that devs
> could still write css if they want more).
>
> I know that all these functions can be accomplished by CSS, but so is
> the columned layout, for example, and the idea is to provide to the
> users an easy way to do it (in this case, WYSIWYG).
>
> I'm +1, regardless of the solution (deprecate or not), but I am very
> convinced of the overlapping, they should not be 2 different
> implementations.
>
> Thanks,
> Anca