Hi Kevin, sorry, never answered this question of yours. Apols. Within...
On 3 September 2014 08:55, Kevin Meyer <[email protected]> wrote: > > Two questions come to mind: > > 1. What do the POJOs look like that can encode such a structure of > configuration records > > I would imagine it's a composite pattern, probably collapsed to single node: public class ConfigRecord { @Optional public ConfigRecord getParent() { ... } public List<ConfigRecord> getChildren() { ... } } forming a 1:n bidirectional with itself. Most likely use view models for this. > 2. Can the Wicket viewer be updated to support a drag-and-drop tree > structure(drag and drop to re-arrange the structure from the "as-parsed") > to reannrage and merge branches. > > It could, by writing a ComponentFactory that "appliesTo" only collections of ConfigRecords. Take a look at CollectionContentsAsAjaxTablePanelFactory [1], or perhaps even better CollectionOfEntitiesAsLocatablesFactory [2] in the gmap3 Wicket extension, for inspiration on that Obviously you'd need to find a Wicket component to actually implement the body of the panel that will render. A quick google suggests that there is a component in Wicket 6, in fact. Let me know if you decide to go this way but need some help. Cheers Dan [1] https://github.com/apache/isis/blob/0af3219129076161143bd388e3fc3ec039cbed79/component/viewer/wicket/ui/src/main/java/org/apache/isis/viewer/wicket/ui/components/collectioncontents/ajaxtable/CollectionContentsAsAjaxTablePanelFactory.java#L45 [2] https://github.com/isisaddons/isis-wicket-gmap3/blob/master/extension/ui/src/main/java/com/danhaywood/isis/wicket/gmap3/ui/collectioncontents/CollectionOfEntitiesAsLocatablesFactory.java#L53 > >
