Ok, I might check that out, but, yes, if the resulting interface doesn't
currently provide forms of accessibility interaction in the end result,
I wouldn't be able to take it too far.
On that note, there's recently been a new screen reader for the android
platform that's not based on talkback's open-source image, like
samsung's voice assist, and works via a slightly different approach,
including allowing forms of real-time on-screen OCR, and, it has two
names - commentary and/or Jieshuo, which is a chinese name, and, partly
since it's being developed by a chinese developer, it's not available
via playstore, but anyway.
Stay well
Jacob Kruger
+2782 413 4791
Skype: BlindZA
"...resistance is futile...but, acceptance is versatile..."
On 2020-11-17 04:15 PM, Gabriel Pettier wrote:
Thanks for sharing your feedback about kivy, though i would like to
clarify that sounds like misconceptions to me.
- Kivy is not based on tkinter, and doesn’t use it, it implements its
own widgets, based on opengl, you might be thinking about pygame, that
we used as a provider years ago, but these days we are not dependent
on it at all, and use SDL directly.
- Kivy doesn’t use a graphical designer, you might be thinking of
things like Glade (for gtk) or QTDesigner (for qt), while some users
have been asking for such a designer, there is no effort to develop
one currently, and we do encourage people to learn kvlang, which is a
yaml-like declarative language to create your UI, you can also use
python directly, but using that dsl does simplify a lot of things.
- Regarding accessibility, i’ll concede that’s a downside on kivy’s
side, we don’t have any integration allowing screen reader to work
with the app, we do have some ideas about how to solve that, there has
been discussions for example in issue 5836
<https://github.com/kivy/kivy/issues/5836>[1] but as far as i’m aware,
nobody is currently working on that, i agree this is a shame, but it
does require a core dev to have both the time (and we are short on
that) and access to users of these software, the former is certainly
more of a blocker than the latter.
[1] https://github.com/kivy/kivy/issues/5836
Le mar. 17 nov. 2020 à 12:47, jacob kruger <[email protected]
<mailto:[email protected]>> a écrit :
I am referring to the fact that toga's layout literally stems from
layout-by-code - add a container to the main window via code, add
elements to it, etc. etc. - no graphical design required as such.
As in, while have worked using a similar process in the past,
making use of wxPython, the ones that might require me to have
done graphical layout design, using forms of drag-and-drop would
be a no-go from my side.
Stay well
Jacob Kruger
+2782 413 4791
Skype: BlindZA
"...resistance is futile...but, acceptance is versatile..."
On 2020-11-16 06:36 PM, Matthew Einhorn wrote:
On Mon, Nov 16, 2020 at 4:46 AM jacob kruger <[email protected]
<mailto:[email protected]>> wrote:
Hi there
Will just mention that while haven't tried out kivy for quite
a while, if, as I think, it uses tkinter, then it would be a
no-go from my side.
Hmm no it doesn't use tkinter in any way!?
And, FWIW, that's since I am myself a 100% blind software
developer, and, certain forms of GUI modules don't cooperate
too well with assisstive technology such as screenreaders.
This is also where the command line interaction with beeware
and it's briefcase suit me nicely, as well as where the toga
layout-by-code also suits me in terms of the development
process, and, the first thing I made sure of was that the
generated android app was accessible while working with the
android talkback screen reading software.
I'm not sure what you mean by command line/layout-by-code. Do you
mean it's not a WYSIWYG? I don't think any of the python GUI
packages I'm aware of (e.g. kivy, qt etc.) are WYSIWYG as they
all rely on layouts to place widgets. But yeah, Kivy's built-in
widgets do not have an accessibility API so I don't think the
generated apks are accessible in that way AFAIK.
Matt
_______________________________________________
Mobile-sig mailing list
[email protected] <mailto:[email protected]>
https://mail.python.org/mailman/listinfo/mobile-sig
_______________________________________________
Mobile-sig mailing list
[email protected]
https://mail.python.org/mailman/listinfo/mobile-sig
