Thursday, April 16th, 2009

Shoes and Swiby; A way to build RIAs that you haven’t thought about

Shoes and Swiby? Changes are you haven’t heard of these technologies, but Paul Hammant had a nice write up with rich clients that access Google App Engine for Java which I linked too from my own piece on the announcement.

Now, Paul has a detailed comparisons of the two Ruby clients with a nice screencast:

Posted by Dion Almaer at 6:46 am
5 Comments

++---
2.2 rating from 17 votes

5 Comments »

Comments feed TrackBack URI

Can anyone explain me what is so rich about this? This all can be done with HTML/Javascript/CSS

Comment by hde — April 16, 2009

“Changes” are you haven’t heard of these technologies

Comment by ilazarte — April 16, 2009

Quick Summary: This video is about rapid prototyping ***Desktop applications*** for doing the same things you’d do with a web app. Video shows a webapp and a Shoes app built on roughly the same data source. This is somehow better because HTML and Javascript are separate languages and awkward and/or ajax apps are hard to build.

Commentary: The main advantages of web applications are the lack of an install and the cross (desktop) platform nature. Why would you throw both away for a mildly cleaner API? I wouldn’t do this for the same reason I’m not particularly interested in Air but at least Air has momentum and some mitigating advantages.

Poor title and summary, I was all disappointed that they were desktop apps. I watched the whole thing expecting them to come out and say “this is GWT for ruby” but nope, just rapid prototyping desktop apps.

Comment by grayrest — April 16, 2009

I stopped watching at “Now for this to run in firefox a pluggin is needed, that would make it really powerful”…

So… a new language to replace HTML, JavaScript and CSS, which would require a plugin for current browsers or a new browser alltogether…

Basically… they build a worse version of flash.

Comment by BenGerrissen — April 16, 2009

As I understand it, Rich Internet Applications aren’t solely limited to web apps. They also encompass the desktop apps that access them, since the apps must be specially equipped to handle the responses and output limitations of RIAs.

I have actually used Shoes for such an application; I had a developmental server that I was tinkering with that was a pain to manipulate, so I wrote a GUI using Shoes. In about 20 minutes, I had a nice little GUI that would allow me to start/stop the server, control the server’s spawned processes, and output the server’s log.

I think one of the points of this article is to show that RIAs extend past the browser and onto the desktop and mobile platforms. Creating an interfacing application need not remove one from the same technologies one has been using to create the RIA; imagine writing a Rails app, then writing an interfacing desktop client in Shoes. One does not have to learn a new language or way of working, one can move from one medium to nother.

Comment by sherrod — April 16, 2009

Leave a comment

You must be logged in to post a comment.