You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Erik Hatcher <er...@ehatchersolutions.com> on 2004/08/17 14:57:53 UTC
Portlet compatibility (Was Re: [window.onload] Multiple components requiring a window.onload function entry)
Walt - please use a new subject when starting a new thread.
Currently Tapestry does not implement the portlet specification. It is
on the TODO list:
http://wiki.apache.org/jakarta-tapestry/PortalSupportProposal?
action=highlight&value=portlet
Erik
On Aug 17, 2004, at 8:45 AM, Walter wrote:
> Howard,
>
> Do you know of any portlet container that works well with Tapestry?
>
> Walt.
>
> Howard Lewis Ship wrote:
>
>> An anonymous JavaScript function is created as the window.onload event
>> handler. The combined contents of all <initialization> of all scripts
>> is placed there. It just works.
>>
>> On Mon, 16 Aug 2004 21:31:07 +0000 (UTC), F Da Costa Gomez
>> <da...@gmail.com> wrote:
>>
>>> Hi,
>>>
>>> Situation:
>>> Page contains the DatePicker component. Works fine and produces a
>>> window.onload
>>> function via the DataPicker.script
>>> If and when i introduce a second component (not the DatePicker
>>> again) that also
>>> utilises a <initialization> in the .script, how would this translate
>>> to an
>>> additional 'entry' in the window.onload function. Assuming it is
>>> possible.
>>>
>>> Reason for question:
>>> Obviously i can't find the initialisation back in the function. I
>>> assume it is
>>> possible so that would imply i'v got en error somewhere. If it is
>>> not i have to
>>> figure out some other way to initialise.
>>>
>>> TIA,
>>> Fermin DCG
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
>>> For additional commands, e-mail:
>>> tapestry-user-help@jakarta.apache.org
>>>
>>>
>>>
>>
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: Portlet compatibility (Was Re: [window.onload] Multiple components
requiring a window.onload function entry)
Posted by Walter <wa...@builditglobal.com>.
Thanks Erik for the help and the link. I will start a new thread with
any questions in the future. Walt.
Erik Hatcher wrote:
> Walt - please use a new subject when starting a new thread.
>
> Currently Tapestry does not implement the portlet specification. It
> is on the TODO list:
>
> http://wiki.apache.org/jakarta-tapestry/PortalSupportProposal?
> action=highlight&value=portlet
>
> Erik
>
> On Aug 17, 2004, at 8:45 AM, Walter wrote:
>
>> Howard,
>>
>> Do you know of any portlet container that works well with Tapestry?
>>
>> Walt.
>>
>> Howard Lewis Ship wrote:
>>
>>> An anonymous JavaScript function is created as the window.onload event
>>> handler. The combined contents of all <initialization> of all scripts
>>> is placed there. It just works.
>>>
>>> On Mon, 16 Aug 2004 21:31:07 +0000 (UTC), F Da Costa Gomez
>>> <da...@gmail.com> wrote:
>>>
>>>> Hi,
>>>>
>>>> Situation:
>>>> Page contains the DatePicker component. Works fine and produces a
>>>> window.onload
>>>> function via the DataPicker.script
>>>> If and when i introduce a second component (not the DatePicker
>>>> again) that also
>>>> utilises a <initialization> in the .script, how would this
>>>> translate to an
>>>> additional 'entry' in the window.onload function. Assuming it is
>>>> possible.
>>>>
>>>> Reason for question:
>>>> Obviously i can't find the initialisation back in the function. I
>>>> assume it is
>>>> possible so that would imply i'v got en error somewhere. If it is
>>>> not i have to
>>>> figure out some other way to initialise.
>>>>
>>>> TIA,
>>>> Fermin DCG
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
>>>> For additional commands, e-mail:
>>>> tapestry-user-help@jakarta.apache.org
>>>>
>>>>
>>>>
>>>
>>>
>>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
>