[xwiki-devs] [Brainstorming] Should we stop setting the parents when creating new pages + mandating parents in the build
4 Aug
2015
4 Aug
'15
11:35 a.m.
Hi devs,
When we create a new page through Add > Page (for example) we are still setting the
parent ATM, even though it’s not used by default in the breadcrumb or elswhere.
Question 1: do we still want to set it or should we stop doing that
when core.hierarchyMode=reference?
Question 2: do we still want to enforce having a parent set in our build?
My preference would to not change any in the 7.x cycle (i.e. keep setting the parent when
creating new pages and keep enforcing parents in the build). The rationale is that:
* 7.x is a transition cycle for Nested Spaces/Documents so it’s good to observe how users
are using them
* We should not use Nested Documents in our apps in the 7.x cycle as this would cause
potential breakages in existing extensions since we would change location of wiki pages.
IMO we need to implement aliases before we start doing so, but not before 8.x.
WDYT?
Thanks
-Vincent
4 Aug
4 Aug
12:19 p.m.
On Tue, Aug 4, 2015 at 11:35 AM, vincent(a)massol.net <vincent(a)massol.net> wrote:
Hi devs,
When we create a new page through Add > Page (for example) we are still setting the
parent ATM, even though it’s not used by default in the breadcrumb or elswhere.
Question 1: do we still want to set it or should we stop doing that when
core.hierarchyMode=reference?
Question 2: do we still want to enforce having a parent set in our build?
My preference would to not change any in the 7.x cycle (i.e. keep setting the parent when
creating new pages and keep enforcing parents in the build). The rationale is that:
* 7.x is a transition cycle for Nested Spaces/Documents so it’s good to observe how users
are using them
* We should not use Nested Documents in our apps in the 7.x cycle as this would cause
potential breakages in existing extensions since we would change location of wiki pages.
IMO we need to implement aliases before we start doing so, but not before 8.x.
WDYT?
* 1: yes, lets move the discussion about that when working on 8.x (and
even I think I will vote for keeping the behavior as long as the
concept of parent exist in the API)
* 2: no, there is not reason to force it anymore IMO. It's not like
having a document without a parent was a technical issue anyway.
Thanks
-Vincent
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
--
Thomas Mortagne
6 Aug
6 Aug
2:36 p.m.
Hi,
On Tue, Aug 4, 2015 at 12:35 PM, vincent(a)massol.net <vincent(a)massol.net wrote:
My preference would be to not enforce it anymore, however, for the same
reasons as above, you might have to... otherwise the
core.hierarchyMode=parent option will be misleading and might not behave as
expected.
> My preference would to not change any in
the 7.x cycle (i.e. keep setting
> the parent when creating new pages and keep enforcing parents in the
> build). The rationale is that:
> * 7.x is a transition cycle for Nested Spaces/Documents so it’s good to
> observe how users are using them
> * We should not use Nested Documents in our apps in the 7.x cycle as this
> would cause potential breakages in existing extensions since we would
> change location of wiki pages. IMO we need to implement aliases before we
> start doing so, but not before 8.x.
> WDYT?
+1 for handling (re-discussing) it in 8.x
Thanks,
Eduard
> Thanks
> -Vincent
> _______________________________________________
> devs mailing list
> devs(a)xwiki.org
> http://lists.xwiki.org/mailman/listinfo/devs
Hi devs,
When we create a new page through Add > Page (for example) we are still
setting the parent ATM, even though it’s not used by default in the
breadcrumb or elswhere.
Question 1: do we still want to set it or should we stop doing that
when core.hierarchyMode=reference?
Well, if we don`t keep setting parents in the create step and still support
the parent-child hierarcy option, this option becomes very misleading. What
I mean is that if you go some time with core.hierarchyMode=reference and at
some point you change it to core.hierarchyMode=parent (or whatever the
value is called), you will end up with tons of orphan documents.
Question 2: do we still want to enforce having a parent set in our build?
10 Aug
10 Aug
10:54 a.m.
I agree with Eddy, we should let everything as it is just in case
`core.hierarchyMode=parent` is used by the user. It's not as if it was
costly to keep it.
Thanks,
2015-08-06 14:36 GMT+02:00 Eduard Moraru <enygma2002(a)gmail.com>om>:
Hi,
On Tue, Aug 4, 2015 at 12:35 PM, vincent(a)massol.net <vincent(a)massol.net>
wrote:
My preference would be to not enforce it anymore, however, for the same
reasons as above, you might have to... otherwise the
core.hierarchyMode=parent option will be misleading and might not behave as
expected.
> My preference would to not change any
in the 7.x cycle (i.e. keep setting
> the parent when creating new pages and keep enforcing parents in the
> build). The rationale is that:
> * 7.x is a transition cycle for Nested Spaces/Documents so it’s good to
> observe how users are using them
> * We should not use Nested Documents in our apps in the 7.x cycle as this
> would cause potential breakages in existing extensions since we would
> change location of wiki pages. IMO we need to implement aliases before we
> start doing so, but not before 8.x.
> WDYT?
+1 for handling (re-discussing) it in 8.x
Thanks,
Eduard
> Thanks
> -Vincent
> _______________________________________________
> devs mailing list
> devs(a)xwiki.org
> http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
--
Guillaume Delhumeau (gdelhumeau(a)xwiki.com)
Research & Development Engineer at XWiki SAS
Committer on the XWiki.org project
Hi devs,
When we create a new page through Add > Page (for example) we are still
setting the parent ATM, even though it’s not used by default in the
breadcrumb or elswhere.
Question 1: do we still want to set it or should we stop doing that
when core.hierarchyMode=reference?
Well, if we don`t keep setting parents in the create step and still support
the parent-child hierarcy option, this option becomes very misleading. What
I mean is that if you go some time with core.hierarchyMode=reference and at
some point you change it to core.hierarchyMode=parent (or whatever the
value is called), you will end up with tons of orphan documents.
Question 2: do we still want to enforce having a parent set in our build?
19 Aug
19 Aug
10:03 a.m.
+1 to keep setting/enforcing the parent for 7.x
Thanks,
Marius
On Tue, Aug 4, 2015 at 12:35 PM, vincent(a)massol.net <vincent(a)massol.net> wrote:
Hi devs,
When we create a new page through Add > Page (for example) we are still setting the
parent ATM, even though it’s not used by default in the breadcrumb or elswhere.
Question 1: do we still want to set it or should we stop doing that when
core.hierarchyMode=reference?
Question 2: do we still want to enforce having a parent set in our build?
My preference would to not change any in the 7.x cycle (i.e. keep setting the parent when
creating new pages and keep enforcing parents in the build). The rationale is that:
* 7.x is a transition cycle for Nested Spaces/Documents so it’s good to observe how users
are using them
* We should not use Nested Documents in our apps in the 7.x cycle as this would cause
potential breakages in existing extensions since we would change location of wiki pages.
IMO we need to implement aliases before we start doing so, but not before 8.x.
WDYT?
Thanks
-Vincent
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
3316
days inactive
3331
days old
4 comments
5 participants
participants (5)
-
Eduard Moraru -
Guillaume "Louis-Marie" Delhumeau -
Marius Dumitru Florea -
Thomas Mortagne -
vincent＠massol.net