8 Dec
2010
8 Dec
'10
6:46 p.m.
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
9 Dec
9 Dec
12:15 p.m.
New subject: [xwiki-devs] [discussion] Replace the box macro with the container macro
Never used the Container macro, while the Box macro IMO is more highly used
(specially on xwiki.org) in combination with "floatinginfobox" class.
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
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
12:33 p.m.
New subject: [xwiki-devs] [discussion] Replace the box macro with the container macro
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
2:33 p.m.
New subject: [xwiki-devs] [discussion] Replace the box macro with the container macro
Hi,
On Thu, Dec 9, 2010 at 12:33, Vincent Massol <vincent(a)massol.net> wrote:
On Dec 9, 2010, at 12:15 PM, Ecaterina Moraru (Valica) wrote:
Write the box macro as a superset of the container macro with the additional
"title" and "image" parameters ;-)
Guillaume
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
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
3:22 p.m.
New subject: [xwiki-devs] [discussion] Replace the box macro with the container macro
Hi guys,
On 12/09/2010 02:33 PM, Guillaume Lerouge wrote:
Write the box macro as a superset of the container macro with the additional
"title" and "image" parameters ;-)
subset you mean (containers that also have an image is a restriction
from containers, not a generalization ;) ).
Thanks,
Anca
Hi,
On Thu, Dec 9, 2010 at 12:33, Vincent Massol<vincent(a)massol.net> wrote:
>
> 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
Probably because container is new (2.5M2+) and because ftm it's not
actually implementing anything of what it should, it only implements the
columns layout.
>> (specially on xwiki.org) in combination with
"floatinginfobox" class.
This should be even easier with a "complete" container, you should just
pick the place it should float to (left, right), and its floating should
not depend on the existence of rules for floatinginfobox in the
particular skin you're using.
It would be more user oriented, from this pov, more complete than the box.
>
> 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.
Vincent, does this mean that you're against both having an image (icon)
in container macro and having the box macro implemented as a
specialization of the container -- proposed in my initial mail and also
reiterated by Guillaume below?
Guillaume
Thanks
-Vincent
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs 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
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
10 Dec
10 Dec
12:10 p.m.
New subject: [xwiki-devs] [discussion] Replace the box macro with the container macro
On Wed, Dec 8, 2010 at 18: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.
+1 and +1 for the superset instead of the replace
Thanks,
Anca
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
--
Thomas Mortagne
2:32 p.m.
New subject: [xwiki-devs] [discussion] Replace the box macro with the container macro
On 12/08/2010 07:46 PM, Anca Luca 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?
+1 for making box macro a particular type of container.
Thanks,
Marius
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
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
2:38 p.m.
New subject: [xwiki-devs] [discussion] Replace the box macro with the container macro
On Dec 10, 2010, at 2:32 PM, Marius Dumitru Florea wrote:
On 12/08/2010 07:46 PM, Anca Luca wrote:
Why not remove it? What would we gain in keeping it?
Thanks
-Vincent
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?
+1 for making box macro a particular type of container. Thanks,
Marius
>
> 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
8:08 p.m.
New subject: [xwiki-devs] [discussion] Replace the box macro with the container macro
On 12/10/2010 03:38 PM, Vincent Massol wrote:
On Dec 10, 2010, at 2:32 PM, Marius Dumitru Florea wrote:
On 12/08/2010 07:46 PM, Anca Luca 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?
+1 for making box macro a particular type of container. Why not remove it? What would we gain in keeping it?
Box macro could extend the container macro with title and icon. Message
macros would still use it.
Thanks,
Marius
Thanks
-Vincent
Thanks,
Marius
>
> 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
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
5029
days inactive
5031
days old
8 comments
6 participants
participants (6)
-
Anca Luca -
Ecaterina Moraru (Valica) -
Guillaume Lerouge -
Marius Dumitru Florea -
Thomas Mortagne -
Vincent Massol