Re: [Evolution-hackers] component information area.

Since the HIG stuff is still in discussion, and perhaps Rodney would like to work on those issues (not the least because he can get much quicker PD feedback), i've just committed the code "as is", i.e. the -5 version of the widget.

If we really need alternatate text support, let me know, i've got some basic code to do it with a gtklabel, although its a little tricky since we need to work out text sizes based on different widgets being clipped, not the displayed one.

The header is
#include "widgets/misc/e-info-label.h"

It is a plain widget, which sets up its own borders etc, so should be packed wherever with no padding.

There are 2 api calls, and they're documented in the source.

The info text could possibly be direct pango layout marked up, but whatever, its easy to change.

On Wed, 2004-04-07 at 17:01 +0200, Rodrigo Moya wrote:
On Wed, 2004-04-07 at 10:45 -0400, JP Rosevear wrote:
> On Wed, 2004-04-07 at 17:20 +0800, Not Zed wrote:
> > Hows this stuff look:
> > 
> >
> > 
> > Took me a while to work out how to do a few things, hence all the tries.
> > I gave up on the multiple-alternate smaller-text idea for now.  The last
> > one (-5) is probably the closest to what we want (although some others
> > are exactly the same height as the search bar).
> > 
> > Tweaks to layout (i.e. borders etc)?  Any hig insights on this?
> > 
> > Or should i just commit and 'work it out later'.
> > 
> > The api is really simple, you create it (telling it what icon to use)
> > and pack it with 0 padding into a vbox which contains your folder tree,
> > then call set_info(location, info) to set the location (i.e. folder
> > name) and extra info, whenever it changes.  It uses a clipped label for
> > the location but a normal gtk label for the other info.
> > 
so, is it implemented as a widget to be used in each component?


evolution-hackers maillist  -  evolution-hackers lists ximian com

Michael Zucchi <notzed ximian com>

Ximian Evolution Software Developer

Novell, Inc.

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]