One of the problems with web viewer is keeping context of the primary "object" 
you are working with e.g. customer, as you navigate around it's related object 
instances. Having to use the browser back button is not acceptable and having 
to relocate your customer again after working on some related object using find 
... is also unacceptable. Which is where the "breadcrumb" panel comes into it's 
own on the wicket viewer. 


However I just want to canvas opinions on an idea: Would it make sense to 
(maybe optionally) limit the breadcrumbs to objects rather than object 
operations to reduce the clutter?

Maybe some way of "pinning" an object to the panel (like a temporary bookmark)?

I guess the other approach is to programatically "backlink" all the connected 
business objects (i.e implement two way relationships) which seems a bit naf if 
the only reason you are doing it is for a specific viewer behaviour - after all 
we are trying to make less work for ourselves rather than more.


Thoughts?

Regards,
David.

Reply via email to