Re: [libreoffice-design] Re: Minutes from the design meeting 2018/Mar/28

2018-03-29 Thread infinitytec
I agree; fix the notebookbar's bugs and make it easy access in 6.1. The removal of the older toolbars can be later.  It could also be a smoother transition for some users. (And help find bugs that would otherwise be forced on everyone) Any sufficiently advanced technology is magic to those who

Re: [libreoffice-design] Re: Minutes from the design meeting 2018/Mar/28

2018-03-29 Thread Pedro Rosmaninho
It would be awesome to see the Notebookbar come out of experimental support for 6.1. IMO, that should be a priority. If supporting these multiple Notebookbar options is not a blocker to that, then I guess it's not bad to maintain them. On Thu, Mar 29, 2018 at 7:49 PM, V Stuart Foote

[libreoffice-design] Re: Minutes from the design meeting 2018/Mar/28

2018-03-29 Thread V Stuart Foote
htietze wrote > ... > > But it's up to the community, which is first the design team. So more > opinions please. Choosing a default Notebookbar mode is trivial--and I do not see too much of a support issue across the modes--it is all .UI assemblage of .uno commands. But there are holes and

Re: [libreoffice-design] Minutes from the design meeting 2018/Mar/28

2018-03-29 Thread kainz.a
First I don't think we need a default cause default is the standard toolbars and all others aren't default arranged in a list. If one should be preferred I go with tabbed toolbar cause the concept is well known since 10 years and it scale pretty well. Groupedbar is for my workflow better but I

Re: [libreoffice-design] Minutes from the design meeting 2018/Mar/28

2018-03-29 Thread jan
I would go with the tabbed bar. * It is somewhat scalable (e.g. for potential addons ) by adding tabs if really needed. * It is similar to the MS office style ** It makes it easier for people who want to switch from MSO ** It can be a good argument for decision makers that it is like applications

Re: [libreoffice-design] Minutes from the design meeting 2018/Mar/28

2018-03-29 Thread Pedro Rosmaninho
To me it unites the best of the classic toolbars (access to drop down menus) and the best of the Ribbon UI. On Thu, Mar 29, 2018 at 5:23 PM, Heiko Tietze wrote: > On 29.03.2018 18:02, Pedro Rosmaninho wrote: > > IMO, the Groupedbar should be the chosen one. > > Here are

Re: [libreoffice-design] Minutes from the design meeting 2018/Mar/28

2018-03-29 Thread Heiko Tietze
On 29.03.2018 18:02, Pedro Rosmaninho wrote: > IMO, the Groupedbar should be the chosen one. > Here are the reasons why I think it is the most suited one: > 1 - *It has a unique look among Office suites > 2 - It's distinctive from the Ribbon UI That was my question. Personally I wouldn't go with

Re: [libreoffice-design] Minutes from the design meeting 2018/Mar/28

2018-03-29 Thread Pedro Rosmaninho
I gave it a bit of thought but I didn't write down all possible reasons why it would be a good idea. Right now there are 4 or 5 variants, and all of them have issues. Instead of packing more and more variants, just create a section in the extension website and just include two Notebookbars by

Re: [libreoffice-design] Minutes from the design meeting 2018/Mar/28

2018-03-29 Thread jan
The reason may got lost in the mail – > …Otherwise we let the user make a decision hard to take > (what does each option do?). > We are in a better position to at least determine > what is most useful most of the time. Jan Am 29.03.2018 um 17:52 schrieb Heiko Tietze: > On 29.03.2018 17:30, jan

Re: [libreoffice-design] Minutes from the design meeting 2018/Mar/28

2018-03-29 Thread Heiko Tietze
On 29.03.2018 17:30, jan wrote: > ... it would make sense to have one version which is the "standard" ... Not opposing the idea but what variant should become the standard and why? Btw: There will be no switch but the menu "User interface" (replacing the current "Toolbar Layout" and

Re: [libreoffice-design] Minutes from the design meeting 2018/Mar/28

2018-03-29 Thread jan
I agree – while it may be not possible to guarantee that a "official" variant will be fixed in time, it would make sense to have one version which is the "standard" so that efforts can be focused. – It might be hard to consider all variants all the time when doing changes, same would go for

Re: [libreoffice-design] Minutes from the design meeting 2018/Mar/28

2018-03-29 Thread Cor Nouws
Hi Pedro, Pedro Rosmaninho wrote on 29-03-18 15:36: > The variants included by default with LO should be supported and fixed by > the UI team. Otherwise there'll be a bunch of bug reports about something > that is not officially supported. There is no such 'official supported' thing that holds

Re: [libreoffice-design] Minutes from the design meeting 2018/Mar/28

2018-03-29 Thread Pedro Rosmaninho
Plus to keep up with the new Colibre icon set (what a great idea to use a colibri as the symbol) it would be really cool to have a Colibre Notebookbar to go with it in 6.1. On Thu, Mar 29, 2018 at 2:36 PM, Pedro Rosmaninho wrote: > Considering that the Notebookbar is

Re: [libreoffice-design] Minutes from the design meeting 2018/Mar/28

2018-03-29 Thread Pedro Rosmaninho
Considering that the Notebookbar is maturing and reaching a maturity point where it is stable, it would be interesting if there was an official UX team variant developed and improved upon by everyone here. It wouldn't have to be the default UI, but something that the UX team would answer to bugs

Re: [libreoffice-design] Minutes from the design meeting 2018/Mar/28

2018-03-29 Thread Heiko Tietze
On 29.03.2018 15:04, Pedro Rosmaninho wrote: > Can I just ask one small thing that I have doubts on? > Is there no "official" UI design team Notebookbar option? The contextual group variant has a foundation [1] but there is nothing specific for the other variants, which is bad for transparency

Re: [libreoffice-design] Minutes from the design meeting 2018/Mar/28

2018-03-29 Thread Pedro Rosmaninho
Can I just ask one small thing that I have doubts on? Is there no "official" UI design team Notebookbar option? On Wed, Mar 28, 2018 at 8:06 PM, Heiko Tietze wrote: > Present: Thomas, Heiko > > * Colibre >+ controversially discussed on the patch; Colibre on Windows