Hello, > Isis actually orders the members (properties, collections, actions) by > looking at the value of the MemberOrderFacet attached to each member. > The default programming model [1] configures the > MemberOrderAnnotationFacetFactory [2] > which looks for the @MemberOrder annotation. > However, you could [3] easily install your implementation that reads this > metadata from somewhere else. >
This is very interesting, store the 'tweaking' data on external storage (let's say a file) giving the option to enable this feature changing the Isis configuration. One caveat: it isn't currently possible to dynamically reorder the members; > they are immutable once the ObjectSpecification representing the class has > been built. > I think see your point, the viewer could look for the 'tweaking' data and override any default behaviour. I'm really impressed, the Isis framework enables to do just the right thing in the right way. Thank you Dan Best Maurizio
