23 Jun
2015
23 Jun
'15
6:13 p.m.
On Tue, Jun 23, 2015 at 5:43 PM, Ecaterina Moraru (Valica)
<valicac(a)gmail.com> wrote:
Hi devs,
So after discussing the topic of Nested in several mails, we need to reach
a conclusion in order to start implementing.
There are several open questions that I will summarize. Please cast your
votes in order to advance on some topics and maybe discover what we still
need to agree on.
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.
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.
Q1.1.1 A consequence is hiding the 'WebHome' name in the UI.
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.)
Q2. **Parent/Child**
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.
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.)
IMO the best is to do 2.2 whatever the long term goal since it will
make migrations much easier. It does not prevent us from discussing
again 2.1.x in the future but we already have lots of changes planned
so lets give us some time before dealing with removing something like
this (if that happen any time).
Please cast your votes / add comments.
Thank you,
Caty
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
--
Thomas Mortagne