• jesse

    This thread has a solution for that:
    http://omz-forums.appspot.com/pythonista/post/5878444697059328

    There might be others.

    posted in Pythonista read more
  • jesse

    I haven't worked with the most recent XCode template, but my experience with the prior one is the same. My splash screen shows up, then everything goes blank for a second or 2, then my interface appears.

    I would really prefer that my splash screen remain visible till my first UI update takes place. Is there some way to force that to happen?

    posted in Pythonista read more
  • jesse

    @jb145491

    The short answer is not right now, but eventually yes.

    It was possible in the recent past (I submitted one, although I had to withdraw it...long story).

    You should also be able to submit them again in the future (probably when Pythonista version 1.6 comes out, or shortly thereafter).

    Apple changed their policy a few months ago and no longer allows 32 bit apps to be submitted, but the old solution for Pythonista involves libraries that don't work with 64 bit apps (at least not easily...it might be possible, but it's not trivial).

    So go ahead and work on your app, get it nice and polished, and hopefully by that time the new xCode template will be available and you'll be able to start the hard part of your journey (figuring out all the obtuse requirements of getting from a "finished" app to actually getting it submitted to the app store).

    posted in Pythonista read more
  • jesse

    I'm sure this is all spelled out at Apple's Developer portal somewhere, I just don't know where off hand.

    From what I recall, XCode is free, and you can use the device simulator for development (it's not bad, and fine for prototyping and early testing). You just won't be able to put it on an iPhone/iPad/iPod/iWatch/iWhatever until you cough up the $99 dollars.

    But it's been quite a while since I signed up, so it may have changed (or I may be remembering it wrong).

    posted in Pythonista read more
  • jesse

    As a long time C/C++ developer (23 years professionally), I found Objective C to be obtuse and hard to learn. I've used it, I've built apps with it for iOS (including one that is still available in the App store, although it's no longer written in Objective C), and I still find that every time I go back to it after any kind of break I have to relearn everything again.

    Conversely, Swift seems more like a nice hybrid of C and Python, at least after reading the initial documents from Apple. While reading the docs, it all made sense to me (I've never been able to say that about Objective C, even while I was using it constantly), and I think I could be up and running with it in a matter of days.

    However, I have not actually tried to use it to build an app using Swift yet, so I can't speak from any real experience.

    My opinion: don't bother with Objective C, go straight to Swift.

    posted in Pythonista read more
  • jesse

    Since no one has listed it:

    iPhone 4s (using Pystone 1.1 and Pythonista 1.5) = 10071.2 (pystones/sec)

    So the iPhone 5s is ~4.9 times faster than the iPhone 4s (but the iPhone 4s is ~2.15 times faster than an iPod 5)

    posted in Pythonista read more
  • jesse

    I use DropBox.

    You can send a file directly from DropBox to Pythonista, and it will show up in the "Inbox" in Pythonista.

    posted in Pythonista read more
  • jesse

    My experience in the past is that the simulators should not require a developer license in order to work, but if you want to run on an actual device (iPhone/iPad/iPod) you must be a registered developer with Apple.

    Since it's working on the iPad simulator, but not the iPhone simulator, the problem is a difference between the 2 builds.

    Sorry I can't help you with the actual problem...but you don't need to pay the developer fees. You just need to figure out why it doesn't work on the iPhone simulator.

    posted in Pythonista read more
  • jesse

    Hi,

    I seem to have run into a bug with the "My Images" screen.

    I added some images for a project I'm working on.

    On one device, I accidentally added the same image twice, with 2 different names.

    When I attempted to replace the bad image with the correct one, I couldn't. I get an error message: "An image with this name already exists." That seems fine (just preventing me from accidentally overwriting a file).

    So I deleted the bad image, and attempted to re-add the correct image with the proper name, and I get the same error message: "An image with this name already exists."

    It's not listed in the files, but it (the bad image) is apparently still in there somewhere, and I have no way to remove it.

    This is not a show stopper (I can hack around it), but it is annoying.

    posted in Pythonista read more
  • jesse

    Is there some way to have the status bar remain visible on the iPhone?

    posted in Pythonista read more

Internal error.

Oops! Looks like something went wrong!