[xwiki-devs] [Brainstorming] Add Export UI for space-level + homogenisation
Hi devs, <bad idea but kept for the sake of the discussion> Now that I’ve implemented http://jira.xwiki.org/browse/XWIKI-11337 I was wondering if it would be a good idea to have 2 menu entries (they would be visible only for admins by I think): - Export Space (in the Space menu of the navbar) - Export Wiki (in the Wiki menu of the navbar) When you click on them they would open a popup similar to the one that opens when you click on Export Page but with 2 options only ATM: XAR and HTML (since these are the 2 that support exporting at space and wiki levels). Now when the multipage export UI is ready, click on any Export (page level, space level or wiki level) would open that UI with a preselection (current page, current space or current wiki selected). We would also need to decide what to do with the Export screen of the Admin UI: Would it be dropped in favor of the “Export Wiki” menu action? </bad idea but kept for the sake of the discussion> <more thinking happened here… :)/> <better idea> More generally speaking we need to think about Admin actions and where we want them. I don’t think it’s a good idea to start putting more and more admin actions in menus. Actually what we should probably do is generalize the concept of the Admin UI at all levels: Page level, Space level and Wiki level. Thus I think I’d prefer the following: - Add an Export admin UI screen at the space level for exporting only a space as XAR - Introduce an admin UI screen at page level too and start moving features in there. I can think of at least 2: Export Page, Page level rights </better idea> WDYT? Thanks -Vincent
One thing I've been hinting about a few times and that I have never seen yet and would be really cool for just about any XWiki installation with a development team would be to have a configurable set servers to which you could export a page or space (and maybe even a list of pages). The scenarios I see there is that you start developing a function, then want to bring up to beta or production. Alternatively, you start to debug an issue and you need to transfer a few potentially problematic data to dev to study it. This would, of course, require admin rights both sides. I am not sure if it's doable as a single shot, using local browser storage, but that would be the coolest. paul On 28 oct. 2014, at 09:26, "vincent@massol.net" <vincent@massol.net> wrote:
Hi devs,
<bad idea but kept for the sake of the discussion>
Now that I’ve implemented http://jira.xwiki.org/browse/XWIKI-11337 I was wondering if it would be a good idea to have 2 menu entries (they would be visible only for admins by I think): - Export Space (in the Space menu of the navbar) - Export Wiki (in the Wiki menu of the navbar)
When you click on them they would open a popup similar to the one that opens when you click on Export Page but with 2 options only ATM: XAR and HTML (since these are the 2 that support exporting at space and wiki levels).
Now when the multipage export UI is ready, click on any Export (page level, space level or wiki level) would open that UI with a preselection (current page, current space or current wiki selected).
We would also need to decide what to do with the Export screen of the Admin UI: Would it be dropped in favor of the “Export Wiki” menu action?
</bad idea but kept for the sake of the discussion>
<more thinking happened here… :)/>
<better idea>
More generally speaking we need to think about Admin actions and where we want them. I don’t think it’s a good idea to start putting more and more admin actions in menus. Actually what we should probably do is generalize the concept of the Admin UI at all levels: Page level, Space level and Wiki level.
Thus I think I’d prefer the following: - Add an Export admin UI screen at the space level for exporting only a space as XAR - Introduce an admin UI screen at page level too and start moving features in there. I can think of at least 2: Export Page, Page level rights
</better idea>
WDYT?
Thanks -Vincent
_______________________________________________ devs mailing list devs@xwiki.org http://lists.xwiki.org/mailman/listinfo/devs
On 28 Oct 2014 at 11:00:03, Paul Libbrecht (paul@hoplahup.net(mailto:paul@hoplahup.net)) wrote:
One thing I've been hinting about a few times and that I have never seen yet and would be really cool for just about any XWiki installation with a development team would be to have a configurable set servers to which you could export a page or space (and maybe even a list of pages).
The scenarios I see there is that you start developing a function, then want to bring up to beta or production. Alternatively, you start to debug an issue and you need to transfer a few potentially problematic data to dev to study it.
This would, of course, require admin rights both sides. I am not sure if it's doable as a single shot, using local browser storage, but that would be the coolest.
This is a bit hijacking the thread I started since it’s different topic altogether… :) Regarding your use case, I know Thomas wanted to have that too, using the Filter Module, see: http://extensions.xwiki.org/xwiki/bin/view/Extension/Filter+Module Specifically I think that’s the intent of the "XWiki instance input and output (xwiki+instance/1.1)” Filter. It doesn’t have any documentation ATM, not sure why. It’s probably missing a UI ATM but I guess it’s scriptable for now. Thomas would know more. Thanks -Vincent
paul
On 28 oct. 2014, at 09:26, "vincent@massol.net" wrote:
Hi devs,
Now that I’ve implemented http://jira.xwiki.org/browse/XWIKI-11337 I was wondering if it would be a good idea to have 2 menu entries (they would be visible only for admins by I think): - Export Space (in the Space menu of the navbar) - Export Wiki (in the Wiki menu of the navbar)
When you click on them they would open a popup similar to the one that opens when you click on Export Page but with 2 options only ATM: XAR and HTML (since these are the 2 that support exporting at space and wiki levels).
Now when the multipage export UI is ready, click on any Export (page level, space level or wiki level) would open that UI with a preselection (current page, current space or current wiki selected).
We would also need to decide what to do with the Export screen of the Admin UI: Would it be dropped in favor of the “Export Wiki” menu action?
More generally speaking we need to think about Admin actions and where we want them. I don’t think it’s a good idea to start putting more and more admin actions in menus. Actually what we should probably do is generalize the concept of the Admin UI at all levels: Page level, Space level and Wiki level.
Thus I think I’d prefer the following: - Add an Export admin UI screen at the space level for exporting only a space as XAR - Introduce an admin UI screen at page level too and start moving features in there. I can think of at least 2: Export Page, Page level rights
WDYT?
Thanks -Vincent
On Tue, Nov 4, 2014 at 6:29 PM, vincent@massol.net <vincent@massol.net> wrote:
On 28 Oct 2014 at 11:00:03, Paul Libbrecht (paul@hoplahup.net(mailto:paul@hoplahup.net)) wrote:
One thing I've been hinting about a few times and that I have never seen yet and would be really cool for just about any XWiki installation with a development team would be to have a configurable set servers to which you could export a page or space (and maybe even a list of pages).
The scenarios I see there is that you start developing a function, then want to bring up to beta or production. Alternatively, you start to debug an issue and you need to transfer a few potentially problematic data to dev to study it.
This would, of course, require admin rights both sides. I am not sure if it's doable as a single shot, using local browser storage, but that would be the coolest.
This is a bit hijacking the thread I started since it’s different topic altogether… :)
Regarding your use case, I know Thomas wanted to have that too, using the Filter Module, see: http://extensions.xwiki.org/xwiki/bin/view/Extension/Filter+Module
Specifically I think that’s the intent of the "XWiki instance input and output (xwiki+instance/1.1)” Filter. It doesn’t have any documentation ATM, not sure why. It’s probably missing a UI ATM but I guess it’s scriptable for now. Thomas would know more.
No it's not, XWiki instance is the current XWiki instance, i.e. the database and other places where you have data in the current instance so nothing to do with a remote instance. In other word it's what you use for what we usually call "import" and "export". A module that would be used to pull or push documents on a remote instance would probably be something like "XWiki REST input and output" (the module providing input/output documents through the XWiki REST interface). That would be the clean way but you can get the same result by using other hacks with the existing modules. For example you can directly import documents from a remote instance using as output the current XWiki Instance and in input the XAR module to which you give a XAR export URL from the other XWiki instance so for example something like http://www.xwiki.org/xwiki/bin/export/ReleaseNotes/ReleaseNotesXWiki523?form... to import http://www.xwiki.org/xwiki/bin/export/ReleaseNotes/ReleaseNotesXWiki523 page in your wiki.
Thanks -Vincent
paul
On 28 oct. 2014, at 09:26, "vincent@massol.net" wrote:
Hi devs,
Now that I’ve implemented http://jira.xwiki.org/browse/XWIKI-11337 I was wondering if it would be a good idea to have 2 menu entries (they would be visible only for admins by I think): - Export Space (in the Space menu of the navbar) - Export Wiki (in the Wiki menu of the navbar)
When you click on them they would open a popup similar to the one that opens when you click on Export Page but with 2 options only ATM: XAR and HTML (since these are the 2 that support exporting at space and wiki levels).
Now when the multipage export UI is ready, click on any Export (page level, space level or wiki level) would open that UI with a preselection (current page, current space or current wiki selected).
We would also need to decide what to do with the Export screen of the Admin UI: Would it be dropped in favor of the “Export Wiki” menu action?
More generally speaking we need to think about Admin actions and where we want them. I don’t think it’s a good idea to start putting more and more admin actions in menus. Actually what we should probably do is generalize the concept of the Admin UI at all levels: Page level, Space level and Wiki level.
Thus I think I’d prefer the following: - Add an Export admin UI screen at the space level for exporting only a space as XAR - Introduce an admin UI screen at page level too and start moving features in there. I can think of at least 2: Export Page, Page level rights
WDYT?
Thanks -Vincent
devs mailing list devs@xwiki.org http://lists.xwiki.org/mailman/listinfo/devs
-- Thomas Mortagne
participants (3)
-
Paul Libbrecht -
Thomas Mortagne -
vincent＠massol.net