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 was wondering about the implications for usage.. I can almost
understand that there's an argument against it (non-linear / detached
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
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
Hi,
Am I going crazy or is the Wicket Viewer missing something...
I can't get the Wicket Viewer to pick up a previously-viewed object as
a parameter to an action.
I thought that if you viewed an object it became available for use as
an action parameter? Or is that only the HTML viewer?
I now
Thanks.. I set up a choices method, and have to admit I don't like that I have
to type something before any choices actually appear.
I can see the use for it later, but when the list is short, it forces an
unneeded keypress.
Is there any way a domain app service can access the bread crumb
