24 Apr
2017
24 Apr
'17
9:17 p.m.
Hi,
On 24 Apr 2017, at 16:07, Ecaterina Moraru (Valica)
<valicac(a)gmail.com> wrote:
Another proposal by Olivier
http://design.xwiki.org/xwiki/bin/view/Proposal/Idea%3A%20Contextual%20Acti…
It would be nice if Olivier could also comment about the other proposals.
I don’t like this new proposal too much for several reasons:
* In general I don’t think it’s a good idea to replace existing button by other ones. This
is a bit a WTF effect IMO and I’m pretty sure some people will not notice the swap in.
* It also prevents easy navigation away from the edit mode and this was very important.
For example you edit in wysiwyg or wiki and then you want to switch to the object mode or
edit permissions, etc
* It completely hides several features such as the save comment text + the minor edit one
and those are typical fields that are well-known and expected in the wiki world. If you
remove them then you can be sure nobody is going to use them ever. Also note that we have
some config properties that forces a save comment and the validation would be really weird
if this field was not visible.
So far I prefer the other proposals.
Thanks
-Vincent
On Mon, Apr 24, 2017 at 3:41 PM, Eduard Moraru
<enygma2002(a)gmail.com> wrote:
> Generally, I like the proposal. A sticky save button is clearly the
> solution.
>
> However, the mobile view is a mess:
> http://design.xwiki.org/xwiki/bin/download/Proposal/
> IdeaVisibleSave/mobile.png
>
> Side note: I think it`s a good time to address the "Save & Continue" +
> "Save & View" duality that I found deeply confusing when I first
started
> with XWiki. If we take it down to only 2 buttons (Save + Cancel), it will
> improve the mobile view as well.
>
> My last note about the proposal is related to the sticky state visible in
> http://design.xwiki.org/xwiki/bin/download/Proposal/
> IdeaVisibleSave/bottomBar.png
> ... I`m not sure on the technical aspects, but I would still prefer it to
> "stick" only to the content area and not overflow to the entire width of
> the screen and go into panels or whatever the skin might have around the
> content area (in edit mode).
>
> Thanks,
> Eduard
>
> On Wed, Apr 12, 2017 at 2:15 PM, Ecaterina Moraru (Valica) <
> valicac(a)gmail.com> wrote:
>
>> On Wed, Apr 12, 2017 at 11:53 AM, Guillaume Delhumeau <
>> guillaume.delhumeau(a)xwiki.com> wrote:
>>
>>> +1 for the solution 3:
>>> http://design.xwiki.org/xwiki/bin/download/Proposal/
>>> IdeaVisibleSave/smallViewPort.png
>>
>>
>> Hi Guillaume,
>>
>> They are not separate proposals, just one, but it looks a bit different
>> when it's fixed at bottom, versus in its position. Just wanted to make
> that
>> clear.
>>
>>
>>>
>>>
>>> 2017-04-11 21:58 GMT+02:00 Vincent Massol <vincent(a)massol.net>et>:
>>>
>>>> Hi,
>>>>
>>>>> On 11 Apr 2017, at 21:25, Denis Gervalle <dgl(a)softec.lu>
wrote:
>>>>>
>>>>> Hi Caty,
>>>>> Very happy to see progress in this area, this is a real pain to
>> scroll
>>>> to the bottom of the document to save it, and there is a long time it
>> is
>>>> affecting us.
>>>>> However, I am not really happy with your current proposal. I found
>> the
>>>> text area for the version summary way too small for the purpose.
>>>
>>
>> Beginner users sometimes don't know what that is for. Somebody asked me
> to
>> remove it all together :) you think it's too small :P
>>
>>
>>> It should
>>>> IMO stay on a separate line in order to be large enough. Since this
> not
>>>> always useful, it might, however, be collapsed somehow in certain
>>>> circumstances.
>>>
>>
>> Currently it is on a separate line. I tried to integrate everything in a
>> single line, that will be always visible, although I agree we have many
>> functionalities (autosave, summary, minor, preview, etc.) and they look a
>> bit crowded.
>>
>>
>>>>> I also wonder if just having some buttons on the top in addition to
>> the
>>>> bottom, wouldn’t be simpler and as efficient, even if the top feature
>> is
>>>> limited (just save / save&view).
>>>
>>
>> Usually save is a the bottom. Still the same view will be also in Full
>> Screen and the top area is already taken by the CkEditor controls, see
>> http://design.xwiki.org/xwiki/bin/download/Proposal/
>> IdeaVisibleSave/fullScreen.png
>>
>> Thanks,
>> Caty
>>
>>
>>> It might also work with your fixed bottom
>>>> UI, that might also be more limited than what you can do by
> scrolling.
>>>>> I hope these are useful comments. I am also curious to see other
>>>> opinions on this important feature.
>>>>
>>>> For me, the issue with the always-on-bar is that it takes up space
> and
>>>> thus reduces the available vertical space for editing content. Thus I
>>> find
>>>> it interesting to have it on only one line and also to only have it
> at
>>> the
>>>> bottom and not repeat it at the top. I’d really not like to see it at
>> the
>>>> top.
>>>>
>>>> Thanks
>>>> -Vincent
>>>>
>>>>> --
>>>>> Denis Gervalle
>>>>> SOFTEC sa - CEO
>>>>> On Tue, Apr 11, 2017 at 17:59, Ecaterina Moraru (Valica) <
>>>> valicac(a)gmail.com> wrote:
>>>>> Hi devs,
>>>>>
>>>>> Some users have complained that when editing they don't know
that
>> they
>>>> need
>>>>> to scroll in order to see the Save buttons.
>>>>>
>>>>> This is a proposal that tackles:
>>>>> - Displaying the save buttons in a bottom area, when they are out
> of
>>> the
>>>>> viewport, see
>>>>> http://design.xwiki.org/xwiki/bin/download/Proposal/
>>>> IdeaVisibleSave/bottomBar.png
>>>>> - Reorganizing the bottom zone in order to compact all the save
>>> functions
>>>>> into a single bar
>>>>> - When the user scrolls, the buttons go into their position, see
>>>>> http://design.xwiki.org/xwiki/bin/download/Proposal/
>>>> IdeaVisibleSave/after.png
>>>>>
>>>>> For the whole proposal and more screenshots, see
>>>>> http://design.xwiki.org/xwiki/bin/view/Proposal/IdeaVisibleSave
>>>>>
>>>>> WDYT?
>>>>>
>>>>> Thanks,
>>>>> Caty
>>>>
>>>>
>>>
>>>
>>> --
>>> Guillaume Delhumeau (guillaume.delhumeau(a)xwiki.com)
>>> Research & Development Engineer at XWiki SAS
>>> Committer on the XWiki.org project
>>>
>>
>