I add my votes: [Iteration 1]
Sol1: +0 Gabi, +0 Jean (with modifications), +0 Guillaume D Sol2: +1 Caty, +0 Gabi, +0 Jean (with modifications), +1 Guillaume D Sol3: +1 Vincent, +1 Jean, +1 Gabi (with modifications), +1 Guillaume D Sol4: +0 Caty, +0 Jean, +0 Guillaume D [Iteration 2] Sol 2.1.1: -1 Guillaume D (because of the display of 'WebHome') Sol 2.1.2: +0 Guillaume D Sol 2.1.3: +1 Caty, +1 Guillaume D Sol 3.1.1: +0 Guillaume D Sol 3.1.2: +0 Guillaume D Sol 3.1.3: +1 Guillaume D 2015-07-30 14:32 GMT+02:00 Ecaterina Moraru (Valica) <[email protected]>: > Hi, > > Summary for the expressed opinions: > > [Iteration 1] > > Sol1: +0 Gabi, +0 Jean (with modifications) > Sol2: +1 Caty, +0 Gabi, +0 Jean (with modifications) > Sol3: +1 Vincent, +1 Jean, +1 Gabi (with modifications) > Sol4: +0 Caty, +0 Jean > > [Iteration 2] > > Sol 2.1.3: +1 Caty > > > > On Fri, Jul 3, 2015 at 8:04 PM, Ecaterina Moraru (Valica) < > [email protected] > > wrote: > > > Hi, > > > > Thanks for all the feedback received. > > > > Since the received feedback favored Sol 2 and Sol 3, I've iterated a bit > > on them, see > > > http://design.xwiki.org/xwiki/bin/view/Proposal/NestedLivetable#HIteration2 > > > > Thanks, > > Caty > > > > > > > > On Fri, Jul 3, 2015 at 6:48 PM, [email protected] <[email protected]> > > wrote: > > > >> Hi again, > >> > >> I’ve thought more about it (and discussed it with Jean Simard) and > here’s > >> my new take: > >> > >> - There are different use cases: > >> ** The case of the AllDocs page where it’s important to display the > >> location since it’s used for navigation > >> ** The case of an App that creates only terminal pages. In this case we > >> shouldn’t display the location since it’s not needed. > >> ** The case of an App that allows to create non terminal pages (e.g. A > >> Project Application which allows you to create projects inside projects > >> inside projects, etc). In this case it’s useful to be able to display > the > >> location *relative* to the top level Space in which the App is located. > >> > >> - Thus it’s important to be able to configure how you wish to display an > >> xproperty of type “Document Reference”. Thus, ideally, we need to find a > >> way to pass some configuration data to the “Document Reference” property > >> Displayer and to configure that in the livetable macro. > >> > >> - The alternative, which is fine with me, is to have a computed > >> “Location” xproperty (which is computed from a “Document Reference” > >> xproperty) and the declaration of the “Location” xproperty metadata > would > >> define how it’s displayed (full reference, reference relative to a given > >> reference, etc), and the Displayer for “Location” would use that. This > >> means always using a “Location” column in LT when you wish to display > the > >> path. > >> > >> This last solution is probably the simplest and should solve the 3 UCs > >> I’ve listed above. > >> > >> WDYT? > >> > >> Thanks > >> -Vincent > >> > >> > >> On 2 Jul 2015 at 00:33:23, [email protected] ([email protected] > (mailto: > >> [email protected])) wrote: > >> > >> > Hi Caty, > >> > > >> > Thanks for the design page! > >> > > >> > Some remarks: > >> > > >> > * For Sol2 do you mean you just display the parent and not the full > >> hierarchy? So for example for A.B.C.D.WebHome you’d display parent = D > >> only? Thus sol2 wouldn’t allow to understand the location of a page. > >> > * My preference goes to Sol3 with the full hierarchy displayed and > with > >> a filter allowing to search in either the page name/title and/or the > >> hierarchy. It should solve the 3 listed UCs > >> > * We could imagine variations of sol3 depending on the use case by > >> showing/hiding the hierarchy and if hidden then it would be shown on > hover > >> (but the filter should allow to filter on it) > >> > * I think we need to work on the filter UI so that it allows to search > >> only on the name+title or only on the hierarchy or on both. It could be > 2 > >> filter fields or one field that searches on all with options (as in > google > >> search or solr search) to specify to search only in the title, only in > the > >> page name, only in the hierarchy: -title:xxx, +title:xxx, +name=xxx, > >> -name:xxx, +location:xxx, -location:xxx), etc. > >> > * If we display page titles, we’ll need to implement that famous title > >> cache we’ve been wanting to have for such a long time now… ;) > >> http://jira.xwiki.org/browse/XWIKI-1253 > >> > > >> > Thanks > >> > -Vincent > >> > > >> > > >> > On 2 Jul 2015 at 00:04:36, Ecaterina Moraru (Valica) ( > [email protected] > >> (mailto:[email protected])) wrote: > >> > > >> > > Hi, > >> > > > >> > > I've added some ideas on how to display 'Space' column in the > AllDocs > >> page: > >> > > http://design.xwiki.org/xwiki/bin/view/Proposal/NestedLivetable > >> > > > >> > > Let me know what you think and if there are other ideas. > >> > > > >> > > Thanks, > >> > > Caty > >> > >> _______________________________________________ > >> devs mailing list > >> [email protected] > >> http://lists.xwiki.org/mailman/listinfo/devs > >> > > > > > _______________________________________________ > 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 _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
