Re: EggDateTime committed to libegg



On Wed, May 28, 2003 at 01:31:04PM +0100, Bill Haneman wrote:

> If we wanted something more general, we'd need a list/array of layouts,
> and names for each layout.  That'd be fine, i.e.
> 
> gint egg_datatime_get_layouts (EggDataTime *edt, PangoLayout  
>                                **layout_rtn, gchar **names_rtn);	
> 
> or perhaps returning a GList of DateTimeLayoutStructs would be cleaner:
> 
> typedef struct {
> 	gchar *name;
> 	PangoLayout *layout;
> } DateTimeLayout;

Ok, for now I will go with the easy solution. But we should keep this in
mind, I think.

> Anything that puts textual info on the screen needs to expose AtkText,
> so the answer to the first question is "yes".  As for the second, the
> policy of GTK+ is to put all ATK implementation code in libgail; other
> widget libraries can and do provide their own ATK implementations
> internally, but for GTK+ widgets, externalizing the implementation means
> that the required internal info must be exposed to GAIL via API.

I understand. I have to admit that I have few prior experience with
a11y, but that it very important to me to get it right. So your input is
very much appreciated.

 - Sebastian




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