On Feb 13, 9:18 am, Heiko Hees <[email protected]> wrote: > Hi, > > there are two possibilites: > 1) Either support the tag (see other examples like <source/>) and > implement a method in the PDF writer, which triggers graphviz and > includes the image. > > 2) Extend the extension to serve images via HTTP-GET requests. You > then could return [[Image:]] markup with a name that encodes the > location and the parameter for the graphviz server. We'd probably need > to add support for arbitrary URLs in images, but this shouldn't be too > hard. I'd prefer this option because it can be used as a webservice > by other applications as well. This approach would also work for > other extensions such as <hiero/> or <timeline/>. > > I assume both option to be some work but we'd assist you in that if > possible. >
I think I also like #2. I'd imagine this could also work for dynamic page list or semantic mediawiki queries... Both of which I'm interested in. Should this be a GET, or a POST? The graphviz extension can take arbitrarily long content between the opening and closing tags, and would likely be too long for a GET request. I'm thinking I could make a special page that takes the content, and attributes, and returns the location of the image. Should I be posting and returning XML? API-like work is fairly new to me. V/r, Ryan Lane --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "mwlib" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/mwlib?hl=en -~----------~----~----~----~------~----~------~--~---
