Re: Outsanding GLib/GTK+ API bugs

[Bill Haneman <Bill Haneman sun com>]

[discussion regarding multihead...]

>
>Hmmm, what I remember coming away from the discussions there was:
> 
> - Confidence that the necessary changes could be done in a binary compatible fashion
> - A rough consensus that we would  do a follow-on release in a short timescale 
>   after 2.0.
>
>But that's water under the bridge... 

Yep.

>> For our part, we tried to clarify the point that 
>> multi-head was more than a must-have for 2.0, from an enterprise perspective - it 
>> was essential if Gnome is to be put forward as the 'standard' enterprise desktop.
>
>While I appreciate the fact that multihead support is an essential
>feature in some application areas, other features in GTK+-2.0:
>
> - Workable text and tree widgets
> - Complex-text and RLT support
> - Accessibility support
> - Etc. 

Yes again.

>Are _also_ essential features. We can't do everything at once if we expect
>to be able to release and to release something that we feel comfortable with.
>
>And there are certainly other very important issues that couldn't be
>done for 2.0. For the average user of GTK+, even, I suspect, on
>Solaris, the current state of the GtkFileSelection widget is going to
>be a bigger issue than the lack of multihead support. We have to
>do what we can for 2.0, then move on and do more for 2.2.

I think we are both worried about the same thing, ultimately - (semi-)timely 
delivery of a suitably featureful and robust desktop.  It seems we have 
different understandings of the 'must' versus 'should' items.  Our apparent
misunderstanding about multihead puts us in a real bind however, since we don't
have time to prepare for the repercussions of a reschedule, and waiting for
2.2 means 6-9 months (+?).

At this point I would like to return to being a bystander in this 
discussion, and focus on accessibility :-) 

Regards,

Bill


------
Bill Haneman x19279
Gnome Accessibility / Batik SVG Toolkit
Sun Microsystems Ireland