Welcome!
This is the community forum for my apps Pythonista and Editorial.
For individual support questions, you can also send an email. If you have a very short question or just want to say hello — I'm @olemoritz on Twitter.
My feature requests
-
(You need space somewhere on this forum for feature requests ;) These are in roughly order of interest
-
Directory support in the editor/browser - my main workspace is getting cluttered, it would be nice to be able to separate out projects by directory, and drop libraries further down.
-
Better traceback support - currently, if I've imported another python file and get a traceback there, it presents as a single line in the file I'm executing, with no real information about where it happened. Getting the file right, and perhaps presenting a traceback browser, would be very cool.
-
In that vein, pdb support, although I haven't really needed it yet. It's potentially tricky with graphical screens though - I already locked the app up once by pdb'ing while a graphics screen was up...
-
I'd love to see something like cocos2d available, but I suspect that's way too much to ask ;) I really like the approach pythonista takes to graphics, btw. I've been working on a little roguelike as an exercise, and it's surprisingly easy to get up and running.
-
Wrappers around other iOS capabilities like the gyro, location services, camera, etc.
Does Pythonista have a roadmap? I ask because I'm debating at the moment whether to continue my (hobby) game dev in pythonista, or just treat it as a prototype for migration to obj-c, and you mentioned in another thread you see pythonista as more a utility/tool thing than a game thing.
-
-
-
Directory support: Definitely planned, will probably be in 1.3
-
Better traceback support: Thinking about that, maybe a popover that shows the full traceback when tapping on the error line could work...
-
pdb support: The problem is mostly that it wouldn't really work with the way the scene module is set up internally (as you've seen). There could be a separate, more limited debugging mode for that (something like "pause and inspect"), but I'm not sure about a lot of details yet. Making a graphical debugger UI is not trivial and will probably take quite some time.
-
There is some limited access to the gyro/accelerometer data with the gravity() function in the scene module, I will probably expand that in the future. Location data could be interesting, haven't really thought about that yet. Camera support is pretty difficult to do because the APIs are either very high-level (the standard image picker) or very low-level (live video feed). The low-level APIs would be more interesting, but I'm not sure how easy it'll be to integrate them with Python - it could very well be that it's just too slow to process the large amount of data that the cameras generate in a meaningful way.
Honestly, I don't really have a roadmap. Of course I do have a pretty long list of things I'd like to add/improve, but it's often hard to predict how long a specific feature will take and my priorities are often shifting, as I use the app myself... A lot of the more interesting features are things I've never done before, so there's no way to know how long those will take or which obstacles I might hit.
-
-
I'm very interested in location services. Has any progress been made?
-
Location services are something I'm looking at for 2.0 (which I've actually started working on, but there will be 1.x updates before that).