> 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 workflow), but it always seemed so useful in the HTML viewer! :) To put in explicit "choices" methods makes the available list programmatically known and predictable. > I've made a note in my private todo list of items that I'm working on for > the wicket viewer, but it's down at about num. 20, I'm afraid. I don't suppose it is straight forward extension that you can easily describe?
