Re: Keyboard navigation bug day

Calum Benson <calum benson sun com> writes:
> Havoc Pennington wrote:
> > 
> > What I'd suggest is more useful right now is to have a day to close
> > all the KEYNAV keyword bugs in GTK bugzilla - it doesn't look like we
> > will have time to do all of those
> Okay, that set a few red lights flashing  :o)
> Would it be possible for you guys to assess and let us know which of the
> gtk keynav bugs you don't think you'll be able to close yourselves, and
> why not?  If it's purely a time issue, it's possible some of the Sun
> guys may be able to take some of them on board, with a bit of support
> from yourself and Owen, so please let us know so we can work out a plan
> of attack.  (If there are other issues preventing them being fixed that
> need addressing, please let us know also).

It's purely a time issue. It's hard to predict in advance how many we
can cover; actually at this point is looks like any that get done will
be done by Owen or by me on the weekends.

So, help would be valuable. We can try to write up a plan.

> Another couple of key questions that came up when we were talking about
> this earlier are:
> - What is the deadline for getting gtk keynav fixes in?
> - Which ones require API changes, and which ones don't?

Owen's hypothesis in the past has been that we can get them all
working without API changes, if we are willing to do a couple bad
hacks. I had earlier posted a list of things I thought probably should
involve API changes if we avoided the hacks.

We aren't considering binding set signals to be an API change.

The deadline is basically "ASAP." ;-)


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