Re: [orca-list] Small status update for plugin system based orca

["Andy Borka" <sonfire11 gmail com>]

This happens in Gnome 4 whether I use the new orca plugin version or the
original 40.1 from master version. Neither version starts on the signin
screen or automatically turns on after login.



-----Original Message-----
From: orca-list <orca-list-bounces gnome org> On Behalf Of José Vilmar
Estácio de Souza
Sent: Thursday, June 17, 2021 11:46 PM
To: Linux A11y <chrys linux-a11y org>; orca-list <orca-list gnome org>
Subject: Re: [orca-list] Small status update for plugin system based orca

Hey chrys.

I did a quick test and found that when I access the orca preferences screen
and change pages by pressing left arrow, right arrow or ctrl+pageup/down,
orca doesn't announce the name of the new page .
Thanks.


On 6/17/21 6:27 PM, Linux A11y wrote:
> Howdy List,
>
> A small update of my current work on an plugin system based orca.
>
> - i merged in all of Joanies work from master (till 1:00 PM UTC June 17
2021). So the plugin system branch is on pair with orca master.
> - i created an SignalManager. This component is, like the name says, used
for register and emit signals or check for its existence. So we can define a
set of signals what plugins can connect to or plugins can register and emit
signals by there own.
> - dynamic API manager: well sounds mystic, but the idea behind is that 
> plugins can register own API, objects, functions, variables and all 
> kind of that. So others can consume those and/ or  extend its 
> functionality based on it
>
> Both objects live in our shiny new orca class.  The orca class should hold
all basic components and all needed API, as goal, all orca code should in an
roof or main class. So we can easy share its API with plugins or let them
extend it.
> I also placed the scriptmanager-, eventmanager-, settings manager classes
there (also if they should be reworked to fit better in shape) and the
plugin system manager. So the way to use ocas API will just happen starting
from that class containing all API, settings and states.
> - i just started implementing an very basic plugin manager. But this is
not useable yet. I will inform as soon as it is ready for testing.
> - i also started with an base class for orca plugins, but here i have 
> some trouble with get mixed plugin objects in libpeas ( they all 
> register just fine, but deregister all as clipboard plugin. Not sure 
> what mix it up, but i will figure anytime lol)
>
> - we already have some early adopters for testing to warranty we don't
break anything. Thanks to Patrick and storm here for much needed testing!
>   
> Current goal is just to bring an basic plugin structure in without break
anything. No new settings, no real new functionality. All should just work
as it is.
> Cheers chrys
> _______________________________________________
> orca-list mailing list
> orca-list gnome org
> https://mail.gnome.org/mailman/listinfo/orca-list
> Orca wiki: https://wiki.gnome.org/Projects/Orca
> Orca documentation: https://help.gnome.org/users/orca/stable/
> GNOME Universal Access guide: 
> https://help.gnome.org/users/gnome-help/stable/a11y.html


_______________________________________________
orca-list mailing list
orca-list gnome org
https://mail.gnome.org/mailman/listinfo/orca-list
Orca wiki: https://wiki.gnome.org/Projects/Orca
Orca documentation: https://help.gnome.org/users/orca/stable/
GNOME Universal Access guide:
https://help.gnome.org/users/gnome-help/stable/a11y.html