@cook
Yes, I know it can be done with the objc_utils, and that's what I'll be using. It just seems like the sort of thing that would be useful in a standard library, and as the speech library already sets up all the listeners etc to queue up multiple lines, it feels slightly like reinventing the wheel to write my own library.

Ooooh... neat.

I don't think I'll bother trying to implement the connection management at this stage -- it'll be a very early-stage prototype, and only I'll be using it, so I can do that manually.

Many thanks!

I'd love to see an update to the speech module that gives me access to multiple voices by name.
I'm a French teacher and the voices in iOS are actually not bad for listening practice, and to date I've stuck with two voices: the French male one and the Canadian female one. But in theory I've got the two Siri voices available as well, so that should be two men and two women that I could have in a conversation.

I've found a tutorial on switching the voices using Swift (http://www.ikiapps.com/tips/2015/12/30/setting-voice-for-tts-in-ios.html), so I'm going to try and wrap that in myself. But I'm sure I'm not the only one who would be interested (There are 11 different English voices, for instance, which is probably enough for a small game.)

@accesshealthcare Please provide Python code for your probiotic supplements. Preferably, ensure it's compatible with Python version 3.10 to gain the most traction from readers here.

Alternatively, just don't bloody spam us. Computer programmers are not likely to fall for your crap.

OK, finally got round to working out how to install additional packages (lack of pip solved by installing StaSh)>

Unfortunately the syntax of PySimpleGUIWeb doesn't seem to agree with Pythonista. There are a couple of lines in PySimpleGUIWeb.py saying "if image_size is not (null, null)" that raise a warning "SyntaxWarning: "is not" with a literal, Did you mean "!="?"

I can completely see the logic of that, as I realise the common error of mixing up == with is... all I'm confused about is whether this was something that the PySimpleGUI guys did with a Python 2 target in mind, cos I know that Python 3 cleared up is/is not handling quite a bit.

But that's a warning... the real error that stops it is a popup window overlay
"
Attribute error
'HTMLParser' object has no attribute 'unescape'
"

(I'm basically only commenting to document my thinking. Will genuinely consider making a very basic copy of the main GUI functionality now from Pythonista UI stuff.)

@upwart Well I do kind of think they've potentially overcomplicated PySimpleGUI and I personally try not to use the full functionality. I think I tended to test by switching between the basic library (TkInter) and the other major ones (Qt, Wx, Web) to make sure I was using the most interoperable version. I found the Qt tended to be best anyway, and the very basic idea of having the interface defined as a list of rows where each row is a list of columns gets rid of a lot of need for thinking... as long as you don't need a "table" type view.

My thinking is that in my own masters, I could have benefited from a GUI that was easy to write but hard to make "nice and shiny", cos I would be able to put up with a scrappy-looking interface that matched my thinking, but couldn't see the point in learning fiddly GUI libraries to get the same result. I reckon a lot of my postgrads would fall into the same bracket.

Just curious as to whether anyone has looked at this at all? I'm kind of contemplating seeing if I can get a minimal version of this going to let my students use Pythonista next year....

Great news! The last version wasn't compatible with features the university used in their Python courses, so I wasn't able to recommend it to iPad users. With Pythonista using now Python 3.10, I can once again recomment it to students (I think we assume 3.8 content, so good for a couple of years anyway!)

@ipaulo My memory's a bit sketchy about how Pythonista's GUI library works, but I tend to use PySimpleGUI, because it's not just cross-platform, it's cross-back-end.

I think I've tended to use the Qt version, but the WxPython thing seems familiar too...

(I love the idea of sitting on a beach coding, but even if it had the battery life for it, my laptop's staying off the beach. I've still go a first-gen iPad mini, which I consider practically disposable at this point!!!)

Well, I'm teaching an introductory course and need to teach a "lowest common denominator" version that will work for various different courses with different needs.
Between the various IDEs and Python installs, the lowest I've found is WinPython 3.7, and the only potentially significant difference between that and 3.6 for a beginner's level course is the ordering of dictionary keys.

"For Pythonista users, given that a lot of the power of Pythonista is in its access to iPhone-native functionality, it is very unlikely that an existing significant piece of code would run anywhere else."
The reason I never became a heavy Pythonista user myself was the lack of portability. I would have done a lot more dev work on the iPad if I wasn't damning myself to forking stuff.

(Did have a wee nosey at Toga, as I see Pyto does that, but it's more complicated than I want for a course where GUI dev is a side-effect of the content, not the main goal. Also, there seem to be serious dependency problems installing Toga on Windows when it comes to Python versions, and that's a hell of lot of discouraging boilerplate for absolute newbies...)

Hi,

I teach programming and I'm now using PySimpleGUI in my courses. The university only officially supports CPython on desktop and Anaconda/Jupyter; however, I'd be happy for students to use an iPad if they've got one (and a keyboard) but only if they can use the right libraries!!

If you're not familiar with PySimpleGUI, it's a fairly basic but robust cross-platform standard that is implemented as a wrapper for all the main Python GUI libraries -- TkInter, Qt, WxWidgets, Remi (web browser as GUI). You'll clearly get different visual results on each, but the functionality will be almost identical on each.

To me, a Pythonista wrapper (PySimpleGUIPythonista or similar) would make perfect sense, as it would give us a way of making cross-platform GUIs on our iPads and would mean a lot more Python apps would work on Pythonista.