1 Oct
2012
1 Oct
'12
12:06 p.m.
On Mon, Oct 1, 2012 at 12:56 PM, Jean-Vincent Drean <jv(a)xwiki.com> wrote:
On Mon, Oct 1, 2012 at 11:36 AM, Thomas Mortagne
<thomas.mortagne(a)xwiki.com> wrote:
On Mon, Oct 1, 2012 at 11:23 AM, Vincent Massol
<vincent(a)massol.net> wrote:
On Oct 1, 2012, at 11:16 AM, Vincent Massol <vincent(a)massol.net> wrote:
I'm OK with CompositeBlock.
I don't have much more argument than "BlockList sounds nicer" so for
now you win.
I'm changing my vote to -0 for BlockList FTM
since I've just realized there might a problem.
BlockList means that it's a list of block. But this is not what it is…
It's a Block like any other block. The important part is not that it's a list of
blocks, all our blocks are list of blocks.
The important part is that it can be used to hold one or several blocks.
More precisely, compared to the other existing block this is a type of block that add no
additional metadata.
It's a no op block basically.
The fact that it's a list of Block is a feature of all blocks so this one doesn't
need to mention that explicitly I think.
ATM I prefer CompositeBlock than BlockList which I find a bit misleading.
NoOpBlock would be ok too I guess but I don't like it too much.
I'm very close to -1 for BlockList. I think CompositeBlock sounds even better.
+1
Thanks,
Marius
JV.
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs