You are viewing a plain text version of this content. The canonical link for it is here.
Posted to pluto-user@portals.apache.org by Yamamoto Masahiro <ya...@lab.ntt.co.jp> on 2004/02/04 07:48:34 UTC
Question on Portlet Window State defined in JSR-168
Hi all,
Does anyone know if the window states NORMAL, MAXIMIZED, MINIMIZED
all are "Required" states or not?
Thanks,
Masa
Re: Question on Portlet Window State defined in JSR-168
Posted by Yamamoto Masahiro <ya...@lab.ntt.co.jp>.
Hi felix,
I have got some information from Michael Westbay at sourceforge on this issue.
The RSS portlet extends the GenericPortlet which has logic for checking window
state and generating html markup fragment respectively in the doDispatch method.
So the RSS portlet can deal with the min, max, normal requests well.
Thanks>Michael
Regards,
Masa
"mail@felixguntrum.de" wrote:
>
> the only thing i can see on
> http://sourceforge.net/projects/portlet-opensrc/ is:
>
> "We're Sorry.
> The SourceForge.net Website is currently down for maintenance.
> We will be back shortly"
>
> i will take a look at this code tomorrow ;)
>
> Yamamoto Masahiro wrote:
>
> >Hi felix,
> >
> >Thanks for your answer.
> >
> >"mail@felixguntrum.de" wrote:
> >
> >
> >>hi masa,
> >>let me try to answer your question.
> >>the answer should be "yes", because the portlet-concept want to enhance
> >>the user experience with this "extra-functionality". if your portlet
> >>does not support the different window-states, for example, you can´t
> >>minimize the portlet to get temporarily more space for another portlet
> >>on your portal-page.
> >>
> >>
> >
> >I have the same opinion with you.
> >
> >
> >
> >>you can only support the different window-states programmatically. the
> >>minimum thing you should do, is to prevent the portlet producing
> >>markup-fragments when it has the window-state "minimized".
> >>
> >>WindowState state = request.getWindowState();
> >>if ( ! state.equals(WindowState.MINIMIZED)) {
> >>//produce your content
> >>}
> >>
> >>
> >
> >Actualy, there is no such code or logic like the one you have shown above
> >in the RSS portlet. But the portlet can deal with the "min","normal" or "max"
> >request well. You can find the whole source code of portlet at the URL in my
> >previous e-mail. That is why I was confused whether the logic for checking
> >window state should be programmed or not.
> >
> >Thanks,
> >Masa
> >
> >
> >
> >
> >>i hope i could help you
> >>felix
> >>
> >>Yamamoto Masahiro wrote:
> >>
> >>
> >>
> >>>Hi Stefan,
> >>>
> >>>Let me explain my question for you.
> >>>I just want to confirm that if the portlet MUST support the NORMAL,
> >>>MAXIMIZED, MINIMIZED states. According to your reply, the answer
> >>>seems to be a 'YES'. Am I right?
> >>>
> >>>Regarding the program to deal with these window states, what will
> >>>be shown up if the portlet does not include an implementation for
> >>>producing respective html fragments according to the window state?
> >>>
> >>>I have used such a RSS portlet from the following URL.
> >>>
> >>>http://sourceforge.net/projects/portlet-opensrc/
> >>>
> >>>The RSS portlet has no routine to deal with window state but it runs
> >>>well on pluto+tomcat platform. The portlet produces the same output
> >>>including 'href's for NORMAL, MAX state and an empty table for MIN.
> >>>Do you know who deals with all window states in this case?
> >>>
> >>>Thanks,
> >>>Masa
> >>>
> >>>Stefan Hepper wrote:
> >>>
> >>>
> >>>
> >>>
> >>>>not sure what you mean with required. required for whom? the portlet?
> >>>>the portal?
> >>>>The portal must support these three window states, whereas the portlet
> >>>>must be programmed that way that it can deal with these window states
> >>>>(simplest way, not the recommendet one, of doing this is just produce
> >>>>the same output for all).
> >>>>
> >>>>Stefan
> >>>>
> >>>>Yamamoto Masahiro wrote:
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>>Hi all,
> >>>>>
> >>>>>Does anyone know if the window states NORMAL, MAXIMIZED, MINIMIZED
> >>>>>all are "Required" states or not?
> >>>>>
> >>>>>Thanks,
> >>>>>Masa
Re: Question on Portlet Window State defined in JSR-168
Posted by "mail@felixguntrum.de" <ma...@felixguntrum.de>.
the only thing i can see on
http://sourceforge.net/projects/portlet-opensrc/ is:
"We're Sorry.
The SourceForge.net Website is currently down for maintenance.
We will be back shortly"
i will take a look at this code tomorrow ;)
Yamamoto Masahiro wrote:
>Hi felix,
>
>Thanks for your answer.
>
>"mail@felixguntrum.de" wrote:
>
>
>>hi masa,
>>let me try to answer your question.
>>the answer should be "yes", because the portlet-concept want to enhance
>>the user experience with this "extra-functionality". if your portlet
>>does not support the different window-states, for example, you can´t
>>minimize the portlet to get temporarily more space for another portlet
>>on your portal-page.
>>
>>
>
>I have the same opinion with you.
>
>
>
>>you can only support the different window-states programmatically. the
>>minimum thing you should do, is to prevent the portlet producing
>>markup-fragments when it has the window-state "minimized".
>>
>>WindowState state = request.getWindowState();
>>if ( ! state.equals(WindowState.MINIMIZED)) {
>>//produce your content
>>}
>>
>>
>
>Actualy, there is no such code or logic like the one you have shown above
>in the RSS portlet. But the portlet can deal with the "min","normal" or "max"
>request well. You can find the whole source code of portlet at the URL in my
>previous e-mail. That is why I was confused whether the logic for checking
>window state should be programmed or not.
>
>Thanks,
>Masa
>
>
>
>
>>i hope i could help you
>>felix
>>
>>Yamamoto Masahiro wrote:
>>
>>
>>
>>>Hi Stefan,
>>>
>>>Let me explain my question for you.
>>>I just want to confirm that if the portlet MUST support the NORMAL,
>>>MAXIMIZED, MINIMIZED states. According to your reply, the answer
>>>seems to be a 'YES'. Am I right?
>>>
>>>Regarding the program to deal with these window states, what will
>>>be shown up if the portlet does not include an implementation for
>>>producing respective html fragments according to the window state?
>>>
>>>I have used such a RSS portlet from the following URL.
>>>
>>>http://sourceforge.net/projects/portlet-opensrc/
>>>
>>>The RSS portlet has no routine to deal with window state but it runs
>>>well on pluto+tomcat platform. The portlet produces the same output
>>>including 'href's for NORMAL, MAX state and an empty table for MIN.
>>>Do you know who deals with all window states in this case?
>>>
>>>Thanks,
>>>Masa
>>>
>>>Stefan Hepper wrote:
>>>
>>>
>>>
>>>
>>>>not sure what you mean with required. required for whom? the portlet?
>>>>the portal?
>>>>The portal must support these three window states, whereas the portlet
>>>>must be programmed that way that it can deal with these window states
>>>>(simplest way, not the recommendet one, of doing this is just produce
>>>>the same output for all).
>>>>
>>>>Stefan
>>>>
>>>>Yamamoto Masahiro wrote:
>>>>
>>>>
>>>>
>>>>
>>>>>Hi all,
>>>>>
>>>>>Does anyone know if the window states NORMAL, MAXIMIZED, MINIMIZED
>>>>>all are "Required" states or not?
>>>>>
>>>>>Thanks,
>>>>>Masa
>>>>>
>>>>>
>
>
>
Re: Question on Portlet Window State defined in JSR-168
Posted by Yamamoto Masahiro <ya...@lab.ntt.co.jp>.
Hi felix,
Thanks for your answer.
"mail@felixguntrum.de" wrote:
>
> hi masa,
> let me try to answer your question.
> the answer should be "yes", because the portlet-concept want to enhance
> the user experience with this "extra-functionality". if your portlet
> does not support the different window-states, for example, you can´t
> minimize the portlet to get temporarily more space for another portlet
> on your portal-page.
I have the same opinion with you.
> you can only support the different window-states programmatically. the
> minimum thing you should do, is to prevent the portlet producing
> markup-fragments when it has the window-state "minimized".
>
> WindowState state = request.getWindowState();
> if ( ! state.equals(WindowState.MINIMIZED)) {
> //produce your content
> }
Actualy, there is no such code or logic like the one you have shown above
in the RSS portlet. But the portlet can deal with the "min","normal" or "max"
request well. You can find the whole source code of portlet at the URL in my
previous e-mail. That is why I was confused whether the logic for checking
window state should be programmed or not.
Thanks,
Masa
> i hope i could help you
> felix
>
> Yamamoto Masahiro wrote:
>
> >Hi Stefan,
> >
> >Let me explain my question for you.
> >I just want to confirm that if the portlet MUST support the NORMAL,
> >MAXIMIZED, MINIMIZED states. According to your reply, the answer
> >seems to be a 'YES'. Am I right?
> >
> >Regarding the program to deal with these window states, what will
> >be shown up if the portlet does not include an implementation for
> >producing respective html fragments according to the window state?
> >
> >I have used such a RSS portlet from the following URL.
> >
> > http://sourceforge.net/projects/portlet-opensrc/
> >
> >The RSS portlet has no routine to deal with window state but it runs
> >well on pluto+tomcat platform. The portlet produces the same output
> >including 'href's for NORMAL, MAX state and an empty table for MIN.
> >Do you know who deals with all window states in this case?
> >
> >Thanks,
> >Masa
> >
> >Stefan Hepper wrote:
> >
> >
> >>not sure what you mean with required. required for whom? the portlet?
> >>the portal?
> >>The portal must support these three window states, whereas the portlet
> >>must be programmed that way that it can deal with these window states
> >>(simplest way, not the recommendet one, of doing this is just produce
> >>the same output for all).
> >>
> >>Stefan
> >>
> >>Yamamoto Masahiro wrote:
> >>
> >>
> >>>Hi all,
> >>>
> >>>Does anyone know if the window states NORMAL, MAXIMIZED, MINIMIZED
> >>>all are "Required" states or not?
> >>>
> >>>Thanks,
> >>>Masa
Re: Question on Portlet Window State defined in JSR-168
Posted by "mail@felixguntrum.de" <ma...@felixguntrum.de>.
hi masa,
let me try to answer your question.
the answer should be "yes", because the portlet-concept want to enhance
the user experience with this "extra-functionality". if your portlet
does not support the different window-states, for example, you can´t
minimize the portlet to get temporarily more space for another portlet
on your portal-page.
you can only support the different window-states programmatically. the
minimum thing you should do, is to prevent the portlet producing
markup-fragments when it has the window-state "minimized".
WindowState state = request.getWindowState();
if ( ! state.equals(WindowState.MINIMIZED)) {
//produce your content
}
i hope i could help you
felix
Yamamoto Masahiro wrote:
>Hi Stefan,
>
>Let me explain my question for you.
>I just want to confirm that if the portlet MUST support the NORMAL,
>MAXIMIZED, MINIMIZED states. According to your reply, the answer
>seems to be a 'YES'. Am I right?
>
>Regarding the program to deal with these window states, what will
>be shown up if the portlet does not include an implementation for
>producing respective html fragments according to the window state?
>
>I have used such a RSS portlet from the following URL.
>
> http://sourceforge.net/projects/portlet-opensrc/
>
>The RSS portlet has no routine to deal with window state but it runs
>well on pluto+tomcat platform. The portlet produces the same output
>including 'href's for NORMAL, MAX state and an empty table for MIN.
>Do you know who deals with all window states in this case?
>
>Thanks,
>Masa
>
>Stefan Hepper wrote:
>
>
>>not sure what you mean with required. required for whom? the portlet?
>>the portal?
>>The portal must support these three window states, whereas the portlet
>>must be programmed that way that it can deal with these window states
>>(simplest way, not the recommendet one, of doing this is just produce
>>the same output for all).
>>
>>Stefan
>>
>>Yamamoto Masahiro wrote:
>>
>>
>>>Hi all,
>>>
>>>Does anyone know if the window states NORMAL, MAXIMIZED, MINIMIZED
>>>all are "Required" states or not?
>>>
>>>Thanks,
>>>Masa
>>>
>>>
>
>
>
Re: Question on Portlet Window State defined in JSR-168
Posted by Yamamoto Masahiro <ya...@lab.ntt.co.jp>.
Hi Stefan,
Let me explain my question for you.
I just want to confirm that if the portlet MUST support the NORMAL,
MAXIMIZED, MINIMIZED states. According to your reply, the answer
seems to be a 'YES'. Am I right?
Regarding the program to deal with these window states, what will
be shown up if the portlet does not include an implementation for
producing respective html fragments according to the window state?
I have used such a RSS portlet from the following URL.
http://sourceforge.net/projects/portlet-opensrc/
The RSS portlet has no routine to deal with window state but it runs
well on pluto+tomcat platform. The portlet produces the same output
including 'href's for NORMAL, MAX state and an empty table for MIN.
Do you know who deals with all window states in this case?
Thanks,
Masa
Stefan Hepper wrote:
>
> not sure what you mean with required. required for whom? the portlet?
> the portal?
> The portal must support these three window states, whereas the portlet
> must be programmed that way that it can deal with these window states
> (simplest way, not the recommendet one, of doing this is just produce
> the same output for all).
>
> Stefan
>
> Yamamoto Masahiro wrote:
> > Hi all,
> >
> > Does anyone know if the window states NORMAL, MAXIMIZED, MINIMIZED
> > all are "Required" states or not?
> >
> > Thanks,
> > Masa
Re: Question on Portlet Window State defined in JSR-168
Posted by Stefan Hepper <st...@hursley.ibm.com>.
not sure what you mean with required. required for whom? the portlet?
the portal?
The portal must support these three window states, whereas the portlet
must be programmed that way that it can deal with these window states
(simplest way, not the recommendet one, of doing this is just produce
the same output for all).
Stefan
Yamamoto Masahiro wrote:
> Hi all,
>
> Does anyone know if the window states NORMAL, MAXIMIZED, MINIMIZED
> all are "Required" states or not?
>
> Thanks,
> Masa
>