Hi Gaël,<br><br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">At the beginning, it was only a pure visualization tool, but it appeared that<br>
interactions were needed (to support actions, changes during graph life time,<br>
etc). And then I started to add editing features. But, you're right view and<br>
edit features could be separated.</blockquote><div><br>Ok !<br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="im">
> 2) Can I implement, in the application, the code to be executed when a<br>
> graph node is clicked or has a mouse over event ? Again, wouldn't the<br>
> kpart have its reuse improved if such interaction features were not<br>
> pre-defined ?<br>
</div>They aren't! They are just signals that you can connect to to handle actions.<br>
Also, when you want to act on a graph element, you use slots to send it<br>
messages.<br>
When you click on a node, the selectionIs signal is sent.<br>
The part is missing hovering signals, though.</blockquote><div><br>Ok, I'll try connect such signals to slots in my KDevelop plugin.<br>BTW, in the attached image you can see some preliminary result on control flow graphs inside KDevelop using the KGraphViewer kpart.<br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="im">
><br>
> 3) Why haven't you used Graphviz as a library (as indicated in<br>
> <a href="http://www.graphviz.org/pdf/libguide.pdf" target="_blank">http://www.graphviz.org/pdf/libguide.pdf</a>) instead of relying in<br>
> QProcess invocation of dot, twopi and output processing (I know, this<br>
> is the KCachegrind approach) ?<br>
</div>You said it: it's the kcachegrind approach and in fact, when I started<br>
kgraphviewer I reused the kcachegrind code :-) Well, there is not much<br>
remaining up to now.<br>
I think it is still a good solution. The xdot format is easy to parse. But I<br>
already thinked to have a look at the graphviz library.</blockquote><div><br>I'm using Graphviz programmatically to construct the graph from the function calls collected in the source code. It's API is quite ease and complete.<br>
<br>Thanks,<br></div></div>- -<br>Sandro Santos Andrade<br>--------------------------------------------------------<br>Distributed Systems Laboratory (LaSiD)<br>Computer Science Department (DCC)<br>Federal University of Bahia<br>
Brazil<br>