John Thornborrow | 18 Jul 13:05

Processing callbacks on scriptaculous forms

Hello,

I'm getting the "Component not found whilst processing callbacks" error 
for a form that is rendered via scriptaculous. Am I missing something?

Root>>initialize
  super initialize.
  editor := Editor new "Editor just renders a form"

Root>>children
  ^Array with: editor

Root>>renderContentOn: html
  html unorderedList: [
    self items do: [:each |
      html listItem: [
        html anchor
          onClick: (html updater
            id: #editor;
            callback: [:ren | ren render: (editor item: each)]);
            with: 'Edit ', item description]]].

  html div id: #editor

Thanks,
John.

******************************************************************************************************************************************
This email is from Pinesoft Limited. Its contents are confidential to the intended recipient(s) at the
email address(es) to which it has been addressed. It may not be disclosed to or used by anyone other than the
(Continue reading)

itsme213 | 18 Jul 17:10
Favicon

Re: Processing callbacks on scriptaculous forms

I'm guessing here, but it may be related to
http://www.nabble.com/Ajax-callback-question%3A-how-to-update-component-tree-before--children-gets-called--to15350231.html#a15359902

To me this was a surprising limitation on Ajax usage in 2.8. I'm holding my 
fingers crossed that 2.9 has this solved but have not seen anything 
definitive about it.
http://www.nabble.com/WAPresenter%3E%3EprocessCallbackStream%3A-aCallbackStream-to16691453.html#a17084726

Sophie

"John Thornborrow" <john <at> pinesoft.co.uk> wrote in message 
news:488079D6.7020501 <at> pinesoft.co.uk...
> Hello,
>
> I'm getting the "Component not found whilst processing callbacks" error 
> for a form that is rendered via scriptaculous. Am I missing something?
>
> Root>>initialize
>  super initialize.
>  editor := Editor new "Editor just renders a form"
>
> Root>>children
>  ^Array with: editor
>
> Root>>renderContentOn: html
>  html unorderedList: [
>    self items do: [:each |
>      html listItem: [
>        html anchor
>          onClick: (html updater
(Continue reading)

Lukas Renggli | 18 Jul 17:37

Re: Re: Processing callbacks on scriptaculous forms

Yes, this is exactly the problem Sophie points out.

>  To me this was a surprising limitation on Ajax usage in 2.8. I'm holding my
>  fingers crossed that 2.9 has this solved but have not seen anything
>  definitive about it.
>  http://www.nabble.com/WAPresenter%3E%3EprocessCallbackStream%3A-aCallbackStream-to16691453.html#a17084726

This is fixed in Seaside 2.9 for quite a while now.

Cheers,
Lukas

--

-- 
Lukas Renggli
http://www.lukas-renggli.ch
John Thornborrow | 18 Jul 18:05

Re: Re: Processing callbacks on scriptaculous forms

Thanks

J.

Lukas Renggli wrote:
> Yes, this is exactly the problem Sophie points out.
>
>   
>>  To me this was a surprising limitation on Ajax usage in 2.8. I'm holding my
>>  fingers crossed that 2.9 has this solved but have not seen anything
>>  definitive about it.
>>  http://www.nabble.com/WAPresenter%3E%3EprocessCallbackStream%3A-aCallbackStream-to16691453.html#a17084726
>>     
>
> This is fixed in Seaside 2.9 for quite a while now.
>
> Cheers,
> Lukas
>
>   

******************************************************************************************************************************************
This email is from Pinesoft Limited. Its contents are confidential to the intended recipient(s) at the
email address(es) to which it has been addressed. It may not be disclosed to or used by anyone other than the
addressee(s), nor may it be copied in anyway. If received in error, please contact the sender, then delete
it from your system. Although this email and attachments are believed to be free of virus, or any other
defect which might affect any computer or IT system into which they are received and opened, it is the
responsibility of the recipient to ensure that they are virus free and no responsibility is accepted by
Pinesoft for any loss or damage arising in any way from receipt or use thereof. *****************************************************************************************
 **************************************************
(Continue reading)

itsme213 | 18 Jul 18:21
Favicon

Re: Re: Processing callbacks on scriptaculous forms

"Lukas Renggli" <renggli <at> gmail.com> wrote

>>  To me this was a surprising limitation on Ajax usage in 2.8. I'm holding 
>> my
>>  fingers crossed that 2.9 has this solved but have not seen anything
>>  definitive about it.
>> 
>> http://www.nabble.com/WAPresenter%3E%3EprocessCallbackStream%3A-aCallbackStream-to16691453.html#a17084726
>
> This is fixed in Seaside 2.9 for quite a while now.

Great!!

Is it ok in 2.9 for any component processing its Ajax callback to (a) cause 
component structure adds/deletes/changes in distant components, and (b) 
selectively call distant (re)rendering methods?

Any different protocols to be used (like the one you added as a workaround 
in 2.8)? Is it OK to start using 2.9 at this point?

Thanks - Sophie
Lukas Renggli | 18 Jul 18:49

Re: Re: Re: Processing callbacks on scriptaculous forms

>  Is it ok in 2.9 for any component processing its Ajax callback to (a) cause
>  component structure adds/deletes/changes in distant components, and (b)
>  selectively call distant (re)rendering methods?

Yes, if I remember correctly.

>  Any different protocols to be used (like the one you added as a workaround
>  in 2.8)?

No.

> Is it OK to start using 2.9 at this point?

No, unless you want to find bugs.

Cheers,
Lukas

--

-- 
Lukas Renggli
http://www.lukas-renggli.ch

Gmane