Re: [orca-list] Is Orca support plug-in architecture ?
- From: Peter Vágner <pvdeejay gmail com>
- To: Thomas Ward <thomasward1978 gmail com>, orca-list <orca-list gnome org>
- Subject: Re: [orca-list] Is Orca support plug-in architecture ?
- Date: Wed, 10 Sep 2014 16:16:10 +0200
Hello,
A bit of speculation on this topic from me as well.
If you were about to create so called portable orca you would have to
statically link all the libraries and include all the orca requirements
and made one huge package of your results. This is highly inpractical on
a modern linux distributions where all the orca requirements are
packaged as a distrospecific packages.
I feel orca is minimalistic in size, in terms of its enviromment, slick
on performance etc. It's really powered by the accessibility API's and
libraries it interfaces to. There is less space to workaround OS
specific issues and / or inovate on this front since doing so is
pointless because on linux issues can be usually addressed where they
are coming from not frequently worked around. There are just a few hacks
here and there temporarily overcoming inaccurate or missing events found
in orca source code as far as I know. Terms and approaches towards
portable, isolated, self contained, in process etc .... stuff are all
concepts you may have noticed when watching e.g. NVDA development on
Windows however these concepts are really difficult or close to
inpossible to carry over to orca I believe because of the things I have
just mentioned.
If you were about to add some real features to orca you can either write
a patch I think if it was usefull we would be all keen to have it
included as soon as possible.
Additionally there is orca_customizations.py file where you don't have
strict API to follow however you are having access to orca internals and
you can add whatewer custom scripts bound to keyboard shortcuts and I
haven't really tested this my-self but I guess you can also override
some events virtually doing the same thing toolkit and / or app specific
orca scripts are doing.
So I think there is a way we just need to get motivated to make some
good use of it and be creative to inovate.
So technically all what NVDA plugins can do on Windows should be also
possible with orca on linux however we don't have a nice user centric
interface for managing addons.
Greetings
Peter
On 10.09.2014 at 15:28 Thomas Ward wrote:
Hi,
Yeah, there is no registry in Linux. That is a Windows concept, and
one I am glad Linux has not emulated.
Cheers!
On 9/10/14, Alex Midence <alex midence gmail com> wrote:
I do not think that Linux has a registry. That is a Windows concept.
Sent from my iPhone
On Sep 10, 2014, at 7:41 AM, Dhairyashil Bhosale
<dhairyashil bhosale584 gmail com> wrote:
Hi all,
hi henry , portaable means , which translates into the fact that it does
not need installation and can be carried on a removable drive and launched
on any machine without affecting the registry.
_______________________________________________
orca-list mailing list
orca-list gnome org
https://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
Log bugs and feature requests at http://bugzilla.gnome.org
Find out how to help at http://live.gnome.org/Orca/HowCanIHelp
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]