![]() 2016 wasn’t the year for that, but small improvements like these make me a little more confident that we’ll get there some day. It might be for him, but for someone like me it still seems quite far away, though I’d love giving up my MacBook Pro for an iPad Pro, if I only was able to get my work done on it. If you believe Apple CEO Tim Cook, the iPad is the future of computing. There are obvious limitations like the fact that you cannot easily update all your scripts at once, and that “local” changes are vicouisly overwritten, but at least it’s something ) For reading, it will pull changes from the remote repository, applies them locally and returns file’s new contents via x-success parameter back to Pythonista, where update_script is called to update the script file. These editors are to be used for a single concept or small snippets of code. The third set of editors will be web based code snippet editors. The second set will cover cloud based editors that allow you to code on the go. The cloned files can be edited directly in Working Copy. I can’t stress enough how easy Working Copy makes using git. Clone, edit, commit and push while allowing other apps access to repositories. Working Copy allows a user to: Access Git repositories on the go. The first type of editors are going to be desktop applications. My writing workflow for this site consists of 2 apps, Working Copy and Textastic. For writing, Working Copy will present a view where you can enter your commit message and choose to either save ( git add), commit, or commit and push. We are going to focus on four types of editors for you to use. Depending on an argv parameter, the update_repo script builds URLs for either writing or reading file changes, and launches the Working Copy app. So, I came up with two small Python scripts which do exactly that: Pushing new code to, and replacing old code by pulling changes from a Github repository: Plus, being able to easily clone them on my Macs for further development, is a huge win for me. ![]() Here’s the idea: I really wanted to keep all my Pythonista scripts at Github, because… well, that’s where code belongs, I guess. ![]() Sadly, there’s no such integration yet with Pythonista, but you can get really far with just using Working Copy’s URL scheme. Yes, you can really integrate your Git work flow with iOS editors like Coda or Textastic. Due to its closed nature, iOS data exchange between apps is still somewhat cumbersome, but gladly, Anders knows all the tricks of the trade: Working Copy registers itself as iOS Document Provider, has a built-in WebDAV server, and offers a pretty extensive URL schema. But there’s one particular called Working Copy by Anders Borum that’s really close. For someone like me, who does not use Python on a regular base, it was a pretty ambitious attempt, because it used the pygithub3 module for pushing new content and some custom UI for user interactions from the iOS share sheet.īack then, I neglected all existing Git clients for iOS, because I couldn’t think of them being anywhere near as useful as the one running on my Mac. ‘Tis the season… for iOS automation, I guess.Īlmost exactly one year ago I blogged about my workflow for publishing new posts from my iOS devices with the help of Ole Zorn’s iOS app Pythonista.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |