Re: Ajax Problem with 5.2

2010-07-02 Thread Pierce Wetter

On Jul 1, 2010, at 4:57 PM, Howard Lewis Ship wrote:

> Details about Tapestry version, browser version, any custom JS you've
> written, steps taken, maybe some of your page class and template.

  Ok, issue entered:

https://issues.apache.org/jira/browse/TAP5-1200

 Templates provided. 

Pierce


-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org



Re: Ajax Problem with 5.2

2010-07-01 Thread Howard Lewis Ship
Details about Tapestry version, browser version, any custom JS you've
written, steps taken, maybe some of your page class and template.

On Thu, Jul 1, 2010 at 4:42 PM, Pierce Wetter  wrote:
>
>
>  Ok, any hint how I should write it up so that someone could actually be able 
> to fix it based on my description of the problem? Programmers don't fix bugs, 
> they fix bug reports.
>
>> This sounds like a new bug, some kind of order-of-operations problem.
>> Please add an issue.
>>
>> On Thu, Jul 1, 2010 at 4:01 PM, Pierce Wetter  wrote:
>>> Background:
>>>
>>>    Page of data, you can click on a "show" button to see a grid for a 
>>> to-many relationship. You can think click on items in the grid to get a 
>>> second reveal with some more data and some buttons.
>>>
>>>  But:
>>>
>>>  It broke sometime in the last few weeks.
>>>
>>>  I'm getting an error on line 2067 of tapestry.js which relates to 
>>> $T(element). In this case the error is that its being called as $T(null),
>>>
>>>  Which I note is deprecated, but I guess is still being used elsewhere, 
>>> because I'm not the one calling it. The XHR stuff looks ok, I see the right 
>>> HTML come through, with the appropriate linkZone definitions.
>>>
>>>  Elsewhere I'm using this exact same component, and everything works, but 
>>> its not behind a second reveal.
>>>
>>>  So is someone working on this and I just just be patient?
>>>
>>>  How can $T(element) be deprecated if elsewhere in T5.2 its still being 
>>> used?
>>>
>>>  Pierce
>>> -
>>> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
>>> For additional commands, e-mail: users-h...@tapestry.apache.org
>>>
>>>
>>
>>
>>
>> --
>> Howard M. Lewis Ship
>>
>> Creator of Apache Tapestry
>>
>> The source for Tapestry training, mentoring and support. Contact me to
>> learn how I can get you up and productive in Tapestry fast!
>>
>> (971) 678-5210
>> http://howardlewisship.com
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
>> For additional commands, e-mail: users-h...@tapestry.apache.org
>>
>>
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
> For additional commands, e-mail: users-h...@tapestry.apache.org
>
>



-- 
Howard M. Lewis Ship

Creator of Apache Tapestry

The source for Tapestry training, mentoring and support. Contact me to
learn how I can get you up and productive in Tapestry fast!

(971) 678-5210
http://howardlewisship.com

-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org



Re: Ajax Problem with 5.2

2010-07-01 Thread Pierce Wetter


  Ok, any hint how I should write it up so that someone could actually be able 
to fix it based on my description of the problem? Programmers don't fix bugs, 
they fix bug reports. 

> This sounds like a new bug, some kind of order-of-operations problem.
> Please add an issue.
> 
> On Thu, Jul 1, 2010 at 4:01 PM, Pierce Wetter  wrote:
>> Background:
>> 
>>Page of data, you can click on a "show" button to see a grid for a 
>> to-many relationship. You can think click on items in the grid to get a 
>> second reveal with some more data and some buttons.
>> 
>>  But:
>> 
>>  It broke sometime in the last few weeks.
>> 
>>  I'm getting an error on line 2067 of tapestry.js which relates to 
>> $T(element). In this case the error is that its being called as $T(null),
>> 
>>  Which I note is deprecated, but I guess is still being used elsewhere, 
>> because I'm not the one calling it. The XHR stuff looks ok, I see the right 
>> HTML come through, with the appropriate linkZone definitions.
>> 
>>  Elsewhere I'm using this exact same component, and everything works, but 
>> its not behind a second reveal.
>> 
>>  So is someone working on this and I just just be patient?
>> 
>>  How can $T(element) be deprecated if elsewhere in T5.2 its still being used?
>> 
>>  Pierce
>> -
>> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
>> For additional commands, e-mail: users-h...@tapestry.apache.org
>> 
>> 
> 
> 
> 
> -- 
> Howard M. Lewis Ship
> 
> Creator of Apache Tapestry
> 
> The source for Tapestry training, mentoring and support. Contact me to
> learn how I can get you up and productive in Tapestry fast!
> 
> (971) 678-5210
> http://howardlewisship.com
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
> For additional commands, e-mail: users-h...@tapestry.apache.org
> 
> 


-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org



Re: Ajax Problem with 5.2

2010-07-01 Thread Howard Lewis Ship
This sounds like a new bug, some kind of order-of-operations problem.
Please add an issue.

On Thu, Jul 1, 2010 at 4:01 PM, Pierce Wetter  wrote:
> Background:
>
>    Page of data, you can click on a "show" button to see a grid for a to-many 
> relationship. You can think click on items in the grid to get a second reveal 
> with some more data and some buttons.
>
>  But:
>
>  It broke sometime in the last few weeks.
>
>  I'm getting an error on line 2067 of tapestry.js which relates to 
> $T(element). In this case the error is that its being called as $T(null),
>
>  Which I note is deprecated, but I guess is still being used elsewhere, 
> because I'm not the one calling it. The XHR stuff looks ok, I see the right 
> HTML come through, with the appropriate linkZone definitions.
>
>  Elsewhere I'm using this exact same component, and everything works, but its 
> not behind a second reveal.
>
>  So is someone working on this and I just just be patient?
>
>  How can $T(element) be deprecated if elsewhere in T5.2 its still being used?
>
>  Pierce
> -
> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
> For additional commands, e-mail: users-h...@tapestry.apache.org
>
>



-- 
Howard M. Lewis Ship

Creator of Apache Tapestry

The source for Tapestry training, mentoring and support. Contact me to
learn how I can get you up and productive in Tapestry fast!

(971) 678-5210
http://howardlewisship.com

-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org



Ajax Problem with 5.2

2010-07-01 Thread Pierce Wetter
Background:

Page of data, you can click on a "show" button to see a grid for a to-many 
relationship. You can think click on items in the grid to get a second reveal 
with some more data and some buttons. 

 But:

  It broke sometime in the last few weeks. 

 I'm getting an error on line 2067 of tapestry.js which relates to $T(element). 
In this case the error is that its being called as $T(null), 

 Which I note is deprecated, but I guess is still being used elsewhere, because 
I'm not the one calling it. The XHR stuff looks ok, I see the right HTML come 
through, with the appropriate linkZone definitions. 

  Elsewhere I'm using this exact same component, and everything works, but its 
not behind a second reveal. 

  So is someone working on this and I just just be patient?

  How can $T(element) be deprecated if elsewhere in T5.2 its still being used? 

 Pierce
-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org