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.
Wish list for next release
-
This may sound a little stupid. But I would love to see a run button incorporated into the Pythonista part of the keyboard. On a iPad Pro, the run button is quite far away. Also with my bad eyesight I often end up hitting a editor tab or its close button quite often. Not sure you need to have bad eyesight for this to happen.
On the iPad Air 2, this wasn't an issue -
Wasn't sure if this Thread was dead or not. But will write here anyway.
@omz, what would be really really and more really cool would to be able to use the drawing functions such as ui.Path etc to draw into Custom Views inside a pyui file. The code/commands could possibly live In dict style construct inside the custom attributes, whist still being able to the custom attribute fields for custom attributes. So the idea is that drawing Cmds would be both executed in the designer as well as runtime.
This would be great for making user controls, like a radio button for example. Of course the custom attributes a huge benefit, already having a built in mechanism to handle state etc.I am sure a more grandiose implementation could be done. But this in its self would be great.
I know, we can implement all this now all except the rendering inside the Designer. For me, I think this type of extensibility is huge.
My fingers are crossed 😇😇 -
I agree it would be nice to show what a custom view looks like in the ui editor, but I don't see how that could work unless the custom view was instantiated as a live object. Most useful
draw
methods, I think, depend in some way on the instance properties. How would the UI editor know which class to instantiate? (custom view class names are not in scope until runtime).I guess what you are suggesting is the ability to set some preview draw code or image. For instance maybe you'd copy your draw code, replacing any self.property's with hard coded values, so the preview would show a sort of generic instance, like the way tableview is shown
You would need to add that custom code at the top level pyui, not your custom view....
Perhaps if there was a "CustomView Library", sort of a snippet manager for the UI editor, where you could define commonly used custom views (size, colors, preview, CustomView, custom dict, etc)
-
@JonB , I am sort of guessing now. I am not 100% sure. But let's say you could put code somewhere, like the Custom Attributes. Some code that looks like a dict or whatever. As an example I put in the pic below.
So let's say the rule is for user drawn controls, locals are not allowed. The code/function defined has no parent. It's just a function. This is where it gets fuzzy for me. I am not sure how you add that text function. Possibly just a exec. Maybe some of the libs like functools. Not sure. But of course the approach needs to be generic so that the ui.View knows how to call it, if it's present. I am sure it can be done. Well pretty sure.
This would be a big break through.
-
If you are thinking that this code would be used when actually presenting, I think the utility will end up being very limited. Most cases for a custom class I can think of need to use instance properties to decide what to draw.
Keep in mind, the ui editor does not load pyui's. It lets you type a name of a class which might not currently exist until runtime.
-
[Edit] This was implemented in version 2.1 and on Pythonista 3. Thanks omz team :)
In the Console window, when I copy a long line from the history, and type something at the start of the line, the part I am typing now is hidden in the left part of the input field. Could you update the app so that the place where I am typing (in other words, around the place of the cursor) is always displayed? Thanks.
-
@omz, I realize this will be not high on the todo list. But would be nice if you extended themes to dialogs.
Eg...def show_about_dialog(): dialogs.list_dialog(items = ['one', 'two'], theme_name = 'Cool Glow')
-
This post is deleted! -
would love to see editor code folding
screen realestate on an idevice is precious
folding would help maximize this -
same code folding, along with vertex shaders in scene and opencv