Re: [xwiki-devs] [Iteration][UX] Nested: Livetable

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, vincent(a)massol.net (vincent(a)massol.net(mailto: vincent(a)massol.net)) wrote: 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. a filter allowing to search in either the page name/title and/or the hierarchy. It should solve the 3 listed UCs showing/hiding the hierarchy and if hidden then it would be shown on hover (but the filter should allow to filter on it) 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. cache we’ve been wanting to have for such a long time now… ;) http://jira.xwiki.org/browse/XWIKI-1253 (mailto:valicac@gmail.com)) wrote: page: _______________________________________________ devs mailing list devs(a)xwiki.org http://lists.xwiki.org/mailman/listinfo/devs