Linked by Thom Holwerda on Fri 7th Dec 2007 19:44 UTC, submitted by Bill Davenport
General Development Ruby on Rails 2.0 has been released. "Rails 2.0 is finally finished after about a year in the making. This is a fantastic release that's absolutely stuffed with great new features, loads of fixes, and an incredible amount of polish. We've even taken a fair bit of cruft out to make the whole package more coherent and lean." On Zenbits, they give tips on how to install 2.0.
Thread beginning with comment 289459
To read all comments associated with this story, please click here.
Wt - Qt for webs
by pgquiles on Fri 7th Dec 2007 22:56 UTC
pgquiles
Member since:
2006-07-16

I started developing with Rails back in the 0.13 days, I bought both editions of Agile Web Development with Rails... I knew one or two things about Ruby and Rails.

But abandoned Rails as soon as I discovered http://www.webtoolkit.eu . It clones the Qt API but it outputs AJAX webapps instead of a GUI application.

Advantages? Many:
- Develop websites in C++, using the Qt API (that includes signals and slots)
- No need for bindings between Ruby/PHP/JSP and C libraries
- More third party libraries available than any other language
- You can build your application as a FastCGI module you can use with Apache/LigHTTP/IIS/etc, or as a standalone application with its own webserver
- It scales like hell: it can deal with more hits than Rails, PHP or any other will ever handle
- Beautiful widgets (ExtJS, http://www.extjs.com )

In a webapp I'm developing (for intranet use) I'm using Wt, Samba and Apache with the mod_auth_ntlm module to authenticate and authorize users without asking them to login: if they are using Firefox or Internet Explorer, I just look for their Active Directory credentials using mod_auth_ntlm (an Apache module, I'm compiling my webapp as a FastCGI module) and check their permissions using Samba: are they allowed to see this or that?. It works like a charm and it's very easy to do. Can you do that painlessly with Rails, PHP or JSP?

Reply Score: 3

RE: Wt - Qt for webs
by sbergman27 on Fri 7th Dec 2007 23:20 in reply to "Wt - Qt for webs"
sbergman27 Member since:
2005-07-24

Is it reliable? Their site seems to be down.

Here is what google has cached:

http://tinyurl.com/2rohon

Reply Parent Score: 2

RE[2]: Wt - Qt for webs
by pgquiles on Fri 7th Dec 2007 23:36 in reply to "RE: Wt - Qt for webs"
pgquiles Member since:
2006-07-16

It is reliable and yes, the site seems to be down now. You can download the source from Sourceforge: http://sourceforge.net/projects/witty/

Ubuntu packages are available at my PPA: https://edge.launchpad.net/~pgquiles/+archive

Koen Deforche, one of the guys behind Wt, is always eager to help in the witty-interest mailing list: http://sourceforge.net/mail/?group_id=153710

Reply Parent Score: 3

RE: Wt - Qt for webs
by Clinton on Sat 8th Dec 2007 07:52 in reply to "Wt - Qt for webs"
Clinton Member since:
2005-07-05

I don't think you can use the words "C++" and "painlessly" in the same sentence. ;)

Reply Parent Score: 3

RE[2]: Wt - Qt for webs
by eosp on Sat 8th Dec 2007 18:16 in reply to "RE: Wt - Qt for webs"
eosp Member since:
2005-07-07

Trust me, coding in Qt is nothing like coding in regular C++. It's like a whole different language.

Reply Parent Score: 1

RE: Wt - Qt for webs
by Richard Dale on Sat 8th Dec 2007 08:43 in reply to "Wt - Qt for webs"
Richard Dale Member since:
2005-07-22

I'm not sure if writing web apps in C++ is my idea of fun. I really like the way you can just change something in a Rails project and try it out instantly without needing a compile step.

There doesn't seem to be a really comprehensive Prototype based widget toolkit, only individual widgets and some interesting extensions at the moment.

Jester is an implementation of ActiveResource written in JavaScript:

http://jesterjs.org

I thought this post was interesting, it shows how you can use Jester with Dojo data aware widgets:

http://mysterycoder.blogspot.com/2007/11/dojo-grid-jester-rails-res...

That would allow a Rails app to serve up a complete JavaScript widget based version of the app, returning the entire application code from a url like say /app. That code would then use ActiveResource and Jester to interact with the web server via RESTful urls.

The methods in the controllers could either return complete html pages for simpler browsers, or the xml for the ActiveResource widget based app. So you could write a single Rails app that would have multiple personalities; straight html, javascript widgets or active resource based web services.

Reply Parent Score: 2