Re: [xwiki-users] [VOTE] Enable default actions for the Flamingo top menu entries
It's good to see in action, I like it! Thanks for this. 2014-12-10 17:17 GMT+01:00 Marius Dumitru Florea mariusdumitru.flo...@xwiki.com: I committed my changes so that those that haven't voted yet can see it in action. Will revert if someone is against it. Thanks, Marius On Mon, Dec 8, 2014 at 11:07 PM, Guillaume Lerouge guilla...@xwiki.com wrote: +1 Thanks a lot for all your effort on this Marius! Guillaume On Mon, Dec 8, 2014 at 1:18 PM, Guillaume Louis-Marie Delhumeau gdelhum...@xwiki.com wrote: +1, looks good. 2014-12-08 12:59 GMT+01:00 Marius Dumitru Florea mariusdumitru.flo...@xwiki.com: On Sat, Dec 6, 2014 at 11:02 PM, Denis Gervalle d...@softec.lu wrote: +1, ideally with a hover feedback very similar to the one of a dropdown button. The color theme is responsible for the hover effect. A flat color theme will probably use a single color highlight, controlled by the @navbar-default-link-hover-bg LESS variable. A 3D color theme may use some gradients to achieve the 3D effect on hover. A minimalistic color theme (like Simplex) will just change the text color on hover, leaving the background transparent. This proposal/vote is about agreeing on: * displaying a small vertical bar between the menu label and toggle (using a color derived from the menu background) to indicate the separation between the two (especially for tablet devices where there's no hover) * hovering/activating the menu label and the toggle separately, as it happens with a drop down button (e.g. the Add button). Thanks, Marius On Fri, Dec 5, 2014 at 6:59 PM, Pascal BASTIEN pbasnews-xw...@yahoo.fr wrote: May I? (you send mail at user list)... then +1 On 6.3 I still use 6.2 menu (I modified the template on my xwiki) I'm agree with you the 2 side of button must be better separate (with color on hoover or a black vertical bar?). IMO we must respect the same logic of actions button (an one-click default action and drop down sub menu level at the right-side-click ) With CSS it should be possible to:- use 2 side button on big screen- use GoTo menu on small screen (with @media min-width) Thxs Pascal BASTIEN De : Marius Dumitru Florea mariusdumitru.flo...@xwiki.com À : XWiki Developers d...@xwiki.org; XWiki Users users@xwiki.org Envoyé le : Vendredi 5 décembre 2014 17h20 Objet : [xwiki-users] [VOTE] Enable default actions for the Flamingo top menu entries Hi everyone, = Short Story = I propose to change the behaviour of the top level menu from Flamingo for tablet and desktop screens (so NOT for phones) to match the behaviour we had in 6.2 BUT improving the separation between the navigation links and the drop down toggle. The idea is that the top level menu entries should behave like a drop down button (e.g. the Add button) but without looking like one. You can see some screen shots at http://jira.xwiki.org/browse/XWIKI-11517. = Long Story = I've heard complains that the current behaviour of the top level menu from Flamingo skin is not perfect. The issue is that you need to click twice to navigate. Ok, with a mouse you can use the middle click (wheel) to open the link in a new tab but still it's annoying for simple uses and for those that use the touch pad or a tablet. An alternative I have investigated in http://jira.xwiki.org/browse/XWIKI-11479 is to open the menu on hover (on devices that support this of course). The result is quite nice and effective but there is a problem: if you have a second horizontal menu displayed under the top level menu then you'll have a hard time hovering the second menu. So I decided to close XWIKI-11479 as Won't Fix. For those that like the open-on-hover behaviour and which don't plan to use a second menu I've published this extension http://extensions.xwiki.org/xwiki/bin/view/Extension/Hover+and+Default+Action+for+Flamingo+Menu . The other alternative to fix the problem is to go back to the behaviour from 6.2. Precisely, each menu has two sides: * on the left is the label which is a link used for navigation * on the right there is a toggle (arrow) used to open the menu. The problem with this, and the reason we change it in 6.3, was that the label and the toggle were not separated very well so the user could easily think they were doing the same action (opening the menu). At the same time this separation felt unnatural on extra small screens (phones) because you couldn't tap easily on the toggle (arrow). The solution I propose is to: * Keep the current behaviour for extra small screens (phones). That means the use has to tap twice to navigate: one tap to open the menu and another
Re: [xwiki-users] [VOTE] Enable default actions for the Flamingo top menu entries
I like it too. What I would 'improve' is: when the dropdown is .open, have the background-color also on entity name, not just the arrow. This would mean removing 'background-color: transparent' from '.navbar-nav.dropdown-split.open.dropdown-split-left'. This way, you can clearly see the separation of link/action in normal mode, but see the affiliation of the menu when open (also this is visible since the menu starts under the entity name, not the arrow). This is just a remark I have, but I'm waiting for more feedback from others. Thanks, Caty On Wed, Dec 10, 2014 at 6:17 PM, Marius Dumitru Florea mariusdumitru.flo...@xwiki.com wrote: I committed my changes so that those that haven't voted yet can see it in action. Will revert if someone is against it. Thanks, Marius On Mon, Dec 8, 2014 at 11:07 PM, Guillaume Lerouge guilla...@xwiki.com wrote: +1 Thanks a lot for all your effort on this Marius! Guillaume On Mon, Dec 8, 2014 at 1:18 PM, Guillaume Louis-Marie Delhumeau gdelhum...@xwiki.com wrote: +1, looks good. 2014-12-08 12:59 GMT+01:00 Marius Dumitru Florea mariusdumitru.flo...@xwiki.com: On Sat, Dec 6, 2014 at 11:02 PM, Denis Gervalle d...@softec.lu wrote: +1, ideally with a hover feedback very similar to the one of a dropdown button. The color theme is responsible for the hover effect. A flat color theme will probably use a single color highlight, controlled by the @navbar-default-link-hover-bg LESS variable. A 3D color theme may use some gradients to achieve the 3D effect on hover. A minimalistic color theme (like Simplex) will just change the text color on hover, leaving the background transparent. This proposal/vote is about agreeing on: * displaying a small vertical bar between the menu label and toggle (using a color derived from the menu background) to indicate the separation between the two (especially for tablet devices where there's no hover) * hovering/activating the menu label and the toggle separately, as it happens with a drop down button (e.g. the Add button). Thanks, Marius On Fri, Dec 5, 2014 at 6:59 PM, Pascal BASTIEN pbasnews-xw...@yahoo.fr wrote: May I? (you send mail at user list)... then +1 On 6.3 I still use 6.2 menu (I modified the template on my xwiki) I'm agree with you the 2 side of button must be better separate (with color on hoover or a black vertical bar?). IMO we must respect the same logic of actions button (an one-click default action and drop down sub menu level at the right-side-click ) With CSS it should be possible to:- use 2 side button on big screen- use GoTo menu on small screen (with @media min-width) Thxs Pascal BASTIEN De : Marius Dumitru Florea mariusdumitru.flo...@xwiki.com À : XWiki Developers d...@xwiki.org; XWiki Users users@xwiki.org Envoyé le : Vendredi 5 décembre 2014 17h20 Objet : [xwiki-users] [VOTE] Enable default actions for the Flamingo top menu entries Hi everyone, = Short Story = I propose to change the behaviour of the top level menu from Flamingo for tablet and desktop screens (so NOT for phones) to match the behaviour we had in 6.2 BUT improving the separation between the navigation links and the drop down toggle. The idea is that the top level menu entries should behave like a drop down button (e.g. the Add button) but without looking like one. You can see some screen shots at http://jira.xwiki.org/browse/XWIKI-11517. = Long Story = I've heard complains that the current behaviour of the top level menu from Flamingo skin is not perfect. The issue is that you need to click twice to navigate. Ok, with a mouse you can use the middle click (wheel) to open the link in a new tab but still it's annoying for simple uses and for those that use the touch pad or a tablet. An alternative I have investigated in http://jira.xwiki.org/browse/XWIKI-11479 is to open the menu on hover (on devices that support this of course). The result is quite nice and effective but there is a problem: if you have a second horizontal menu displayed under the top level menu then you'll have a hard time hovering the second menu. So I decided to close XWIKI-11479 as Won't Fix. For those that like the open-on-hover behaviour and which don't plan to use a second menu I've published this extension http://extensions.xwiki.org/xwiki/bin/view/Extension/Hover+and+Default+Action+for+Flamingo+Menu . The other alternative to fix the problem is to go back to the behaviour from 6.2. Precisely, each menu has two sides: * on the left is the label which is a link used for navigation * on the right there is a toggle (arrow) used to open the menu. The problem with this, and the reason we change it
Re: [xwiki-users] [xwiki-devs] [VOTE] Enable default actions for the Flamingo top menu entries
On Thu, Dec 11, 2014 at 12:05 PM, Ecaterina Moraru (Valica) vali...@gmail.com wrote: I like it too. What I would 'improve' is: when the dropdown is .open, have the background-color also on entity name, not just the arrow. This would mean removing 'background-color: transparent' from '.navbar-nav.dropdown-split.open.dropdown-split-left'. This way, you can clearly see the separation of link/action in normal mode, but see the affiliation of the menu when open (also this is visible since the menu starts under the entity name, not the arrow). If we activate the entire menu item then there won't be any hover effect on the label when the menu is open so the user might think the link doesn't work in this case. Moreover, this behaviour diverges from the one of a drop down button (like the Add button). This is just a remark I have, but I'm waiting for more feedback from others. Thanks, Caty On Wed, Dec 10, 2014 at 6:17 PM, Marius Dumitru Florea mariusdumitru.flo...@xwiki.com wrote: I committed my changes so that those that haven't voted yet can see it in action. Will revert if someone is against it. Thanks, Marius On Mon, Dec 8, 2014 at 11:07 PM, Guillaume Lerouge guilla...@xwiki.com wrote: +1 Thanks a lot for all your effort on this Marius! Guillaume On Mon, Dec 8, 2014 at 1:18 PM, Guillaume Louis-Marie Delhumeau gdelhum...@xwiki.com wrote: +1, looks good. 2014-12-08 12:59 GMT+01:00 Marius Dumitru Florea mariusdumitru.flo...@xwiki.com: On Sat, Dec 6, 2014 at 11:02 PM, Denis Gervalle d...@softec.lu wrote: +1, ideally with a hover feedback very similar to the one of a dropdown button. The color theme is responsible for the hover effect. A flat color theme will probably use a single color highlight, controlled by the @navbar-default-link-hover-bg LESS variable. A 3D color theme may use some gradients to achieve the 3D effect on hover. A minimalistic color theme (like Simplex) will just change the text color on hover, leaving the background transparent. This proposal/vote is about agreeing on: * displaying a small vertical bar between the menu label and toggle (using a color derived from the menu background) to indicate the separation between the two (especially for tablet devices where there's no hover) * hovering/activating the menu label and the toggle separately, as it happens with a drop down button (e.g. the Add button). Thanks, Marius On Fri, Dec 5, 2014 at 6:59 PM, Pascal BASTIEN pbasnews-xw...@yahoo.fr wrote: May I? (you send mail at user list)... then +1 On 6.3 I still use 6.2 menu (I modified the template on my xwiki) I'm agree with you the 2 side of button must be better separate (with color on hoover or a black vertical bar?). IMO we must respect the same logic of actions button (an one-click default action and drop down sub menu level at the right-side-click ) With CSS it should be possible to:- use 2 side button on big screen- use GoTo menu on small screen (with @media min-width) Thxs Pascal BASTIEN De : Marius Dumitru Florea mariusdumitru.flo...@xwiki.com À : XWiki Developers d...@xwiki.org; XWiki Users users@xwiki.org Envoyé le : Vendredi 5 décembre 2014 17h20 Objet : [xwiki-users] [VOTE] Enable default actions for the Flamingo top menu entries Hi everyone, = Short Story = I propose to change the behaviour of the top level menu from Flamingo for tablet and desktop screens (so NOT for phones) to match the behaviour we had in 6.2 BUT improving the separation between the navigation links and the drop down toggle. The idea is that the top level menu entries should behave like a drop down button (e.g. the Add button) but without looking like one. You can see some screen shots at http://jira.xwiki.org/browse/XWIKI-11517. = Long Story = I've heard complains that the current behaviour of the top level menu from Flamingo skin is not perfect. The issue is that you need to click twice to navigate. Ok, with a mouse you can use the middle click (wheel) to open the link in a new tab but still it's annoying for simple uses and for those that use the touch pad or a tablet. An alternative I have investigated in http://jira.xwiki.org/browse/XWIKI-11479 is to open the menu on hover (on devices that support this of course). The result is quite nice and effective but there is a problem: if you have a second horizontal menu displayed under the top level menu then you'll have a hard time hovering the second menu. So I decided to close XWIKI-11479 as Won't Fix. For those that like the open-on-hover behaviour and which don't plan to use a second menu I've published this extension
[xwiki-users] Xwiki 6.3 : issue when import xar file larger than 32mb
Hi, First, sorry for my bad english. I've got an issue when i want to import a XAR file (size : 53 mb). When i want to import it, i've got an error message who said that max size for the import is 32 Mb. I understood the the WikiStream allowed to import files of any size. So can you explain me why i've got a limit and, if it's possible, how i can bypass them. Thanks. Kevin. -- View this message in context: http://xwiki.475771.n2.nabble.com/Xwiki-6-3-issue-when-import-xar-file-larger-than-32mb-tp7593446.html Sent from the XWiki- Users mailing list archive at Nabble.com. ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
Re: [xwiki-users] Xwiki 6.3 : issue when import xar file larger than 32mb
There is two separated things, during the actual import yes pretty much any size of XAR is supported now but the current UI still work with an attachent and the error you get is when you attach the XAR, not when you import it. Le 11 déc. 2014 14:46, Kevin k.gues...@animalis.fr a écrit : Hi, First, sorry for my bad english. I've got an issue when i want to import a XAR file (size : 53 mb). When i want to import it, i've got an error message who said that max size for the import is 32 Mb. I understood the the WikiStream allowed to import files of any size. So can you explain me why i've got a limit and, if it's possible, how i can bypass them. Thanks. Kevin. -- View this message in context: http://xwiki.475771.n2.nabble.com/Xwiki-6-3-issue-when-import-xar-file-larger-than-32mb-tp7593446.html Sent from the XWiki- Users mailing list archive at Nabble.com. ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
