[ANN] LibreOffice 3.6.0.0 beta2 available for testing

[Jan Holesovsky]

Hi Ape,

On 2012-06-21 at 08:10 -0700, ape wrote:

> A few notes about LibO-dev_3.6.0.0.beta2 (ID: f010139); OS - Windows.
>  
> 1st note (see - gui_error_win_x86.gif).
>  Error GUI. The description is difficult to make because my English is very
> bad. But I made an animation (gui_error_win_x86.gif) that will explain
> everything without me.
>  
> http://nabble.documentfoundation.org/file/n3991595/gui_error_win_x86.gif
> gui_error_win_x86.gif 

Thank you for noticing this; luckily Andras already pointed me to this
problem - if you can create a bug report, and add it to the 3.6 Most
Annoying Bugs, that would be great :-)  [And please send me the bug
number.]

> 2nd note (see - capt_01.png).
>  With a little work, I realized that because of Innovations - the bright
> background of the workspace applications:
>  - my eyes get tired more quickly;
>  - my monitor "hooked" more intense;
>  - sometimes I confused, where is my (left) cursor now - on the edge of the
> page, on the working area or on the ruler ...

Adding UX advise - what do you think of this, please?  

[The color is configurable, though, you can set it to something that
fits you better; but we still should have a good default, of course.]
 
> 3rd note (see - capt_01.png, on the right - LibreOffice-3.5).
>  The right cursor showed a new error GUI LibO-3.5.4rc1 (perhaps only for
> me): the button "Update" is attached to the right edge of the toolbar
> "Menu", but not separated by "X" pixels from the right edge of the "Help".
> The visual effect - the button closes the menu, making it unavailable - is
> obvious. I think that I'll see the same error in version 3.6.0 when it will
> be possible to upgrade to 3.6.1.
> 
> http://nabble.documentfoundation.org/file/n3991595/capt_01.png capt_01.png 

Not sure I understand you here - so the problem you are reporting here
is that the Update button is painted over the menu, when the window is
too narrow?  The best solution to this one is to update, of course ;-) -
from what I've seen in the code, the button itself is quite a hack, and
not part of the menu, so it is not that easy to optimize the painting of
the menu vs. painting of the button; but still UX ideas appreciated here
too.

Thank you,
Kendy