Fluid 0.8.3 Released
0.8.3 contains a couple of bug fixes. Including one serious, intermittent crasher that was introduced in 0.8.
Also, this release fixed the bug where deselecting “Fluid attempts to show Dock badge labels” didn’t work (the Dock badge labels were erroneously still updated). This fix will allow Userscript hackers to move forward with developing Userscripts for Gmail, Google Reader, Facebook and Flickr that update the Dock Badge.
I’ve also noticed an issue with Gmail SSBs. It seems that upon creation, a Gmail SSB will not load until you reload the page 3- 5 times. After that all seems fine. I don’t know what this is about, but the issue is present at least back to 0.8 and possibly earlier. So I thought I’d at least get these fixes out now, and look into that soon.
Changes in 0.8.3:
- FluidInstance.app: Bug fix for a common crasher introduced in 0.8 (Crash log will show -[TODAppDelegate fetchHomeURL] in crashed thread).
- FluidInstance.app: Bugg fix: Disabling Preference: “Fluid attempts to show Dock Badges” actually works now.
- FluidInstance.app: SSBs are smarter about what URLs match the “home URL”.
March 4th, 2008 at 12:51 am
I would like to distribute an application that I created with Fluid on the internet. I will, of course, be more than happy to give you credit etc., but I have added to it by putting some GPL’ed code in the application bundle, and wrapping FluidInstance with a script which starts a web local server.
I am wondering if you will legally allow me to do this, or what stipulations you might want to put on it. You can see the full description of what I did at:
wiki.sagemath.org/SageMacApplication
Incidentally, it would be great if there were an official hook that I could use to start the server rather than having to hack around things. I realize this isn’t the main purpose of Fluid, so I understand if you aren’t interested in adding it, but something like Platypus with a browser would be awesome.
March 4th, 2008 at 2:04 am
Hello,
great tool!!! awesome
but i have one question, do you think there will be a windows version? it would be so great to use the webkit engine for both worlds…
March 4th, 2008 at 4:55 am
First, thanks for nice application!
I think Userscript feature conflicts with Greasekit. I use Greasekit with Safari, and I also use some scripts with Fluid. But when I enable some scripts on any of my fluid apps, Safari’s Greasekit scripts are all disabled(I have to enable all the scripts every time I run Safari). And when I quit safari, all scripts on my fluid apps disabled.
In short, when I first run Safari or any Fluid apps after rebooting, I should turn on scripts manually(actually, when I quit Safari and Fluid apps, I have to turn the scripts on manually, again).
I think the setting/preference of Fluid’s script and Greasekit conflict in some way. It seems that they reset each other.
March 4th, 2008 at 5:04 am
Hello Todd,
first and foremost kudos for the great work you do with Fluid. I use Fluid mainly for Google Reader and it has proven a godsend, despite being a bit rough around the edges, which you are probably aware of and which can be worked around or ignored (for instance, it occasionally reverts to calling instances FluidInstance.app, creating ghost entries for this in Application Support and Growl application configuration ; updating SSBs used by multiple users regularly borks up the SSB — I re-create these each time I update. Also, in Google Reader’s case, the unread count is always off / lagging behind, which I know you’re working on).
My only real quibble is the fact that user scripts aren’t sticky. Each time I start my Google Reader SSB, I have to tick on all my scripts and reload, which makes using user scripts a bit of a hassle…
I have seen this commented upon before ; do you think you could make me even happier with Fluid than I am by having a look at the issue ? I’d be happy to provide feedback on this if it helps.
Again, great work and thank you so much for providing Fluid free of charge.
March 4th, 2008 at 5:09 am
@Byungho Min : I am not sure this is an interaction with your GreaseKit install and / or Safari — my user scripts do reset themselves too, each time I start Fluid, even though I don’t use GreaseKit.
March 4th, 2008 at 7:28 am
@Rheta Shan: I thought in that way because my Greasekit for Safari are reset repeatedly, after I use Fluid’s userscripts feature. Actually, it is true that Fluid and Greasekit conflict. But I think Fluid has some bug on its userscripts feature, seeing you(who has not installed Greasekit) also have the similar problem. Maybe the bug of Fluid influences Greasekit for Safari.
March 4th, 2008 at 1:11 pm
@Janko Fluid for windows might actually be interesting.. I’ve done some .NET development in the past and enjoyed it. I will say this… if Fluid is ever available for Windows, it will be a *native* windows app and will not be based on the same source code as Fluid for Mac OS X. Also, this will not be happening any time soon at all… I have **way** too many plans for Fluid on Mac. In the meantime you should check out Prism and Bubbles.
@Byungho Min now that Userscripting/GreaseKit is integrated directly into Fluid, it is no longer compatible with GreaseKit run normally (as a SIMBL Plugin). You Should exclude (or just never include) any Fluid SSB in GreaseKit’s preferences. In other words, don’t enable the GreaseKit plugin for any Fluid SSB.
As for the Userscripting bugs in Fluid (scripts dont remember their ‘enabled’ state across launches) I’m looking into that and will get you a fix ASAP. Userscripting is about to go into high gear in Fluid… With the next release I’ll be shipping Fluid with some default Userscripts and all site-specific behavior will live there instead of in Fluid itself.
I’m also looking into the Growl icon bug.
thanks all!!!!
March 4th, 2008 at 2:40 pm
I am having a problem with Fluid. I created two different web application as a FluidApp today. Both of them (different vendors) do work in Safari perfectly.
However the Fluid version hangs on logging into the web app. The transfer stops in the middle and nothing happens from there.
I don’t use any special options or else. What am I doing wrong ?
March 4th, 2008 at 3:40 pm
@Bret, I’ll need a much more detailed bug report than that to help you out.
March 4th, 2008 at 8:18 pm
I am really liking fluid, but just came across something that is a little bit of a problem/annoyance. When I close the application I created and then reopen it the new version retains the same window size as the last created window. This means if the last created window was a pop-up then my new window is the same size as the pop-up was. Would it be possible to have a generic window size that the application opens with every time instead of it remembering the size of the last created window?
Just wondering.
March 5th, 2008 at 2:57 am
Hi Todd,
what can I say.
I am doing the following steps on a German installation of Mac OS X (10.5.2):
1. Launch FluidApp (0.8.3)
2. Enter a Name and URL (see list below)
3. Click “Create” and launch the new application directly.
While the first page loads perfectly, I can’t navigate to any other page. Once I click on a link or submit a form the requested URL starts loading but never finishes.
Typing the URLs in a Safari window works ok.
Here is the list of (public) URLs I tried:
- http://www.yahoo.com
- http://www.appmite.de
- http://www.stuttgart.de
If there is anything else I can lookup for you (log files, error console) please let me know.