upgrading SSB's

[Yi Qiang]

Hey all,
I was wondering how you guys updated your SSB's when a new version of
Fluid comes out. I have something like 8 SSB's and it's rather
annoying to open each one up individually and upgrade them one by
one.

What do you guys do?

Cheers,
Yi

http://yiqiang.org

[Dane]

I'm also running about 4 SBS's and a more centralised update approach
would be great - although I'm not exactly sure how it would work out?
Maybe the main fluid app can keep a log of the SBS's and then when an
update comes through it knows to update them all.

Although a bigger issue I think is that each time I upgrade I loose my
pretty icon that I have set for each! Any way that the update system
can somehow keep the SBS's icon?

On Apr 15, 5:52 am, Tim Harper <timchar...@gmail.com> wrote:
> nothing more than you are doing :)
>
> However, I only update them when I really want a feature for a given  
> SSB.
>
> And, hey, at least it's better than recreating the application :)
>
> TIm

[Chuck]

When I update my SSBs it keeps the icon all right and I see a generic
icon'd application in my trash.

So *that* is a bit weird, but otherwise, yeah--maintaining updates for
a bunch of SSBs is a bit annoying. Just one of the tradeoffs I guess.

Cheers,
Chuck

/sorry, got nuthin

[todd.dit...@gmail.com]

@Yi Qiang Updating each SSB individually is the expected/supported way
to upgrade your SSBs. When you consider that it's only a 2 click
process for each it's not so bad. In version 0.1, I had not yet
included the Sparkle Update framework... at that time you would have
had to delete and recreate all SSBs manually. that wold *not* be
cool.

So the individual updates for the SSBs is definitely a feature, not a
bug. :0]

@Dane re: tracking all SSBs you create and updating all at once... if
you think about it that's not really possible. After you create an SSB
you are free to drag the SSB anywhere you like on your system or even
other systems... there's really no way for Fluid to track where you
drag each SSB, and if it were to try, frankly that would be a little
creepy.

The only possible alternative to the current setup is to have some
centralized resource that runs all Fluid SSBs that can be updated in
one go. This design would have some nice benefits, but also many
drawbacks:

1. Installation of fluid would require an installer (Rather than just
drag and drop) to install the centralized resource. although i dont
mind installers so much, many users go ballistic when they see an
installer, and demand to know what is being installed on their system.
I dont even want to go there (and i wont).

2. This would kill the ability to drag SSBs to other systems or share
them with friends (both of which Fluid users have been quite adamant
about doing). The current design allows complete freedom to do what
you want with any SSB.


So.. as you can see, the current situation is the least sucky of
several sucky options. Two click updates... not so bad. :0] This
design is here to stay.


Todd

[Brian J. Landau]

I whole heartedly agree with this.
The problems with other possible update options are significantly
worse than having to update each SSB, independently.

[Dane]

Thanks for the replies.

I guess I'll have to keep an eye on the missing Icon thing for the
next update. It definately did happen to one of my SBS's, but I did
see last night I updated another one and it kept the icon so it might
have been a one off.

Regarding the multiple/centralised updates - that all makes sense - I
love the flexability of fluid and I agree implementing any of those
systems is going to cripple the program rather than improve it.

I was just concerned about your bandwidth usage with everyone spawning
off multiple updates :-)