Wish list for next release
scj643 last edited by
M2Crypto and more crypto support
A built in script in the wrench menu to print to the screen and copy to the clipboard a forum friendly list of device/Pythonista info. Just see many times when some is trying to help someone here, they need more info, Pythonista Version , device etc...
dgelessus last edited by
Speaking of forum-friendly, a way to view and copy a traceback in plain text form. The debugger is nice, but it cuts off long error messages and there's no way to copy the traceback (AFAICT).
Phuket2 last edited by Phuket2
ui.parse_color To have an optional param alpha. Seems to me you normally would use this when you want access to the alpha setting when you have a css color name eg. 'teal'. Maybe there is a trick I don't know about, but becomes a multi step process because it's a tuple.
Small thing, but every little bit helps.
I also think that ui.parse_color could be repeated in the documentation in different sections. It's out on a island as far as documentation goes.
Ui.View - a margin property that is of course honoured by the whole ui API. I think this would be a big step forward for ui.Views. I can see could be many implementations of this. In my mind, the bounds would be adjusted to adhere with the margin. In theory at least you would hope that flex could also be applied to the margin. Maybe I am wrong, but I think this could do away with the concept of a container view out of convention is often end named cv.
As soon as views start getting complex, it seems normal practice to create a enclosing view. It's not that it's rocket science, but a lot of extra work involved. If for any uiView you could set a margin and it's margin flex, would be so great.
Personally, in terms of the ui Suite, I would say this would give the biggest bang for the buck so to speak. A lot of lines of code could be saved, over and over
khilnani last edited by khilnani
running and display output of a script on the today screen itself .. like a multiline row cell per script (eg. custom metrics or feed)
I've experimented a little with that a while ago, but today widgets just don't get enough RAM to be all that useful for scripting.
@omz That would have been nice to have, but am glad you already thought of that.
iphone 6/5s line numbers
Line numbers are already available as an option on iPhone 6 (not on 5s, I find the screen too small for line numbers, I might change my mind though).
Just found - https://forum.omz-software.com/topic/1430/show-lines-number - nice! i assume its coming officially in the beta
speech.is_speaking()– I just noticed that this is undocumented.
As for the modules, these are all popular requests. SciPy is unfortunately very hard to port, so I can't promise anything there. Pandas is more likely to happen (again, no promises!).
@omz Thanks for responding, Pandas would be great!!
erikcw last edited by
A Picker UI component (i.e. HTML select list).
Niall last edited by
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.)
cook last edited by
@omz Improvement suggestion -> iPad UI editor persistent controls panel state across sub views /maybe files
What I mean by the above is that currently the view detail panel to the right of the UI layout area currently does not persist across sub views. For example, If I expand the "Auto-resizing / Flex" panel on one sub view and then switch to another one, it's collapsed again. It's also collapsed again if I switch back to the sub view for which I expanded it. I think it would be useful to have all collapsed/expanded panel states persevere across subviews, and possibly even across pyui files...
Another thing -> in the current 3 beta, the new floating traceback view seems to only sometimes want to list the trace backs... Pythonista 2 seems to have the full traceback for the same scripts. Also, when the correct trace backs are listed, there's no way to jump to the appropriate file on iPad Pro....while the floating view of that file is nice, it would be great if there was also a way to jump to the actual file in full screen editing mode.
+1 for a debugger.post_mortem(), and also moving along stack should open the appropriate file ( or long tap to open, etc)
craftmojo last edited by
Please fix string.maketrans() method. It not working at all. Thanks.
dgelessus last edited by
@craftmojo See my response in your other thread, this is not a bug in Pythonista.
craftmojo last edited by
Thanks for fast responses. Now, it worked :)
suggestion: adjustable line height for fonts (especially useful for those on smaller devices). Sometimes text size alone isn't enough to optimize for the screen size.
@omz one more suggestion regarding line numbers on different device sizes. What if you had line numbers be an optional toggle on all devices, with sane defaults in place. In fact, I'd love to be able to turn it off temporarily on an iPad Pro. And besides that way maybe you'd be recycling code anyways?
Yes, it would be nice if all device specific ( as opposed to crrent size specific) settings were togglable, to facilitate cross-app development.
In the ui designer, ability to change the font name of the ui.Table object rows.
Also, would be great if for the CUSTOM ATTRIBUTES panel, if this could be done in a pop up window (ui.View) and better still if that view subclassed the editor so that you had a full editor in the ui.View. Not a ui.TextField which is pretty clunky to type into compared to the editor. Not critical, but I think would be a big enhancement
@omz Suggestion: simple built in sqlite3 viewer. When you go to a SQLite 3 db file in the Pythonista file browser, it would be great if instead of just showing a large icon and open in, it showed the contents. Would be useful as a quick reference while developing...remove friction for just quickly checking a result.