29 May
2018
29 May
'18
6:04 p.m.
On Tue, May 29, 2018 at 6:59 PM, Adel Atallah <adel.atallah(a)xwiki.com>
wrote:
On Tue, May 29, 2018 at 5:41 PM, Ecaterina Moraru
(Valica)
<valicac(a)gmail.com> wrote:
We could:
- [custom] opt to make special controls for tablet / mobile modes,
dropdowns with the rest of the options, modal to ask for version summary;
- [limitation] limit the options available in mobile mode, like keep the
summary, but don't have auto-save;
- [removal] or just don't display the save/summary features, and just keep
the buttons.
Usually we don't provide custom implementations for the mobile version, we
usually hide/remove in order to make it simpler, but depends on the
functionality.
Thanks,
Caty
So preferable in inline mode, the bar should not
be full width, but just
the size of the content.
+1, I think it's weird to have a full width bar both on the
WYSIWYG/XWiki editor and inline editor.
This needs to be prototyped to see if it's
possible to implement easily (without JS).
Ideal on tablet and mobile mode, the bar should contain just the vital
buttons (no minor edit, auto-save, etc.), otherwise the bar takes too
much
screen space (sometimes more than 40% of screen
size).
We could maybe have a dropdown showing the buttons?
So for the problematic inline and responsive modes we would need to
iterate
more until we find the ideal solution.
Thanks,
Adel
Thanks,
Caty
On Tue, May 29, 2018 at 6:23 PM, Ecaterina Moraru (Valica) <
valicac(a)gmail.com> wrote:
> Hi devs,
>
> Just to make sure we are on the same page since there were some
> ambiguities on the proposal, I've put some screenshot on how it will
look
> like:
> http://design.xwiki.org/xwiki/bin/view/Proposal/
> IdeaVisibleSave#HProposal10.x
>
> This proposal extracts the save controls and puts them on a fixed bottom
> bar.
> There are some problems with the inline mode and with the responsive
> versions. With the inline version we could decide to keep the current
> behavior and have the fixed bar only in Wiki and WYSIWYG modes. I guess
we
> should do some implementation tests and see
what's possible.
>
> Thanks,
> Caty
>