Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Wolfgang Fahl
    @WolfgangFahl
    https://github.com/BITPlan/diagrams is intended to be an alternative based on a different technology stack (python)
    Wolfgang Fahl
    @WolfgangFahl
    More examples can be found at https://github.com/yfuruyama/real-world-plantuml
    Wolfgang Fahl
    @WolfgangFahl
    http://diagrams.bitplan.com/ has a GUI prototype - functionality is in the works ...
    Wolfgang Fahl
    @WolfgangFahl
    Some diagrams are now successfully rendered
    Wolfgang Fahl
    @WolfgangFahl
    The service should now be useable with the mediawiki extension - it will only serve graphviz dot as png at this time when $wgDiagramsServiceUrl='http://diagrams.bitplan.com'; is specified
    There is some documentation at http://wiki.bitplan.com/index.php/Diagrams
    Wolfgang Fahl
    @WolfgangFahl
    BITPlan/diagrams#4 BITPlan/diagrams#5 are in the works. The wrapping issue is a compatibility issue
    Wolfgang Fahl
    @WolfgangFahl
    Mark Wrote:
    I'm confused by this bit: "The primary reason for a different extension is to not store the rendered images in the wiki database."
    Is there a reason GraphViz or PlantUML couldn't just store the images they produce in the same way that the Math extension does?
    I wasn't aware of this being an issue until just now. Since I see you've been working on this since July, but I, personally, haven't looked at it closely otherwise, I hope you can provide some insight.
    AFAIK, Math just creates a separate, unique directory in the images directory and doesn't try to use the entire WikiImage infrastructure.
    This seems like a simpler solution than creating an additional service that people need to install
    Wolfgang Fahl
    @WolfgangFahl
    This message was deleted
    Wolfgang Fahl
    @WolfgangFahl

    or the image handling in plantuml and graphviz we need access via the API in read mode

    see samwilson/diagrams-extension#9

    So if a local image is mentioned we need to get access to it which in the past could be done like in https://www.mediawiki.org/wiki/Topic:Pzvu1613ewnfahcd

    For storing images it would be good to allow different methods of reference:

    • by name

    • by name / version

    • by crc32 code

    and then it should not make much of a difference whether a local or remote service delivers the result. This would give us quite some flexibility. I find it interesting that there are so many extensions with similar issues:

    the extensions have in common that the input is some markup and the output a graphical representation - in case of the 3D extensions even in an interactive manner - and that some external software is needed for rendering.