7 Mar
2012
7 Mar
'12
10:22 p.m.
I have been looking around the web for an app to convert C++ source code to flow diagrams.
I'm looking in the wrong places or nothing exists other than a few commercial apps.
I was hoping the Umbrello tool could help, but that does not convert anything directly.
Is there a way to do this?
I want to map the entire docbook process. As I am still very much a novice C++ coder, I am
in over my head trying to trace how everything connects. The process should be documented
for the wiki.
Ideas?
Thanks.
Darrell
7 Mar
7 Mar
10:34 p.m.
New subject: [trinity-devel] Creating flow diagrams from sources?
On Thursday 08 March 2012 00:22:11 Darrell Anderson wrote:
I have been looking around the web for an app to
convert C++ source code to
flow diagrams. I'm looking in the wrong places or nothing exists other than
a few commercial apps.
I was hoping the Umbrello tool could help, but that does not convert
anything directly.
Is there a way to do this?
I want to map the entire docbook process. As I am still very much a novice
C++ coder, I am in over my head trying to trace how everything connects.
The process should be documented for the wiki.
Ideas?
Thanks.
Darrell
Check http://www.graphviz.org/Gallery.php
--
Serghei
9 Mar
9 Mar
4:33 a.m.
New subject: [trinity-devel] Creating flow diagrams from sources?
On Thu, Mar 8, 2012 at 2:34 AM, Serghei Amelian <serghei(a)thel.ro> wrote:
On Thursday 08 March 2012 00:22:11 Darrell Anderson
wrote:
Doxygen uses graphviz. De-facto standard of documenting sources.
I have been looking around the web for an app to
convert C++ source code to
flow diagrams. I'm looking in the wrong places or nothing exists other than
a few commercial apps.
I was hoping the Umbrello tool could help, but that does not convert
anything directly.
Is there a way to do this?
I want to map the entire docbook process. As I am still very much a novice
C++ coder, I am in over my head trying to trace how everything connects.
The process should be documented for the wiki.
Ideas?
Thanks.
Darrell
Check http://www.graphviz.org/Gallery.php
--
Serghei
5:29 a.m.
New subject: [trinity-devel] Creating flow diagrams from sources?
> I have
been looking around the web for an app to
convert C++ source code to
> flow diagrams. I'm looking in the wrong
places or
nothing exists other than
> a few commercial apps.
>
> I was hoping the Umbrello tool could help, but that
does not convert
> anything directly.
>
> Is there a way to do this?
>
> I want to map the entire docbook process. As I am
still very much a novice
> C++ coder, I am in over my head trying to
trace how
everything connects.
>> The process should be documented for the wiki.
>>
>> Ideas?
>>
>> Thanks.
>
> Check http://www.graphviz.org/Gallery.php
Doxygen uses graphviz. De-facto standard of documenting
sources.
Thank you both.
My understanding of doxygen was that software takes existing commentation in the source
code to create documents. If no commentation exists then does doxygen still create
documentation? How?
This is all very new to me. I would be grateful to receive a description/outline how this
process works.
The goal here is for me to understand how the docbook support process works with respect
to the source code --- so I can document this process at the wiki. I very much am a C++
newbie and can't simply browse the source code to create a flow diagram. Just
can't happen with my current C++ skills. For me to get to that point will take a long
time. :) So yes, by looking for some way to convert the source code to a flow diagram I
take a shortcut toward understanding the process and will learn about the source code
because the flow diagram is a guide.
Thanks!
Darrell
6:07 a.m.
New subject: [trinity-devel] Creating flow diagrams from sources?
On Fri, Mar 9, 2012 at 9:29 AM, Darrell Anderson
<humanreadable(a)yahoo.com> wrote:
Just run 'doxygen -g'. In generated Doxyfile turn RECURSIVE = YES,
HAVE_DOT = YES, CALL_GRAPH = YES, CALLER_GRAPH = YES or whatever you
want to be included in the output. After that run 'doxygen' and look
at 'html/index.html'.
Yes, it generates info independently of comments. It uses comments (in
proper format) to get descriptions of functions and arguments.
But I must warn you that diagrams are not silver bullet to understand
the code. Unless you want to see big picture (from the point of bird
fly) which is rarely needed (f.ex. for global architecture changes,
what is not your case anyway). The best way to learn code is to get
your debugger into interested points and examine call stacks and
arguments from them. And of course there is no point to learn the code
without specific task you want to achieve.
> I have been looking around the web for an app to
convert C++ source code to
> flow diagrams. I'm looking in the wrong
places or
nothing exists other than
> a few commercial apps.
>
> I was hoping the Umbrello tool could help, but that
does not convert
> anything directly.
>
> Is there a way to do this?
>
> I want to map the entire docbook process. As I am
still very much a novice
> C++ coder, I am in over my head trying to
trace how
everything connects.
>> The process should be documented for the wiki.
>>
>> Ideas?
>>
>> Thanks.
>
> Check http://www.graphviz.org/Gallery.php
Doxygen uses graphviz. De-facto standard of documenting
sources.
Thank you both.
My understanding of doxygen was that software takes existing commentation in the source
code to create documents. If no commentation exists then does doxygen still create
documentation? How?
This is all very new to me. I would be grateful to receive a description/outline how this
process works.
The goal here is for me to understand how the docbook support process works with respect
to the source code --- so I can document this process at the wiki. I very much am a C++
newbie and can't simply browse the source code to create a flow diagram. Just
can't happen with my current C++ skills. For me to get to that point will take a long
time. :) So yes, by looking for some way to convert the source code to a flow diagram I
take a shortcut toward understanding the process and will learn about the source code
because the flow diagram is a guide.
Thanks!
Darrell
4703
days inactive
4705
days old
4 comments
3 participants
participants (3)
-
Aleksey Midenkov -
Darrell Anderson -
Serghei Amelian