[kgraphviewer-devel] Re: Bundle graphviz abstraction into one library (e.g. libkgraphviz)

[Milian Wolff]

Kevin Funk, 09.12.2010:
> Hey guys,
> 
> I'm about to write an application which needs to visualize graphs
> dynamically. Dynamically means, graphs are expected to be changed (as in
> nodes/edges are added/removed) during runtime programmatically.
> 
> For this to work I need an working graphviz abstraction layer. Your
> kgraphviewerlib provides most of features that I need to achieve this.
> However, most of this is not exported in a way that external users can use
> this API.
> 
> I'd like to change this, using and extending your code base without
> breaking the API to the kgraphviewer GUI interface. More concrete, I'd
> like to export the classes required to build and display a "DotGraph"
> graph programmatically. This means exporting and extending following
> classes of your code: * DotGraphView (already exported)
> * DotGraph
> * GraphElement
>   * GraphNode, CanvasNode
>   * GraphEdge, CanvasEdge
>   * GraphSubgraph, CanvasSubgraph
> * GraphExporter
> * DotRenderOp, DotGrammar (dependencies)
> 
> Afaics this could be bundled in something like "libkgraphviz".
> 
> I already have some trivial patches lying around which are removing most
> all of the graphviz includes and most of the boost includes from public
> headers to decrease the libs footprint (which should be included in
> kgraphviewer code anyway). If you want me to post them to reviewboard,
> tell me.
> 
> For all the other refactoring I'm going to work in a local branch for now.
> If you want me to make it public or push it to git.kde.org, I can do this.
> 
> What are your thoughts on all this stuff?

As I told you already, I think this is a very good idea.

You should put it into a branch on git.kde.org, call it e.g. libkgraphviz :)

What you will also have to care about

- harden the lib against BIC, e.g. introduce d pointers and move code to them.
- generally do a cleanup of the API where required, make it Qt-ish where it is 
not already

anyways, having it public cannot hurt, quite the contrary, we could look at it 
directly and give you feedback.

Bye


-- 
Milian Wolff
mail at milianw.de
http://milianw.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
Url : http://mail.kde.org/pipermail/kgraphviewer-devel/attachments/20101209/16c94b81/attachment.sig