GNOME.org
 

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

I hadn't thought of that! It makes sense.
On 6/20/21 12:49 PM, Linux A11y wrote:

Howdy José,

You can figure what version you are using currently by pressing orca +w. This is currently hardcoded to an 
test plugin what speaks the clipboard. Orca master doesn’t offer this currently.

Cheers chrys



Am 19.06.2021 um 16:02 schrieb José Vilmar Estácio de Souza <vilmar informal com br>:

Hi Chrys.
I have noticed this problem since the older versions of orca. I don't think it would be easy to find the 
commit that introduced this problem using bisect.
Anyway, I'm going to see if I can find a way to reproduce the problem and see if the debug has something that 
might help.

I would like to take the opportunity to suggest that in the version presented by orca, an information was 
added that we are using the version of orca that implements plugins.
The information presented by orca is activated by pressing orca_keh+h.
I usually put my machine in hibernate mode and I end up forgetting which version of orca is active.

Thanks and congratulations for the excellent work.


On 6/18/21 6:32 PM, chrys wrote:
howdy José,

yea i see this here as well while programming and testing. i thought this would be normal. also if it does 
not always happen.
maybe can you bisect this?

cheers chrys


Am 18.06.21 um 19:33 schrieb José Vilmar Estácio de Souza:
Hi Chrys, works for me.


Just for the record, one thing I've noticed about orca is that every now and then, when exiting the 
preferences screen with the esc key, the orca takes at least 5 seconds to get back up and running. This has 
nothing to do with the implementations made by Chrys as it has been happening for some time.


On 6/18/21 12:10 PM, chrys wrote:

Howdy Patrick, Howdy storm,

i found and fixed the issues. i forgott to migrate some bits :).
please pull and retry.

Am 18.06.21 um 15:22 schrieb Patrick ZAJDA:

Hi chrys,


It is 991a99a78479c4dff524c35798f3c26c2d9e1c63

Which has the same commit message as e868211f43d9b0d8cb8399c23742882b724a3e46 where make install fail.

That is why I supose it is the first commit I told.


HTH,


Patrick


Le 18/06/2021 à 14:43, chrys a écrit :

Howdy Patrick,

you say since this morning,
are you able to bisect the commit what breaks mate-panel for you?

Am 18.06.21 um 13:12 schrieb Patrick ZAJDA:

Hi Chrys,


I pulled this morning and since this, I cannot use Alt+F1 (on Mate) anymore. Arrows does not make Orca 
announcing anything.

Revision: fcda9658e7c957f6b1169de1361fa9d4dcc2d192

When switching to Orca Master, revision b379c1a8453832fc871c67703297551dd46fdc55 all is OK.


Another question about the plugin system itself: are plugins placed in the user directory (in the plugins 
directory) supposed to work?


Best regards,


Patrick


Le 17/06/2021 à 23:27, Linux A11y a écrit :

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

--
Patrick ZAJDA



--
Patrick ZAJDA


_______________________________________________
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
[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]