It depends what you mean by "fat". One option is to develop the "back
end" in Hobo and then write the front end in something developed
specifically for that. I'd recommend Sproutcore, but you could
certainly use Flex. I don't think anybody's tried it with Hobo, but
restfulx, a Flex<->Rails bridge, is certainly widely used.
Or you could write everything in Hobo. The standard Hobo is more "web
2.0" and less "fat client", but you can certainly do a lot of rich stuff
on the front using a good Javascript library such as jQuery or MOO.
Bryan
Wildman wrote:
I'll be looking at the book as I try out hobo...it does look
impressive.
I've mostly done client server apps with fat clients, and a major
issue I have with rails (vs say flex) is that the user interface which
rails generates is less rich. I know rails is not focused on rich
client interfaces...and I'm also sure that one can build rich user
interfaces on top of rails/hobo. To get there, I assume that I'd need
to be pretty good with html, javascript, and css? I am not eager to go
there, but that's the way to get a rich ui with rails, right? I've
also heard that there have been some experiments with rails using flex
for the ui, but not sure it's a mainstream, ie well developed, path?
--
You received this message because you are subscribed to the Google Groups "Hobo
Users" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/hobousers?hl=en.
