On Wed, Jul 1, 2015 at 11:41 AM, Marius Dumitru Florea < [email protected]> wrote:
> On Fri, Jun 26, 2015 at 7:48 PM, Ecaterina Moraru (Valica) > <[email protected]> wrote: > > Hi, > > > > Some conclusions with the current votes: > > > > Q0. **Nested Spaces in model** > >> > >> No matter the UI decisions we still need to take, we are implementing > >> Nested Spaces for 7.2 roadmap. The future is still uncertain regarding > >> changing the model to accommodate Nested Documents, since we can > simulate > >> ND using NS. > >> > > > > 7 x (+1) 'Already decided' > > > > > >> > >> Q1. **NS vs ND in the UI** > >> > >> Q1.1 The majority agreed that since the final purpose are ND, we should > >> display ND in the UI, since it simplifies the mental model of the user. > >> This implies removing the Space concept from the UI. > >> > > > > 7 x (+1) 'Already decided' > > > > > >> Q1.1.1 A consequence is hiding the 'WebHome' name in the UI. > >> > > > > 6 x (+1) , 1 x (+0) 'Already decided' > > > > > >> > >> Q1.2 Although the default should be ND, the question is if we want to > give > >> the option to display NS in the UI. This would be implemented as an > >> advanced and technical option. The main problem is that we might need to > >> provide UI alternatives for several components (menus, create step, > etc.) > >> > > > > 6 x (-0) -> so we will not give an additional option to display NS in the > > UI (see Terminal Pages) > > > > > >> > >> Q2. **Parent/Child** > >> > > > > Parent/Child deprecation is a bit more difficult to calculate, since the > > votes are mixed depending on the definition of 'deprecation', not clearly > > stated the vote or given partially votes. > > > > The conclusion is that in order not to confuse the user, we should > > deprecate the P/C concept. > > It will not be dropped from the DB (and will be available if someone > wants > > to create additional extensions to display it), but it will not be > > displayed by default in the UI, since breadcrumbs/trees will display the > ND. > > > > > >> > >> Q2.1 Deprecate the notion of Parent/Child. > >> Q2.1.1 Provide a migration to transform the relation into NS/ND. > Problem: > >> the old URLs[A] (bookmarks) are broken + the user is stuck with long > >> URLs[B] if he wants to keep the hierarchy. Additionally we might need to > >> provide an extension/configuration to transform into short URLs [B -> > C]. > >> > > Q2.1.2 Don't migrate: the parent/child hierarchy will be lost but the old > >> URLs[A] (bookmarks) will be kept. The user needs to use NS/ND to create > >> hierarchies. > >> > > > > The 'migration' got: > > 3 x (-1) > > 1 x (-0) > > 1 x (+1) > > > > Don't 'migrate' got: > > 2 x (+1) > > 2 x (+0) > > > > The general feeling is that we don't need to provide such a migration > > automatically. Script could be put into place (to transform P/C into ND), > > but this should be applied on a case by case scenario. > > > > Other needed script is in order to transform the existing pages from A/B > > into A/B/WebHome. > > > > > >> > >> Q2.2 Don't deprecate the notion of Parent/Child. > >> Q2.2.1 Provide a configuration in the Administration to switch the > >> breadcrumbs between displaying Parent/Child or NS/ND. We might need to > >> provide UI alternatives for several components (tree, breadcrumb > >> navigation, create, etc.) > >> > > > > Configuration between P/C and NS/ND: > > 4 x (-0) > > 1 x (+0) > > 1 x (+1) > > > > The general feeling is that this is not needed. There could be an option > > from UI/config to turn the P/C relation on, but it would be off by > default. > > > > Q3. **Terminal Pages** > > > > Since we will have 'Terminal Pages' and 'Non Terminal Pages', it was > > proposed to have an option in the Profile or associate this behavior > with > > the Advanced user role, in order to display a checkbox ('Create a page > > without children') in the 'Create Page' step. > > > > Additional, for the users that have this checkbox selected, if they land > on > > a non existing page, instead of being transferred directly into Edit > mode, > > when they click 'You can edit this page to create it', they will be > > directed to the 'Create Page' step, in order to be able to select the > > 'Create a page without children' checkbox. (Use case mentioned by > Vincent). > > > > > Terminal and Non Terminal pages will be displayed in the Tree, by having > > associated an expand icon or not. > > This is not enough / right. There's a difference between pages that > don't have child documents (currently) and pages that can't have child > documents (because they don't support it). > > Currently I see 2 solutions: - Instead of '+' symbol we could have like a new icon, a terminal icon, something like 'ꜜ' in order to differentiate between the 2 types; - Or for non-terminal pages, we can display the '+' icon and when expanding have an 'Add child' link; > > > > Maybe there are other ideas regarding 'Terminal Pages'? > > > > Please let me know if I summarized correctly and if others want to cast > > additional votes. > > > > 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 > _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
