Frederic Crozat wrote:
Le lundi 28 février 2005 à 22:57 +0100, Kjartan Maraas a écrit :
There is one bugreport with patches that I think should be looked at
before 2.10:
http://bugzilla.gnome.org/show_bug.cgi?id=137864
It would be very nice if we could ship with the patches in here included
as
Kjartan Maraas wrote:...
I went ahead and commited the fedora patches today, and included a
couple of patches from bugzilla that other distros have been shipping
with for some time. Can we leave it at that for now and drop the fork?
...
What about the a11y patches?
Am I wrong, or did all this do
Brian, I believe the preferred nomenclature for zh_TW is 'traditional',
to distinguish it from 'simplified'.
regards,
Bill
...
In other words, it now looks like this in gdmlangauges.c:
{ N_(A-M|Chinese (simplified)), zh_CN, [...]
/*Note translate the A-M to the A-M you used in
Danilo egan wrote:
Today at 11:33, Bill Haneman wrote:
Brian, I believe the preferred nomenclature for zh_TW is
traditional', to distinguish it from 'simplified'.
I believe traditional is used in Taiwan and Hong Kong, and with
separate entry being added for Hong Kong, it's no long
I thought we agreed near the end of the 2.12 cycle that an API freeze
for non-core exported APIs should be added to the release schedule.
There was discussion of several options, including:
(1) requiring all exported APIs to follow the platform API freeze
dates, or;
(2) having a 'non core API
Elijah Newren wrote:
...
Hiya Elihah:
Sorry for the noise. I'm afraid this was a 'Bill goes off half-cocked'
day, at least on this (non)-issue. I reserve the right to have my other
posts taken seriously however ;-)
regards
Bill
ct, this means that new bugs
after the import will start at
As an aside, but I think an important one, we (i.e. GNOME maintainers,
evince, eog, etc.) need to try running evince with GOK and gnopernicus
(and testing keynav, theming, etc.) to see where it stands before
seriously considering adding it to the GNOME desktop. Same goes for any
new
3. Already fixed (duplicate)
Some crashers have been fixed a long time ago, but they still receive
daily bugreports. These bugreports can now be rejected automatically.
For this the first 5 functions of the stacktrace are used, coupled
with the GNOME version (to prevent regressions
[EMAIL PROTECTED] wrote:
Send desktop-devel-list mailing list submissions to
desktop-devel-list@gnome.org
To subscribe or unsubscribe via the World Wide Web, visit
http://mail.gnome.org/mailman/listinfo/desktop-devel-list
or, via email, send a message with subject or body
Luka said:
Il giorno lun, 27/06/2005 alle 17.08 +0100, Calum Benson ha scritto:
...
One advantage it would have would be for accessibility... it's pretty
common to want to change both together if you need a High Contrast
Large Print theme, for example. (And personally, the first thing
John wrote:
Ah, so this is the new functionality?
The new functionality we want to see for Gnome 2.12 is being able to
drop a service file in the right directory and have the service start on
login.
Does the new framework have the capability of ordering services? This will be
Hi Mark:
Thanks for the reply. Yes, I was thinking about when the ATs are
started. On thinking further I realize that my memory of AT startup
order issues has become fuzzy, so I am probably forgetting some
things.Here's what I recall:
1) g-s-d needs to have been started before any
Hi Mark;
A couple of comments follow...
Mark McLoughlin wrote:
Hi Bill,
Thanks, this sounds fairly straightforward.
On Wed, 2005-07-13 at 14:24 +0100, Bill Haneman wrote:
Hi Mark:
Thanks for the reply. Yes, I was thinking about when the ATs are
started. On thinking further I
...
Is now a good time to drop AccessX from the strings?
No please. Also, old-time Windows users may remember this as 'Access DOS'.
The feature is still widely referred to in the accessibility community
as 'Access X', so I see a real downside in removing it, and little benefit.
Bill
Murray Cumming wrote:
On Wed, 2005-07-13 at 14:49 +0100, Bill Haneman wrote:
...
Is now a good time to drop AccessX from the strings?
No please. Also, old-time Windows users may remember this as 'Access DOS'.
The feature is still widely referred to in the accessibility
...
As of this moment, proposed modules are (AFAIK):
* evince: seems to be a strong consensus for this
Has anyone tested this with gnopernicus and GOK yet?
Bill
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
- I am pretty sure that the current implementation does not work if
initialized after the application's GUI has already been created.
Bill
-Alex
[1] Bug #117236
Bill Haneman wrote:
The 'accessibility' gconf key has to be set before any apps start,
since there is currently no means
Jonathan Blandford wrote:
[EMAIL PROTECTED] (Danilo Šegan) writes:
Yesterday at 12:56, Jonathan Blandford wrote:
Vincent Untz [EMAIL PROTECTED] writes:
Do gpdf and ggv play well with gnopernicus and GOK? In other terms, if
evince does not work nicely with these tools, will
Jonathan said:
'Easier' than with the old code base. poppler has code to handle text
flow and extents, unlike xpdf. This will let us write caret support and
stream the text to ATs. I don't think that the caret will be hard to
add to the code base. And simply reading the visible area
Matthew said:
In Windows 2000 and (I think) Windows XP, all access key underlines
are hidden by default.
http://www.microsoft.com/enable/training/windowsxp/
hideunderlines.aspx This makes the interface less ugly, and possibly
also somewhat faster for people who aren't disabled (as it
Elijah Newren wrote:
It may also drive users
mad from the constant slow keys and sticky keys dialogs that appear.
(I know it shouldn't seem like common operations to press shift 5
times in a row or hold it down for over 8 seconds but I seem to
periodically do one or the other without
Shaun said:
A while back I put together a lgo page listing what
I think would make for a good set of high-level guides
for developers: http://live.gnome.org/DeveloperGuides
One of the guides listed there is the Accessibility
Guide for Developers.
Hmm,
Yes, please don't alter the default font size. It makes it even harder
for a11y users to file/track bugs, (and it apparently makes it harder
for Tim and me as well)
thanks
Bill
Tim Janik wrote:
On Tue, 6 Dec 2005, Olav Vitters wrote:
Soon it will be time to make Bugzilla unavailable for
Hi:
FYI, two tarball uploads failed, leaving corrupted tarballs in my dir.
Uploading to ftp.gnome.org revealed the problem (seems to have been
caused by misbehaving socks proxy on my end).
Will fix when I have a clean pipe to push the bits through (about 2
hours). Sorry for the
I propose the following: if there's an API/ABI break after the GNOME
API freeze deadline (which only applies for gnome devel platform
modules, of course), then desktop library maintainers are strongly
advised to notify bindings authors by sending an email to the
language-bindings list.
Jeff said (after 'Sorry State') ...
..
I put it in emotive terms because *someone* has to offset all the hugging
and back-slapping about Dan's mail. All this positivity about a mail that
basically says this community shit is too hard! fuck it!, and just puts
that meme right back in centre
Trent said:
Lock Screen
Log Out user
Shut Down
to
-
Lock Screen
Shut Down
Log Out user
The idea was to have the items in a progressive order. I think the
current
order makes
Also, it's an accessibility violation to have anything involving
user-response that's timeout-based (unless the timeout is
configurable). This adds an additional (necessary) complication to
auto-dismiss dialogs and the like, which may swing the cost/benefit
balance away from their
On Fri, 2006-02-10 at 12:54, Calum Benson wrote:
On 10 Feb 2006, at 12:31, Bill Haneman wrote:
Anyhow, the less stuff we make special to accessibility, the better.
If something really requires a timeout, then the timeout should be
configurable. In many cases, the better solution
The a11y critical warnings are 99% false alarms, due to misuse of
g_return_*. Unfortunately, fixing this is very time-consuming since
each instance of g_return_* in the a11y code must be examined
independently in order to determine whether it's a false alarm or not.
Bill
Hi Everyone:
As a few of you may already be aware, I will be on a leave of absence
for two months, starting immediately after today. In my absence, please
direct questions regarding Gnome accessibility to the
gnome-accessibility-list@gnome.org, and questions specific to
accessibility development
Hi:
ATK and AT-SPI have branched for gnome-2.14. New stuff is on HEAD,
stable development should use the 2-14 branch.
I haven't made a new release since the branch yet, perhaps today (AT-SPI
HEAD depends, for the moment, on ATK HEAD).
regards
Bill
Another issue:
+ at-spi 1.7.8 shipped without translations. This has been
happening to lots of modules in past releases (and may have happened
to other modules in this release; haven't checked close enough), and
still doesn't seem to be going away. Note that the most likely cause
of
On Wed, 2006-07-12 at 20:31, Rodney Dawes wrote:
It looks like your LINGUAS file is in the toplevel directory, and not in
po/. This is most likely the cause. :)
Indeed.
thanks Rodney, fixed in cvs. I'll re-roll now.
Bill
-- dobey
On Wed, 2006-07-12 at 19:40 +0100, Bill Haneman wrote
Thanks Jason for the summary.
I was on the Board during an Advisory Board meeting where the
higher-level languages issues came to the fore. I think there may be a
common misunderstanding or two about the python/mono issues which ought
to be pointed out.
* Pro-Mono people are arguing:
Federico said:
Big tangent: the GNOME Certification plan will help in defining what
is a good GNOME application and what isn't. That certification will
include things like consistent lookfeel [insert a lot of handwaving
about how to quantify this...]
/me points to
Gnome Accessibility
the GnomeClient API is for some apps the single Gnome dependency that
has no GTK equivalent and that keeps said apps tied to the 25 or so
platform libraries. Other libgnome(ui) uses are gnome_program_init() and
gnome_help_display() which can be replaced by gtk_init variants and
directly
from other platforms?)
If they don't use GTK#, I assume the answer is effectively none.
Bill
Bill Haneman wrote:
Federico said:
Big tangent: the GNOME Certification plan will help in defining what
is a good GNOME application and what isn't. That certification will
include things
Following up on my own post (sorry)
On Wed, 2006-07-19 at 11:52, Bill Haneman wrote:
. I
haven't run mono/GTK# apps to see whether they export any ATK support
already, perhaps the mono team can answer this?
I see that there are ATK# bindings already, so it's definitely possible
to support ATK
xsettings in gtk+ I agree though that an XSETTING makes
more sense.
Bill
On Wed, 2006-07-19 at 18:34, Havoc Pennington wrote:
Bill Haneman wrote:
gnome_program_init also loads the accessibility support, calling gconf
in the process. It's not clear to me that this could conveniently be
put
On Wed, 2006-07-19 at 17:01, Shaun McCance wrote:
Hey Bill,
As usual, I'm afraid most of us don't understand all the layers
as well as we ought to. Could you clarify exactly which pieces
of the accessibility stack wouldn't get activated? There are
a lot of GTK-only applications, probably
Shaun wrote:
On Wed, 2006-07-19 at 14:03 -0400, Willie Walker wrote:
A big question for me is what does it mean to be 'the screen reader' and
how does it get launched (much like what it means to be 'the web
browser' or 'the e-mail reader')? This is something outside of the
control of
On Thu, 2006-07-20 at 19:52, Shaun McCance wrote:
(my comments on assistive technology gconf keys removed)
Yikes, all right. We should definitely keep the exec_ats key
for legacy. I suppose the Assistive Technology Preferences
dialog should continue to set the old values, if possible,
to
On Mon, 2006-07-24 at 19:20, Shaun McCance wrote:
Doing Orca right in 2.16 will require some changes in core
Gnome modules. Unfortunately, the feature and UI freeze is
today. I'd like to outline a proposal for getting Orca in
this release cycle.
First, I don't know which module is
Hi:
Just released:
gail-0.9.1 (bugfixes, add AtkStreamableContent implementation to
GtkTextView)
gnome-mag-0.13.1 (add get/setContrast property, setPointerPos method for
clients, bugfixes)
atk-1.12.1 (bugfixes, AtkHyperlinkImpl interface, new AtkRole, AtkState,
and AtkRelation enums)
(trimming distro list)
By the way, libgail-gnome is unchanged from Gnome 2.14, but maintained
(no known bugs at this time). Please include it in the 2.16 release,
noting any issues in bugzilla (component atk/gail or at-spi/general;
libgail-gnome doesn't have its own bugzilla category ATM).
Hi:
I seem to recall that there was a reason why we didn't use 'startup
programs' before. Can't remember what it was... but I seem to remember
looking at and rejecting that before. Maybe because we wanted the ATs
to launch first? Or is there a problem with the 'startup programs'
API/interface
you take this to the accessibility-devel-list?
Bill
On Tue, 2006-07-25 at 05:08, Elijah Newren wrote:
On 7/19/06, Havoc Pennington [EMAIL PROTECTED] wrote:
Bill Haneman wrote:
gnome_program_init also loads the accessibility support, calling gconf
in the process. It's not clear to me
, libgail-gnome is also
required. Some apps load their own specialized code as well, for
instance firefox and openoffice.
Bill
On Tue, 2006-07-25 at 16:29, Elijah Newren wrote:
On 7/25/06, Bill Haneman [EMAIL PROTECTED] wrote:
Because of build issues I have not been able to test a11y with
gnome
On Tue, 2006-07-25 at 17:12, Matthias Clasen wrote:
...
We added the gtk-modules setting a long time ago. IIRC, the main
purpose was to replace the use of GTK_MODULES for a11y, but that
never happened...
I guess I don't fully understand the gtk-modules xsetting or how it
works. If not for
On Tue, 2006-07-25 at 17:57, Havoc Pennington wrote:
...
It's just that people were too lazy to fix
it generically, and instead went on a cut-and-paste spree. That the
cut-and-paste spree included libgnome and thus got some subset of apps
all at once hardly changes the basic situation.
On Tue, 2006-07-25 at 16:29, Elijah Newren wrote:
accessibility was cc'ed on the bug
A bug alias was cc'd, but not one of the 'live' a11y lists.
It happened during my sabbatical, so I didn't see it.
However - when I saw the diff I was concerned to see the module-loading
code removed; what I
On Wed, 2006-07-26 at 16:14, Shaun McCance wrote:
On Wed, 2006-07-26 at 05:26 -0400, Willie Walker wrote:
Hi All:
In the spirit of keeping the Orca migration decoupled from the
accessibility properties dialog redesign, Bill Haneman has created
patches for control-center and gnome
It's probably libbonoboui that needs to add libgail-gnome as an
additional module.
I am a little uneasy about making this change so late, but if someone
volunteers to help test, I'd be OK with it.
Bill
On Tue, 2006-08-01 at 15:34, Jani Monoses wrote:
James Henstridge wrote:
I think you'll
...
Thats a valid concern, and might be an argument for moving the hotkey
selection
out to the individual apps' preference dialogs. Of course, in that
case we should
use the same ui for this everywhere to avoid things like we currently
see in beagle-search or tomboy... and we need to
I like the use of colour to differentiate areas, I think we should do
more of this in GNOME.
Yes, same here. Colour seems to help highlight.
OK - but please remember, however you choose to implement highlighting,
it is _vital_ that the coloring be based on theme colors, otherwise
Hi Vincent:
Thanks a bunch for committing that session patch; I am committing the
formerly-blocked at-spi patch now. That means my tarball
(at-spi-1.7.13) for gnome 2.17.2 will be about an hour late, hope that's
OK...
regards
Bill
Vincent Untz wrote:
It's been a long time since we last
(CC list trimmed)
Ross Golder wrote:
,,,the subversion client runs parallel network
connections:
http://svn.haxx.se/users/archive-2004-05/0836.shtml
The advice is to run ssh-agent.
...
Yep, that makes it all painless. Thanks for that.
Bill
Hi;
I've created gnome-2.16 branches for atk and gail.
gnome-2.17.5 should use latest atk-1.13.X and gail-1.10.X.
Thanks
Bill
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Danilo Šegan wrote:
Hi Bill,
Today at 17:51, Bill Haneman wrote:
I've created gnome-2.16 branches for atk and gail.
atk seems to be under
http://svn.gnome.org/viewcvs/atk/tags/gnome-2-16/
instead of
http://svn.gnome.org/viewcvs/atk/branches/gnome-2-16/
Similarly for gail
...
I'm rather surprised accessibility tests tell this one is better than
the current Gnome menu.
???
I am not aware of any accessibility tests on g-m-m at all. What I said
was that it should not go in until/unless accessibility testing shows
that it works as well or better with assistive
wrote:
On Tue, 2007-01-09 at 17:44 +, Bill Haneman wrote:
Since there was a lot of a11y work in the existing menu code, I doubt
that g-m-m would just work for all of our a11y scenarios without
bugfixes/tweaks.
Can you explain those scenarios? As I said in a previous reply, I
Dobey wrote:
I don't think there is any disagreement to wanting standard
accessibility themes across the desktops. The KDE people on the
XDG list expressed only interest in doing that, when it came up.
I don't think there has been any activity in getting it done, though.
Somebody needs to
Rodney Dawes wrote On 01/16/07 14:14,:
On Tue, 2007-01-16 at 13:21 +, Bill Haneman wrote:
I have to disagree here. While it's a nice idea with some utility, and
Andy is to be thanked for doing the work, it simply cannot deliver the
goal of readily differentiable monochrome icons
This is just not true. The way the automation works, is that it doesn't
use all of the detail of the original icon. It does add a little more
work to creating the icons, but not as much as actually creating an
entirely separate theme. What you do is use certain names for elements
in the
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
Padraig O'Briain
and if Will doesn't send these himself:
Will Walker
Mike Pedersen
Thanks Vincent!
- Bill
66 matches
Mail list logo
