Community Page
- toxicsoftware.com Jump to website »
-
Subscribe -
Community
-
Top Commenters
-
Popular Threads
-
Recent Comments
- thank you for the information..
- I'm interested in migrating an EE site to WordPress, but I'm not as tech savvy as you. Do you ever do freelance jobs?
- just found your page, do you if there is a "generic" bluetooth app to remote control the nxt with a mac book? your software works only with space navigator?
- Three things: www.bitbucket.org causes a certificate problem because of the "www" subdomain. Pure python keychain access:...
- Hi. So can you please provide the the code for that application? Would be really appreciated!
Jump to original thread »
I’ll be adding a couple more subversion related automator actions to my site soon. It turns out writing actions is incredibly embarrasingly easy. The SVN Update action is now in subversion at: http://toxic-public.googlecode.com/svn/tags/Blo...
... Continue reading »
2 years ago
great idea!
I found a problem while trying to use both of these together.
1. Automator would not not import the actions.
2. "SVN Commit" release will build a file named "SVN Update"
Both problems were solved in XCode by changing the properties of the target.
The description was called something like "com.toxicsoftware.checkout" (for Automator these need to be unique, so I changed them to "com.toxicsoftware.update" and "com.toxicsoftware.commit")
I also changed the Product Name for SVN Commit (Release) to "SVN Commit" (from "SVN Update").
Now both seem to work! All that is needed is a separate "SVN Checkout"....as a starting point.
I was also thinking of an action that could traverse the -folder and color all up-to-date files as green and others would be labeled with red. What do you think?
Cheers!
2 years ago
I dont actually use those automator actions (which could expain all the little gotchas you found).
1 year ago
1 year ago
Try here: http://toxic-public.googlecode.com//trunk/Proje...