Push to GitHub 2022-11-24 #28
Conversation
|
Great news, thanks for this! Hope it will be merged soon. |
|
Seams there is major issue with this push. Google forgot to include source code of screenunderstanding library, there is only prebuilt .arr file. |
|
What's the issue and where can I see it? |
|
It is precompiled library with obfuscation enabled, so to be clear and fair TalkBack is becoming more and more closed-source. @thestinger could you explain it better with licensing issue background? |
|
I will check how to replace this library by the source codes. |
|
@JackyKaoGoogle is there any progress? i'm now learning internals of talkback to optimize it for specific android device. Could you please state a clear official position on screen understanding library so we can clearly understand what is happening with that? Why it is closed source? |
|
We moved to GrapheneOS being based on this and there are substantial issues with it. People are reporting that the Braille keyboard doesn't work anymore. It's not a good situation. We aren't sure if we can safely downgrade it. |
|
Thanks all. |
|
@JackyKaoGoogle Is the open source talkback going to continue to receive updates, or is that ending? If it depends on this library and it can't simply be omitted, does that imply the open source releases are ending? |
|
Yes, the open source releasing is ending. |
|
That's extremely disappointing. It would have been nice if Google released more of the accessibility services as open source and provided more frequent updates for them instead of moving away from it. |
|
I'm confused about this since bdead86 was pushed. |
|
We don't move away this new updates, and just release this version to open source through another way. I release the same version without this library to open source directly after I got the right for releasing codes for the google/talkback project. |
|
@JackyKaoGoogle why open source google/talkback doesn't include braille display implementation? only stub class why does absolutely nothing. I think it is a bit unserious doing such things and not telling anything somewhere. |
|
My guess is that Google is keeping new implementations they make, for stuff like Braille displays, proprietary. This really isn’t good for AOSP based Android options. If I as a blind person want to mod a Pixel use a different ROM when support ends, I should be able to have a complete, and modern, TalkBack version. The Fuchsia team is doing everything in public. Why not do Android accessibility the same way?
Devin Prater
***@***.***
Https://write.as/devinprater
… On Jan 6, 2023, at 5:38 AM, Beqa Gozalishvili ***@***.***> wrote:
@JackyKaoGoogle <https://github.com/JackyKaoGoogle> why open source google/talkback doesn't include braille display implementation? only stub class why does absolutely nothing.
I think it is a bit unserious doing such things and not telling anything somewhere.
people are not PIGS to behave like talkback team is behaving.
—
Reply to this email directly, view it on GitHub <#28 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADUMTTWOSFQJ5AYSN44O5YTWQ774HANCNFSM6AAAAAASK33T3M>.
You are receiving this because you are subscribed to this thread.
|
|
The reason is Braille display was announced in July 2022, so the open-source might haven't included it. |
So just to be clear here, will talkback releases continue to be made here? Or is that going to end? If it is going to end, when will that be? |
|
We wil release the TalkBack directly, and won't use the "Pull Request" way! |
Ah, so Google does intend to push future releases of talkback to the main branch of https://github.com/google/talkback ? This is not stopping? |
|
Yes, we will push future releases of talkback to the main branch of https://github.com/google/talkback! |
|
@JackyKaoGoogle |
|
This would indeed be great. Not only would this improve the developer community around TalkBack and Android accessibility, but the much wider blind community can provide diverse perspectives, from long-time Android users, to iOS converts, to people new to smart phones in general. I’d love to see Google consider the community of blind Android users further.
Thanks so much for communicating with us on this.
|
|
@JackyKaoGoogle Any update on this?
|
|
@JackyKaoGoogle hello. Are there any news about next open-source talkback release? There are interesting features which we want to have in open-source builds. Thanks. |
|
@beqabeqa473 exactly. |
@JackyKaoGoogle Any updates here? Looks like this repo hasn't been updated in 2 years. |
|
@JackyKaoGoogle @simplexatg @ChadBrowerAtGoogle It's been over a year without any pushes to GitHub for the TalkBack source code. We're eagerly awaiting your contributions, especially with the absence of releases in the v14.x range. Please prioritize pushing the latest changes. Thank you. |
|
@JackyKaoGoogle @simplexatg @ChadBrowerAtGoogle joining to this discussion. Here is an android device in the work which will use talkback, but it was not updated for a while. Please pay an attention to 3rd-party devs and push latest changes. |
|
hello @JackyKaoGoogle @simplexatg @ChadBrowerAtGoogle Sorry for mentioning you in closed pull request, this is because there are no issues permitted and this pr is most applicable for this kind of thing. Could you please tell us when tb 15 will be pushed to github? |
No description provided.