[Sparkle] Sparkle for Automator Action update

[Mark Munz]

One way to do this might be to wrap the automator action(s) in an app
bundle. There is not a huge benefit of actually installing the actions
inside the /Library folder vs. just putting them inside an app bundle.
The system automatically recognized them when your app is installed.

After a certain period of time elapses, when your action is run, you
could run your parent app, which could do the check for updates and if
nothing, quit.

Mark Munz


On Thu, Feb 14, 2008 at 11:27 AM, Mortimer Porte <mortimer.pa at free.fr> wrote:
> Hello there,
>
>  I have searched a bit, but couldn't find anything. If there is already
>  resources about that, let me know.
>
>  The only thing I could find about non-apps and sparkle is a post about
>  sparkle 2, but it's not clear if we can do anything with sparkle 1.5 and
>  if Automator actions are really "non-apps"...
>
>  So, I am developing an Automator action, that I do sometime need to
>  update as anything. I was wondering if anyone has tried to use Sparkle
>  to manage Automator actions updates?
>  The actions do have a UI, where a "check for update" could be put, but:
>  1- it's not clear if Sparkle will be able to install the .action in the
>  right directory (i.e. not in Applications but in Library/Automator)
>  2- when compiled into a workflow (or finder plugin, or whatever), the
>  action UI is then hidden (or at least, partially hidden), so it's not
>  clear how the check for update will work then.
>
>  Any idea on this?
>
>  Mort'
>  _______________________________________________
>  Sparkle mailing list
>  Sparkle at lists.andymatuschak.org
>  http://lists.andymatuschak.org/listinfo.cgi/sparkle-andymatuschak.org
>



-- 
Mark Munz
unmarked software
http://www.unmarked.com/