Re: [xwiki-devs] [Proposal] App Within Minutes - Improvements
Hi Gabriela, In general, I like the proposition of renewing the theme for AppWithinMinutes which indeed, looks not completely in line with the new Flamingo skin. I'm commenting below based on Marius's answer. On 23/04/2015 11:21, Marius Dumitru Florea wrote: Hi Gabriela, Thanks for this proposal. As a general remark, it's not easy to see the differences between your proposal and the current state. A side-by-side comparison would have helped. = Wizard Header = I like how the step number is displayed before the step title. I don't see be benefit of not showing the numbers for the steps on the right. Also, I'm not sure blue is the best color to mark the current step. About numbers, I'm torned. Marius is right: why removing an information that exists. However, I'm not sure how useful this information is for end-user. Marius, do you have any idea what could be the use of having this information (the number of the step)? For colors, I disagree with you Marius, green (for done steps), blue (for current step) and gray (for coming steps) seems pretty logic. Maybe red could have been used for current step but red also often represent warning or danger so blue seems fine. Or did I miss some obvious color for a current step? = Icons = Are all those icons available in the Icon Theme? Some of the icons are not well chosen. For instance we are already using the bricks icon for XWiki Objects (in the document tree and the search UI). I don't think it's suited for Steps. I wouldn't put icons everywhere just for the sake of having an icon, unless that icon is really useful. I don't think we need icons everywhere. Yes, don't put icons everywhere just to put icons and be careful about the choice of the icons. However, I completely agree that trying to improve the UI with icons is a good idea. So I'm mainly in favor of this improvement. = Home Page = I like this idea of changing the look of these buttons to be more in line with Flamingo theme (seriously, the old one are only underlined text!). And I like the idea of merging all the actions except Add (which is the main one) into a dropdown menu. I'm not convinced by the position of the new buttons. They don't look right for me because there is also Edit More Action above. I feel there are too many buttons spread over the page. Some options (no necessarily better): However, Marius is right about that, maybe having to much buttons on the right is not the best. But even with this drawback, I would vote +1 for this improvement. * display the buttons on the left, above the live table (we plan to add batch operations to the live table and we'll add some buttons there anyway) To be tested, why not. * merge the buttons with the Edit / More Actions. Display Add Entry before Edit and put app actions inside More Actions * move Add Entry to the top menu (as an option under the Add button) and the app actions inside other menus or inside More Actions I'm not confident that end-users will find how to add an entry if we go with this solution (note that I may be wrong :-P) And sorry but I don't find other propositions (thanks Marius for the ideas by the way). Hope this helps, Same here ;-) Marius On Wed, Apr 22, 2015 at 5:08 PM, Gabriela Smeria gabriela.sme...@xwiki.com wrote: Hello, I made a proposal on how we could improve App Within Minutes design. In order to have an idea about that, you can visit - http://design.xwiki.org/xwiki/bin/view/Proposal/AppWithinMinutesImprovements7x . The main purpose of creating this design proposal is to help integrate the following applications created with App Within Minutes with Flamingo Skin. What I would like for you to take into consideration is the new layout for the homepage of newly created applications, since there I proposed a bigger change. Thank you, Gabriela http://www.xwiki.com/ *Gabriela Smeria* *Web Developer * gabriela.sme...@xwiki.com corina.lu...@xwiki.com tel: +40 742 024 392 skype: smeria.gabriela ___ devs mailing list devs@xwiki.org http://lists.xwiki.org/mailman/listinfo/devs ___ devs mailing list devs@xwiki.org http://lists.xwiki.org/mailman/listinfo/devs -- Jean Simard jean.sim...@xwiki.com Research engineer at XWiki SAS http://www.xwiki.com Committer on the XWiki.org project http://www.xwiki.org ___ devs mailing list devs@xwiki.org http://lists.xwiki.org/mailman/listinfo/devs
Re: [xwiki-devs] [VOTE] Remove xwiki-platform-legacy-crypto-script module
+1, I like to see legacy code gone. On 04/23/2015 03:22 AM, vinc...@massol.net wrote: Hi devs, With the upgrade of BouncyCastle to version 1.52 the xwiki-platform-legacy-crypto-script legacy module doesn’t build anymore since BC has removed deprecated code. We have of course the option to try to fix the legacy code to use newer APIs. However I think this is overkill and not needed because I don’t believe this legacy code was ever used (Caleb, the author of it, seems to agree with this). See the comments at http://jira.xwiki.org/browse/XCOMMONS-794 Thus, according to our rules, I’m sending this VOTE to decide to break this API voluntarily by removing this legacy module. Here’s my +1 Thanks -Vincent -- Sergiu Dumitriu http://purl.org/net/sergiu/ ___ devs mailing list devs@xwiki.org http://lists.xwiki.org/mailman/listinfo/devs
[xwiki-devs] [VOTE] Remove xwiki-platform-legacy-crypto-script module
Hi devs, With the upgrade of BouncyCastle to version 1.52 the xwiki-platform-legacy-crypto-script legacy module doesn’t build anymore since BC has removed deprecated code. We have of course the option to try to fix the legacy code to use newer APIs. However I think this is overkill and not needed because I don’t believe this legacy code was ever used (Caleb, the author of it, seems to agree with this). See the comments at http://jira.xwiki.org/browse/XCOMMONS-794 Thus, according to our rules, I’m sending this VOTE to decide to break this API voluntarily by removing this legacy module. Here’s my +1 Thanks -Vincent ___ devs mailing list devs@xwiki.org http://lists.xwiki.org/mailman/listinfo/devs
Re: [xwiki-devs] [VOTE] Remove xwiki-platform-legacy-crypto-script module
Unused afaik, +1 for moving it to .git directory ;) Caleb On 04/23/2015 09:22 AM, vinc...@massol.net wrote: Hi devs, With the upgrade of BouncyCastle to version 1.52 the xwiki-platform-legacy-crypto-script legacy module doesn’t build anymore since BC has removed deprecated code. We have of course the option to try to fix the legacy code to use newer APIs. However I think this is overkill and not needed because I don’t believe this legacy code was ever used (Caleb, the author of it, seems to agree with this). See the comments at http://jira.xwiki.org/browse/XCOMMONS-794 Thus, according to our rules, I’m sending this VOTE to decide to break this API voluntarily by removing this legacy module. Here’s my +1 Thanks -Vincent ___ devs mailing list devs@xwiki.org http://lists.xwiki.org/mailman/listinfo/devs -- Satire is the escape hatch from the cycle of sorrow, hatred and violence. #JeSuisCharlie ___ devs mailing list devs@xwiki.org http://lists.xwiki.org/mailman/listinfo/devs
Re: [xwiki-devs] [VOTE] Remove xwiki-platform-legacy-crypto-script module
+0 On Thu, Apr 23, 2015 at 9:33 AM, Denis Gervalle d...@softec.lu wrote: I have look quickly into the changes, and it is no so trivial to fix this legacy code. I agree, there is very little chance that anyone as ever used that legacy API. So, +1 to remove. On Thu, Apr 23, 2015 at 9:22 AM, vinc...@massol.net vinc...@massol.net wrote: Hi devs, With the upgrade of BouncyCastle to version 1.52 the xwiki-platform-legacy-crypto-script legacy module doesn’t build anymore since BC has removed deprecated code. We have of course the option to try to fix the legacy code to use newer APIs. However I think this is overkill and not needed because I don’t believe this legacy code was ever used (Caleb, the author of it, seems to agree with this). See the comments at http://jira.xwiki.org/browse/XCOMMONS-794 Thus, according to our rules, I’m sending this VOTE to decide to break this API voluntarily by removing this legacy module. Here’s my +1 Thanks -Vincent ___ devs mailing list devs@xwiki.org http://lists.xwiki.org/mailman/listinfo/devs -- Denis Gervalle SOFTEC sa - CEO ___ devs mailing list devs@xwiki.org http://lists.xwiki.org/mailman/listinfo/devs -- Thomas Mortagne ___ devs mailing list devs@xwiki.org http://lists.xwiki.org/mailman/listinfo/devs
Re: [xwiki-devs] [VOTE] Remove xwiki-platform-legacy-crypto-script module
+0 Thanks, Marius On Thu, Apr 23, 2015 at 10:22 AM, vinc...@massol.net vinc...@massol.net wrote: Hi devs, With the upgrade of BouncyCastle to version 1.52 the xwiki-platform-legacy-crypto-script legacy module doesn’t build anymore since BC has removed deprecated code. We have of course the option to try to fix the legacy code to use newer APIs. However I think this is overkill and not needed because I don’t believe this legacy code was ever used (Caleb, the author of it, seems to agree with this). See the comments at http://jira.xwiki.org/browse/XCOMMONS-794 Thus, according to our rules, I’m sending this VOTE to decide to break this API voluntarily by removing this legacy module. Here’s my +1 Thanks -Vincent ___ devs mailing list devs@xwiki.org http://lists.xwiki.org/mailman/listinfo/devs ___ devs mailing list devs@xwiki.org http://lists.xwiki.org/mailman/listinfo/devs
[xwiki-devs] [XWiki Day] BFD#86
Hi devs, Today is BFD#86: http://dev.xwiki.org/xwiki/bin/view/Community/XWikiDays#HBugfixingdays Our current status for the 1 year period is 78 bugs behind. See: http://jira.xwiki.org/secure/Dashboard.jspa?selectPageId=1#Created-vs-Resolved-Chart/10470 Here's the BFD#86 dashboard to follow the progress during the day: http://jira.xwiki.org/secure/Dashboard.jspa?selectPageId=13196 Thanks and enjoy your bug fixing day! -Eduard ___ devs mailing list devs@xwiki.org http://lists.xwiki.org/mailman/listinfo/devs
Re: [xwiki-devs] [VOTE] Remove xwiki-platform-legacy-crypto-script module
I have look quickly into the changes, and it is no so trivial to fix this legacy code. I agree, there is very little chance that anyone as ever used that legacy API. So, +1 to remove. On Thu, Apr 23, 2015 at 9:22 AM, vinc...@massol.net vinc...@massol.net wrote: Hi devs, With the upgrade of BouncyCastle to version 1.52 the xwiki-platform-legacy-crypto-script legacy module doesn’t build anymore since BC has removed deprecated code. We have of course the option to try to fix the legacy code to use newer APIs. However I think this is overkill and not needed because I don’t believe this legacy code was ever used (Caleb, the author of it, seems to agree with this). See the comments at http://jira.xwiki.org/browse/XCOMMONS-794 Thus, according to our rules, I’m sending this VOTE to decide to break this API voluntarily by removing this legacy module. Here’s my +1 Thanks -Vincent ___ devs mailing list devs@xwiki.org http://lists.xwiki.org/mailman/listinfo/devs -- Denis Gervalle SOFTEC sa - CEO ___ devs mailing list devs@xwiki.org http://lists.xwiki.org/mailman/listinfo/devs
Re: [xwiki-devs] [Proposal] App Within Minutes - Improvements
Hi Gabriela, Thanks for this proposal. As a general remark, it's not easy to see the differences between your proposal and the current state. A side-by-side comparison would have helped. = Wizard Header = I like how the step number is displayed before the step title. I don't see be benefit of not showing the numbers for the steps on the right. Also, I'm not sure blue is the best color to mark the current step. = Icons = Are all those icons available in the Icon Theme? Some of the icons are not well chosen. For instance we are already using the bricks icon for XWiki Objects (in the document tree and the search UI). I don't think it's suited for Steps. I wouldn't put icons everywhere just for the sake of having an icon, unless that icon is really useful. I don't think we need icons everywhere. = Home Page = I'm not convinced by the position of the new buttons. They don't look right for me because there is also Edit More Action above. I feel there are too many buttons spread over the page. Some options (no necessarily better): * display the buttons on the left, above the live table (we plan to add batch operations to the live table and we'll add some buttons there anyway) * merge the buttons with the Edit / More Actions. Display Add Entry before Edit and put app actions inside More Actions * move Add Entry to the top menu (as an option under the Add button) and the app actions inside other menus or inside More Actions Hope this helps, Marius On Wed, Apr 22, 2015 at 5:08 PM, Gabriela Smeria gabriela.sme...@xwiki.com wrote: Hello, I made a proposal on how we could improve App Within Minutes design. In order to have an idea about that, you can visit - http://design.xwiki.org/xwiki/bin/view/Proposal/AppWithinMinutesImprovements7x . The main purpose of creating this design proposal is to help integrate the following applications created with App Within Minutes with Flamingo Skin. What I would like for you to take into consideration is the new layout for the homepage of newly created applications, since there I proposed a bigger change. Thank you, Gabriela http://www.xwiki.com/ *Gabriela Smeria* *Web Developer * gabriela.sme...@xwiki.com corina.lu...@xwiki.com tel: +40 742 024 392 skype: smeria.gabriela ___ devs mailing list devs@xwiki.org http://lists.xwiki.org/mailman/listinfo/devs ___ devs mailing list devs@xwiki.org http://lists.xwiki.org/mailman/listinfo/devs
Re: [xwiki-devs] [VOTE] Remove xwiki-platform-legacy-crypto-script module
+0 Thanks, Eduard On Thu, Apr 23, 2015 at 11:21 AM, Marius Dumitru Florea mariusdumitru.flo...@xwiki.com wrote: +0 Thanks, Marius On Thu, Apr 23, 2015 at 10:22 AM, vinc...@massol.net vinc...@massol.net wrote: Hi devs, With the upgrade of BouncyCastle to version 1.52 the xwiki-platform-legacy-crypto-script legacy module doesn’t build anymore since BC has removed deprecated code. We have of course the option to try to fix the legacy code to use newer APIs. However I think this is overkill and not needed because I don’t believe this legacy code was ever used (Caleb, the author of it, seems to agree with this). See the comments at http://jira.xwiki.org/browse/XCOMMONS-794 Thus, according to our rules, I’m sending this VOTE to decide to break this API voluntarily by removing this legacy module. Here’s my +1 Thanks -Vincent ___ devs mailing list devs@xwiki.org http://lists.xwiki.org/mailman/listinfo/devs ___ devs mailing list devs@xwiki.org http://lists.xwiki.org/mailman/listinfo/devs ___ devs mailing list devs@xwiki.org http://lists.xwiki.org/mailman/listinfo/devs
Re: [xwiki-devs] [XWiki Day] BFD#86
Reminder: Don`t forget about today's BFD! -Eduard On Thu, Apr 23, 2015 at 11:35 AM, Eduard Moraru enygma2...@gmail.com wrote: Hi devs, Today is BFD#86: http://dev.xwiki.org/xwiki/bin/view/Community/XWikiDays#HBugfixingdays Our current status for the 1 year period is 78 bugs behind. See: http://jira.xwiki.org/secure/Dashboard.jspa?selectPageId=1#Created-vs-Resolved-Chart/10470 Here's the BFD#86 dashboard to follow the progress during the day: http://jira.xwiki.org/secure/Dashboard.jspa?selectPageId=13196 Thanks and enjoy your bug fixing day! -Eduard ___ devs mailing list devs@xwiki.org http://lists.xwiki.org/mailman/listinfo/devs
Re: [xwiki-devs] [Proposal] App Within Minutes - Improvements
On Thu, Apr 23, 2015 at 5:37 PM, Jean SIMARD jean.sim...@xwiki.com wrote: Hi Gabriela, In general, I like the proposition of renewing the theme for AppWithinMinutes which indeed, looks not completely in line with the new Flamingo skin. I'm commenting below based on Marius's answer. On 23/04/2015 11:21, Marius Dumitru Florea wrote: Hi Gabriela, Thanks for this proposal. As a general remark, it's not easy to see the differences between your proposal and the current state. A side-by-side comparison would have helped. = Wizard Header = I like how the step number is displayed before the step title. I don't see be benefit of not showing the numbers for the steps on the right. Also, I'm not sure blue is the best color to mark the current step. About numbers, I'm torned. Marius is right: why removing an information that exists. However, I'm not sure how useful this information is for end-user. Marius, do you have any idea what could be the use of having this information (the number of the step)? I don't see why you would display the number of the current step (on the left) and not the number of the next/previous steps (on the right). The list of steps is an ordered list so it makes sense to me to show the step numbers. For colors, I disagree with you Marius, green (for done steps), blue (for current step) and gray (for coming steps) seems pretty logic. Maybe red could have been used for current step but red also often represent warning or danger so blue seems fine. Or did I miss some obvious color for a current step? You cannot hard-code the color (blue). It needs to come from the Color Theme. So the question is: what variable would you use? = Icons = Are all those icons available in the Icon Theme? Some of the icons are not well chosen. For instance we are already using the bricks icon for XWiki Objects (in the document tree and the search UI). I don't think it's suited for Steps. I wouldn't put icons everywhere just for the sake of having an icon, unless that icon is really useful. I don't think we need icons everywhere. Yes, don't put icons everywhere just to put icons and be careful about the choice of the icons. However, I completely agree that trying to improve the UI with icons is a good idea. So I'm mainly in favor of this improvement. = Home Page = I like this idea of changing the look of these buttons to be more in line with Flamingo theme (seriously, the old one are only underlined text!). I'm in favour of grouping the actions too. I'm just not sure about the position of the buttons. And I like the idea of merging all the actions except Add (which is the main one) into a dropdown menu. I'm not convinced by the position of the new buttons. They don't look right for me because there is also Edit More Action above. I feel there are too many buttons spread over the page. Some options (no necessarily better): However, Marius is right about that, maybe having to much buttons on the right is not the best. But even with this drawback, I would vote +1 for this improvement. * display the buttons on the left, above the live table (we plan to add batch operations to the live table and we'll add some buttons there anyway) To be tested, why not. * merge the buttons with the Edit / More Actions. Display Add Entry before Edit and put app actions inside More Actions * move Add Entry to the top menu (as an option under the Add button) and the app actions inside other menus or inside More Actions I'm not confident that end-users will find how to add an entry if we go with this solution (note that I may be wrong :-P) And sorry but I don't find other propositions (thanks Marius for the ideas by the way). Hope this helps, Same here ;-) Marius On Wed, Apr 22, 2015 at 5:08 PM, Gabriela Smeria gabriela.sme...@xwiki.com wrote: Hello, I made a proposal on how we could improve App Within Minutes design. In order to have an idea about that, you can visit - http://design.xwiki.org/xwiki/bin/view/Proposal/AppWithinMinutesImprovements7x . The main purpose of creating this design proposal is to help integrate the following applications created with App Within Minutes with Flamingo Skin. What I would like for you to take into consideration is the new layout for the homepage of newly created applications, since there I proposed a bigger change. Thank you, Gabriela http://www.xwiki.com/ *Gabriela Smeria* *Web Developer * gabriela.sme...@xwiki.com corina.lu...@xwiki.com tel: +40 742 024 392 skype: smeria.gabriela ___ devs mailing list devs@xwiki.org http://lists.xwiki.org/mailman/listinfo/devs ___ devs mailing list devs@xwiki.org http://lists.xwiki.org/mailman/listinfo/devs -- Jean Simard jean.sim...@xwiki.com Research engineer at XWiki SAS http://www.xwiki.com Committer on the XWiki.org project http://www.xwiki.org
