[ZDP] ZDPFAQ questions

[Maik Roeder]

Hi Rik !


> Hi Maik,
> 
> I was starting to implement it. There are some choices to be made
> however. We could implement this in several ways, but they all have
> disadvantages.The options are:
> - use properties in the objects themselves. THen list thim on a special
> form with objectValues sort etcetera.

I think this is the way to go.

> The disadvantage is that the order porperty then becomes a property of
> the item, when in reality it is only of importance to its container

Model/View/Controller:

Model: FAQ Questions (dumb domain objects)
View: The ordered View of the FAQ Questions
Controller: Changing the order of FAQ Questions is done in the FAQ Sections

The Model does not know what to do with itself, but only has properties
which are modified by the FAQ Section Controller. The View is completely
separate, and by my reckoning should not contain the order information.
Rather the View only looks on the FAQ Questions, and based on what it
sees decided how to display them.

> (you could imagine a situation where more orders would be possible)

When more orders are possible you can either define new views or 
define new order properties.

> THis option does provide for arbitrary numbers for ordering, however.

yep.

> - use a registry in the container.

A registry may become a little bit complicated.

> I implemented this with a lines  property (at least, so far), and it
> works well, except that lines properties have the disadvantage that
> they can only contain one item per line or you will have to split
> lines up manually. (splitting with sequence-key:sequence-item does
> not work, I tried it) 

One item per line is what we need, isn't it ?

> THis last option would be alright, but it doesn't provide for a fixed
> ordering (the ordering numbers are dynamically generated)
> 
> Hm, is this clear?

I don't see what exactly you are storing in the line property. I also
don't understand how the ordering numbers are then dynamically generated.

Greetings,

Maik Röder