Re: [xwiki-devs] [Iteration][UX] Nested: Page Actions

Hi, = Create +1 for TIL [1] +1 for 2.B - based on TL, with the mention that the unexpanded view is the one above, i.e. [1], and, when expanding you get [2] which can then be further expanded in an advanced mode to [3]. In other words, reverse in 2.B the position of the breadcrumbs with the tree selector so that, by default, you only see the breadcrumbs and can then edit (see the tree selector) and finally edit advanced (see the reference editor where you can input "holes" in the parent reference). = Delete I gues Delete 3: Accordion would be the nicest, allowing both to see and to select all the children/backlinks to affect (IMO we should not complicate things with individual children/backlinks selection), but be aware that we will have the same issue that we are currently discussing about displaying documents in the livetable, in a separate thread. The current document being deleted could be a top level document and underneath it there could be 2-3-10-20 levels of hierarchy which *will* introduce scalability issues. Given the above, I believe either "Delete 2: Link" (the extra highlighting would not hurt IMO, since it's a destructive operation) or "Delete 1+2: Count + Link" would be a better candidate. I also see an "pencil" (edit) icon next to the source section. I am not sure if we should allow changing the page to be delete in this view, since we are already on the delete action of a specific page. If we want a dedicated page for the delete operation (or other operations as well) then we should discuss it an do it as such, but mixing the 2 is not a good idea IMO. = Move/Rename/Copy Regarding the target field, we should reuse whatever UI control we decide to use for the create operation, to preserve consistency and minimise duplication. Mentioning it since I do not see this reflected in the proposals. IMO, it should be an implementation detail if we reuse the code in the background for these 3 operations, but the user should be presented with at least 2 (Move/Rename = Relocate? + Copy) or even 3 (Move + Rename + Copy) operations, so that his task is clear. = General note After going through this, my impression is that we risk cluttering the UI with all the possible options around the target field (tree + "holes" in references + ID + etc.) and we should be very careful to keep this to a minimum. Thanks, Eduard ---------- [1] http://design.xwiki.org/xwiki/bin/download/Proposal/NestedCreate/createTitl… [2] http://design.xwiki.org/xwiki/bin/download/Proposal/NestedTreeDisplayer/Tre… [3] http://design.xwiki.org/xwiki/bin/download/Proposal/NestedTreeDisplayer/Tre… On Thu, Aug 6, 2015 at 11:17 AM, Gabriela Smeria <gabriela.smeria(a)xwiki.com> wrote: