20 Sep
2016
20 Sep
'16
4:41 p.m.
Note that it’s very very hard ATM to write an app that will work when installed in any
space. Some gotchas:
* xobject references in wiki pages are absolute
* class sheet bindings are absolute
Before we can do this we need to work on inventing the new syntax for relative references,
see
http://design.xwiki.org/xwiki/bin/view/Proposal/DeprecatingSpaceAndSpaceRef…
For example we need to be able to write in a class sheet binding xobject: .XXXSheet (or
..SomePage.XXXSheet).
And we need to save xobject references as relative in the DB.
Basically we need to have everything stored relative in the DB…
Thanks
-Vincent
On 20 Sep 2016, at 13:41, Vincent Massol
<vincent(a)massol.net> wrote:
Hi devs,
Now that we support Nested Pages, I think it would be nice if we had the option to
install an Extension in a space (i.e. a page from a user POV).
Technically at the Component Manager level, we can already register a component at the
farm level (root), in the current wiki, in the current space or for the current user.
We already have the option to install an extension in a wiki and it would be nice to
extend that concept to a space.
We also already have the concept of space admin UI.
Of course the app should tell whether it supports being installed in several spaces or
not.
The use case is simply to be able to install several times a given application.
From a UI perspective, when you go the the space admin UI (called the Page Administration
for users), you’d have the option to list installed extensions and install new extensions
(basically what you currently have at the wiki level).
Now, the same should be doable also for importing XARs, i.e. also have an Import option
in the Page Administration UI.
WDYT?
How complex would it be to do that?
Do we already have a JIRA for this (couldn’t find one)?
Thanks
-Vincent