On 15 February 2013 22:03, Maurizio Taverna <[email protected]>wrote:
> > 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 was thinking more that a domain service would provide a mechanism to invalidate the ordering in an ObjectSpecification and thus cause it to be re-computed. Or, perhaps just bake in some sort of "re-layout" button within the Wicket viewer itself. On this general topic (and you mentioning Balsamiq mock-ups made me think of this), there's has been some work done on by others on a "Naked Objects View language". There's an NO framework developed in Brazil that uses this. Even if you don't speak Portugese (I certainly don't), you'll get the general idea from [1] and [2]. The reason in Isis that the MemberOrderLayoutArranger (when all it currently does is the sorting of members) is that in future it might be able to get hold of an NOVL-like specification and actually layout the elements somehow. All very sketchy at the moment, but a placeholder for future improvements. Looping this back, one could imagine an end-user having some sort of web tool that generates the NOVL to some well-known location, such that the running application would dynamically read this information and lay itself out. One could also imagine that individual users might have their own custom layouts, and/or be able to share them. A bit like the iGoogle portal page [3], in other words. Dan [1] http://www.slideshare.net/marciusbrandao/naked-objects-view-languageinfo-brasil [2] http://www.infobrasil.inf.br/userfiles/16-S2-1-97119-Naked%20Objects___.pdf [3] http://www.google.com/ig
