I understand where you're coming from.. implicitly add a specific "choices" facet to methods that don't already provide one. Have it contribute from the breadcrumb trail as appropriate.
I can't say I know the details of how to do this, but this description is a start. I'm going to add it to my list of "TODOs".. and move this thread into dev@isis. On 3 Mar 2013 at 18:39, Dan Haywood wrote: > On 3 March 2013 16:36, Kevin Meyer - KMZ <ke...@kmz.co.za> wrote: > > > > I suppose there's no reason that the Wicket viewer can't do something > > > similar to the HTML viewer, which is to present a list of objects > > recently > > > encountered. > > > > I don't suppose it is straight forward extension that you can easily > > describe? > > > > > As a first cut, you could write a FacetFactory (register it explicitly > using the technique documented in [1]), such that it would install a > ChoicesFacet on any properties or parameters that don't already have a > ChoicesFacet or AutoCompleteFacet. > > You could either look inside the Breadcrumbs stuff to find a list of > visited OIDs, or - perhaps even better - in the WebRequestCycleForIsis's > onEndRequest() method you could reach into the objectstore (I'm not quite > certain what API to use here) and get and cache the oid and title of all > the objects that were brought into memory during the transaction. You > could probably just store this list in the Wicket Session object > (Session.get()). > > Let me know if that makes any sort of sense...
