I know many folks who check my site already read Signal vs. Noise, but this program they posted about today is such a cool concept that I had to write it up as well.
Fluid is a tool from Todd Ditchendorf which allows users to create a stand-alone desktop "app" for any web app. This is accomplished through the generation of a standalone browser for the page, and it supports RSS and the like as well.
Some questions I have (until I try it out at home this evening):
1. What's the resource usage on this puppy - does an "app" for GMail use more ram than Flickr? Is there a minimum RAM/CPU usage regardless of the web app?
2. Does the Fluid app have to stay running in order to use the "apps" you've created? Or is Fluid just the generator?
3. Once you reveal the regular Webkit controls, can you then navigate away from the site? Wouldn't that then make these "apps" simply standalone instances of a Webkit browser? If that's the case, it sounds like running multiple instances of Toad on my Windows 2000 work PC, where each instance has a process ID, and each can crash independently (which they do!).
I'll update this with my findings as soon as I get to play with the new program.
UPDATE: Ha haaaaaa...Seems I missed the fine print. This requires Leopard, and it seems I don't have that. Whoops!
Fluid is a tool from Todd Ditchendorf which allows users to create a stand-alone desktop "app" for any web app. This is accomplished through the generation of a standalone browser for the page, and it supports RSS and the like as well.
Some questions I have (until I try it out at home this evening):
1. What's the resource usage on this puppy - does an "app" for GMail use more ram than Flickr? Is there a minimum RAM/CPU usage regardless of the web app?
2. Does the Fluid app have to stay running in order to use the "apps" you've created? Or is Fluid just the generator?
3. Once you reveal the regular Webkit controls, can you then navigate away from the site? Wouldn't that then make these "apps" simply standalone instances of a Webkit browser? If that's the case, it sounds like running multiple instances of Toad on my Windows 2000 work PC, where each instance has a process ID, and each can crash independently (which they do!).
I'll update this with my findings as soon as I get to play with the new program.
UPDATE: Ha haaaaaa...Seems I missed the fine print. This requires Leopard, and it seems I don't have that. Whoops!