Vincent Untz wrote:
Willie: do you have any idea when the a11y team would be able to give a
+1 for webkit? Being able to know it's okay as soon as possible would
definitely help us organize things.
I'm CC'ing Joanie, who'll be the person doing most of the work on the
assistive technology side
Just to chime in here - based upon our experiences with Gecko,
accessibility support for browsers is no trivial task. Xan and Joanie
have been hammering away at an impressive pace so far.
Joanie, Xan - what do you think it would take to hit 2.28? Would more
people from the WebKit internals s
point
we need the rest of the community to chime in.
Take care.
--joanie
Cheers, Xan
On the Orca side of things, I'm confident that when that list of bugs
has been addressed I'll be able to implement support. My concern (again)
is discovering additional issues at that point and it be
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 work
Hi Andre:
(resend since my other e-mail server seems to be having issues)
> > 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
> >
, Aug 20, 2009 at 3:27 PM, 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.
> >
> > And
e the discussion to the
gnome-accessibility-list (while I'll do in a follow up).
Many many thanks for being supportive of accessibility. You rock.
Will
Shaun McCance wrote:
On Sun, 2009-08-23 at 11:54 -0400, Willie Walker wrote:
Thanks everyone! Based upon the responses, I think the gap
Hi All:
Immediately after releasing Orca v2.27.91 today, I branched Orca for
gnome-2-28. The gnome-2-28 branch will be used for the remainder of the
GNOME 2.28.x cycle and all new work will take place on master.
Thanks everyone!
Will
___
desktop-d
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 access
Hi All:
We're slated to have the AT-SPI/D-Bus stuff in place for 2.29.2. Things
are chugging away and looking positive. I have some questions about
some approaches we are going to take and would like some opinions and
advice for how to do it better if your stomach is weakened by the
propose
Due to others hardcoding the string "atk-bridge" in their code (e.g.,
Firefox and OOo), the GTK+ a11y module has to be named "atk-bridge". We
could ask Firefox and OOo to not hardcode the name, but we'd end up in a
versioning hell with external apps not tied to the GNOME release schedule.
So, I'
Alberto Ruiz wrote:
2009/10/21 Willie Walker :
Due to others hardcoding the string "atk-bridge" in their code (e.g.,
Firefox and OOo), the GTK+ a11y module has to be named "atk-bridge". We
could ask Firefox and OOo to not hardcode the name, but we'd end up in a
vers
Hi All:
There is a convention of having the user press F7 to enable caret
browsing. For example, when running Firefox, one can press F7 to
enable the caret in the document content and you can then arrow around
the content and select/copy text. yelp has something similar, which I
believe is
Thanks Shaun!
Epiphany and Evolution also both respond to F7 to enable
caret navigation. (And, by the way, though Yelp stores
this in GConf, it also responds to F7.) We're seeing
more and more applications use an HTML renderer for core
parts of their interfaces, such as Gwibber, and Empathy
wi
Hi Owen:
Many thanks for making this a formal proposal for comments. I think we
all want to get behind GNOME Shell as a nice whiz-bang feature to make
people want to move to GNOME 3. With the magnification support going
into GNOME Shell, the accessibility team is also building in a
dependency on
applet and the {Sticky/Slow}Keys feedback keyboard applet)
would need to be ported.
Will
On Mon, 2009-11-02 at 20:15 -0500, Willie Walker wrote:
> Hi Owen:
>
> Many thanks for making this a formal proposal for comments. I think we
> all want to get behind GNOME Shell as a nice whiz-
FYI...regarding Memphis a11y...
Will
--- Begin Message ---
On Mon, 2009-11-02 at 10:20 -0500, Willie Walker wrote:
> External dependencies: gmime, vala, Memphis (for libchamplain), libdb
> (already approved).
Memphis is quite unaccessible. It generates an opaque image from
OpenStreetMa
Hi All:
Here's some really simple questions that all new module proposers should
be able to answer for accessibility (note that this applies to things
that expose a GUI). It's not an exhaustive analysis by any means, but
it will capture some of the most blatant failures. It's so simple, even
Sorry for the late reply to this. I'm curious how closed captioning
and/or subtitles will be rolled into this. Do you video folks have any
thoughts?
I'm also curious if we might also want to consider some sort of gconf
setting that says "give me closed captioning" that any video player can
(Hrm, I'm obviously late ;-))
:-)
As a potential solution, we can modify the AT-SPI/CORBA *.desktop
file to key off of a new gconf key,
/desktop/gnome/interface/at-spi-corba. The existing
/desktop/gnome/interface/accessibility key will be used everywhere
else as normal, but this new key will b
Hi Stormy:
Neat!
Do you (or someone) have specific examples of pages where this has been done?
For example, the URL of a page as well as a pointer to the source code behind
that URL that's maintained somewhere in git?
Thanks,
Will
On Jan 26, 2010, at 2:50 PM, Stormy Peters wrote:
> Thanks
uire a login of some sort, but I'm not sure what to use.
Thanks!
Will
On Jan 26, 2010, at 4:24 PM, Stormy Peters wrote:
>
> On Tue, Jan 26, 2010 at 2:01 PM, Willie Walker wrote:
> Hi Stormy:
>
> Neat!
>
> Do you (or someone) have specific examples of pages where thi
Hi Owen:
Many thanks to the GNOME Shell team for writing this and the WIKI page. It is
very promising to see accessibility included in the roadmap. I have a few
questions:
1) I believe accessibility should be a requirement for GNOME Shell for GNOME 3.
Does the presence of it in the roadmap
Per the instructions at http://live.gnome.org/MaintainersCorner, we have
created a new branch of Orca for GNOME 2.18.
Note to you wonderful translators who are still working away, I'm not
sure of the appropriate svn terminology to describe the revisions at the
time I made the branch. Here's t
Sure and:
Rich Burridge
Joanmarie Diggs
Lynn Monsanto
Thanks!
Will
Bill Haneman wrote:
> Hi Vincent:
>
> I've never been included in the Gnome contributors' list. I reckon it's
> about time!
>
> Bill Haneman
>
> also
>
> Carlos Eduardo Rodrigues Di\xf3genes
> Li Yuan
> Harry Lu
> David Bolter
Hi:
> Making it accessible would be rather nice too... it hasn't worked well
> with high contrast themes for years[1], and I'm guessing screenreaders
> can't do much with it either.
>
Thanks for bringing this up, Calum! Orca definitely has issues with it:
http://bugzilla.gnome.org/show_bug.
Hi Claudio:
>> Categories=GNOME;GTK;Utility;Accessibility;
>>
>> Hm, that's because of the 'Utility' category. If you remove it, orca
>> will appear only under the Accessibility menu. Don't know why dasher
>> uses both, though.
>>
Thanks! With this line, things end up looking good:
Categori
Hi:
I need a little hand-holding on this one for Orca. :-( Orca
(http://live.gnome.org/Orca) is a screen reader for people with visual
impairments. When I build/install Orca from SVN on Ubuntu using the
existing orca desktop file, it ends up in the
Applications->Accessibility menu.
I notic
Pete - I see that the accerciser module still uses a *.zip file of code
zipped up from LSR. This seems a little strange to me. For GNOME 2.20,
I think it is important to get rid of this *.zip file and migrate to the
new 'official' Python bindings for AT-SPI that you and I are working on
for t
s such as official Python bindings for AT-SPI.
Thanks!
Will
>
> On 4/3/07, Willie Walker <[EMAIL PROTECTED]> wrote:
>> Pete - I see that the accerciser module still uses a *.zip file of code
>> zipped up from LSR. This seems a little strange to me. For GNOME 2.20,
&g
> Quick question: How hard would it be for you (as project maintainers)
> to make a list of major user-oriented changes in your module (since
> the last stable release) and send it to gnome-doc-list by feature
> freeze? This would include things like changes to the interface, new
> features and ho
Hi All:
At CSUN in March, Peter Parente and I sat down to talk about a unified
Python wrapper for the AT-SPI: http://live.gnome.org/GAP/PythonATSPI
The main goals were:
* To create a single Python wrapper for AT-SPI reusable across all
Python assistive technologies and test tools for GNOME
For gnome-speech: it's mostly in maintenance mode, with drivers for new
speech engines to be added over time. When something changes in
gnome-speech, I tend make a new release of gnome-speech to coincide with
the next point release of whatever happens to be coming out (i.e.,
either even or odd),
Hi All:
With the release of Orca v2.19.6, we've branched Orca for GNOME 2.20.
The Orca v2.19.6 sources represent the beginning of the branch
(svn.gnome.org/svn/orca/branches/gnome-2-20), and we will soon be
starting some aggressive refactoring work on the trunk.
Between now and the release of GNO
I fully support the inclusion of accerciser. Members of the Orca team
have been using it with good success, and it's accessible to boot.
Furthermore, the maintainer(s) have migrated it to the new pyatspi
bindings, which alleviates any concerns I had.
Will
On Mon, 2007-07-30 at 23:09 +0200, Andre
Sorry to send this to desktop-devel, but I recall this error coming up
at a talk at GUADEC. Someone from the audience yelled "THAT'S BEEN
FIXED!!!":
GThread-ERROR **: GThread system may only be initialized once.
aborting...
We have people pinging us on the Orca list about this, a
Hi All:
Ever since we moved to SVN, I've really been missing the *checkout*
feature that we used to have with the old web interface to CVS. With
the *checkout* feature, I was able to maintain documentation in our CVS
module and just point people to the *checkout* path. For example:
http://cvs.g
Well now, how simple is that? I had been beating my head against the
wall for months trying to figure out the magical incantation only to
find it was too simple.
Thanks everyone!
Will
On Fri, 2007-08-24 at 10:19 -0700, Brad Taylor wrote:
> > > I've not been able to figure the equivalent of this
Hi All:
In prepping for a different problem we're investigating with the Firefox
team, we've been running pychecker on the Orca sources.
We came across two serious problems. The first is that one of our
scripts (the one for nautilus) was importing a module that no longer
exists. The second is
Thanks everyone! Committed the patch to exactly as it was given to you.
Will
On Wed, 2007-09-12 at 18:05 +0200, Vincent Untz wrote:
> Le mercredi 12 septembre 2007, à 17:03 +0200, Frederic Crozat a écrit :
> > Le mercredi 12 septembre 2007 à 10:52 -0400, Willie Walker a écrit :
>
Hi All:
The pychecker fixes from earlier this week were the result of us looking
hard at some impending Firefox changes. Thanks for letting us get those
in. :-) Now for the real problem...
We've been working with the Firefox team and the AT-SPI maintainers on
an approach to allow applications
We tested and tested and could not find any regressions. Thanks
everyone! Committed per the patch.
Will
On Thu, 2007-09-13 at 17:27 +0200, Frederic Crozat wrote:
> Le jeudi 13 septembre 2007 à 17:06 +0200, Vincent Untz a écrit :
> > Le jeudi 13 septembre 2007, à 10:33 -0400, Willie
h FF3 in this next release.
> >
> > The second one is an API conformance bug. We would like to have this in
> > the earliest version possible since it is a small but fairly significant
> > fix.
> >
> > The above is the opinion of Willie Walker and I with Li Yuan
Hi Alex:
Thanks for sending out this call for input. :-)
Being able to reliably interact with the gnome-panel and its applets via
the keyboard alone would be a major boost to its usability.
Thanks again!
Will
On Mon, 2007-09-24 at 04:00 +0100, Alex Jones wrote:
> Hi list
>
> What do we want
I'm curious about the overall accessibility of Empathy. Has anyone done
a survey of how well it works with existing assistive technologies for
GNOME (e.g., GOK, Dasher, Orca, etc.) as well as its keyboard-only
access model?
Will
On Sun, 2007-09-23 at 10:59 +0200, Xavier Claessens wrote:
> Hi,
>
> Hi Willie,
>
> Le lundi 24 septembre 2007, à 10:01 -0400, Willie Walker a écrit :
> > Hi Alex:
> >
> > Thanks for sending out this call for input. :-)
> >
> > Being able to reliably interact with the gnome-panel and its applets via
> > the keyb
Francesco:
If you know of anyone that might even be remotely related to MouseTweaks
and could talk about it (e.g., demo, use cases, remaining work, etc.),
I'd be
really happy to add it to the agenda for the accessibility summit.
I'd also like to hear more about onBoard and future plans for it.
and useful
tool, and your recordmydesktop video demo of it was great.
I've added it to the agenda for today and will bring it up for discussion.
Thanks for the effort!
Will
Francesco Fumanti wrote:
> Hello,
>
>
> First of all, sorry for replying so late.
>
>
> At 3:2
perhaps the
server extension idea is not that important.
Thanks!
Will
PS - Your video really helped a lot with the understanding of why
MouseTweaks is important and useful.
Willie Walker wrote:
> Hi Francesco:
>
> No problem with replying late - I happen to be up late. :-) I took a
Hey All:
Just wanted to drop a note regarding the GNOME Boston Accessibility
Summit. Many thanks for letting us have the room to hammer away on
problems and planning, and many thanks to Owen Taylor for all the work
he did.
I think the GNOME Boston Accessibility Summit went very very well this
ecially those that made it possible to have it demoed during that
> event.
>
>
> At 2:24 PM -0400 10/8/07, Willie Walker wrote:
>> We discussed MouseTweaks at the summit at think it definitely looks
>> like it provides great functionality for the intended users. Overall
It would probably also be good to carry the discussion on the
gnome-accessibility-devel or gnome-accessibility lists, too, since those
folks are going to be the ones most affected by the changes. ;-)
Will
Murray Cumming wrote:
> On Fri, 2007-10-12 at 18:08 +0200, Jens Granseuer wrote:
>
>>
eeds to be
adjustable and what the numerical ranges should be.
Will
Calum Benson wrote:
>
> On 1 Nov 2007, at 12:45, Willie Walker wrote:
>
>> Anyway, my main point is to ask real users about what tasks they
>> typically want to accomplish with mouse keys. Then, figure out the be
Thanks Matthias!
I think the main thing to remember is that the settings may seem too
finely granular for people who don't have to use them. But, the
granularity allows the target user to fine tune their experience to get
the most effective experience and highest throughput.
Will
Matthias Cla
Carlos:
It's been a pleasure to work with you over the past year. Your work on
gnome-mag is greatly appreciated and we're going to miss your energy.
Do you have any maintainers in mind and/or ideas for where to take
gnome-mag? For example, thoughts about where we can fit things in the
space
I definitely like the mockups -- nice work!
Regarding the mouse keys settings, one needs to take into consideration
that the target users of this are people with differing physical
abilities who may need finer control over the parameters. This might
possibly result in more knobs and dials, but
I have a general comment with respect to accessibility. I'm curious if
any of the developers of modules that expose new UI to users have done
any accessibility and/or theming testing with them.
For example, can the UI be used from the keyboard alone? Does the UI
respect theming? Have they tr
Agreed -- we try to do what we can with the resources we have. We, of
course, would also like to see developers make accessibility part of
their normal practice, just as I'm sure the docs and i18n folks desire. ;-)
Will
Bastien Nocera wrote:
> On Thu, 2008-01-03 at 11:26 -0500, Willi
Hi All:
I might be opening a big can of worms with this question, and I
apologize if someone is already working in this space and I just don't
know it.
What is the automated testing strategy for GUIs in GNOME? Is there a
well defined way to create a 'make test' target and have it do the right
Hey All:
Just a quick note -- Eitan Isaacson and I have GNOME accessibility
articles published in the March 2008 Linux Journal. Mine is on Orca and
Eitan's is on Accerciser. This is exciting stuff to me because it helps
get our GNOME accessibility story out to a large range of mainstream
dev
Hey All:
Great discussion so far. I just want to add something about why
regression testing is important to me. In the Orca project, we have a
regression test suite that we use regularly. It helps give us great
sanity checking that our changes and bug fixes don't introduce new
problems. It
David Bolter wrote:
> To my mind, adding regression tests is like spending 1 hour to save 100.
Definitely. :-) It also gives me piece of mind when a refactor is
done, and it never forgets those special cases that we sometimes forget
about when doing manual testing. You can also build them up
Hi All:
With the release of Orca v2.21.92, we've branched Orca for GNOME 2.22.
The Orca v2.21.92 sources represent the beginning of the branch
(svn.gnome.org/svn/orca/branches/gnome-2-22).
Thanks everyone!
Will
___
desktop-devel-list mailing list
des
I'm retitling this because I was just deleting GSOC mail -- my inbox is
flooding and I needed to do some drastic filtering. Many thanks to
Behdad for seeing this message and thinking of me. :-)
For HTML accessibility, the best support is provided by the Gecko engine
that's in Firefox 3. We'v
ojo are doing the same but unlike dojo, I
> only care (the accessible thing) about GNOME and its technology, is
> ARIA the best approach to make dynamic web site accessible to GNOME
> users? and how do I test those ARIA roles on GNOME?
>
>
> On Thu, Feb 28, 2008 at 5:40 PM, Willie Walk
Hi All:
Just my 2 cents here:
I would definitely object to WebKit being the de facto rendering engine
if it did not support accessibility. In addition, as WebKit
accessibility work is done, I recommend looking at the existing AT-SPI
implementation done in Gecko as a potential model for how th
>> Accessibility
>> =
>>
>> In the last few weeks we've started to look at formal accessibility
>> support for document navigation and manipulation. The first WebCore
>> patches have landed and we intend to provide AT-SPI accessibility for
>> the 2.24 release. This is partly in response
Hi All:
I just want to send out a reminder to let you know "GNOME Outreach
Program: Accessibility" stuff is still underway and that there are still
tasks available: http://www.gnome.org/projects/outreach/a11y/.
We had some really good interest in the documentation task and Vincent
Alexander, a
From Li Yuan regarding a11y:
"Accessibility is a problem for conduit. The GUI is simple, but the
left tree view doesn't support keyboard navigation well. Also one has
to drag some items to the right "sync area", there is no way to do this
by keyboard. And the "sync area" is not accessible. I s
part of the GNOME Outreach Program: Accessibility work.
Thanks again for your consideration for accessibility!
Will
John Stowers wrote:
On Wed, 2008-07-30 at 07:37 -0400, Willie Walker wrote:
From Li Yuan regarding a11y:
"Accessibility is a problem for conduit. The GUI is simple, but the
left tree
Hi All:
I recently had a nice discussion with the release team about the
viability of enabling accessibility (i.e., the AT-SPI infrastructure) by
default for GNOME. As a result of that discussion, I'm approaching the
broader GNOME community with a proposal to do this. :-)
Accessibility has
Alexander Jones wrote:
> Isn't this a distro decision?
Ultimately, I guess the value for any gconf setting in
schemas/desktop_gnome_interface.schemas can be whatever a distro wants
it to be. What I'm proposing, however, is that the default value that
we choose for GNOME is that accessibility
x27;d still argue to turn a11y on by
default: it's far easier for someone without a disability to turn it off
than it is for a person with a disability to turn it on.
Will
Mathias Hasselmann wrote:
Am Mittwoch, den 30.07.2008, 13:11 -0400 schrieb Willie Walker:
Alexander Jones wro
Excellent discussion so far. I'm going to write up a summary shortly.
Just to clarify one thing, though, especially since this has come up
more than once (at least in e-mail to me):
The only downside I found when using GNOME with a11y enabled on my
system was that somehow the mousekeys were e
reputation for being
heavy. However, if a11y goes unused there shouldn't be any created.
I've cc'd Mark Doffman for his imput as he's probably got the most
experience profiling current AT-SPI behaviour.
Rob
Willie Walker wrote:
The way accessibility support works
Willie Walker wrote:
Excellent discussion so far. I'm going to write up a summary shortly.
Here's what I'm seeing from this good discussion:
PRIMARY ARGUMENTS AGAINST ENABLING A11Y BY DEFAULT:
---
1) Performance. From recent
Wow - that polling really does bite. :-( Looks like it's been in there
for 6 years!
http://svn.gnome.org/viewvc/at-spi/trunk/registryd/deviceeventcontroller.c?revision=326&view=markup
To me, it kind of seems rather inefficient for the prototypical use case
of mouse motion events, which is to
Yuan, is *very* good and is remarkable in his abilities
to diagnose and resolve problems.
Will
On Thu, 2008-07-31 at 17:56 -0400, Willie Walker wrote:
> Wow - that polling really does bite. :-( Looks like it's been in there
> for 6 years!
>
> http://svn.gnome.org/viewvc/at-sp
gation.
We'll get there, :-)
Will
Willie Walker wrote:
PS - Bug/RFE logged here:
http://bugzilla.gnome.org/show_bug.cgi?id=545849.
If there are other specific problems that people know about, I really
encourage them to log bugs. Otherwise, the team will likely not know
about them and the
Gestures are definitely a very good way to launch the assistive
technologies. The work Jon McCann and company are doing with
gnome-session and gdm should also make the gestures available in a
logged-in session as well.
Thanks!
Will
On Wed, 2008-08-06 at 17:29 +0200, Patryk Zawadzki wrote:
> On
Hi:
I know Jon McCann and company did some proactive work to include
accessibility in the redesign (thanks Jon!), but I'm not sure what the
status of that is. If they can show that accessible login works, along
with the keyboard/mouse/dwell gesturing mechanisms to launch assistive
technologi
achines anymore without jumping through hoops.
Will
Vincent Untz wrote:
Le mercredi 10 septembre 2008, à 09:39 -0400, Willie Walker a écrit :
Hi:
I asked this earlier, but I might have missed the response. Have the
accessibility issues been resolved with the new GDM? In particular,
embre 2008, à 17:23 -0400, Willie Walker a écrit :
Well...hmm...if I read the answers correctly, I think what I'm
hearing
is that there are a lot of great ideas, but they aren't done yet. If
this is the case, then I think this sounds like a regression.
I see nobody jumping in to say i
Brian Cameron wrote:
I'm not sure this is a really important regression. You can configure
the new GDM to always launch various AT programs as needed. The main
lost feature is that users cannot launch AT programs on demand.
I'm curious who the "you" is "you can configure." The important thin
While I disagree with Brian's assessment (I think he tends to lean more
to the 'it's OK as long as an able-bodied sysadmin can configure the
system for the disabled user' side than the 'let the user be
independent' side), I'll support the decision nonetheless.
Will
Vincent Untz wrote:
Le lun
Hi All:
We just branched Orca for GNOME 2.24. I forgot to do this when we
released Orca v2.24.0 (D'Oh!). orca/branches/gnome-2-24 starts with
Orca v2.24.1, which was created today.
Will
___
desktop-devel-list mailing list
desktop-devel-list@gnome.or
Hi Jeff:
My assumption is that http://live.gnome.org/RoadMap contains the plans
and that projects should add to this if they haven't created their road
maps yet.
Hope this helps,
Will
On Mon, 2008-11-03 at 17:57 +0800, Jeff Cai wrote:
> Hi,
>
> Could I get the information if not considering th
For me, one of the most important problems we face with WebKit is its
lack of accessibility support right now. I have a great fear that Alp
may have grossly underestimated the scope of the work. I have some
confidence, however, that the WebKit folks who were at GNOME Boston
should be able to do a
I would *love* to see this bug get fixed:
http://trac.galago-project.org/ticket/91
Will
On Thu, 2008-11-06 at 19:43 +0100, Cosimo Cecchi wrote:
> On Thu, 2008-11-06 at 17:00 +0100, Vincent Untz wrote:
>
> > I'm more worried about the fact that there has been no release since
> > early 2007 (if
ble these days, but I don't think we should be
too hasty here. If we going to switch let's do it for the right reasons.
[1] https://developer.mozilla.org/en/ARIA_User_Agent_Implementors_Guide
cheers,
David
Willie Walker wrote:
For me, one of the most important problems we fac
Hi Alp:
> I'm not sure what you think is being underestimated here. Instead of
> throwing our hands in the air and despairing at the size of the task,
> my company (Nuanti Ltd.) and I made the decision to make WebKit GTK+
> accessibility happen early in 2008.
I'm certainly not throwing my hands u
Some ideas for better handling of notifications can be found here:
http://live.gnome.org/AlternativeNotificationsUI
it looks nice, but where would immediate-action-required notifications
be shown? Things like 'your battery is about to die'?
Stay-on-top, non-focus-stealing dialogues without any
Believe me, if I had direct control over it, I'd hire Joanie in an
instant. She's an awesome contributor and is the type of person every
project needs.
Will
Joanmarie Diggs wrote:
For whatever it's worth:
Joanmarie Diggs works for Sun on accessibility (mostly Orca).
I happen to be a volu
Someone on the Orca list mentioned something about gnome.org having no
TXT record:
"[etha...@moiraine ~]$ host -t txt gnome.org
gnome.org has no TXT record"
I don't know what a TXT record is, so I'm not sure how that would help.
But, the user certainly seemed adamant that gnome.org sho
+1 -- I'm very excited about this. Many thanks to the people involved
who have the energy and courage to pull this off.
Will
On Feb 10, 2009, at 8:48 AM, Luis Villa wrote:
On Tue, Feb 10, 2009 at 4:14 AM, Ara Pulido wrote:
Hello,
We are proud to announce that a new GNOME team has been cre
Hi All:
The ditching of Bonobo goes beyond AT-SPI. It also has an impact on
gnome-speech and gnome-mag. This is a fair amount of work to pull off
and we currently have a dearth of resources to do the work.
We're not at the "uh oh, we're completely screwed" point yet, however.
The good thin
SPI_ methodsAccessible* methods
dasher 5 9
mousetweaks 7 22
gok 15 78
libcspi 29 230
A subset approach makes a lot of sense. I also wonder, however, if just
doing directly
Vincent Untz wrote:
team will roll tarballs for those modules. Volunteers to help roll
tarballs are welcome.
...
gnome-mag 0.15.4 0.15.4
I've checked in NEWS and README changes into trunk and I have a
gnome-mag-0.15.5.tar.gz on master.gnome.org ready for an install-module
Vincent Untz wrote:
Hi all,
Here's a list of modules that didn't see a release since quite some
time. It'd be nice to be sure that they either had no change at all, or
that someone rolls a tarball for 2.26.0 in 10 days.
Note that if there's no news for a module before March 16th, the release
te
Hi All:
Orca has branched for gnome-2-26. The branches/gnome-2-26 branch will
be used for continued GNOME 2.26.x release and trunk will be used for
the GNOME 2.27.x release series.
Will
___
desktop-devel-list mailing list
desktop-devel-list@gnome.o
1 - 100 of 129 matches
Mail list logo