Resources on iOS

[Ian Lawrence]

I am developing sketches on both iOS and OS X. On OS X I can edit some pre files that I have loaded as resources(Even in procoding). But on iOS the open in… menu comes up blank (that is it offers nothing for the pde files. By contrast open in on the DropBox app on the same device allows me to open a pde file in Textastic. What is the expected behaviour here, please?

[audiocommander]

Hi Ian,

thanks for contacting me about this: this is a bug affecting all iPads with iOS 8. Usually it should present the sharing screen that you also know from Dropbox, but the presentation inside the popover is not working. Apple changed the way how actionSheets are presented with iOS8, so I think this is broken since the latest iOS 8 updates (and I did not notice because I’m using my iPhone more frequently than my old iPad and it works fine on the iPhone).

Will fix this asap with the next update, sorry for the inconvenience.

As a temporary workaround: exporting seems to work; if you selected Dropbox, the resource should be exportable to Dropbox and can be then imported back after editing.

And by the way: editable code resources is #2 on my top priority list, but there are a couple of issues in regard how the app is designed, that make this quite a complicated task.

All best,
Michael

[Ian Lawrence]

Morning Michael,

OK, thanks. I have a workaround. I kind of assume this is the best place to seek clarification on features/bugs..

If I had open in working, I’d be more than happy to open up these resources in say, Textastic. It seems to me that the best reason to keep editable code resources as resources, and not have them in the sketch is because they are big. And maybe proceeding is well suited to smaller, more nimble footling.

kind regards

Ian

[audiocommander]

Hi Ian,

Procoding definitely has its strength in handling smaller, well defined sketches and less in managing big projects with many resources. There are definitely better ways to handle huge projects. At some point, there are also device limited restrictions on how many resources you can add dynamically before something goes wrong. These kind of projects should then probably be compiled before publishing them. That’s what you cannot do with Procoding.

I usually have four to five early experiments in Procoding, and only when I’m certain these encapsulated functionalities work as expected, I’m moving them into a resource.
Or I have some common.js files and third party libraries that I can add as a resource on a as-needed basis.

I would publish this bugfix asap, but I’m currently working on supporting iCloud Drive and I need to make sure everything works all right before I send out this update.

Thanks for the report, though!

Best,
Michael

[audiocommander]

Just FYI: there’s a version submitted for review since last week that addresses this issue.
Thanks again for notifying me about this!

Michael

[Author]

Posts