http://bugs.meego.com/show_bug.cgi?id=1699

jku <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Priority|High                        |Medium
                 CC|                            |[email protected],
                   |                            |syncevolution-gtk-ui-b...@m
                   |                            |eego.bugs
          Component|SyncEvolution               |GTK UI

--- Comment #1 from jku <[email protected]> 2010-05-04 12:28:23 PDT ---
> Left pane: Since this button can be long, it's better to redesign the box
> altogether, making the yellow text go all the way to the right and positioning
> the button below the text.

GtkInfoBar is a standard component: We really don't want to change that. I
think a better option is to make the button label multiline when needed, like
this: "Seleziona servizio/ndi sincronizzazione".

A translator comment about the maximum line length would be good though. 

There is a _really good_ solution to this problem as well: height-for-width
layout in GTK+:
http://blogs.gnome.org/tvb/2010/04/22/gtk-learns-height-for-width-geometry/ .
Then I wouldn't have to hard code the text width as I have to now... but even
in that case I think multiline buttons make sense for 'long winded' languages
like Italian.

> Right pane: Many languages need bigger buttons - please make the right pane
> wider to avoid truncations

The pane probably is too tight. I can't change that before release because
thoroughly testing the effects of that on the main pane is not easy (as an
example of possible problems: this would affect the spacing in the GtkInfoBar
we discussed above).

I hope using multiline text will work here as well for the time being.

-- 
Configure bugmail: http://bugs.meego.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
You are watching someone on the CC list of the bug.
_______________________________________________
Syncevolution-issues mailing list
[email protected]
http://lists.syncevolution.org/listinfo/syncevolution-issues

Reply via email to