|
Hi all.
I'm working in a portlet class with some extensions
to implement
functionalities like mynetscape. The class adds
the
following methods:
+ getAllowClose(): the portlet can be eliminated
quickly from the home
page
+ getAllowMinimize(): the portlet can be minimized in the home page
(only the title bar is visible)
+ setAttribute(): to store a permanent value
in the portle config
(using PersistentService)
+ getAttribute(): to retrieve a permanent value
from the portlet config
+ isMinimized(): to ask if the portlet is
minimized
+ setMinimized(): to put the portlet in
minimized state
+ setNormal(): to put the portel in the normal
state
With this extensions I made a new PortletControl
class that:
+ Shows the title bar with Config,
Minimize/restore, Maximize, Close
buttons
+ Adds in the path info some values so the portlet
knowns when
the user click Configure/Maximize
buttons
+ Adds an action to process
Close/Minimize/Restore
+ Uses Velocity to render the title and
borders
So:
+ Using velocity in the PortletControl class the
users
have differents themes to
choice
+ You can implement portlets like
this:
- A message list. In
minimized state shows how many
message are in the
inbox, in normal state shows the last
messages
received (subject), in maximized state
shows the last
x messages (subject, author, date), In
config state set how
many messages you can see
- A calendar. In minimized state
shows how many alerts
you have today, in normal
state shows a little calendar,
in maximized state shows
an agenda, ...
Additionaly I made the Portlet extension to support
Velocity so
with just un portlet class and a screen you can
make all your
portlets
All is working fine, with some hacking in the code
(pathinfo, PersistenceService)
What do you think about this ?. Is possible to
include
the extensions in the AbstractPortlet class
?
That's all ( eso no + )
excuse me for my english :-(
---
Roberto Carrasco R. |
- Re: Portlet extensions & Velocity Roberto Carrasco
- Re: Portlet extensions & Velocity Rapha�l Luta
