Jean-Marc Orliaguet wrote:
Jim Fulton wrote:
Jean-Marc Orliaguet wrote:
Stephan Richter wrote:
On Sunday 11 September 2005 11:32, Jean-Marc Orliaguet wrote:
it there any technical reason why:
tal:define="displayable nocall:context/displayable"
could not return the adapted object
Jim Fulton wrote:
> Jean-Marc Orliaguet wrote:
>
>> Stephan Richter wrote:
>>
>>
>>> On Sunday 11 September 2005 11:32, Jean-Marc Orliaguet wrote:
>>>
>>>
>>>
it there any technical reason why:
tal:define="displayable nocall:context/displayable"
could not return the adapt
Jean-Marc Orliaguet wrote:
Stephan Richter wrote:
On Sunday 11 September 2005 11:32, Jean-Marc Orliaguet wrote:
it there any technical reason why:
tal:define="displayable nocall:context/displayable"
could not return the adapted object based on the context instead of
triggering a travers
Stephan Richter wrote:
>On Sunday 11 September 2005 11:32, Jean-Marc Orliaguet wrote:
>
>
>>it there any technical reason why:
>>
>> tal:define="displayable nocall:context/displayable"
>>
>>could not return the adapted object based on the context instead of
>>triggering a traversal error?
>>
On Sunday 11 September 2005 11:32, Jean-Marc Orliaguet wrote:
> it there any technical reason why:
>
> tal:define="displayable nocall:context/displayable"
>
> could not return the adapted object based on the context instead of
> triggering a traversal error?
Yes. You are not using the path adap
Stephan Richter wrote:
>On Friday 02 September 2005 04:20, Jean-Marc Orliaguet wrote:
>
>
>>this only solution I found was to write:
>>
>>tal:define="getDisplay nocall:context/displayable/getDisplay;
>> display python: getDisplay(param);"
>>
>>But it means that I have to adapt
On Friday 02 September 2005 04:20, Jean-Marc Orliaguet wrote:
> this only solution I found was to write:
>
> tal:define="getDisplay nocall:context/displayable/getDisplay;
> display python: getDisplay(param);"
>
> But it means that I have to adapt the same object each time, why ca
