Re: [xwiki-devs] [Proposal] Switch to USER for the default visiblity for translations + extend to all component-based pages
BTW I’ve noticed that the documentation is missing ONDEMAND + explanations about required permissions at http://extensions.xwiki.org/xwiki/bin/view/Extension/Localization/#HRegisterawikitranslation Thanks -Vincent > On 9 Feb 2018, at 21:49, Vincent Massol wrote: > > Yes I had missed it. I wanted to implement it but first wanted to make sure > we agreed before doing anything, hence this email. > > I really disagree about using ONDEMAND as the default since it’s an important > usability regression as it wouldn’t work OOB and the translations are not > going to be applied and do anything useful. > > Thanks > -Vincent > >> On 9 Feb 2018, at 19:42, Thomas Mortagne wrote: >> >> Looks like you missed https://jira.xwiki.org/browse/XWIKI-15013. >> >> IMO the safest is more ON DEMAND (which is a concept that does not >> exist for macros). >> >> On Fri, Feb 9, 2018 at 6:15 PM, Vincent Massol wrote: >>> Hi, >>> >>> Right now we have: >>> >>> xclass.addStaticListField(TranslationDocumentModel.TRANSLATIONCLASS_PROP_SCOPE, >>> "Scope", >>> "GLOBAL|WIKI|USER|ON_DEMAND”); >>> >>> However for wiki macros for example we have: >>> >>> xclass.addStaticListField(MACRO_VISIBILITY_PROPERTY, "Macro visibility", 1, >>> false, >>> "Current User|Current Wiki|Global", ListClass.DISPLAYTYPE_SELECT, >>> PROPERTY_PIPE); >>> >>> The rationale is that it’s safe to use USER first to try out and then to >>> extend to Wiki or Global if it’s working fine. >>> >>> So I’d suggest to change the default visibility for wiki translations to >>> USER and more generally to do this for all component-based xobjects. >>> >>> WDYT? >>> >>> Thanks >>> -Vincent >>> >> >> >> >> -- >> Thomas Mortagne >
Re: [xwiki-devs] [XWiki Day] BFD#165
Results: http://www.xwiki.org/xwiki/bin/view/Blog/Bug%20Fixing%20Day%20165. Thanks, Alex On Thu, Feb 8, 2018 at 9:04 AM, Alex Cotiugă wrote: > Hello devs, > > This Thursday is BFD#165: > http://dev.xwiki.org/xwiki/bin/view/Community/XWikiDays#HBugfixingdays > > Our current status is: > * -95 bugs over 365 days (1 year) > * -67 bugs over 500 days (between 1 and 2 years) > * -281 bugs over 1600 days (4.3 years) > * -685 bugs since the beginning of XWiki > > See https://jira.xwiki.org/secure/Dashboard.jspa?selectPageId=10352 > > > Here's the BFD#165 dashboard to follow the progress during the day: > https://jira.xwiki.org/secure/Dashboard.jspa?selectPageId=13949 > > Happy Bug Fixing Day, > Alex >
Re: [xwiki-devs] [Proposal] Switch to USER for the default visiblity for translations + extend to all component-based pages
Yes I had missed it. I wanted to implement it but first wanted to make sure we agreed before doing anything, hence this email. I really disagree about using ONDEMAND as the default since it’s an important usability regression as it wouldn’t work OOB and the translations are not going to be applied and do anything useful. Thanks -Vincent > On 9 Feb 2018, at 19:42, Thomas Mortagne wrote: > > Looks like you missed https://jira.xwiki.org/browse/XWIKI-15013. > > IMO the safest is more ON DEMAND (which is a concept that does not > exist for macros). > > On Fri, Feb 9, 2018 at 6:15 PM, Vincent Massol wrote: >> Hi, >> >> Right now we have: >> >> xclass.addStaticListField(TranslationDocumentModel.TRANSLATIONCLASS_PROP_SCOPE, >> "Scope", >>"GLOBAL|WIKI|USER|ON_DEMAND”); >> >> However for wiki macros for example we have: >> >> xclass.addStaticListField(MACRO_VISIBILITY_PROPERTY, "Macro visibility", 1, >> false, >>"Current User|Current Wiki|Global", ListClass.DISPLAYTYPE_SELECT, >> PROPERTY_PIPE); >> >> The rationale is that it’s safe to use USER first to try out and then to >> extend to Wiki or Global if it’s working fine. >> >> So I’d suggest to change the default visibility for wiki translations to >> USER and more generally to do this for all component-based xobjects. >> >> WDYT? >> >> Thanks >> -Vincent >> > > > > -- > Thomas Mortagne
Re: [xwiki-devs] [Proposal] Switch to USER for the default visiblity for translations + extend to all component-based pages
Looks like you missed https://jira.xwiki.org/browse/XWIKI-15013. IMO the safest is more ON DEMAND (which is a concept that does not exist for macros). On Fri, Feb 9, 2018 at 6:15 PM, Vincent Massol wrote: > Hi, > > Right now we have: > > xclass.addStaticListField(TranslationDocumentModel.TRANSLATIONCLASS_PROP_SCOPE, > "Scope", > "GLOBAL|WIKI|USER|ON_DEMAND”); > > However for wiki macros for example we have: > > xclass.addStaticListField(MACRO_VISIBILITY_PROPERTY, "Macro visibility", 1, > false, > "Current User|Current Wiki|Global", ListClass.DISPLAYTYPE_SELECT, > PROPERTY_PIPE); > > The rationale is that it’s safe to use USER first to try out and then to > extend to Wiki or Global if it’s working fine. > > So I’d suggest to change the default visibility for wiki translations to USER > and more generally to do this for all component-based xobjects. > > WDYT? > > Thanks > -Vincent > -- Thomas Mortagne
[xwiki-devs] [Proposal] Switch to USER for the default visiblity for translations + extend to all component-based pages
Hi, Right now we have: xclass.addStaticListField(TranslationDocumentModel.TRANSLATIONCLASS_PROP_SCOPE, "Scope", "GLOBAL|WIKI|USER|ON_DEMAND”); However for wiki macros for example we have: xclass.addStaticListField(MACRO_VISIBILITY_PROPERTY, "Macro visibility", 1, false, "Current User|Current Wiki|Global", ListClass.DISPLAYTYPE_SELECT, PROPERTY_PIPE); The rationale is that it’s safe to use USER first to try out and then to extend to Wiki or Global if it’s working fine. So I’d suggest to change the default visibility for wiki translations to USER and more generally to do this for all component-based xobjects. WDYT? Thanks -Vincent
Re: [xwiki-devs] [Usability] Create a dedicated Logo section in Administration
On Fri, Feb 9, 2018 at 4:56 PM, Alex Cotiugă wrote: > On Fri, Feb 9, 2018 at 4:36 PM, Ecaterina Moraru (Valica) < > vali...@gmail.com > > wrote: > > > On Fri, Feb 9, 2018 at 4:32 PM, Alex Cotiugă < > alexandru.coti...@xwiki.com> > > wrote: > > > > > +1 > > > > > > Adding more elements in the Themes section could make the `Themes` term > > to > > > loose its meaning for > > > what is configurable inside.As a user, I might be tempted to go first > in > > > the Presentation section for > > > changing something like Logo. > > > > > > Because Skin and Color Themes have logo functionalities and also because > > the Look & Feel section description mentions you can change the Logo from > > there, these were the criteria based on what I've chosen the section. > > > > > > > > > Then, would we consider to make logo > > > changeable as is the profile > > > picture (making the logo editable directly in header)? > > > > > > > I don't understand this question. > > I'm talking about showing the edit mark (pencil) to admin users right on > the logo in the header adn be able to edit it right there. > I attached a picture in the proposal: > http://design.xwiki.org/xwiki/bin/download/Proposal/ > IdeaChangeLogo/editableLogo.png > I think this way it would be even easier for users to change logo. Is not > about Admin section but about easing the way the logo is changed. > This was proposed by Olivier, some time ago. Still I would prefer that we leave the navigation functionality for the logo as the primary action. Admins change the logo just in the beginning. Is not a recurrent action, but one important that they expect to find in the Administration. > > > > > > > > > > > Thanks, > > > Alex > > > > > > On Fri, Feb 9, 2018 at 4:18 PM, Thomas Mortagne < > > thomas.morta...@xwiki.com > > > > > > > wrote: > > > > > > > +1 > > > > > > > > On Fri, Feb 9, 2018 at 2:34 PM, Ecaterina Moraru (Valica) > > > > wrote: > > > > > Hi, > > > > > > > > > > As some of you know, in January we had another session of usability > > > tests > > > > > performed. As a result of those tests, I have prioritized [1] some > > > issues > > > > > that we might want to improve in our next 10.x+ Roadmaps. > > > > > > > > > > One of the entries from that list is: "Create a dedicated Logo > > section > > > in > > > > > Administration". > > > > > > > > > > Although we made some improvements in this area, users still > struggle > > > to > > > > > find the Logo changing area (takes more than 3 minutes). Plus there > > is > > > a > > > > > lot of confusion between the Skin and ColorThemes overriding. > > > > > > > > > > This is a proposal to explicitly have a Logo section inside the > > Themes > > > > > section of Administration > > > > > http://design.xwiki.org/xwiki/bin/view/Proposal/IdeaChangeLo > > > > go#HSolution1-1 > > > > > > > > > > Let me know what you think, > > > > > Caty > > > > > > > > > > [1] > > > > > http://design.xwiki.org/xwiki/bin/view/Proposal/Usability/Ta > > > > sks5/Prioritization/ > > > > > > > > > > > > > > > > -- > > > > Thomas Mortagne > > > > > > > > > >
Re: [xwiki-devs] [Usability] Menus inside Administration
That would also mean that we remove the AWM dependency from the Menu application. On Fri, Feb 9, 2018 at 4:42 PM, Thomas Mortagne wrote: > +1 > > On the implementation detail side I hope the plan is not to add a > special #if for an extension and instead the extension itself will be > able to place itself there. > > On Fri, Feb 9, 2018 at 3:35 PM, Alex Cotiugă > wrote: > > Sounds like a good idea to me. If this would be a voting session, it > would > > be +1 from me. > > > > > > On Fri, Feb 9, 2018 at 4:25 PM, Ecaterina Moraru (Valica) < > vali...@gmail.com > >> wrote: > > > >> Hi, > >> > >> This mail is also part of the Usability priorititzation list [1] > >> > >> Admins expect to manage custom navigation from the Administration. > >> > >> This proposal integrates the Menu application in Administration, see > >> http://design.xwiki.org/xwiki/bin/view/Proposal/ > IdeaMenuInAdministration# > >> HProposals > >> > >> Let me know what you think, > >> Caty > >> > >> [1] > >> http://design.xwiki.org/xwiki/bin/view/Proposal/Usability/ > >> Tasks5/Prioritization/ > >> > > > > -- > Thomas Mortagne >
Re: [xwiki-devs] [Usability] Create a dedicated Logo section in Administration
On Fri, Feb 9, 2018 at 4:36 PM, Ecaterina Moraru (Valica) wrote: > On Fri, Feb 9, 2018 at 4:32 PM, Alex Cotiugă > wrote: > > > +1 > > > > Adding more elements in the Themes section could make the `Themes` term > to > > loose its meaning for > > what is configurable inside.As a user, I might be tempted to go first in > > the Presentation section for > > changing something like Logo. > > > Because Skin and Color Themes have logo functionalities and also because > the Look & Feel section description mentions you can change the Logo from > there, these were the criteria based on what I've chosen the section. > > > > > Then, would we consider to make logo > > changeable as is the profile > > picture (making the logo editable directly in header)? > > > > I don't understand this question. I'm talking about showing the edit mark (pencil) to admin users right on the logo in the header adn be able to edit it right there. I attached a picture in the proposal: http://design.xwiki.org/xwiki/bin/download/Proposal/IdeaChangeLogo/editableLogo.png I think this way it would be even easier for users to change logo. Is not about Admin section but about easing the way the logo is changed. > > > > > > Thanks, > > Alex > > > > On Fri, Feb 9, 2018 at 4:18 PM, Thomas Mortagne < > thomas.morta...@xwiki.com > > > > > wrote: > > > > > +1 > > > > > > On Fri, Feb 9, 2018 at 2:34 PM, Ecaterina Moraru (Valica) > > > wrote: > > > > Hi, > > > > > > > > As some of you know, in January we had another session of usability > > tests > > > > performed. As a result of those tests, I have prioritized [1] some > > issues > > > > that we might want to improve in our next 10.x+ Roadmaps. > > > > > > > > One of the entries from that list is: "Create a dedicated Logo > section > > in > > > > Administration". > > > > > > > > Although we made some improvements in this area, users still struggle > > to > > > > find the Logo changing area (takes more than 3 minutes). Plus there > is > > a > > > > lot of confusion between the Skin and ColorThemes overriding. > > > > > > > > This is a proposal to explicitly have a Logo section inside the > Themes > > > > section of Administration > > > > http://design.xwiki.org/xwiki/bin/view/Proposal/IdeaChangeLo > > > go#HSolution1-1 > > > > > > > > Let me know what you think, > > > > Caty > > > > > > > > [1] > > > > http://design.xwiki.org/xwiki/bin/view/Proposal/Usability/Ta > > > sks5/Prioritization/ > > > > > > > > > > > > -- > > > Thomas Mortagne > > > > > >
Re: [xwiki-devs] [Usability] Menus inside Administration
+1 On the implementation detail side I hope the plan is not to add a special #if for an extension and instead the extension itself will be able to place itself there. On Fri, Feb 9, 2018 at 3:35 PM, Alex Cotiugă wrote: > Sounds like a good idea to me. If this would be a voting session, it would > be +1 from me. > > > On Fri, Feb 9, 2018 at 4:25 PM, Ecaterina Moraru (Valica) > wrote: > >> Hi, >> >> This mail is also part of the Usability priorititzation list [1] >> >> Admins expect to manage custom navigation from the Administration. >> >> This proposal integrates the Menu application in Administration, see >> http://design.xwiki.org/xwiki/bin/view/Proposal/IdeaMenuInAdministration# >> HProposals >> >> Let me know what you think, >> Caty >> >> [1] >> http://design.xwiki.org/xwiki/bin/view/Proposal/Usability/ >> Tasks5/Prioritization/ >> -- Thomas Mortagne
Re: [xwiki-devs] [Usability] Create a dedicated Logo section in Administration
On Fri, Feb 9, 2018 at 4:32 PM, Alex Cotiugă wrote: > +1 > > Adding more elements in the Themes section could make the `Themes` term to > loose its meaning for > what is configurable inside.As a user, I might be tempted to go first in > the Presentation section for > changing something like Logo. Because Skin and Color Themes have logo functionalities and also because the Look & Feel section description mentions you can change the Logo from there, these were the criteria based on what I've chosen the section. > Then, would we consider to make logo > changeable as is the profile > picture (making the logo editable directly in header)? > I don't understand this question. > > Thanks, > Alex > > On Fri, Feb 9, 2018 at 4:18 PM, Thomas Mortagne > > wrote: > > > +1 > > > > On Fri, Feb 9, 2018 at 2:34 PM, Ecaterina Moraru (Valica) > > wrote: > > > Hi, > > > > > > As some of you know, in January we had another session of usability > tests > > > performed. As a result of those tests, I have prioritized [1] some > issues > > > that we might want to improve in our next 10.x+ Roadmaps. > > > > > > One of the entries from that list is: "Create a dedicated Logo section > in > > > Administration". > > > > > > Although we made some improvements in this area, users still struggle > to > > > find the Logo changing area (takes more than 3 minutes). Plus there is > a > > > lot of confusion between the Skin and ColorThemes overriding. > > > > > > This is a proposal to explicitly have a Logo section inside the Themes > > > section of Administration > > > http://design.xwiki.org/xwiki/bin/view/Proposal/IdeaChangeLo > > go#HSolution1-1 > > > > > > Let me know what you think, > > > Caty > > > > > > [1] > > > http://design.xwiki.org/xwiki/bin/view/Proposal/Usability/Ta > > sks5/Prioritization/ > > > > > > > > -- > > Thomas Mortagne > > >
Re: [xwiki-devs] [Usability] Create a dedicated Logo section in Administration
On Fri, Feb 9, 2018 at 4:29 PM, Vincent Massol wrote: > Hi Caty, > > I see in the screenshot that it says “The default logo can be overridden > (typo in your text btw ;)) by Color Themes or at wiki or page level”. > > Several questions: > * What does it mean “at wiki or page level”? How do you do that? Using a > custom skin? Using a color theme? > * Does it mean this is adding yet another way of defining the logo, which > means that we would the ability to set it in the new admin UI, in skins & > in color themes? Isn’t that too much? > * What does it mean in practice when you set it in the admin UI, i.e. > where is it materialized? > Well these are the questions we need to answer from a development point of view. In theory it would be nice to be able to change the Skin logo using this control. Somehow create a shortcut between this default logo and the skin logo, or change the base skin logo from the filesystem. This way the Color Themes will display the logo. Other ideas are welcomed. The description is technical I know, still there are so many ways in XWiki to change to logo and override it, that a warning is welcomed. Thanks, Caty > > Thanks > -Vincent > > > On 9 Feb 2018, at 14:34, Ecaterina Moraru (Valica) > wrote: > > > > Hi, > > > > As some of you know, in January we had another session of usability tests > > performed. As a result of those tests, I have prioritized [1] some issues > > that we might want to improve in our next 10.x+ Roadmaps. > > > > One of the entries from that list is: "Create a dedicated Logo section in > > Administration". > > > > Although we made some improvements in this area, users still struggle to > > find the Logo changing area (takes more than 3 minutes). Plus there is a > > lot of confusion between the Skin and ColorThemes overriding. > > > > This is a proposal to explicitly have a Logo section inside the Themes > > section of Administration > > http://design.xwiki.org/xwiki/bin/view/Proposal/ > IdeaChangeLogo#HSolution1-1 > > > > Let me know what you think, > > Caty > > > > [1] > > http://design.xwiki.org/xwiki/bin/view/Proposal/Usability/ > Tasks5/Prioritization/ > >
Re: [xwiki-devs] [Usability] Menus inside Administration
Sounds like a good idea to me. If this would be a voting session, it would be +1 from me. On Fri, Feb 9, 2018 at 4:25 PM, Ecaterina Moraru (Valica) wrote: > Hi, > > This mail is also part of the Usability priorititzation list [1] > > Admins expect to manage custom navigation from the Administration. > > This proposal integrates the Menu application in Administration, see > http://design.xwiki.org/xwiki/bin/view/Proposal/IdeaMenuInAdministration# > HProposals > > Let me know what you think, > Caty > > [1] > http://design.xwiki.org/xwiki/bin/view/Proposal/Usability/ > Tasks5/Prioritization/ >
Re: [xwiki-devs] [Usability] Create a dedicated Logo section in Administration
+1 Adding more elements in the Themes section could make the `Themes` term to loose its meaning for what is configurable inside.As a user, I might be tempted to go first in the Presentation section for changing something like Logo. Then, would we consider to make logo changeable as is the profile picture (making the logo editable directly in header)? Thanks, Alex On Fri, Feb 9, 2018 at 4:18 PM, Thomas Mortagne wrote: > +1 > > On Fri, Feb 9, 2018 at 2:34 PM, Ecaterina Moraru (Valica) > wrote: > > Hi, > > > > As some of you know, in January we had another session of usability tests > > performed. As a result of those tests, I have prioritized [1] some issues > > that we might want to improve in our next 10.x+ Roadmaps. > > > > One of the entries from that list is: "Create a dedicated Logo section in > > Administration". > > > > Although we made some improvements in this area, users still struggle to > > find the Logo changing area (takes more than 3 minutes). Plus there is a > > lot of confusion between the Skin and ColorThemes overriding. > > > > This is a proposal to explicitly have a Logo section inside the Themes > > section of Administration > > http://design.xwiki.org/xwiki/bin/view/Proposal/IdeaChangeLo > go#HSolution1-1 > > > > Let me know what you think, > > Caty > > > > [1] > > http://design.xwiki.org/xwiki/bin/view/Proposal/Usability/Ta > sks5/Prioritization/ > > > > -- > Thomas Mortagne >
Re: [xwiki-devs] [Usability] Create a dedicated Logo section in Administration
Hi Caty, I see in the screenshot that it says “The default logo can be overridden (typo in your text btw ;)) by Color Themes or at wiki or page level”. Several questions: * What does it mean “at wiki or page level”? How do you do that? Using a custom skin? Using a color theme? * Does it mean this is adding yet another way of defining the logo, which means that we would the ability to set it in the new admin UI, in skins & in color themes? Isn’t that too much? * What does it mean in practice when you set it in the admin UI, i.e. where is it materialized? Thanks -Vincent > On 9 Feb 2018, at 14:34, Ecaterina Moraru (Valica) wrote: > > Hi, > > As some of you know, in January we had another session of usability tests > performed. As a result of those tests, I have prioritized [1] some issues > that we might want to improve in our next 10.x+ Roadmaps. > > One of the entries from that list is: "Create a dedicated Logo section in > Administration". > > Although we made some improvements in this area, users still struggle to > find the Logo changing area (takes more than 3 minutes). Plus there is a > lot of confusion between the Skin and ColorThemes overriding. > > This is a proposal to explicitly have a Logo section inside the Themes > section of Administration > http://design.xwiki.org/xwiki/bin/view/Proposal/IdeaChangeLogo#HSolution1-1 > > Let me know what you think, > Caty > > [1] > http://design.xwiki.org/xwiki/bin/view/Proposal/Usability/Tasks5/Prioritization/
[xwiki-devs] [Usability] Menus inside Administration
Hi, This mail is also part of the Usability priorititzation list [1] Admins expect to manage custom navigation from the Administration. This proposal integrates the Menu application in Administration, see http://design.xwiki.org/xwiki/bin/view/Proposal/IdeaMenuInAdministration#HProposals Let me know what you think, Caty [1] http://design.xwiki.org/xwiki/bin/view/Proposal/Usability/Tasks5/Prioritization/
Re: [xwiki-devs] [Usability] Create a dedicated Logo section in Administration
+1 On Fri, Feb 9, 2018 at 2:34 PM, Ecaterina Moraru (Valica) wrote: > Hi, > > As some of you know, in January we had another session of usability tests > performed. As a result of those tests, I have prioritized [1] some issues > that we might want to improve in our next 10.x+ Roadmaps. > > One of the entries from that list is: "Create a dedicated Logo section in > Administration". > > Although we made some improvements in this area, users still struggle to > find the Logo changing area (takes more than 3 minutes). Plus there is a > lot of confusion between the Skin and ColorThemes overriding. > > This is a proposal to explicitly have a Logo section inside the Themes > section of Administration > http://design.xwiki.org/xwiki/bin/view/Proposal/IdeaChangeLogo#HSolution1-1 > > Let me know what you think, > Caty > > [1] > http://design.xwiki.org/xwiki/bin/view/Proposal/Usability/Tasks5/Prioritization/ -- Thomas Mortagne
[xwiki-devs] [Usability] Create a dedicated Logo section in Administration
Hi, As some of you know, in January we had another session of usability tests performed. As a result of those tests, I have prioritized [1] some issues that we might want to improve in our next 10.x+ Roadmaps. One of the entries from that list is: "Create a dedicated Logo section in Administration". Although we made some improvements in this area, users still struggle to find the Logo changing area (takes more than 3 minutes). Plus there is a lot of confusion between the Skin and ColorThemes overriding. This is a proposal to explicitly have a Logo section inside the Themes section of Administration http://design.xwiki.org/xwiki/bin/view/Proposal/IdeaChangeLogo#HSolution1-1 Let me know what you think, Caty [1] http://design.xwiki.org/xwiki/bin/view/Proposal/Usability/Tasks5/Prioritization/
