[Sparkle] SparkleCaster Developer Preview

[Josef W. Wankerl]

On 03/10/2007, Adam Radestock <raddish at glassmonkey.co.uk> wrote:
> That's a very interesting idea... to have the application run from a
> build script as you build the app.
>
> How would you like to see it implemented?
> How would you enter release notes? I suppose that if you used a URL
> for your release notes, rather than embedding them, you could supply
> the command line tool with the URL as an argument...

I typically write my release notes as I go along.  You should be able
to import them from a text or rtf file.  So I think something like
this to create a new sparkle caster document:

sparklecast --create --product "product name" --productpage
"www.mypage.com" --description "some description" --output
"newcast.scast"

...and then once you have one created you'd add the new version:

sparklecast --add --cast "newcast.scast" --enclosure "pathtoenclosure"
--version "vers" --releasenotes "text" [or --releasenotesfile
"path-to-notes-file"] --embed [or maybe --noembed] [optional --date
"some date"

...and then you'd make the appcast:

sparklecast --make-appcast --cast "newcast.scast" --output "mycast.xml"

Somehow you'd have a way to remove versions from a sparkle caster
document too.  Basically you'd mirror all the functionality of the
main app in a command line tool.  If you follow a good MVC convention
in the main app, you can re-use the model code in the command line
tool.  You'd only need a front end to parse the command line and feed
its argumeents to the model.