Chris Messina's dashboard

this is identical in concept to work i did about a year and half ago:

SOAP Client:

http://ditchnet.org/soapclient

swap out WSDL + SOAP for XRDS + XML

(although this would prolly be easier to implement as WSDL and SOAP are exceedingly (and needlessly) complex)

I'll be candid on this one... i won't add xrds support unless it becomes much more widely deployed than it is currently. There is a very long laundry list of exciting features I'd like to add to Fluid.. and while I find this area interesting (obviously since I've done significant work on it in the past), it's not very compelling at the moment from a user stand point.

Fluid currently has a JavaScript api for adding Dock menu items. Further expanding this api to main menu items has been in the plans for quite some time, but I've been working on features I thought were more exciting. the JS API for altering the main menu will come eventually. It will also allow easy setting of keyboard shortcuts as those are bound to main menu items in os x.

even if xrds does become popular, I'm still not sure that auto-detection and auto-menu building (as i did with SOAP Client in the past) will be more compelling for developers than the ability for devs to craft userscripts for altering the main menu more 'manually'. the JS API should offer a lot more flexibility

I think this is a fantastic idea. I've been planning an "Ajax" Plug-in API for some time... the Ajax Plug-in api will be fairly light layer on top of the existing Cocoa plugin api... basically, I'll provide a plugin template with a webview and javascript context already setup for you. this will serve as the foundation of what you have suggested above.

it might be interesting to try to make the ajax plugin api compatible with some other existing 'widget' platforms like iGoogle, netvibes etc, so those widgets can just run as a Fluid SSB Ajax plugin with little to no changes...

But frankly, being an OpenSocial container interests me even moooaaaar. Stay tuned.. I have some more fun stuff coming out this week, but I'll be getting to this stuff soon after.

This has now been resolved with Today 1.1's release. Enjoy!

Ok cool. I mean, if it could be done w/ an "after market" Greasemonkey script, that'd be cool too. I just don't know how hard it would be, given how slick the Mail implementation is. – Chris Messina, 1 day ago

This would be totally great... i wish the webkit team would add this to webkit. the problem for fluid is that something like this would require customization of webkit, which in turn requires shipping a custom version of the framework... which I'm not doing,and I dont want to do due to both the size of the framework and other issues (webkit team actually recommends against shipping a custom webkit framework with yr app... although its not unprecedented)

i may file an enhancement request for this on webkit.org...

woopsie!

I like this quite a lot... Fluid.app proper def needs some attention. The difficulty will be in keeping it ultra-simple.... good news is that I think something like this passes the KISS test... watch for something similar soon...

The twitter link doesn't seem to be working for me...