@ShadowSlayer: I tried pcista to port a simple game I wrote on my phone, but ran into a problem: translate
seems not to be supported, and I use it. Also, pcista looks like it's Python 2 only (string.uppercase
no longer exists in Python 3). Cool idea though, I'd like to be able to use pcista.
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.
Latest posts made by Helgi
-
RE: UI on desktop
-
RE: Editorial v1.2 is now up on the Apple App Store... Go get it!
It was sad for me to see that even in 1.2, I still won't be able to type in Russian as easily as I can in iA Writer and Drafts.
Which is too bad, as Editorial clearly beats both of them. But alas, still no extended keyboard customization. :(
-
RE: Beta Status Update
Can somebody among the beta users tell me whether the extensions can be made to handle files (e.g., Mail attachments) in a way that was possible with Open In?
The scenario I used in the days of Open In was this: I have an email attachment of specific type (e.g., .txt), I open it in Pythonista, the Open In handler then performs some automated actions (in my case, uploads it via SCP and then runs several commands on the remote server). Can this be done with the extensions now? Should I wait for the new release or try and find other ways to do this?
-
RE: Working Copy integration sidebar
By the way, check out my pull request on Github. I think I improved the script a little by removing the need for the user to configure INSTALL_PATH.
-
Sidebar UI -- close programmatically
I've stumbled upon a nice sidebar UI script made to work together with the Working Copy app.
The script presents a very narrow sidebar with just one column of buttons. As it turns out, for a sidebar that narrow, the close button overlaps with the 'open console' chevron, so it's impossible to close the sidebar. Is it a known issue?
To circumvent this, I wanted to add a custom 'close' button that calls
close()
on the view. However, it looks likeclose()
doesn't work for sidebars (it works OK for me for sheets, fullscreens and popovers). Is it a known issue? I wasn't able to find anything stating this in the docs.If I succeed with adding a custom close button, I'd like to hide the standard close button on the sidebar (which is not usable anyway). Is there any way I can do this?
hide_title_bar
doesn't work for me.I believe this questions are not covered on the forum, at least I wasn't able to find anything like them.
Tested with Pythonista 1.5.
-
RE: Own Python Modules?
You can place a
.py
module in Editorial's Local Storage, and then import it from inside a Run Python Script action. This works, but is cumbersome:- You can't edit a Python file stored in Local Storage. You have to create a
.txt
file, then rename it to.py
with the help of a custom workflow. - If you want to edit this module, you have to repeat the edit-as-txt / rename loop over and over. If you have a ready-to-use module already, this might work for you.
As for me, I wanted to be able to share some code that is common to a number of workflows. Say, one workflow uploads a post to my blog, and another one downloads a post, updating an Editorial document. Obviously I'd like to share the upload/download code, but the approach I described doesn't work as I want to iterate on my upload/download module.
I wish there was a shared storage of Custom Actions, so if I edited the code of a Custom Action in one workflow, all other workflows having the same Custom Action would receive the updated copy of the script. As far as I understand, this is not the case.
Does anyone happen to have any ideas regarding this? I just really hate Copy & Paste for code.
- You can't edit a Python file stored in Local Storage. You have to create a
-
Extended keyboard customization
On an English keyboard on the iPad, the most important punctuation (period, comma, question mark, exclamation mark) are readily available and convenient to use. On other keyboards, unfortunately, this isn't the case. Russian keyboard, for example, lacks any punctuation in the default mode. This means one has to tap the
.?123
button very often, and this is especially annoying in the case of commas (the tap-spacebar-twice-to-enter-period trick helps with the other often-needed punctuation).There are different solutions to this that I've seen. iA Writers's extension is language-specific, and this is quite convenient to use. Other editors allow to customize the extended keyboard.
I've recently purchased Pythonista and Editorial, and I'm trying to adjust Editorial for my writing needs. I really loved the whole experience, and the automation blew my mind. But, unfortunately, as I write in Russian, the lack of comma on the keyboard is a real inconvenience.
Can you make the keyboard extension customizable? I'd happily sacrifice one of the buttons in exchange for a comma.
And while we're there: auto-paired customizable quotation marks (like «this» for Russian, or „this“ for German) would be absolutely great as well.
-
RE: Extended keyboard customization
By the way, a workflow that inserts a comma is what I currently use. But the workflow buttons are too far at the top to be used smoothly while typing.
But it looks like iA Writer could be a great source of inspiration.
-
RE: Pythonista 1.4
I wanted to say that wolf71 isn't the one struggling with the Cmd-Space shortcut. I have two keyboards set up (English and Russian), and I confirm that Pythonista intercepts the Cmd-Space shortcut, which otherwise switches between keyboards. The only workaround is to open the on-screen keyboard (via the Eject key on the Apple Wireless Keyboard), tap the Next Input Method button on the on-screen keyboard, and then hide the on-screen keyboard. (Version 1.4.)