[ZDP] ZDPFAQ questions

[Rik Hoekstra]

Maik Roeder wrote:
> 
> Sounds ok, but we don't need the moving up and down part.
> 
> We can make a view of the FAQ Questions in the FAQ Section where you can
> see the following:
> 
> _1_ Question x
> _2_ Question y
> _3_ Question z
> 
> Each line starts with the order number, and then comes the question.
> 
> You can change all order numbers in this view by hand. Like this:
> 
> _3_ Question x
> _2_ Question y
> _1_ Question z
> 
> Result when viewing the Order view again:
> 
> _1_ Question z
> _2_ Question y
> _3_ Question x
> 
> Alternatively, you can also completely change the order ad hoc as in:
> 
> _1233_ Question x
> _122_ Question y
> _1_ Question z
> 
> After that, the view is always built up in order:
> 
> _1_ Question z
> _122_ Question y
> _1233_ Question x
> 
> So, in this case, you are very sure that Question z should come first.
> Question y is so lala, and Question x should be fairly far behind.
> 
> When you add a new Question, it gets an order number 0, and will
> always be listed on top. You can add more and more Questions, which
> will also stay on top, but in random order, which is ok.
> 
> When you think the order is not ok, you click on the ordering view,
> 
> _0_ Question a
> _0_ Question b
> _0_ Question c
> _1_ Question z
> _122_ Question y
> _1233_ Question x
> 
> and change the order:
> 
> _50_ Question a
> _2000_ Question b
> _2_ Question c
> _1_ Question z
> _122_ Question y
> _1233_ Question x
> 
> Here, you already know Question c should come directly after
> Question 1. Question a is somewhere in the middle, and Question b
> can come at the back.
> 
> Reviewing shows:
> 
> _1_ Question z
> _2_ Question c
> _50_ Question a
> _122_ Question y
> _1233_ Question x
> _2000_ Question b
> 
> I think this is really cool, because it allows for some chaos,
> while trying to define order :-)
> 
> Who is going to implement this ? ;-)

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. 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 (you could imagine a situation where more
orders would be possible)
THis option does provide for arbitrary numbers for ordering, however.
- use a registry in the container. 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)
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?

If so, what shall I do?

Rik