[Seaside] Seaside Portlet [IDEA]

[Avi Bryant]

On Wednesday, October 29, 2003, at 10:18 AM, Giovanni Giorgi wrote:

> In short Portlet are a sub-spec of Servlet, born to get "resuable 
> portal components"  for aggregating data inside a web site, thinked as 
> a portal.

Can you summarize what makes "portlets" different from regular 
"servlets"?

>   1. Seaside can define an abstract PortletRenderer to be mapped as a
>      render for HTML, WML and so on.
>      We should only stop to use "html text:...." and start to think in
>      terms of
>      "view renderText:...." and so on, speaking of "abstract buttons"
>      instead of form buttons etc.
>      For example a MorphRenderer should be able to render a seaside
>      component onsqueak screen!

Does anyone actually use WML anymore?  The trend I'm seeing is to have 
full HTML browsers on handheld devices.  I'm skeptical that there's 
much utility in supporting multiple markups (simple XHTML + CSS is the 
way things are going to go, IMO).

>   2. We can  aggregate seaside components in a very simple way!
>      Sometimes I think the render: and call: method are the TRUE power
>      of seaside....

I agree.  Although HTMLRenderer is pretty cool too ;).

> We can start only defining a SeasidePortletComponent and starting form 
> here...do you like it? ;)

Well, why don't you write an example portlet or two that we can look at?