portlet support for rails?

Hi,

I want to know if there is something in the roadmap (I have not seen anything in the trac) about portlet support on rails. What I mean is a rails application or part of it being marked as portlet and automatically the support for the portlet standard being build for it. Also a rails application should be able to load a portlet component. I know is asking a lot but being rails, one can only expect the best :smiley:

That will allow to extend any other application with rails components and load any other already made component even if not done in Ruby.

Thanks

Nope, sounds like plugin territory.

the portlet standard

which standard? :wink:

anyways, I don’t think an implementation of whatever standard you choose is within the scope of rails.

Regards,

Lawrence

Java Portlet Specification - Wikipedia i suppose.

See this one better:

Basically allows code to become an "object" that can be used locally or not. For instance :

I have not idea about how was that implemented but with portlets you can have any of the "widgets" in any machine (think about the weather widget served by some weather-specialized portal) and you just call them and use them. Other way to express it: a standard to make a WWW callable API. DBUS for the WWW. AFAIK it has been implemented in Java and .NET

For instance, in the rubyonrails web there is a demo about how use Flickr API to search some photos. With portlets, you'll catch an already done flickr widget and insert it in your page. Calling the API is more powerful (you build the UI yourself, etc.), calling the portlet is much easier (you get a possibly very complex object already done).

A www ecosystem of widgets done in rails that can be imported with a few lines ... Rocks!

I know the current aim of RoR is not that, so I was wanted to know if it was somewhat in the radar or no.

Thank you for RoR!

Syndication doesn't require any support from Rails core. Let's move this conversation over to the general list.

See this one better:

Basically allows code to become an "object" that can be used locally or not. For instance : Google

I have not idea about how was that implemented but with portlets you can have any of the "widgets" in any machine (think about the weather widget served by some weather-specialized portal) and you just call them and use them. Other way to express it: a standard to make a WWW callable API. DBUS for the WWW. AFAIK it has been implemented in Java and .NET

For instance, in the rubyonrails web there is a demo about how use Flickr API to search some photos. With portlets, you'll catch an already done flickr widget and insert it in your page. Calling the API is more powerful (you build the UI yourself, etc.), calling the portlet is much easier (you get a possibly very complex object already done).

A www ecosystem of widgets done in rails that can be imported with a few lines ... Rocks!

I know the current aim of RoR is not that, so I was wanted to know if it was somewhat in the radar or no.

Thank you for RoR!

> > > > > > the portlet standard > > > which standard? :wink: > > http://en.wikipedia.org/wiki/Portleti suppose. > > -- > Rick

Olsonhttp://lighthouseapp.comhttp://weblog.techno-weenie.nethttp://mephistoblog.com

So, I post this message to rubyonrails-talk?