Element order in views

[feisley]

In the new views that were introduced in #20 the order of the elements/fields is dictated by the <profile> rather than the <view>

This presents a slight challenge: on one hand the <profile> allows for groups of elements to separate information logically. In this case it makes sense for <profile> to drive the ordering. However, for something like the "compact" view used for the hover profiles, it might be useful to be able to set the order in that view.

For example, in the sample configuration if we look at the fields Name, Email and Position. For the profile the order is Name, Email, grouped in Personal and Position grouped in Business. When we create a view for the hover, if we want to use the order: Name, Position, Email, this is not possible currently as the order is defined globally at <profile> and the <view> only controls visibility.

It may be worth considering changing <profile> to simply be the data definition only and <view> become the presentation definition. Thus we would move groups out of <profile> and into <view>

[blaubaer]

Agree. I also think about this.

Summary: For this it is required to change the whole way how to define the elments.
I it required the delete the <group>s from the profile and move them to the <view>s.

From this moment on the order of <element> are respected in <view> and <report>.

Problem: Structure change will be required. But I have no desire to provide a configuration migration for a beta version. ;-)

[feisley]

Thats why its beta ;-) Just make note of it and upgrade. Better to do it now before loads of people are using it and have to migrate...