Thanks.
I agree with your reasons and for some diagrams Gliffy will be a better
choice.
If we go with AsciiDoc, GraphViz is built-in and will become more
familiar to everyone.
There is also a Javascript version of Graphviz so that it is not a bad
tool for generating some types of drawings using the browser to do the
drawing.
This speeds up drawing creation by reducing the amount of bits flowing
and lightens the load on the server since you just send the description
of the relationships rather than the rendered output.
The only drawback is that, so far, the Javascript rendering engine does
not provide a way to make the drawing interactive.
Ron
On 16/01/2015 3:16 PM, Jacques Le Roux wrote:
> Thanks for the glance Ron. I must say I have never used Gliffy, nor
> Graphviz, so you have certainly a better opinion than I.
> I recommended (not requested ;)) to use Gliffy because it's available
> and kind of included with Confluence at the ASF.
> But since Graphviz is open source and use the "Eclipse Public License
> - v 1.0" I see no problems using it, instead of Gliffy
>
> Jacques
>
> Le 16/01/2015 15:54, Ron Wheeler a écrit :
>>
https://cwiki.apache.org/confluence/display/OFBIZ/Component+and+Component+Set+Dependencies
>> contains a drawing done using Graphviz
>> Jacques requested that I look at using Gliffy instead.
>> I had a quick look but Gliffy is requires manual creation and layout
>> of the artifacts on the drawing and this would be harder to create
>> and maintain as relationship are added and removed from the application.
>> I have added a child page called "Drawing Source" with the source for
>> the image and instructions about how to regenerate the drawing.
>>
>> Ron
>>
>
--
Ron Wheeler
President
Artifact Software Inc
email:
[hidden email]
skype: ronaldmwheeler
phone: 866-970-2435, ext 102
Locked
