[xwiki-devs] [Proposal] Wiki macros improvement ideas
Hi, Wiki macros currently require programming rights and thus are limited and in addition cannot be created in subwikis by the majority of users. Since I've now almost finished implementing component isolation I'd like to agree on what we want for wiki macros. Proposal: * Modify the wiki macro class to add a "Visibility" field with 2 values: - visible only in the current wiki - visible to everyone * Visible to everyone will require admin rights * Make the macro available to a user only if that user has view rights to the wiki macro page. This is to allow making a wiki macro private (when testing for example). It also allows making a macro visible only to a given group of users. Note: I considered having a "visible only to the current user" value for the Visibility field but I don't think it means much since if someone else edit the page and saves it, then suddenly the macro becomes visible only to that person... WDYT? Thanks -Vincent
On Sep 14, 2009, at 10:03 AM, Vincent Massol wrote:
Hi,
Wiki macros currently require programming rights and thus are limited and in addition cannot be created in subwikis by the majority of users.
Since I've now almost finished implementing component isolation I'd like to agree on what we want for wiki macros.
Proposal: * Modify the wiki macro class to add a "Visibility" field with 2 values: - visible only in the current wiki - visible to everyone * Visible to everyone will require admin rights * Make the macro available to a user only if that user has view rights to the wiki macro page. This is to allow making a wiki macro private (when testing for example). It also allows making a macro visible only to a given group of users.
hmm... this one might be hard to implement. I need to think a bit more about it. The pb is that when you look up a component you don't have a way to know it's a wiki macro and thus get the macro document and check if it's viewable by the current user... -Vincent
Note: I considered having a "visible only to the current user" value for the Visibility field but I don't think it means much since if someone else edit the page and saves it, then suddenly the macro becomes visible only to that person...
WDYT?
Thanks -Vincent
On Sep 14, 2009, at 10:07 AM, Vincent Massol wrote:
On Sep 14, 2009, at 10:03 AM, Vincent Massol wrote:
Hi,
Wiki macros currently require programming rights and thus are limited and in addition cannot be created in subwikis by the majority of users.
Since I've now almost finished implementing component isolation I'd like to agree on what we want for wiki macros.
Proposal: * Modify the wiki macro class to add a "Visibility" field with 2 values: - visible only in the current wiki - visible to everyone * Visible to everyone will require admin rights * Make the macro available to a user only if that user has view rights to the wiki macro page. This is to allow making a wiki macro private (when testing for example). It also allows making a macro visible only to a given group of users.
hmm... this one might be hard to implement. I need to think a bit more about it. The pb is that when you look up a component you don't have a way to know it's a wiki macro and thus get the macro document and check if it's viewable by the current user...
Ok after more thoughts I think I can do it quite easily. Thanks -Vincent
Note: I considered having a "visible only to the current user" value for the Visibility field but I don't think it means much since if someone else edit the page and saves it, then suddenly the macro becomes visible only to that person...
WDYT?
Thanks -Vincent
On Sep 14, 2009, at 10:03 AM, Vincent Massol wrote:
Hi,
Wiki macros currently require programming rights and thus are limited and in addition cannot be created in subwikis by the majority of users.
Since I've now almost finished implementing component isolation I'd like to agree on what we want for wiki macros.
Proposal: * Modify the wiki macro class to add a "Visibility" field with 2 values: - visible only in the current wiki - visible to everyone * Visible to everyone will require admin rights * Make the macro available to a user only if that user has view rights to the wiki macro page. This is to allow making a wiki macro private (when testing for example). It also allows making a macro visible only to a given group of users.
Note: I considered having a "visible only to the current user" value for the Visibility field but I don't think it means much since if someone else edit the page and saves it, then suddenly the macro becomes visible only to that person...
WDYT?
Ok after a discussion with Thomas we think it's better to do something simple for now: * Modify the wiki macro class to add a "Visibility" field with 3 values: - "Visible to current author". This is to allow to have some macro that only you can see as avail macro while you test it for example. - "Visible in current wiki". Default value. - "Visible to all wikis". Requires admin rights on the main wiki. It won't cover all use cases but it should be enough for now and we can refine it later. The permission stuff is interesting but too complex for now. WDYT? Thanks -Vincent
HI
Ok after a discussion with Thomas we think it's better to do something simple for now: * Modify the wiki macro class to add a "Visibility" field with 3 values: - "Visible to current author". This is to allow to have some macro that only you can see as avail macro while you test it for example. - "Visible in current wiki". Default value. - "Visible to all wikis". Requires admin rights on the main wiki.
+1 - Asiri
On Mon, Sep 14, 2009 at 12:11 PM, Vincent Massol <[email protected]> wrote:
On Sep 14, 2009, at 10:03 AM, Vincent Massol wrote:
Hi,
Wiki macros currently require programming rights and thus are limited and in addition cannot be created in subwikis by the majority of users.
Since I've now almost finished implementing component isolation I'd like to agree on what we want for wiki macros.
Proposal: * Modify the wiki macro class to add a "Visibility" field with 2 values: - visible only in the current wiki - visible to everyone * Visible to everyone will require admin rights * Make the macro available to a user only if that user has view rights to the wiki macro page. This is to allow making a wiki macro private (when testing for example). It also allows making a macro visible only to a given group of users.
Note: I considered having a "visible only to the current user" value for the Visibility field but I don't think it means much since if someone else edit the page and saves it, then suddenly the macro becomes visible only to that person...
WDYT?
Ok after a discussion with Thomas we think it's better to do something simple for now: * Modify the wiki macro class to add a "Visibility" field with 3 values: - "Visible to current author". This is to allow to have some macro that only you can see as avail macro while you test it for example. - "Visible in current wiki". Default value. - "Visible to all wikis". Requires admin rights on the main wiki.
It won't cover all use cases but it should be enough for now and we can refine it later. The permission stuff is interesting but too complex for now.
WDYT?
Some more information on the implementation I'm doing (and one question): * When visibility = current user, if the user is logged on the main wiki then he'll have access to macros registered with "current user" on all subwikis. * When visibility = current wiki, what rights do we require for registering the macro? Two options: Admin rights or simply Edit rights (on the wiki macro document)? I think edit rights should be enough but I need your opinion. * When visibility = global, I'll require programming rights which is the closest we have at the moment to "wiki farm rights". Let me know if you see any problem with the above. Thanks -Vincent
participants (2)
-
Asiri Rathnayake -
Vincent Massol