On 19 July 2013 21:44, GESCONSULTOR - Óscar Bou <[email protected]>wrote:

>
>
> With current pattern, perhaps if the breadcrumb panel would be "always
> visible" horizontally under the menus would be "enough intuitive" for the
> user. If he knows that at the upper left corner is always the last accessed
> "domain object" he always now how to navigate. The list of bookmarks should
> be ordered from left to right,  having on the left the most recent element,
> as I think it was before introducing the new design.


Yes, this is pretty much how things were.  But it didn't work too well,
hence the sliding bookmark panel we now have.

I'm not saying that there aren't other improvements that could be made, but
a simple list of bookmarks along the top doesn't really work.  (On the
Naked Objects .NET system I work on as well, that also abandoned bookmarks).


> It should only show "aggregate roots". If I navigate to an Invoice, it
> should be bookmarked. If I navigate to an invoice item, it shouldn't be
> bookmarked (or bookmarked under its invoice).
>
>
We have this feature - in effect - through the @Bookmarkable(AS_ROOT) or
@Bookmarkable(AS_CHILD) annotations.  It's great to be able to leverage the
Isis metamodel in this way to slot the items into their "aggregates".



> If popup dialogs would be allowed, the navigational pattern could be
> different.
> The user would first select any repository list available through the
> menus and, when clicking on any Entity or action, it would be shown on a
> popup dialog that the user would close wherever he wanted (or the action
> was invoked or cancelled).
>
> The latter is the chosen approach at MS CRM and others. See a brief
> description of the current UI at [1].
>
> Also on [2], starting at 17:05, you can see the current version's UI where
> you will see how an entity's view dialog is open by clicking on a
> previously defined list (repository finder).
> If you want to see the new interface, it's on minute 3:00, but any
> navigation is showed.
>
> SAP uses the same navigational pattern as MS CRM.
>
> Thanks for those links, Oscar, some useful viewing.

The SAP UI might be considered rather old fashioned, but I can see that it
would be quite effective in use.  However, I think that Wicket is probably
the wrong technology to implement MDI-style floating windows.

Jeroen and I have considered implementing a UI using something like Vaadin
[6], and Maurizio's DHTMLX viewer [7], [8] could probably also support such
a viewer.




> On SalesLOGIX don't directly use dialogs, so there's a "Recently viewed
> items list". See [3]. At minute 1:57 you will see the recently view items
> grouped by "entity type". In another video [4] you will see the "new tab"
> hint for opening multiple entity views at once.
>
> That's quite funny... the guy doing the demo is simply using a feature of
the web browser (open in new tab).  Obviously one could do that in Isis
too, and it's a useful side effect of running an app in a browser.  But I
don't think we should rely on users to do this (some might like to run full
screen - F11 - where tabs cannot be seen).



>
> These companies has invested a lot on UI development for applications
> quite similar "in concept" to the ones made with Isis.
>

The one additional idea I got from these videos was that the breadcrumbs
panel could, perhaps, organize by entity type.


>
> Hope this helps at least for thinking about different approaches, hints,
> etc.
>

It does.  Thx again.

Dan

[6] https://vaadin.com/ <https://vaadin.com/home>
[7] http://isis-viewer-dhtmlx.appspot.com/
[8] https://github.com/madytyoo/dhtmlx-isis-viewer



> Regards,
>
> Oscar
>
>
> [1]
> http://www.preact.co.uk/preact_blog/how-to-navigate-the-microsoft-dynamics-crm-interface
>
> [2] http://www.preact.co.uk/preact_blog/dynamics-crm-flow-interface
>
> [3]
> http://www.youtube.com/watch?v=H8rlmZKpV44&list=PLp766Vomquq7khRdyOv_8f3LEWTR9FF4D
>
> [4] http://www.youtube.com/watch?v=ewLTsJIkxwA
>
> [5] http://www.youtube.com/watch?v=Fe8yg6amIJ0
>
>

Reply via email to