• CarlRJ

    Wait, you had a device that runs a key piece of software for you, and you replaced it with one that doesn't run that key application? Why?

    A very old, yet still quite true, adage is, buy the software that does the necessary task, then buy the OS that the software requires to run, then buy the hardware that the OS requires to run. (In the iOS case, of course, the latter two parts are combined.)

    Since iOS is a proprietary system, an emulator of any sort for it on a PC is undoubtedly going to involve breaking a lot of license agreements. You can't buy a separate copy of iOS, it is licensed only for running on Apple hardware.

    This thread, on the Pythonista forum, might be more well received if it were titled, "Pythonista alternatives for Android".

    Your best bet might be an iPod touch or an iPad. If money is a concern, it doesn't have to be the latest gen to meet the requirements; secondhand or a refurb from Apple are worth considering.

    FWIW, I've used Kivy quite extensively, on the Raspberry Pi. It's a good UI library, but it has nothing equivalent to Pythonista's IDE, and while you can definitely use it to write apps for Android, I'm not at all sure you can write them on Android.

    posted in Pythonista read more
  • CarlRJ

    I know Apple's restrictions prevent access to other syncing services from something that can run code (such as Pythonista), but does that also apply to a Pythonista-specific folder on Apple's own iCloud Drive?

    posted in Pythonista read more
  • CarlRJ

    Success! Thanks, guys. I was missing something obvious.

    posted in Pythonista read more
  • CarlRJ

    Nope, tried that already. I feel like I'm missing something obvious, but I'm pretty good at working through the the permutations.

    visual explanation on imgur

    posted in Pythonista read more
  • CarlRJ

    I'm swiping left-to-right, and it hides the console on the right... and opens the file browser on the left. Losing one-third of the screen width to a sidebar either way. :-/

    This is on an iPad Air (1), running iOS 9.2, in either portrait or landscape.

    posted in Pythonista read more
  • CarlRJ

    Im having fun poking around the v2.0 release of Pythonista... I could have sworn it initially opened on my iPad with the Welcome(dot)md file displaying in a full-width window, but halter opening the console, I can't get back to full-width now - it seems I can see "file browser & editor" or "editor & console" or just "console" but not just "editor". Am I missing something? Sorry if I've skipped over something obvious.

    Also, is there a way to display a "preview" from a Markdown file? Either full-width, or in the console sidebar? I thought I remembered something like that from earlier, but perhaps I'm confusing features between Pythonista and Editorial.

    (Also, while posting this, the forum helpfully decided that "Welcome(dot)md" - with an actual "." - was a url, and then proceeded to tell me that my message was spam, because hey, url. That I didn't put in.)

    posted in Pythonista read more
  • CarlRJ

    Hmm, signed up, haven't heard anything back.

    posted in Editorial read more
  • CarlRJ

    This seems to be more of a problem on iOS 8, maybe there's more aggressive memory clearing, and it's driving me a bit batty...

    When I switch away from Editorial, in the middle of a large file, to go grab some text from another app (often Safari, but not always), frequently when I switch back to Editorial I'm shown right where I left off for a split second, then I get the dark screen with the asterisk (reload screen?) - okay, I'm guessing this means Editorial got shoved out of memory. But the big problem is, Editorial then reloads, and gets me in the right file, but it puts me at the top of the file. Every single time. If you had been, say, roughly two-thirds of the way through a 500 line file, it's extremely tedious to scroll back to where you had just been. Especially the 20th time in five minutes. It's particularly frustrating because you were shown that exact right place just before the reload screen (yeah, guessing that's probably just a snapshot, but it's still like its teasing).

    Would it be possible to modify Editorial so when iOS tells Editorial that it is being switched away from, it saves the current offset into the file as well as the current filename/handle/whatever, and then when switching back, if that saved-offset is set, it positions back to that offset into the file? It'd save me from tearing out any more hair.

    Thanks!
    Carl

    posted in Editorial read more
  • CarlRJ

    I third this - I've been noticing on my iPhone 6 that the rows of keys in the keyboard are much farther apart in Editorial than in Apple's built in apps - using up a bunch of extra screen real estate needlessly.

    posted in Editorial read more
  • CarlRJ

    Have to say, I happened across the versioning stuff yesterday, and was pretty thrilled - it's awesome, it'll diff any two previous/current versions of a document, kinda like Wikipedia's history.

    posted in Editorial read more
  • CarlRJ

    Gee, I go away for a little bit and miss all the fun...

    @jonmoore

    Personally, since the next versions of Pythonista and Editorial are going to involve some radical changes anyway, I'd vote for making them "Pythonista2" and "Editorial2", with Python 3.x (only), and keep the existing versions around in maintenance mode

    I would disagree with this as I still believe a version of Pythonista that supports 2.7 should be publicly available and this strategy will mean that only those that already own Pythonista will be able to access a version that supports Python 2.7.

    To be clear, by "maintenance mode" I wasn't suggesting pulling the current versions from the store, just not upgrading them beyond bugfixes. They both work fine on iOS 7 as is.

    Short of "no Python 3.x ever", and given that both flavors can't run in the same executable, the remaining choices are either to switch both existing apps to Python 3.x at some point (leaving users with no choice), or to release new "v2" (or "v3", if you will) versions of the apps and keep the current (Python 2.x based) apps around, in which case Ole can either put extra work into keeping all four of the apps in sync, featurewise, or he can leave the current ones pretty much as-is (save for bugfixes) and concentrate new work and features on the Python 3.x versions going forward. I was voting for this latter case (and yes, I completely get that it's Ole's baby, this isn't a democracy, and we can only make suggestions / express preferences).

    I was promoting the idea of doing the change at this point because (aside from "hey, more new toys for us"), Ole's recent work points towards releasing new versions of both apps simultaneously, with significant user-visible changes (sounds like Editorial's workflow entry has been "reimagined" because of the iPhone), and with Editorial going Universal.

    If Ole doesn't hard-switch both apps (and all the users) over to Python 3.x at some point in the future, there will eventually need to be new Editorial3 / Pythonista3 apps, and casual users will want to see substantial user-visible changes when facing the prospect of paying for a brand new "edition" of an app (particularly on the Editorial side, since it presents to the casual user as "merely" a text editor - Pythonista users, on the other hand, will tend to see Python 3.x itself as a new major feature), and Ole's got those kind of changes in hand already, so it'd be a fitting time to make the jump.

    And now I'll stop talking (sorry, I sometimes explain at length in cases where it looks like I'm arguing vigorously for or against something, when I'm actually just trying to clearly convey the precise "flavor" of my point - that's sort of what's going on here - sure, I'd like to see Python 3.x sooner vs. later, but what I'm most anxiously awaiting is the iPhone version of Editorial, so I'll be able to use the same text editor on both iPhone/iPad).

    posted in Pythonista read more
  • CarlRJ

    I haven't read the whole of this thread so I'm not sure if it's been raised already but is there any reason why you can't have a single 2.7 distribution and a 3.4 version that's only available via an IAP.

    It's stated several places in this thread and others on the site that yes, there's a reason why he can't do Python 2.x and 3.x in the same app: iOS apps are required to contain a single executable with no dynamic libraries, and the two versions of Python would collide if they were not separate libraries (can't compile both into the same executable). We'd all love to have it, but it can't practically happen. (Uh, maybe with major hacking on both Python codebases, but it'd be sort of a Frankenstein-ian job of rewiring two brains to one body.)

    The alternatives are: a) no Python 3.x ever; b) have a flag day and switch the app over to Python 3.x, dropping Python 2.x support - leaving a bunch of existing users scrambling; or c) release a Python 3.x version in parallel to the Python 2.x version.

    Personally, since the next versions of Pythonista and Editorial are going to involve some radical changes anyway, I'd vote for making them "Pythonista2" and "Editorial2", with Python 3.x (only), and keep the existing versions around in maintenance mode.

    posted in Pythonista read more
  • CarlRJ

    Wow! I'm impressed! As someone who normally lives in Vim (and MacVim) on Mac/Linux systems (with the full power of the command line & scripts for filtering available), Editorial is like a godsend, being able to write Python tweaks/filters for text editing on iOS. And having an iPhone version is going to greatly simplify some things for me, not having to make do with lesser apps on the smaller device.

    At the risk of delaying things further, this seems like a large enough milestone that you could quite reasonably rename them to Editorial2, Pythonista2, charge anew for them (as universal apps), and use the occasion to switch over to Python 3.x. Sort of make a clean break all around. Keep up maintenance/bugfixes on the 1.x versions (if needed), since they both work well on iOS 7 (and folks can stay with them if they're happy), but have all new work/features/etc going into the new v2 versions.

    Either way, there's a bunch of folks who'd cheerfully use a "buy Ole a drink" IAP button, or, if Apple won't allow that, maybe a bonus/premium button that gives us some themes or whatnot in return. I understand a title of the "what price will fly" dilemma, but you I think you should get more money for Pythonista and Editorial.

    Take all the time you need. ("As long as I can have it tomorrow" Ha! *anxiously waiting*...)

    posted in Editorial read more
Internal error.

Oops! Looks like something went wrong!