Re: xforms build help

Okay, so that's good stuff! I've uploaded a sample using foreignObject. It's 
very close to what I want, but it seems like implementing the svg interfaces 
would rock even more. Note: you'll need xforms and svg support for this.

http://artforms.progressivex.com/mozilla/sample01.xml

I'm working on translating the calculator demo to use svg.. some of that 
will need to output dynamic svg.. so once I get to that point I'll post it. 
I'll also post some "wouldn't it be nice" versions too.

Thanks for the info!

-Andrew


"T Rowley" <[email protected]> wrote in message 
news:[email protected]...
> Andrew Douglas wrote:
>> As far as my testing goes.. I've run several svg tests with xforms beside 
>> it and everythings fine.. what I haven't gotten working is any "built in" 
>> integration of the two (I know there are other ways around that such as 
>> javascript, xslt, etc.). For example something like the following would 
>> be great it if it actually worked:
>>
>> ... header/namespace declarations..
>>
>> <svg:svg>
>>     <svg:text style="blah">
>>             <xf:output value="Hello World" />
>>     </svg:text>
>> </svg:svg>
>>
>> Obviously there are some xf tags that wouldn't work in this scenario, but 
>> using output like this would rock. Alternatively, I can't get <xf:ouptut> 
>> to output actual svg content for the life of me.. generally it breaks on 
>> tag issues or I get nothing at all. I can send some "complete" broken 
>> examples if you think it might help to visualize what I'm trying to do 
>> with it.
>
> Non-svg children of a svg container won't draw anything, as painting goes 
> through a svg paint propagation scheme at that point, so anything
> that doesn't implement the nsISVGChildFrame interface won't be notified
> to draw.  If you place the non-svg content in a <svg:foreignObject> then
> it should be drawn correctly.
>
> Looking at the SVG specification, I couldn't see if what we currently 
> implement is what should be happening for compound documents or not. 
> Compound documents structured the other way around, with svg as the 
> "embedded language" should work fine with our current implementation.
>
> If you could make the full examples of what you're experimenting with 
> available it would be useful as we try to figure out the correct behavior.
>
> Thanks.
>
> -tor