<html>
<head>
<base href="https://bugs.documentfoundation.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Change the default UI"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=135501#c29">Comment # 29</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Change the default UI"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=135501">bug 135501</a>
from <span class="vcard"><a class="email" href="mailto:vermelhusco1904@gmail.com" title="Pedro <vermelhusco1904@gmail.com>"> <span class="fn">Pedro</span></a>
</span></b>
<pre>(In reply to Thorsten Behrens (CIB) from <a href="show_bug.cgi?id=135501#c25">comment #25</a>)
<span class="quote">> (In reply to Heiko Tietze from <a href="show_bug.cgi?id=135501#c24">comment #24</a>)
> >
> > Caolan, Thorsten: What do you think about default and selection of MUFFIN?
>
> As said during ESC - generally in favour. Also siding with Caolan, that then
> we'd want to limit the number of choices to perhaps 2 or 3 max (classic UI,
> and one or two notebookbar flavours).
>
> How to make this least disruptive for existing users, and at the same time
> keep help, documentation etc ~up to date is predominantly a UX decision
> (perhaps with project-wide input).
>
> But broadly, the reason why the project implemented the notebookbar, is to
> eventually have it as the 1st tier UI. ;)</span >
Since there seems to have been some discussion about this in the ESC meeting
about this I would like to remark that 2 or 3 max UIs do not showcase the
flexibility of LibO, which is one of the stronger points I would suggest that
at least 4 UIs are presented.
I would propose to remove from the old toolbar layouts the Single toolbar
layout.
>From the Notebookbar layouts I would remove the contextual layouts, and if
necessary the Compact layouts.
However, I think the Compact layouts are awesome, so I would keep them and
increase UI choice to 6 layouts.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>