Re: Cforms, Binding & Cross-Referenced data

["Timur Izhbulatov,,," <ti...@yxo.ru>]

On Fri, Jul 30, 2004 at 01:45:23AM +0100, Ben Pope wrote:
> When you say "Use xinclude (or cinclude) transformer:" I'm not sure if you
> mean I should actually parse the above data with it... If so, then the rest
> of the example doesn't seem to make sense as I lose the xi:include elements.
> E.g., the repeater row-path"xi:include" would fail, so I'll have to assume
> that I'm leaving the data as it is, not transforming it.
Of course, you don't have to use this transformer when you do binding.
But you may use it in another pippeline (e.g. to display the data).

> 
> The identity won't work, 'cos <xi:include> elements don't have an id
> attribute.  Of course... I could give it an idref, but that would seem to be
> going back to the way I had it.
What if you just add the "id" attribute to the "xi:include" element?

> My personName doesn't work either, there is obviously no variable named id,
> I don't know how to locate the correct element to bind to.  I think this is
> the crux of the problem.
Oops. I didn't think about it =)
In case if we can have an "id" attribute in each "xi:include" element,
can we find the way to "ask" repeater for current id value?

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org

RE: Cforms, Binding & Cross-Referenced data

[Ben Pope <no...@hotmail.com>]

 

>-----Original Message-----
>From: Timur Izhbulatov,,, [mailto:timur@yxo.ru] 
>Sent: 01 August 2004 16:01
>To: users@cocoon.apache.org
>Subject: Re: Cforms, Binding & Cross-Referenced data
>
>On Fri, Jul 30, 2004 at 01:45:23AM +0100, Ben Pope wrote:
>> When you say "Use xinclude (or cinclude) transformer:" I'm 
>not sure if 
>> you mean I should actually parse the above data with it... 
>If so, then 
>> the rest of the example doesn't seem to make sense as I lose 
>the xi:include elements.
>> E.g., the repeater row-path"xi:include" would fail, so I'll have to 
>> assume that I'm leaving the data as it is, not transforming it.

>Of course, you don't have to use this transformer when you do binding.
>But you may use it in another pippeline (e.g. to display the data).

OK, makes sense.


>> The identity won't work, 'cos <xi:include> elements don't have an id 
>> attribute.  Of course... I could give it an idref, but that 
>would seem 
>> to be going back to the way I had it.

>What if you just add the "id" attribute to the "xi:include" element?

Yeah... Or an idref attribute, so I know that it's a reference to an id, not
actually in id.


>> My personName doesn't work either, there is obviously no variable 
>> named id, I don't know how to locate the correct element to 
>bind to.  
>> I think this is the crux of the problem.

>Oops. I didn't think about it =)
>In case if we can have an "id" attribute in each "xi:include" 
>element, can we find the way to "ask" repeater for current id value?

Well that should do it, I guess... Whih is kinda where I was stuck.

However, I've had a bit of enlightenment: instead of serving my form
definition, template and binding file from the filesystem, I serve them
through a pipeline, allowing me to apply an XSLT, modifying them with
runtime parameters.  Using keys and various other technologies, I see no
reason why I cannot get this done... Just need to find some time to think
about it.

Need to move tomorrow, so I guess that will hold me up - how inconvenient!

Cheers,
Ben.

P.S.  Sorry for the screwy formatting of included lines... Installing
Outlook-QuoteFix now...

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org