Name: Seaside-Core-lr.296
Author: lr
Time: 22 October 2008, 9:43:36 am
UUID: abbac93f-0d2e-4497-ae56-efec27c04d8b
Ancestors: Seaside-Core-lr.295

- WACollection attributes have a defined order (Issue 217)

Name: Seaside-Tests-Core-lr.15
Author: lr
Time: 22 October 2008, 9:46:08 am
UUID: d8512b8a-7e48-487e-8af8-4c40dc87c04a
Ancestors: Seaside-Tests-Core-jf.14

- WACollection attributes have a defined order (Issue 217)

Now, we should also be able to define the order from the UI.

I'm still concerned about how this is actually going to work in practice. In
particular, it seems like adding an item to your inherited list is problematic. 
How
do you specify where in the list it should go? If these attributes only ever 
override
the inherited value, then it's relatively straightforward.

Currently it is not possible to specify the order, even if you override. That's 
a GUI issue though and could be 
improved. The items are stored in an ordered collection, so providing the items 
in the right order is already 
possible if done programmatically.

In some cases it is useful to be able to add new items to an inherited list. 
Currently new items are always 
added to the end of the list. For all my uses of this functionality this is 
exactly the right thing to do. We might 
consider adding another list to inherited properties that adds to the 
beginning, but I would wait with that 
before somebody actually requests it. Inherited list attributes can't solve 
everything, but they are useful in 
many cases (the WADevelopmentConfiguration wants to add the stylesheet of the 
toolbar). If they do not suit 
your needs, you can always override and provide a fixed list.

Ok, so your desired behaviour is:

 * you always specify an ordered list in the UI
 * if you specify "override" then that list is used as the value of the attribute
 * if you specify "modify" then your ordered list is added to the END of the
inherited list

Is that right?

Exactly, and all the points you mentioned already work like that. The only 
remaining problem is that of the UI 
(you can specify the order only programmatically).

See also Issue 142