[orca-list] Fwd: Re: Status of Jokosher accessibility?

[Nolan Darilek <nolan thewordnerd info>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Oopse, I always forget which of my lists sets which reply-to setting.
Sent this earlier today.



- -------- Original Message --------
Subject: Re: [orca-list] Status of Jokosher accessibility?
Date: Sat, 21 Aug 2010 11:49:02 -0500
From: Nolan Darilek <nolan thewordnerd info>
To: Mike Sheldon <mike mikeasoft com>

Sorry for the delay in responding. I just received my recording hardware
yesterday, so now am interested in finding apps with which to edit/mix.

I'm playing with stock Jokosher from Lucid, which seems quite
accessible, though unfortunately doc.jokosher.org appears down at the
moment so I can't determine whether the issues I am having are
accessibility ones or user error.

Out of curiosity, if the accessibility changes you made don't break
anything else, might they be merged into the main branch? Or have they
been already? Even if there are issues needing to be worked out,
committing the changes to trunk would at least make them available both
to end users, and to anyone wishing to continue the work later.

Thanks, I'm really excited about the increased accessibility in the
Linux audio editing space. When I did this same thing a few years ago,
my choices were Audacity and that was it, and while it does seem usable
now that I experiment with it more, that it was written using WX would
seem to place hard limits on what can ever be accomplished with it. It's
also cool that you've taken the time to join and monitor this list.

I've been looking into Ardour, and maybe they have lurkers here too, but
while it seems accessible at first glance, I ran into some showstoppers
that I may post about here in a later message. While I'd like to file
issues with them, their Mantis requires a CAPTCHA, and while I can
defeat those, I don't have the patience to right now.

So, thanks again.

On 08/10/2010 06:01 AM, Mike Sheldon wrote:
> > Several months back, there was dialog about improving Jokosher
> > accessibility, with a few tangible suggestions from Orca users. I was
> > just wondering if those changes were ever incorporated anywhere, even
> > if only in BZR for the moment?
>
> Some changes were made in this branch:
> https://code.launchpad.net/~michael-sheldon/jokosher/accessibility
>
> Unfortunately the main bulk of the work has stalled due to us running
> into some problems creating custom ATK objects with PyGTK (see here:
> http://www.mail-archive.com/pygtk daa com au/msg19260.html for further
> details). I've been rather busy the past couple of months so haven't had
> a chance to pursue this any further. I don't think I'll get much of a
> chance to look into it again until after we've finished reviewing and
> merging the work from our summer of code students, but we do still plan
> on improving our accessibility when time allows.
>
> Cheers,
>  Mike.
>
> _______________________________________________
> orca-list mailing list
> orca-list gnome org
> http://mail.gnome.org/mailman/listinfo/orca-list
> Visit http://live.gnome.org/Orca for more information on Orca.
> The manual is at http://library.gnome.org/users/gnome-access-guide/nightly/ats-2.html
> The FAQ is at http://live.gnome.org/Orca/FrequentlyAskedQuestions
> Netiquette Guidelines are at http://live.gnome.org/Orca/FrequentlyAskedQuestions/NetiquetteGuidelines
> Log bugs and feature requests at http://bugzilla.gnome.org
> Find out how to help at http://live.gnome.org/Orca/HowCanIHelp

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkxwCkEACgkQIaMjFWMehWLRLACeMV3OsNrhWKhUTQO2qX9hbYiA
RfIAn1EhknO1kJYtuvq5aPPyi7mp1ziR
=RSWW
-----END PGP SIGNATURE-----