Re: [Libreoffice] [UX] LO status bar annoyances

2010-12-04 Thread Wols Lists
On 30/11/10 16:25, Kohei Yoshida wrote: I too think that the title bar would be the most logical place to put this info if we were to find a replacement location. But I'm not sure if it can be easily identified by those users who currently rely on the save icon status. The save icon is big

Re: [Libreoffice] [UX] LO status bar annoyances

2010-12-01 Thread Kohei Yoshida
Hi Christoph, On Tue, 2010-11-30 at 22:31 +0100, Christoph Noack wrote: DOCUMENT CHANGED INDICATION I read all the comments very carefully and I understand some thoughts and concerns. However, the constraints / requirements do support Kohei's solution (if we want to keep the current save

Re: [Libreoffice] [UX] LO status bar annoyances

2010-12-01 Thread Christoph Noack
Hi all! Am Mittwoch, den 01.12.2010, 08:12 +0100 schrieb Sebastian Spaeth: On Tue, 30 Nov 2010 22:31:44 +0100, Christoph Noack wrote: [...] STATUS BAR For example, the little '*' is mainly caused by the need for a very compact symbol - here, please think in 480px width. Is there still a

Re: [Libreoffice] [UX] LO status bar annoyances

2010-11-30 Thread Thorsten Behrens
Sebastian Spaeth wrote: Am I the only one finding the current status bar pretty much useless? Nope. I hear you, pretty much unconditionally. Adding UX tag Cc-ing my favourite UX homie. :) Cheers, -- Thorsten pgphW56AvlvY5.pgp Description: PGP signature

Re: [Libreoffice] [UX] LO status bar annoyances

2010-11-30 Thread Kohei Yoshida
On Tue, 2010-11-30 at 16:11 +0100, Thorsten Behrens wrote: Kohei Yoshida wrote: b) We warn when closing a modified doc anyway, so there is no need to always warn me and use up precious space. I propose to just do away with it. Sorry I have to disagree there. I'm the one

Re: [Libreoffice] [UX] LO status bar annoyances

2010-11-30 Thread Regina Henschel
Hi Thorsten, Thorsten Behrens schrieb: Kohei Yoshida wrote: b) We warn when closing a modified doc anyway, so there is no need to always warn me and use up precious space. I propose to just do away with it. Sorry I have to disagree there. I'm the one who put that icon there,

Re: [Libreoffice] [UX] LO status bar annoyances

2010-11-30 Thread Kohei Yoshida
On Tue, 2010-11-30 at 16:42 +0100, Regina Henschel wrote: Hi Thorsten, Thorsten Behrens schrieb: Kohei Yoshida wrote: b) We warn when closing a modified doc anyway, so there is no need to always warn me and use up precious space. I propose to just do away with it.

Re: [Libreoffice] [UX] LO status bar annoyances

2010-11-30 Thread Cor Nouws
Hi Kohei, Kohei Yoshida wrote (30-11-10 17:25) [...] Removing that would not radically improve the real estate of the status bar. Indeed. Plus that I guess there are quite some interesting Calc/Excel issues out there, waiting for 'some love', as Thorsten always can say so kindly. As

Re: [Libreoffice] [UX] LO status bar annoyances

2010-11-30 Thread Kohei Yoshida
On Tue, 2010-11-30 at 19:44 +0100, Cor Nouws wrote: Hi Kohei, Kohei Yoshida wrote (30-11-10 17:25) [...] Removing that would not radically improve the real estate of the status bar. Indeed. Plus that I guess there are quite some interesting Calc/Excel issues out there,

Re: [Libreoffice] [UX] LO status bar annoyances

2010-11-30 Thread Christoph Noack
Hi Thorsten, hi Sebastian, all! :-) Am Dienstag, den 30.11.2010, 12:00 +0100 schrieb Thorsten Behrens: Sebastian Spaeth wrote: Am I the only one finding the current status bar pretty much useless? Nope. I hear you, pretty much unconditionally. Adding UX tag Cc-ing my favourite UX homie.

Re: [Libreoffice] [UX] LO status bar annoyances

2010-11-30 Thread Cor Nouws
Hi Christoph, all, Christoph Noack wrote (30-11-10 22:31) Some more issues of the current design: [...] Agreed? I do not object improving the Status Bar. Although I tend to find other subjects more important. But that is just me of course, who fights more with compatibility issues then

Re: [Libreoffice] [UX] LO status bar annoyances

2010-11-30 Thread Sebastian Spaeth
Part 2 on the Changed icon part. On Tue, 30 Nov 2010 22:31:44 +0100, Christoph Noack wrote: DOCUMENT CHANGED INDICATION A solution should: * just work * be unobtrusive (don't catch attention if it isn't required, don't waste space) * be self-explanatory (if