Hi All:
Just to follow up -- for GNOME 2.29.90, we've made the decision to make the
stable stuff the default. So, the CORBA infrastructure will be installed to
the same locations as it was with GNOME 2.28.x and the D-Bus infrastructure
will be installed in a relocated spot. You can read more
I tend to be conservative: if users want/need/expect stability (and
what user doesn't expect that?), then it would be unacceptable if they
ended up with an inconsistent, buggy, crashy, experience.
But, I am out of my depth, so let me ask questions. Has GNOME has been
in this position
Le lundi 01 février 2010, à 14:54 -0500, Willie Walker a écrit :
Please, speak up with your thoughts. The collective opinion of our
group matters and it will help shape what recommendations we will make
to the release team for GNOME 2.30.
I think both should be shipped, and we should document
Hi Will,
I think both versions of at-spi should be included in gnome-2.30,
because at-spi2 need a lot of testing and not all users want to build
it from source.
BTW.: Do we have a big improovement of a11y in gnome 2.30 compared to
gnome 2.28?
If not, we should make at-spi2 as default for gnome
Speaking from the standpoint of a user. I want it to be stable. I don't
mind working with an unstable version on a virtual machine but I want my
main machine to remain stable so I can work and I want to be able to
upgrade my OS (ubuntu) without loosing my accessibility.
Granted I do most of
Hi All:
GNOME 2.30 is coming out on the Ides of March (March 15). I have one main
question for you: do you want it to be stable or do you want it to have more
cutting edge stuff? This question is predicated on the assumption that GNOME
2.30 is the last of the GNOME 2 releases and GNOME 3 is
On Mon, Feb 01, 2010 at 11:54:19AM PST, Willie Walker wrote:
Hi All:
GNOME 2.30 is coming out on the Ides of March (March 15). I have one main
question for you: do you want it to be stable or do you want it to have more
cutting edge stuff? This question is predicated on the assumption
at-spi2 has been put into OpenSolaris' development releases. But I can't
put it into stable release without
http://defect.opensolaris.org/bz/show_bug.cgi?id=13438 fixed. I believe
this is a at-spi and at-spi2 co-exist bug. And we still have not run a
full test for CORBA based accessibility under
I'm afraid the performance of Firefox is very bad with AT-SPI2.
We need to fix it before end-user gets it.
Firefox tries to send children-changed event for every child add/remove,
AT-SPI2 tries to update the whole children set when it gets a children-changed
event.
I'm wondering if there're
