Here’s a concept, one that i’ve been toying around with myself, actually (more to come soon on my end) — It’s WebCmd — It’s an ajax-based command line. It uses perl + libXmlRequest to produce a “remote command line in a browser” — which is something that would have previously been unheard of without using java, say, oh, 2 days ago.
What does this actually get you? Well, alone, you might be able to do some system administration w/o having to use SSH, which might be an “ok” thing — but really, the key concept is really to provide a new way of accessing old applications. I know there are companies out there that have been really pushing hard to get old green screen applications pushed into the present by doing various things like wrapping the old “screens” in HTML, using java to interface w/ the old application, providing a slightly fancier interface to the old app.
Now everyone’s got a new choice for doing this kind of thing. What i’m more interested, being a linux guy, is the ability to do with ajaxified methods some of the basic things i would normally have to do by opening up a shell, logging into a server, and running some commands.
I’m working on a little utility that i myself will find useful, and i hope others will too.
Both of these are added to the Ajax Toolkit and Project List. I think i’m going to start calling it something else — maybe “rich web framework toolkit and project list” — because it doesn’t really cover “just” ajax anymore.
Ok, I understand that Sabre used the word ‘Rico’ to mean that they’ve got a framework for ‘rich applications.’ However, whenever i read or hear about rico, i can’t help but think of one of two things.
- Tony Soprano — How many times do you hear the mobsters mention the ‘RICO’ laws?
- Rico….. Suave!
Now, I think Rico is exactly what the “Rich Web Application” community needs. Not because of what it is, but because of who is behind it. Sabre is a fairly large company, and they’ve been sponsoring Rico, finally releasing it into the wild. It’s nice that toolkits exist, but you really need an all-encompassing package that supports lots of functionality.
It’s hard to develop an application with lots of little pieces. Prototype is nice, but it doesn’t have all the pieces there. Backbase is great, but it’s not open source, and costs some real money. Dojo will be nice, when/if it gets here. I’m not criticizing, they’re new — they just need time to get everything put together.
For something as complicated as a rich web app framework, you really need some financial backing to put enough people on the project to make it worthwhile. Lone developers go so far, but we need more. I think that’s what we’ve got with Rico. Dojo might have it, i’m not sure how many people from Jot work on Dojo, and how much money Jot has / will have to develop with.
Anyway, I think Sabre’s shown some “enlightened self interest” with releasing Rico, and I think that it’s going to take the web app framework community to new, very good, places.
A couple things: Backbase now has a ‘community edition,’ there’s a greasemonkey script that does ajax debugging, Multiple Text Applicator does ajax lists.
Oh, and here’s something i wished i had yesterday — Live Http Headers — This is a mozilla extension that gives you the ability to see http headers as they’re sent.
All of this is over at my page of ajax toolkits & projects
I’ve been interested in Greasemonkey, a plugin for firefox that lets you customize webpages as you view them. That’s right, it lets you change a webpage or pages on the client, without the server having the slightest clue.
Anyway, I’ve been wanting to learn more about how it works, so when I ran across Dive Into Greasemonkey, I thought, “hey, cool”
So i’m off reading this crap about greasemonkey, now. What will i figure out first, Greasemonkey or Dojo/Ajax?
Ugh. I am too compelled to figure this shit out.