Fluid 0.8 coming soon
Just a heads up to Fluid user community… The next version of Fluid is almost ready for release with lots of new goodies including Bookmarks (hidden by default), resizable search box, “apple-touch-icon” support, auto spell checking, TinyURL support, more JavaScript APIs, hideable status bar, and integrated Userscripting (greasekit/monkey). I just need to do some testing of userscripting. If anyone wants to help beta test the userscripting feature, let me know by email or comment and I’ll hook you up within a day or two.
I’m dedicated to adding a few more important features like blacklists/whitelists and session restore on my way to a 1.0 release, so stay tuned.
In the meantime, I’m looking for a solution for an online community/issue tracker/wiki for the Fluid user base… I’d prefer something open source that I can host myself, but I’m open to pretty much any ideas, including 3rd party solutions. If I have to host it myself, a tool based on PHP/MySQL is pretty much required… as that’s all I’ve got from my hosting provider. Any recommendations?
February 25th, 2008 at 05:44 am
Is Fluid going Open Source? You could use Google Code. Trac looks pretty cool, too, but uses Python. You’ve probably got that at your provider, too.
February 25th, 2008 at 11:14 am
blalor’s suggestions are good.
I’d be willing to beta test the user scripting. If you open source it, I’d also be willing to contribute.
Will 0.8 separate the cookies from Safari?
Ciao!
February 25th, 2008 at 14:12 pm
Fluid is not open source, so… Google Code is not an option. As for Trac… well, Python would actually be my first choice for a server side language… but again, my virtual hosting provider offers PHP/MySQL only. If there’s a compelling for-pay 3rd party Trac-hosting service, I’m all ears, but I can’t host it.
February 25th, 2008 at 18:02 pm
hi Todd -
I have a question/request. Would it be possible down the road for the logo to be a specific SSB icon.
So like it looks for site_spec.png in the root. The reason I would request this is, we have one of these web apps that people use in this way. And, while the touch icon is a step forward, because we are assuming it goes through that bending/trimming process that apple puts it through, it actually looks kinda weird without it.
Anyhow thanks!
February 25th, 2008 at 19:19 pm
oh, and @The Doctor What… unfortunately, no, v0.8 will not introduce separate cookie jars. I would _love_ to add that feature, but if I understand the advice I’ve gotten from the WebKit team, cookie management is a feature of CFNetwork itself… AFAIK, you cannot easily plug an entirely different networking stack into WebKit at will.. and even if you could, I wouldn’t know where to begin. In other words, that feature is a potentially very large task, and I’m not even entirely sure it’s possible with WebKit. :0[ If anyone can prove me wrong, I’m all ears, as I’d love to add that feature.
@Ben Smith, I think that’s a great idea. Stay tuned.
February 26th, 2008 at 00:12 am
Panic uses Google Groups for their Coda user community, but that might not be an optimal solution for issue tracking.
You could use mediawiki, it’s easy to install and configure.
Bugzilla seems popular for issue tracking, but requires PERL.
Some things I’d like to see in Fluid are:
* Each fluid app is a separate unit so that cookies etc aren’t shared.
* Ability to turn off history, so it doesn’t hog memory over time like Safari. (I would use Safari if I actually needed a real browser history)
* Tab behavior like Safari or Firefox (or even better, the options that Safari Stand brings to Safari)
Otherwise Fluid is looking good!
February 26th, 2008 at 00:24 am
@Erik… thanks for trying Fluid! I’ve addressed the separate cookie jar issue above. As for tabbed browsing… it’s in there, just turned off by default. Enable it in the preferences window.
As for disabling History.. nah. I’m not convinced.
February 26th, 2008 at 04:08 am
@Todd, I take a long time writing comments, should have reloaded before I posted. Didn’t know cookies are part of CFNetwork - but I know that the other ports of webkit (http://planet.webkit.org/) are looking at replacing CFNetwork, since it won’t be open source anymore. Maybe that’s what we need to wait for?
About the tabs: when closing a tab, the tab on the left gets activated in Fluid, but Safari picks the tab to the right. Firefox picks the previously active tab. I think either of these behaviours would be more intuitive.
February 26th, 2008 at 16:20 pm
Will it be possible to open the link in the default browser Behind the Fluid app?
February 26th, 2008 at 23:49 pm
I highly recommend the Mantis bug tracking system. It’s written in PHP, and most importantly, just works.
February 27th, 2008 at 02:54 am
Came back to Fluid and I really appreciate where it’s going.
One thing I noticed is that GMail badge support does not work when using http*s*://mail.google.com/mail
I’m sure this will be easy to fix for the next release.
Keep up the good work!
February 27th, 2008 at 12:42 pm
@Erik I agree about the tabs… this will be fixed before 1.0.
@Tiago I’ll look into that.
@Ben thanks!
@Crazor Glad you’re liking Fluid. But sorry no… there will be no fixes to the site-specific functionality in 0.8. I’m integrating Userscripting directly into Fluid via GreaseKit. After that is done, the plan is to move *all* site-specific functionality into community-maintained userscripts (javascript). More on that once 0.8 is out.
And as for issue tracking… I’m beginning to think something like Google Groups might be what I’m looking for after all rather than something as structured as Bugzilla/Mantis. More news to come after 0.8 (this week).