[xwiki-devs] [Iteration][UX] Nested: Tree Location
Hi devs, By default our Tree is localized in AllDocs. This iteration investigates additional ways to access the current's page position in the hierarchy. http://design.xwiki.org/xwiki/bin/view/Proposal/NestedTreeLocation Thanks, Caty
Good initiative. I like the combination of sol 3, 5 and 6. Sol 1: too much clicks and hidden in the crowd Sol 2: nice one but it does not have my preference (a bit complicated maybe) Sol 3: not sufficient but I believe this information panel should have this tree anyway Sol 4: too much clutter Sol 5: my favourite. Easy to use and find, but easily to hide too. Sol 6: not sufficient but I believe this popup should have this tree anyway Thanks, Guillaume 2015-07-09 11:55 GMT+02:00 Ecaterina Moraru (Valica) <[email protected]>:
Hi devs,
By default our Tree is localized in AllDocs. This iteration investigates additional ways to access the current's page position in the hierarchy.
http://design.xwiki.org/xwiki/bin/view/Proposal/NestedTreeLocation
Thanks, Caty _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Guillaume Delhumeau ([email protected]) Research & Development Engineer at XWiki SAS Committer on the XWiki.org project
On 9 Jul 2015 at 12:08:16, Guillaume Louis-Marie Delhumeau ([email protected](mailto:[email protected])) wrote:
Good initiative.
I like the combination of sol 3, 5 and 6.
Sol 1: too much clicks and hidden in the crowd Sol 2: nice one but it does not have my preference (a bit complicated maybe) Sol 3: not sufficient but I believe this information panel should have this tree anyway Sol 4: too much clutter
Actually this a wireframe. Visually you wouldn’t see any difference and it’s only when you click on the breadcrumb item that you’d see the dropdown. But that raises the issue with mobile (same issue as we had with the top menu) so indeed we’re a bit stuck.
Sol 5: my favourite. Easy to use and find, but easily to hide too.
Me too. Thanks -Vincent
Sol 6: not sufficient but I believe this popup should have this tree anyway
Thanks, Guillaume
2015-07-09 11:55 GMT+02:00 Ecaterina Moraru (Valica) :
Hi devs,
By default our Tree is localized in AllDocs. This iteration investigates additional ways to access the current's page position in the hierarchy.
http://design.xwiki.org/xwiki/bin/view/Proposal/NestedTreeLocation
Thanks, Caty
Hi Caty, Thanks for this design page! On 9 Jul 2015 at 11:55:23, Ecaterina Moraru (Valica) ([email protected](mailto:[email protected])) wrote:
Hi devs,
By default our Tree is localized in AllDocs. This iteration investigates additional ways to access the current's page position in the hierarchy.
http://design.xwiki.org/xwiki/bin/view/Proposal/NestedTreeLocation
* I don’t like sol2 because depending the usage done for the wiki, you won’t always want to display a nav panel. So this is an adhoc solution and not a generic one. * I don’t like sol3 too much (even though it’s interesting) because I find it too hidden away for the users and navigation is a key feature * sol1 is not optimal since it requires 2 clicks and you navigate away from your current page (if you want to cancel the nav it’s not nice). It could be implemented easily though if we want to have something quickly while waiting for a better solution * I like sol6 very much and we should have it but it’s not enough IMO * Sol4 and 5 are very nice IMO So overall my preference goes to Sol4 or 5 (and sol6 done in addition). Thanks a lot -Vincent
Thanks, Caty
2015-07-09 12:11 GMT+02:00 [email protected] <[email protected]>:
Hi Caty,
Thanks for this design page!
On 9 Jul 2015 at 11:55:23, Ecaterina Moraru (Valica) ([email protected] (mailto:[email protected])) wrote:
Hi devs,
By default our Tree is localized in AllDocs. This iteration investigates additional ways to access the current's page position in the hierarchy.
http://design.xwiki.org/xwiki/bin/view/Proposal/NestedTreeLocation
* I don’t like sol2 because depending the usage done for the wiki, you won’t always want to display a nav panel. So this is an adhoc solution and not a generic one.
But look at the top menu in this image. On the right, there is a new menu where you can chose if you want to display the standard app bar or the tree. It is not very obvious and the fact that you did not even see it proves that it is not very intuitive. * I don’t like sol3 too much (even though it’s interesting) because I find
it too hidden away for the users and navigation is a key feature * sol1 is not optimal since it requires 2 clicks and you navigate away from your current page (if you want to cancel the nav it’s not nice). It could be implemented easily though if we want to have something quickly while waiting for a better solution
* I like sol6 very much and we should have it but it’s not enough IMO
* Sol4 and 5 are very nice IMO
So overall my preference goes to Sol4 or 5 (and sol6 done in addition).
Thanks a lot -Vincent
Thanks, Caty
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Guillaume Delhumeau ([email protected]) Research & Development Engineer at XWiki SAS Committer on the XWiki.org project
On 9 Jul 2015 at 12:24:50, Guillaume Louis-Marie Delhumeau ([email protected](mailto:[email protected])) wrote:
2015-07-09 12:11 GMT+02:00 [email protected] :
Hi Caty,
Thanks for this design page!
On 9 Jul 2015 at 11:55:23, Ecaterina Moraru (Valica) ([email protected] (mailto:[email protected])) wrote:
Hi devs,
By default our Tree is localized in AllDocs. This iteration investigates additional ways to access the current's page position in the hierarchy.
http://design.xwiki.org/xwiki/bin/view/Proposal/NestedTreeLocation
* I don’t like sol2 because depending the usage done for the wiki, you won’t always want to display a nav panel. So this is an adhoc solution and not a generic one.
But look at the top menu in this image. On the right, there is a new menu where you can chose if you want to display the standard app bar or the tree. It is not very obvious and the fact that you did not even see it proves that it is not very intuitive.
Indeed, I missed it. Still the AppBar on the left is also only for some flavors and not for all so it cannot be a generic solution. We already have a Navigation Panel (I hope it’s using the new Tree but I don’t recall and if not then it should) and admins can decide to use it where they want. We could have it for some flavors where it makes sense, for example for the documentation flavor but I think we need a more generic solution and sol5/sol6 are better in this regards. Thanks -Vincent
* I don’t like sol3 too much (even though it’s interesting) because I find
it too hidden away for the users and navigation is a key feature * sol1 is not optimal since it requires 2 clicks and you navigate away from your current page (if you want to cancel the nav it’s not nice). It could be implemented easily though if we want to have something quickly while waiting for a better solution
* I like sol6 very much and we should have it but it’s not enough IMO
* Sol4 and 5 are very nice IMO
So overall my preference goes to Sol4 or 5 (and sol6 done in addition).
Thanks a lot -Vincent
Thanks, Caty
Hello, Thanks for your effort, Caty! - Solution1: I think in order to see the tree, there are required a minimum number of clicks and this solution clearly doesn’t cover this condition - Solution2: it seems a bit hidden, IMO and also too many clicks, as Sol1 - Solution3: is a very good idea, but is not sufficient and also a bit hidden - Solution4: is too crowded, IMO a breadcrumb should be as simpler as it can be - Solution5: this is the best solution from my point of view, because it also preserves the old breadcrumb and it adds a new element, with a “home” icon which I think is intuitive enough - Solution6: same as Sol3 - really nice to have, but not sufficient As a conclusion, my choice will be a combination between 3 and 5, or 5 and 6. Thanks, Gabriela
+1 for 5 for reasons already mentioned and because I find it to be the most natural. Thanks, Eduard On Thu, Jul 9, 2015 at 2:27 PM, Gabriela Smeria <[email protected]> wrote:
Hello,
Thanks for your effort, Caty!
- Solution1: I think in order to see the tree, there are required a minimum number of clicks and this solution clearly doesn’t cover this condition - Solution2: it seems a bit hidden, IMO and also too many clicks, as Sol1 - Solution3: is a very good idea, but is not sufficient and also a bit hidden - Solution4: is too crowded, IMO a breadcrumb should be as simpler as it can be - Solution5: this is the best solution from my point of view, because it also preserves the old breadcrumb and it adds a new element, with a “home” icon which I think is intuitive enough - Solution6: same as Sol3 - really nice to have, but not sufficient
As a conclusion, my choice will be a combination between 3 and 5, or 5 and 6.
Thanks,
Gabriela _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
Hi, Some summary of the expressed opinions: Sol1: -0 (GD), -0 (Vincent), -0 (Gabi), +0 (Caty) Sol2: -0 (GD), -1 (Vincent), -0 (Gabi), +1 (Caty) Sol3: +0 (GD), -0 (Vincent), +0 (Gabi), +0 (Caty) Sol4: -1 (GD), +1 (Vincent), -0 (Gabi), -1 (Caty) Sol5: +1 (GD), +1 (Vincent), +1 (Gabi), +0 (Caty), +1 (Eduard) Sol6: +0 (GD), +0 (Vincent), +0 (Gabi), +1 (Caty) So currently the proposal that have the most positive feedback are: Sol5 and Sol6. Thanks, Caty On Wed, Jul 15, 2015 at 5:26 PM, Eduard Moraru <[email protected]> wrote:
+1 for 5 for reasons already mentioned and because I find it to be the most natural.
Thanks, Eduard
On Thu, Jul 9, 2015 at 2:27 PM, Gabriela Smeria <[email protected]
wrote:
Hello,
Thanks for your effort, Caty!
- Solution1: I think in order to see the tree, there are required a minimum number of clicks and this solution clearly doesn’t cover this condition - Solution2: it seems a bit hidden, IMO and also too many clicks, as Sol1 - Solution3: is a very good idea, but is not sufficient and also a bit hidden - Solution4: is too crowded, IMO a breadcrumb should be as simpler as it can be - Solution5: this is the best solution from my point of view, because it also preserves the old breadcrumb and it adds a new element, with a “home” icon which I think is intuitive enough - Solution6: same as Sol3 - really nice to have, but not sufficient
As a conclusion, my choice will be a combination between 3 and 5, or 5 and 6.
Thanks,
Gabriela _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
+1 for Sol5 Thanks, Marius On Thu, Jul 30, 2015 at 4:29 PM, Ecaterina Moraru (Valica) <[email protected]> wrote:
Hi,
Some summary of the expressed opinions:
Sol1: -0 (GD), -0 (Vincent), -0 (Gabi), +0 (Caty) Sol2: -0 (GD), -1 (Vincent), -0 (Gabi), +1 (Caty) Sol3: +0 (GD), -0 (Vincent), +0 (Gabi), +0 (Caty) Sol4: -1 (GD), +1 (Vincent), -0 (Gabi), -1 (Caty) Sol5: +1 (GD), +1 (Vincent), +1 (Gabi), +0 (Caty), +1 (Eduard) Sol6: +0 (GD), +0 (Vincent), +0 (Gabi), +1 (Caty)
So currently the proposal that have the most positive feedback are: Sol5 and Sol6.
Thanks, Caty
On Wed, Jul 15, 2015 at 5:26 PM, Eduard Moraru <[email protected]> wrote:
+1 for 5 for reasons already mentioned and because I find it to be the most natural.
Thanks, Eduard
On Thu, Jul 9, 2015 at 2:27 PM, Gabriela Smeria <[email protected]
wrote:
Hello,
Thanks for your effort, Caty!
- Solution1: I think in order to see the tree, there are required a minimum number of clicks and this solution clearly doesn’t cover this condition - Solution2: it seems a bit hidden, IMO and also too many clicks, as Sol1 - Solution3: is a very good idea, but is not sufficient and also a bit hidden - Solution4: is too crowded, IMO a breadcrumb should be as simpler as it can be - Solution5: this is the best solution from my point of view, because it also preserves the old breadcrumb and it adds a new element, with a “home” icon which I think is intuitive enough - Solution6: same as Sol3 - really nice to have, but not sufficient
As a conclusion, my choice will be a combination between 3 and 5, or 5 and 6.
Thanks,
Gabriela _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
Notes: * I still think that some variation of sol4 (to make it not too crowded) would be the best, not just for the navigation but also to have common actions be readily accessible for any level (watch, etc). But this could be tuned in the future and having at least sol5 now is good IMO. * However, I think that Sol 6 is a must too and we could offer commons actions there too (currently we have view and edit). It’s not incompatible at all with sol5, so we shouldn’t choose sol5 vs sol6. So I’m big +1 to have sol6 in addition to sol5. In term of priority, sol5 is more important. Thanks -Vincent On 2 Sep 2015 at 14:06:25, Marius Dumitru Florea ([email protected]) wrote: +1 for Sol5 Thanks, Marius On Thu, Jul 30, 2015 at 4:29 PM, Ecaterina Moraru (Valica) <[email protected]> wrote:
Hi,
Some summary of the expressed opinions:
Sol1: -0 (GD), -0 (Vincent), -0 (Gabi), +0 (Caty) Sol2: -0 (GD), -1 (Vincent), -0 (Gabi), +1 (Caty) Sol3: +0 (GD), -0 (Vincent), +0 (Gabi), +0 (Caty) Sol4: -1 (GD), +1 (Vincent), -0 (Gabi), -1 (Caty) Sol5: +1 (GD), +1 (Vincent), +1 (Gabi), +0 (Caty), +1 (Eduard) Sol6: +0 (GD), +0 (Vincent), +0 (Gabi), +1 (Caty)
So currently the proposal that have the most positive feedback are: Sol5 and Sol6.
Thanks, Caty
On Wed, Jul 15, 2015 at 5:26 PM, Eduard Moraru <[email protected]> wrote:
+1 for 5 for reasons already mentioned and because I find it to be the most natural.
Thanks, Eduard
On Thu, Jul 9, 2015 at 2:27 PM, Gabriela Smeria <[email protected]
wrote:
Hello,
Thanks for your effort, Caty!
- Solution1: I think in order to see the tree, there are required a minimum number of clicks and this solution clearly doesn’t cover this condition - Solution2: it seems a bit hidden, IMO and also too many clicks, as Sol1 - Solution3: is a very good idea, but is not sufficient and also a bit hidden - Solution4: is too crowded, IMO a breadcrumb should be as simpler as it can be - Solution5: this is the best solution from my point of view, because it also preserves the old breadcrumb and it adds a new element, with a “home” icon which I think is intuitive enough - Solution6: same as Sol3 - really nice to have, but not sufficient
As a conclusion, my choice will be a combination between 3 and 5, or 5 and 6.
Thanks,
Gabriela _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
participants (6)
-
Ecaterina Moraru (Valica) -
Eduard Moraru -
Gabriela Smeria -
Guillaume "Louis-Marie" Delhumeau -
Marius Dumitru Florea -
vincent@massol.net