On 18 July 2013 00:58, David Tildesley <[email protected]> wrote: > > 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? >
Certainly happy to introduce this feature. As you know, we have the @Bookmarkable annotation which applies to classes only. For actions, any safe (@ActionSemantics(Of.SAFE)) is also automatically bookmarked. But we could change this default behaviour so that only those actions annotated as bookmarkable are bookmarked. We could then also potentially allow a developer to annotate non-safe actions. eg for queues of objects that go through a status, eg UserStory class with status: pending -> in-progress -> done, then UserStories#playNext() gets the next UserStory and marks it as in progress for the current user. It'd be nice to make this action as a bookmark. > > Maybe some way of "pinning" an object to the panel (like a temporary > bookmark)? > > Yes, that's a separate feature... also been considering this for a while. By all means raise a JIRA ticket for each of these, describing your preferred behaviour. > 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. > > Agreed, not really the way to go. Dan > > Thoughts? > > Regards, > David. >
