OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

wsrp-wsia message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Subject: Re: [wsrp-wsia] Issue #31: MINIMIZED state does not necessarilymeannomarkup.


Carsten,
    You are right the JSR is in sync with us here.  I was confused by the JSRs
desire to prevent this behavior in the base class it encourages all portlets to
use.  Unless others object, we should move this issue to resolved.
    -Mike-

Carsten Leue wrote:

> Again I think that there is no issue here. From what I heard from Stefan
> Hepper JSR 168 also mandates that the render method of the portlet will be
> called in minimized state, but that the portlet should not return visible
> markup.
>
> Best regards
> Carsten Leue
>
> -------
> Dr. Carsten Leue
> Dept.8288, IBM Laboratory Böblingen , Germany
> Tel.: +49-7031-16-4603, Fax: +49-7031-16-4401
>
>
>              Rich
>              Thompson/Watson/I
>              BM@IBMUS                                                   To
>                                        wsrp-wsia
>              10/17/2002 02:11          <wsrp-wsia@lists.oasis-open.org>
>              PM                                                         cc
>
>                                                                    Subject
>                                        RE: [wsrp-wsia] Issue #31:
>                                        MINIMIZED state does not
>                                        necessarily       meanno markup.
>
>
>
>
>
>
>
> I agree that it is preferable for JSR168 to be a subset of what we enable.
> Questions relative to differences need to be explicit about what the JSR
> semantics are so that we can work towards a resolution.
>
>                       Andre Kramer
>
>                       <andre.kramer@eu.        To:       wsrp-wsia
> <wsrp-wsia@lists.oasis-open.org>
>                       citrix.com>              cc:
>
>                                                Subject:  RE: [wsrp-wsia]
> Issue #31:  MINIMIZED state does not
>                       10/17/2002 07:09          necessarily    meanno
> markup.
>                       AM
>
> Can returning no markup on MINIMIZED not be up to the remote Entity (and
> leaving it up to the consumer to include it in presentation)? I was more
> concerned by the spec mentioning javascript and other non-visible content
> being allowed as a return from getMarkup() but not visible content. Also,
> there is a separate question of whether getMarkup() should be called at all
> (e.g. to return a title for MINIMIZED Portlet). We should make sure (which
> I
> think is already the case) that JSR168 is a sub-set of possible WSRP
> behaviour.
>
> -----Original Message-----
> From: Gil Tayar [mailto:Gil.Tayar@webcollage.com]
> Sent: 17 October 2002 08:49
> To: wsrp-wsia
> Subject: RE: [wsrp-wsia] Issue #31: MINIMIZED state does not necessarily
> meanno markup.
>
> I have added Rich's text below to the issue's proposed resolution, and left
> it as tentatively resolved.
>
> Mike, I think we should create a new issue on the difference from JSR168.
> Would you like me to create it?
>
> Gil
>
> -----Original Message-----
> From: Michael Freedman [mailto:Michael.Freedman@oracle.com]
> Sent: Wed, October 16, 2002 17:57
> To: wsrp-wsia
> Subject: Re: [wsrp-wsia] Issue #31: MINIMIZED state does not necessarily
> meanno markup.
>
> My point was that the JSR has defined different semantics than this and
> that
> this issue indicated the
> proper result was for it to do otherwise.  If you think this issue is about
> defining the semantics of VIEW_MINIMIZED, it does and can therefore be
> marked resolved.  I will just go
> ahead and open a new issue stating that our semantics of VIEW_MINIMIZED
> differ from the JSR.  When I
> wrote this note, I assumed it might make sense to use this issue as the
> placeholder for being out of
> sync.  Let me know if you want me to open an issue.
>      -Mike-
>
> Rich Thompson wrote:
>
> > I think we do need to define semantics for things such as this and while
> > syncing up with the JSR work is important, it should not impede producing
> > such definitions (if the JSR suggest changes after we define semantics,
> we
> > should engage them in a discussion as to why and re-resolve the
> semantics).
> > Perhaps the sentence that suggests it is in sync with JSR168 should be
> > deleted (Gil?). Current language is:
> >
> >   When  the window state is VIEW_MINIMIZED, the entity SHOULD render
> itself
> >   using  minimal  space. The entity SHOULD render no visible markup in
> this
> >   case,  but  is  free  to  include  non-visible data such as javascript
> or
> >   hidden  forms. The Consumer MUST invoke the getMarkup() operation for
> the
> >   VIEW_MINIMIZED  state  just  as for all other window states. The
> Consumer
> >   MAY render the title, controls and decorations related to the entity.
> >
> >   I  would note that Andre suggested that some Consumers may want to show
> a
> >   small  image  when  the entity is minimized ... I would suggest that
> this
> >   not  pollute  these semantics, but that it would be a custom window
> state
> >   of the flavor 'Iconized'.
> >
> >
> >                       Michael Freedman
> >                       <Michael.Freedman@        To:       wsrp-wsia
> <wsrp-wsia@lists.oasis-open.org>
> >                       oracle.com>               cc:
> >                                                 Subject:  [wsrp-wsia] re:
> Issues for 10/7
> >                       10/15/2002 06:53
> >                       PM
> >
> >
> >
> > There are few issues this week that have been marked to move from
> > tentative to resolved that I don't think are ready yet.  Here are the
> > comments for those issues:
> >
> > Issue #31:  MINIMIZED state does not necessarily mean no markup.
> >     The resolution suggests that its in sync with JSR 168.  However, the
> > JSR has not synched with this resolution.  This should remain open until
> > we can resolve with the JSR.
> >
> >     -Mike-
> >
> > ----------------------------------------------------------------
> > To subscribe or unsubscribe from this elist use the subscription
> > manager: <http://lists.oasis-open.org/ob/adm.pl>
> >
> > ----------------------------------------------------------------
> > To subscribe or unsubscribe from this elist use the subscription
> > manager: <http://lists.oasis-open.org/ob/adm.pl>
>
> ----------------------------------------------------------------
> To subscribe or unsubscribe from this elist use the subscription
> manager: <http://lists.oasis-open.org/ob/adm.pl>
>
> ----------------------------------------------------------------
> To subscribe or unsubscribe from this elist use the subscription
> manager: <http://lists.oasis-open.org/ob/adm.pl>
>
> ----------------------------------------------------------------
> To subscribe or unsubscribe from this elist use the subscription
> manager: <http://lists.oasis-open.org/ob/adm.pl>
>
> ----------------------------------------------------------------
> To subscribe or unsubscribe from this elist use the subscription
> manager: <http://lists.oasis-open.org/ob/adm.pl>
>
> ----------------------------------------------------------------
> To subscribe or unsubscribe from this elist use the subscription
> manager: <http://lists.oasis-open.org/ob/adm.pl>



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Powered by eList eXpress LLC