@Webmaster4o still adding people? My email is <deleted>.
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.
Posts made by andymitchhank
-
RE: Pythonista Slack or Mattermost
-
RE: Pythonista Slack or Mattermost
Or Telegram. It is built for open communities and anyone can add anyone to the group without having to know their email or phone number. As long as they have a telegram handle.
-
(Physical) Keyboard shorcut key bug
When the console is docked, you can toggle to the console using CMD+J, but cannot use the shortcut to toggle back to the source (like you can when the console is not docked).
I have tried this using both betas on an iPad Air 2 with a BT keyboard and the iPad Pro with the Smart Keyboard.
-
RE: Pythonista hung- can't stop program. Stop (X) button was disabled
@cappy Try this: https://gist.github.com/f1dfe29f99b7bf5b700b
I caught the KeyboardInterrupt in the threads just to keep it from printing the interrupt error message.
But the time.sleep(1) at the end keeps the main thread alive allowing the KeyboardInterrupt to kill the script. I tested this on my iPad (which has the same specs as yours) and was able to kill the script each time.
-
RE: Pythonista hung- can't stop program. Stop (X) button was disabledis able to be pressed.
-
RE: New Xcode Template on GitHub
@Webmaster4o Oh, I don't need/want it. I just wanted to make sure that it was removed and I don't have access to my mac at the moment to test it.
-
RE: New Xcode Template on GitHub
@Webmaster4o I know this was an issue with previous versions of the template. If you look at the Pythonista-Tools github repo and download some of the apps in the apps store, you can close the app window.
-
RE: New Xcode Template on GitHub
@omz Has the 2 finger slide down gesture to close the Pythonista script been removed from the template? It doesn't appear to be working directly in Pythonista anymore. (This may have been addressed already, but I can't seem to find anything about it being removed).
-
RE: New Xcode Template on GitHub
Thanks for this! The instructions are very thorough also. It is much appreciated.
-
RE: Pythonista IRC channel
@Webmaster4o supposedly the rocket chat mobile apps have push notifications. Haven't tested this yet though.
-
RE: Pythonista IRC channel
I've been looking around for an alternative to slack and found Rocket Chat. I've created an instance on heroku (to test) and enabled Github and Twitter logins. Also, anyone can join without an invitation.
Join here: https://pythonista-chat.herokuapp.com/
-
RE: Pythonista IRC channel
@ccc I'm not sure why it is forcing to give access to all your contacts. I don't allow it access to mine and it never asks. I am running the beta app (I assume we are talking iOS), so maybe it's a bug they have fixed.
My email is [...] if you could add me to the slack team. (I will either edit or remove this post after I'm added, thanks.)
Also, if you could make me an admin, I will set up this app on heroku so that people don't have to post their emails publicly and anyone can join the team.
-
RE: Pythonista IRC channel
@ccc The app only requests access to your contacts in order to let you invite people in your contacts list to the new team. It's a fairly standard practice for chat applications.
-
RE: Pythonista IRC channel
@ccc You are right that slack was built with internal company teams in mind.
Maybe we have different ideas of how slack would work for the community here. I see it as a way for more of the regular Pythonista users to chat and collaborate about the app or larger projects they are working on before sharing it on the forum where everyone can view it.
Of courses, the admin will be generous with inviting new users, but it won't be completely open to the public.
I also agree with you that it would be nice to use a google login with slack, but I can see why they chose not to include it, with users able to be a part of multiple teams. I think one of the paid versions lets you use a Google Apps account, but that's a different story.
-
RE: Pythonista IRC channel
@ccc I'm not sure that the https://pythonista.slack.com team is related to the app. I may be wrong, but I couldn't find any mention of someone setting up a slack team for the app in the forum, so that URL probably points to a different group of people. (Someone please correct me if I'm wrong.) Someone would need to register a pythonista-app (or something similar) team with slack (since you can't reuse team names and all).
I use slack at work and think it'd work great for the community here, but it is more of a closed system, requiring an invitation to join a team. Of course, anyone who wanted access could request it here and the admins/owners of the slack team (@omz and some other people probably) could send them an invite. I think it can be opened up where anyone can send invitations, but don't quote me on that.
-
RE: Working Copy integration sidebar
@Webmaster4o I haven't looked at the git support in
stash
recently. Are you able to use ssh keypairs for authentication? That's the primary reason I moved to Working Copy initially. -
RE: Working Copy integration sidebar
I have updated the Working Copy Sync script again with a couple of changes.
Before updating to the latest version, push all of your changes from Pythonista to Working Copy. After updating, you will need to clone each of your repositories again, overwriting any changes not pushed to Working Copy.
- Repo information is now stored in a .wcsync file in the repo root directory and doesn't use the currently directory to determine the repo-name. This means that you can rename a folder or move it to a different location (out of the documents dir) and you can still use Working Copy with the repo.
(You can also move the Working_Copy_Sync.py script to the root directory if you like, but I recommend leaving it in its own directory in order to pull changes from the repo in Working Copy.) - If you run the script (from the action menu) in a folder without a .wcsync file, it will only show the option to clone a new repo from Working Copy. In folders containing a .wcsync file, it will provide the regular fetch, push, etc. options.
Note: The script searches for the .wcsync file recursively (up the folder tree). So you can still have folders within your repo and it should all work. Also, there is an issue with spaces in folder/file names when using URL schemes between Working Copy and Pythonista, so I would avoid spaces.
Link for completeness: https://github.com/ahenry91/wc_sync
- Repo information is now stored in a .wcsync file in the repo root directory and doesn't use the currently directory to determine the repo-name. This means that you can rename a folder or move it to a different location (out of the documents dir) and you can still use Working Copy with the repo.
-
RE: Working Copy integration sidebar
@mrcoxall Sorry for the (really) delayed response here. You need to create a repo in Working Copy called wc_sync so that it will have somewhere to push the changes. For other repos, you need to add the Working_Copy_Sync.py script to the quick actions in Pythonista.
-
RE: A MVC analogy in Pythonista terms?
MVC is a way of organizing an applications code base so that the data (model) and the presentation (view) layers are abstracted away from the logic (controller). Most how-to guides will typically use a web development example when explaining the MVC architecture.
Model refers to the data model and how it is updated. (Typically it is a wrapper around a database). For example, a person model would be a class with the variables first name, last name, age, etc and would include methods for getting and setting these components (as well as saving the data back to the database).
A View is how the data is displayed to the user. In Pythonista, this refers to the UI portion of the app (whether coded or build using the UI editor).
The Controllers handle event requests, contain the logic of the application, and determine how the models work together to make the application run, which in turn calls the views to display the data to the user.
I found an interesting link that tries to explain the concept of MVC using legos if that helps.
-
RE: Working Copy integration sidebar
@ccc the error is caused by the script being in the root (home) directory. So the full path doesn't have a
\
, just the script name. When you split it (line 47), you only get one return value and the script tries to unpack it into repo, path.The script uses the project directory as the repo name. I'm looking into a possible solution for this.