Would this be viewed as an improvement? Home |-- Subwikis |---- Sub Wiki 1 |---- Sub Wiki 2 |---- ... |---- Sub Wiki N |-- Document 1 |-- Document 2 |-- ... |-- Document N
...same logic we apply for objects, and attachments in a document. Of course, when displaying the tree only for Sub Wiki X (isolated), there would be no "Subwikis" entry as first child. That would be the difference when displaying a subwiki or when displaying the main wiki. I`m not 100% on this, just mentioning a possibility. Thanks, Eduard On Wed, Sep 2, 2015 at 3:22 PM, [email protected] <[email protected]> wrote: > > > > On 2 Sep 2015 at 13:34:27, Marius Dumitru Florea ( > [email protected]) wrote: > > On Mon, Aug 24, 2015 at 4:09 PM, [email protected] <[email protected]> > wrote: > > > > > > > > > > > > On 24 Aug 2015 at 14:21:19, Marius Dumitru Florea ( > [email protected](mailto:[email protected])) > wrote: > > > >> Hi devs, > >> > >> I recently discussed with Edy about how the breadcrumb should look and > >> there may be an inconsistency with the hierarchy displayed by the > >> document tree. > >> > >> Breadcrumb on the main wiki: > >> > >> Home Icon (pointing to the main wiki home page) / MDoc1 / MDoc2 / ... / > MDocX > >> > >> Breadcrumb on a subwiki (that has only global users): > >> > >> Home Icon (pointing to the main wiki home page) / Subwiki Pretty Name > >> (pointing to the subwiki home page) / SDoc1 / SDoc2 / ... / SDocX > >> > >> After seeing the breadcrumbs both on the main wiki and on a subwiki > >> the user might think that the document MDoc1 and the wiki "Subwiki > >> Pretty Name" are on the same level: both children of the main wiki. > >> > >> Next if the user tries the document tree macro using: > >> > >> {{documentTree showWikis="true" /}} > >> > >> he will notice that "Subwiki Pretty Name" is not actually a child of > >> the main wiki but a top level node (a child of the "farm"), on the > >> same level with the main wiki. > >> > >> Can this be considered as an inconsistency? In our model (e.g. > >> document reference) there is no hierarchy between wikis, although, as > >> Edy pointed out, there are places where we consider the main wiki to > >> be the "parent" of the subwikis (e.g. in the authorization module, by > >> inheriting access rights from the main wiki). > >> > >> WDYT? Is the main wiki the parent of the subwikis or just a sibling? > > > > Good question and indeed we need to decide what we want to do since we > have the 2 options. > > > > Personally I think it’s interesting to mark the main wiki as special > since it is special (accounts there are different than on subwikis) so I’d > be in favor of considering subwikis as children of the main wiki. > > > >> Should the breadcrumb be synchronized with the tree? > > > > > I’d say the other way around. The tree should probably show the main > wiki as the parent of all subwikis. And when there’s only one wiki (ie the > main wiki), we could simply not show the wiki level for simplicity. We > could also decide to open the tree to the level below the main wiki by > default so that users don’t have to open it themselves. > > I find it strange to display: > > Home > |-- Sub Wiki 1 > |-- Sub Wiki 2 > |-- ... > |-- Sub Wiki N > |-- Document 1 > |-- Document 2 > |-- ... > |-- Document N > > Not to mention the pagination. If there are too many subwikis then you > may not see the documents initially. I much prefer the current > display. > I would find it painful to have to open the tree for nodes that you need > to open anyway. > > Another idea: when you click on Document Index from a menu, the Tree opens > on the current doc. > > Thanks > > -Vincent > > > > Thanks, > Marius > > > > > Thanks > > -Vincent > > > >> > >> Thanks, > >> Marius > _______________________________________________ > devs mailing list > [email protected] > http://lists.xwiki.org/mailman/listinfo/devs > _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
