26 May
2015
26 May
'15
11:17 a.m.
On 26 May 2015 at 10:47:13, Ecaterina Moraru (Valica)
(valicac@gmail.com(mailto:valicac@gmail.com)) wrote:
Hi Vincent,
The iteration follows two ideas:
A. combine the global menu functionality with breadcrumbs (this was again
suggested by you when we proposed Macaw skin);
B. use trees inside the breadcrumb;
I've iterated on A) in order to demonstrate how it will look like, what
problems/confusions might appear.
My conclusion is that combining the 2 functionalities will increase
complexity and cause either harder navigation or confusion (depending if we
display or not the entity icons).
Note that the current top level menu is already a navigation menu and it already plays the
role of a limited breadcrumb (wiki > space > page).
There are 2 questions I see:
1) what does the top level menu becomes with nested spaces. Following the current logic,
if you have Space1 and Space2 you’d have: Wiki > Space1 > Space2 > Page
2) when we implement nested spaces, do we still need the parent/child relationship. My
opinion is “no” and we should turn it off by default and keep it only as an advanced
feature for those who really need/want it. Once this is said, it means that if we rewrite
the breadcrumb based on the current document’s reference we would have the top level menu
and the breadcrumb display the same thing (if we follow the current logic), which is
probably not good.
I’d like to know your proposal for point 1).
The solution could be to keep the
breadcrumb for navigation, while transferring the global-menu actions
inside the content-menu (but this ideally needs to be adaptive - which is
again not that straightforward to implement) + Drawer.
I've iterated also on B). The usage of tree
depends on how many entries we
plan to display in the breadcrumb (3, 5+, etc.) in order to provide added
value by tree usage. This direction could have further iterations if we
want to go this way, like:
- provide also actions inside the Tree displayer (still actions needs to be
limited + plus think about mobile usage);
- have a common activator (we could use the Home icon) or localized tree
activator (the mockup displays a localized activator on '...');
- other?
Some questions that appeared during this iteration:
- what do we do with the parent/child backwards compatibility?
See point 2 above
- when we have nested spaces, we display the space or
the space.webhome?
the type of the entry is a space or the page?
I don’t understand the question.
- how important is to limit the breadcrumb display?
usually how many
entries we have in a breadcrumb? Should we default for more than 7 entries
or keep 3 like we currently have?
I don’t understand. Currently the breadcrumb allows for more than 3 entries...
- how important is to provide fast access for Watch or
Delete space
actions? or other actions inside the global-menu? Administration and
Indexes could be displayed in the Drawer, Watch+Delete inside the
content-menu (
http://design.xwiki.org/xwiki/bin/view/Proposal/MacawSkin#HGlobalMenu)
Note that it’s more than just Watch/Delete space:
- watch space
- space admin
- space index pages
- delete space
Note that IMO http://design.xwiki.org/xwiki/bin/view/Proposal/MacawSkin#HGlobalMenu is
missing a Space Index menu entry to make it relatively simple to navigate to any space
from anywhere (and thus we able to watch/delete/etc).
I have 2 solutions that I would find nice:
Solution 1
==========
- drawer menu as
on http://design.xwiki.org/xwiki/bin/view/Proposal/MacawSkin#HGlobalMenu (+ something to
navigate easily to any space)
- keep the current breadcrumb location but base it on the reference (instead of
parent-child)
- add the ability to click on any element of the breadcrumb to perform the actions that
are currently in the top level menu (but don’t make is visible, ie keep the current
L&F, it’s only when you hover or click on an element that you get a dropdown, making
it a “hidden/advanced” feature
like: https://www.evernote.com/l/AHect8iy7ylGWLtlW0uvk2pvkenGBiMFcDQ
Solution 2
==========
- drawer menu as
on http://design.xwiki.org/xwiki/bin/view/Proposal/MacawSkin#HGlobalMenu (+ something to
navigate easily to any space)
- keep the current breadcrumb location but base it on the reference (instead of
parent-child)
- add the ability to click on any element of the breadcrumb but when you click on them you
get a dropdown with all children of the current element (using a treeview set on the
children of the current element).
With solution 2 you wouldn’t have the actions anymore and you’d need to navigate to the
element to get its actions. OTOH you’d get a quick way to navigate a bit everywhere from
your current location.
I’m hesitating between both solutions. They solve different needs.
Thanks
-Vincent
Compared to other proposals (when the 'final'
solution was presented), here
it was mostly an iteration, exploring possible approaches and requesting
feedback or other ideas.
Thanks,
Caty
On Tue, May 26, 2015 at 11:02 AM, vincent(a)massol.net
wrote:
Hi Caty,
On 22 May 2015 at 17:39:58, Ecaterina Moraru (Valica) (valicac(a)gmail.com
(mailto:valicac@gmail.com)) wrote:
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs Hi,
This is an iteration for:
Extended-Breadcrumb's purpose is to provide a solution to *combine* the
global-menu functionality with the current breadcrumb functionality,
while
supporting *nested spaces* concept and being
backwards compatible with
*parent/child* relationship.
Proposal:
http://design.xwiki.org/xwiki/bin/view/Proposal/ExtendedBreadcrumb
It’s cool that you started working on this! :)
However I don’t understand the conclusion. You say:
“The recommendation is to keep separate the navigation (breadcrumb) from
entity type actions (menus).“
However the 3 screenshots don’t reflect that since the entity type action
have disappeared!
Could you explain what’s your proposal for the entity type action menu and
how you implement nested spaces in it?
Thanks
-Vincent
Thanks,
Caty