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]
https://mail.python.org/mailman/listinfo/mobile-sig
