Wooshy.docs
Wooshy.docs copied to clipboard
godbout
Non-native App - Zotero
Many thanks. There are some issues (not all text readable) still, please see below:
yeah Wooshy needs the app to expose its data. Zotero seems to be a really not standard app (Java?) so i think what you're getting now is only what is accessible. the rest is not.
have you tried with other tools, like Vimac? how does it do.
i can investigate more, but i need data inside Zotero. i've tried to add stuff but i just don't get it. is there a feed or something you can give me to populate that thing? thanks.
I tried Shortcat and Homerow with the exact behaviour. Surely a Zotero problem then. I'll open an issue with Zotero if they suggest anything.
Thanks for looking into it in detail.
@hasantahir if you want, paste here the link to the issue you fill with them so that we can follow. you can also send them here for a discussion. thanks!
I have opened a Github issue here and a discussion on their forum here. I don't have the privilege to post on their developer mailing list.
Got a response from them and quoting it here:
It should work as well as it works in Firefox 60 ESR. Firefox 60 didn't support VoiceOver very well, so to the extent that the apps rely on the same macOS accessibility APIs, they might not work that well with the current version.
If it works better in Firefox 102 ESR, it will work better in Zotero 7 later this year.
Probably not that — see my update and https://github.com/zotero/zotero/issues/2734.
Also, @godbout, are you only activating on certain bundle identifiers? If so, would you mind adding org.zotero.zotero-beta, org.zotero.zotero-dev, and org.zotero.zotero-source so this works in our dev builds and for our beta-channel users?
Also, @godbout, are you only activating on certain bundle identifiers?
yes. i can't find a reliable way to avoid blasting every app with special AX attributes, and because i need to curate apps for kindaVim that requires way more AX info, i'm using the same catalog for Wooshy. so yeah, i curate the apps. keeps Wooshy fast and not resource greedy.
If so, would you mind adding
org.zotero.zotero-beta,org.zotero.zotero-dev, andorg.zotero.zotero-sourceso this works in our dev builds and for our beta-channel users?
will absolutely do. i'm not familiar with Zotero. any place where i can download the apps that hold those three bundle identifiers? for a try first. thanks.
It's the exact same app, so nothing to check — we just assign different bundle identifiers to our different update channels (e.g., our beta channel).
It's the exact same app, so nothing to check — we just assign different bundle identifiers to our different update channels (e.g., our beta channel).
thank you so much for taking the time and energy to answer that very dumb question 😂️ can't remember what i was thinking at the time. maybe i wanted to check the bundle identifiers myself because of a lack of trust 👀️
will add for the next alpha release (probably later today).
It's the exact same app, so nothing to check — we just assign different bundle identifiers to our different update channels (e.g., our beta channel).
oh i remember now. not so dumb anymore! i need to get the bundles and try, to get the correct name to show in kV etc. thanks.
like they could have the same name but they could have different ones. i had the case (Discord?) where each channel was using a different name.
ok i'm seeing the beta and the official build use the same name. gonna use the same then for the beta, dev and source, at least for today's release. can be changed later.
@hasantahir can you try a16 and see if it works better with Zotero? https://github.com/godbout/Wooshy.docs/releases/tag/1.a16
thanks.
Thanks, @godbout for the update. Unfortunately, similar issues are being observed in Zotero. Neither the Items pane (papers list in the middle) nor the Collections Pane (list on the left) is accessible in a16.