motion-sparkle
motion-sparkle copied to clipboard
motion-sparkle makes it easy to use Sparkle in your RubyMotion OS X apps
the `short_version` contains the app's version number, while the `version` contains the build number. Fixes #15
And just re-use the helper method for the sparkle config dir
The RM Rakefile can have different settings for development and release, for example by using ``` app.release do end ``` use `App.config_without_setup.build_mode = :release` to make sure we pick up...
It seems that the version numbers are backwards. In RubyMotion., `version` maps to `CFBundleVersion`, and `short_version` maps to `CFBundleShortVersionString`. In an OSX app, the `CFBundleShortVersionString` is the real app's version...
Also, [ChocTop](https://github.com/drnic/choctop) seems to have code for rsync/scp/sftp/ftp.
Take a look at [ChocTop](https://github.com/drnic/choctop) as they have implemented this for regular Cocoa apps.
Not only can people use other targets in their setups, Sparkle is also capable of handling .pkg installers, which means motion-sparkle could work with the results of `build archive`. This...