Difference between revisions of "Phone Photo Sync"

From rukapedia
Jump to: navigation, search
 
(8 intermediate revisions by 4 users not shown)
Line 9: Line 9:
 
== References ==
 
== References ==
  
* [http://homepage.mac.com/jonassalling/Shareware/Clicker/index.html Salling Clicker] looks like it might make this really easy
+
* [http://homepage.mac.com/jonassalling/Shareware/Clicker/index.html Salling Clicker] looks like it might make this really easy:
 +
 
 +
<blockquote>
 +
Phone event scripting: Phone Event scripts have handlers to react to proximity events, connect/disconnect events, and call events. They are pretty straightforward to write. When you create a new phone event script, it will have all the handlers supported in it already; all you need to do is add your code. Again, script properties are persisted across callbacks, and this can be very useful.
 +
</blockquote>
 +
 
 +
* [http://www.macosxhints.com/article.php?story=20040804182812579&query=bluetooth the MacOSXHints.com hint] has examples of calling Bluetooth File Exchange from the command line
 +
* [http://www.irowan.com/romeo/ Romeo] might also work
 
* [http://digitalmedia.oreilly.com/2004/11/03/iphoto_import.html Automatically Import Images into iPhoto]
 
* [http://digitalmedia.oreilly.com/2004/11/03/iphoto_import.html Automatically Import Images into iPhoto]

Latest revision as of 10:29, 9 March 2006

I want a system that does the following:

  • I walk into my office with my bluetooth phone.
  • My iMac detects this, and automatically looks to see if I've taken any new photos.
  • If so, they are downloaded and posted to Flickr and I'm alerted.

Should be simple, assuming there's a way to script the "Bluetooth File Exchange" app.

References

Phone event scripting: Phone Event scripts have handlers to react to proximity events, connect/disconnect events, and call events. They are pretty straightforward to write. When you create a new phone event script, it will have all the handlers supported in it already; all you need to do is add your code. Again, script properties are persisted across callbacks, and this can be very useful.