Re: Accessing SVG's in Cocoon via SVG Serializer

2002-09-11 Thread Torsten Knodt

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi Michael,
 I also have Problems including external Images during SVG serialization. In
 my case it's about JPEGs, but that shouldn't do a difference.
No, it isn't.

 My Sitemap and XSLT look quite similar to yours, but the only way I can
 include external images into the SVG is through a http:// URL. This might
 be a solution for your Problem with including dynamically generated images.
 But for me it is not a that good solution, since the http:// URL on my
 develpment system is different from the one on the production system.
Same problem for me.

  The example above doesn't work.
 Being able to use the cocoon: protocol would be great, but it does not seem
 to work in my webapp either. Do you have any idea why? I've already tried
 it with cocoon 2.0.1, 2.0.2 and 2.0.3. I think this should be fixed if
 possible...
Yes, I have. I'm currently working with the batik sources. The problem seems 
to be the URI resolving. Batik has an own version of it.
Currently I'm working on the transcoders of Batik. When this is done, I would 
work on the URL resolving problem. But I think my current work will take 
perhaps two weeks or more. So perhaps, you can take the other problem. Some 
java knowledge would be good for it. ;) I think the best would be to start in 
the Bridge code of batik (easy to find). It transforms the parsed SVG 
document into a SVG DOM tree. For every tag, including image, there's a 
bridge class. From there you have to look for the URI resolving. I had found 
it very fast, but don't rember where it exactly was. This has to be modified 
for using the cocoon resolver. The problem is, that batik isn't based on 
avalon/ excalibur. So it could be some work. But then, you would have all URI 
features of cocoon avalaible. If you want to try it, feel free to ask me (but 
don't forget I'm a newbie to batik) or the batik developers mailing list.

  Using file:// is no problem, but I want to use
  it with dynamically created content, so I can't access the filesystem
  directly.
 I suppose this only works with absolute paths, which is again no good
 solution for me. Have you ever had it running with relative paths? I wasn't
 able to...
I had the same problem.

With kind regards
Torsten Knodt
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE9fw68vxZktkzSmiwRAk4aAJoCDqIBP/RBeWZYPF1ASQrFjQ+oSQCgj79x
dWFAwgmLTSqe3Ll/0IoONX8=
=chba
-END PGP SIGNATURE-


-
Please check that your question  has not already been answered in the
FAQ before posting. http://xml.apache.org/cocoon/faq/index.html

To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail:   [EMAIL PROTECTED]




Re: Accessing SVG's in Cocoon via SVG Serializer

2002-09-10 Thread Michael Riedel

 I've a question regarding href's in the image tag of SVG's. Is there a way
to
 access the actual sitemap context from an svg?
I also have Problems including external Images during SVG serialization. In
my case it's about JPEGs, but that shouldn't do a difference.

 Example Sitemap:
 map:pipeline
 map:match pattern=resources/**
 map:mount check-reload=yes src=resources/
uri-prefix=resources
 /
 /map:match
 map:match pattern=resize/**
 map:generate src=dummy.xml /
 map:transform src=resizer.xsl
 map:parameter name=uri value={1} /
 /map:transform
 map:serialize type=svg2jpeg /
 /map:match
 /map:pipeline

 Example resizer.xsl:
   xsl:param name=uri select='' /
   xsl:template match=/
 svg viewpoint=0 0 320 240 width=320 height=240
   image width=320 height=240 xlink:href=cocoon:{$uri}/
 /svg
 /xsl:template

My Sitemap and XSLT look quite similar to yours, but the only way I can
include external images into the SVG is through a http:// URL. This might be
a solution for your Problem with including dynamically generated images. But
for me it is not a that good solution, since the http:// URL on my
develpment system is different from the one on the production system.

 The example above doesn't work.
Being able to use the cocoon: protocol would be great, but it does not seem
to work in my webapp either. Do you have any idea why? I've already tried it
with cocoon 2.0.1, 2.0.2 and 2.0.3. I think this should be fixed if
possible...

 Using file:// is no problem, but I want to use
 it with dynamically created content, so I can't access the filesystem
 directly.
I suppose this only works with absolute paths, which is again no good
solution for me. Have you ever had it running with relative paths? I wasn't
able to...

-- Michael Riedel


-
Please check that your question  has not already been answered in the
FAQ before posting. http://xml.apache.org/cocoon/faq/index.html

To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail:   [EMAIL PROTECTED]