Le dimanche 23 août 2009 à 11:54 -0400, Willie Walker a écrit :
So...I'd like to appeal to the yelp developers to keep the accessible
solution turned on by default for 2.28 while we continue our work
towards WebKit a11y for GNOME 3.0.
Let me warn you that downstream, we are getting short of
Hi Andre:
Distros that think that webkit a11y is not good enough in 2.28 are
free to ship older module versions that do not depend on webkit, or
(better) put additional manpower on fixing the remaining webkit a11y
issues. ;-)
I hear you, but this seems to go against the idea that
Hi Shaun:
Thanks for sticking with Gecko for 2.28. Very much appreciated and very
much the right thing to do IMO. :-) As I mentioned, we'll continue on
our WebKit a11y path for GNOME 3.0, but sticking with Gecko for now is a
huge relief.
For other questions, I think we can move the
Thanks everyone! Based upon the responses, I think the gap that would
have no alternative accessible solution would be if yelp chose to ship
with a WebKit-only solution.
The unfortunate thing about this is that yelp is quite important for our
users. Many of them are coming to GNOME for the
On Sun, 2009-08-23 at 11:54 -0400, Willie Walker wrote:
Thanks everyone! Based upon the responses, I think the gap that would
have no alternative accessible solution would be if yelp chose to ship
with a WebKit-only solution.
The unfortunate thing about this is that yelp is quite important
On Thu, Aug 20, 2009 at 3:27 PM, Andre Klapperak...@gmx.net wrote:
Am Donnerstag, den 20.08.2009, 08:40 -0400 schrieb Willie Walker:
Which projects are going to use it
According to the jhbuild 2.28 moduleset:
devhelp, epiphany, seed, yelp.
And under suggests (no hard dependency):
anjuta
Hi All:
I'm trying to assess the impact WebKit a11y is going to have on GNOME
in 2.28.
Which projects are going to use it and will there be alternatives for
people to use Gecko-based technology if WebKit a11y isn't quite soup
yet for 2.28?
Note that this is not a slam on the very hard
Am Donnerstag, den 20.08.2009, 08:40 -0400 schrieb Willie Walker:
Which projects are going to use it
According to the jhbuild 2.28 moduleset:
devhelp, epiphany, seed, yelp.
And under suggests (no hard dependency):
anjuta (for devhelp plugin), empathy.
and will there be alternatives for people
On Thu, 2009-08-20 at 16:27 +0200, Andre Klapper wrote:
Am Donnerstag, den 20.08.2009, 08:40 -0400 schrieb Willie Walker:
Which projects are going to use it
According to the jhbuild 2.28 moduleset:
devhelp, epiphany, seed, yelp.
Hi there. Yelp maintainer here. Who exactly decided to
use
Hey,
On Thu, 2009-08-20 at 09:21 -0500, Shaun McCance wrote:
Yelp will not be using WebKit for 2.28, but it will almost
certainly use it for 2.30/3.0, unless there are serious
problems we can't iron out. That includes accessibility
issues. Please keep us posted.
Is there any specific
I'll leave it to the Yelp maintainer to answer that question. But FWIW,
it took (what felt like) quite a while to have accessible help for the
GNOME desktop -- a topic which was regularly raised on the Orca users
list. Now we have it. I think it would be a shame to take this valuable
tool away
On Thu, 2009-08-20 at 11:44 -0300, Gustavo Noronha Silva wrote:
Hey,
On Thu, 2009-08-20 at 09:21 -0500, Shaun McCance wrote:
Yelp will not be using WebKit for 2.28, but it will almost
certainly use it for 2.30/3.0, unless there are serious
problems we can't iron out. That includes
Am Donnerstag, den 20.08.2009, 09:42 -0500 schrieb Shaun McCance:
On Thu, 2009-08-20 at 16:27 +0200, Andre Klapper wrote:
According to the jhbuild 2.28 moduleset:
devhelp, epiphany, seed, yelp.
Hi there. Yelp maintainer here. Who exactly decided to
use the webkit branch in that
Shaun McCance wrote:
This means that anybody running 2.27.x from jhbuild has
been unable to use the new Mallard stuff, which is the
single most noteworthy thing in Yelp 2.28.
The modulesets were using webkit for a while, as it was the easiest
way to get webkit support exposed, but switched
Am Donnerstag, den 20.08.2009, 09:50 -0500 schrieb Shaun McCance:
I was busy working on Mallard support for 2.28, and didn't
have time (or make time) to review the WebKit stuff. And
now I consider it to be way too late in the release cycle
for this kind of change.
I agree it's late in the
On Thu, 2009-08-20 at 09:50 -0500, Shaun McCance wrote:
I was busy working on Mallard support for 2.28, and didn't
have time (or make time) to review the WebKit stuff. And
now I consider it to be way too late in the release cycle
for this kind of change.
I can easily agree with that
On Thu, 2009-08-20 at 23:29 +0200, Josselin Mouette wrote:
Le jeudi 20 août 2009 à 09:50 -0500, Shaun McCance a écrit :
Is there any specific reasons why it will not use WebKit for 2.28? I
understand we have little time for real world testing, but it would be
useful to understand whether
17 matches
Mail list logo
