Flow Diagram as a ProcedureList option

[PeterPanettone 157]

I have filed this new feature Request:

 

The Procedure List should have a Flow Diagram option. What does this mean?

Let's assume a unit has this source code:

Then the Flow Diagram option would show the following diagram in the Procedure List window (instead of the list of procedures):

Left-clicking on a diagram item would show the clicked procedure source code in the source pane.

Double-clicking on a diagram item would show the clicked procedure source code in the source code editor.

This would be a VERY USEFUL Procedure List view mode!

Here is the URL of the Feature Request:

https://sourceforge.net/p/gexperts/feature-requests/74/

 

 

Edited August 7, 2019 by PeterPanettone

[Der schöne Günther 316]

Wasn't ModelMakerTools for Delphi able to do that?

[PeterPanettone 157]

55 minutes ago, Der schöne Günther said:

Wasn't ModelMakerTools for Delphi able to do that?

AFAIR, ModelMakerTools had a lot of complicated abstractions. But what I need is only a very simple flow diagram as shown above.

[Uwe Raabe 2057]

I now that MM can create a Sequence Diagram from the call stack. I am unsure about this static analysis mentioned above.

[PeterPanettone 157]

1 hour ago, Uwe Raabe said:

I now that MM can create a Sequence Diagram from the call stack.

You mean when debugging? No, no, just a representation of the source code in the source code editor. With "MM" you mean ModelMakerTools or MMX?

[Uwe Raabe 2057]

5 minutes ago, PeterPanettone said:

With "MM" you mean ModelMakerTools or MMX?

MM = ModelMaker, the other - now discontinued - tool from ModelMaker Tools

[PeterPanettone 157]

I could also imagine the Flow Diagram View as an additional IDE main view tab after Code, Form Designer and History:

 

Edited August 7, 2019 by PeterPanettone

[PeterPanettone 157]

Colors in the Flow Diagram (this is a personal suggestion which could be customized):

 

• FormEventHandler procedures: Fuchsia 

 

• ClickHandler procedures: Green 

 

• General ClassMethod procedures: ...

 

• Functions: ...

 

• Etc. etc.

[dummzeuch 1505]

So, when can I expect a patch, that implements this functionality?

[PeterPanettone 157]

7 minutes ago, dummzeuch said:

So, when can I expect a patch, that implements this functionality?

That partly depends on my body's ability to metabolize large quantities of coffee.

 

No, but seriously: Is it allowed to use a closed source DLL dependence? Or do you know a good open-source diagram component?

Edited August 8, 2019 by PeterPanettone

[dummzeuch 1505]

26 minutes ago, PeterPanettone said:

No, but seriously: Is it allowed to use a closed source DLL dependence? Or do you know a good open-source diagram component?

That depends on the license of that DLL, I guess. This sounds as if you have got a particular DLL in mind. Which one?

[PeterPanettone 157]

23 minutes ago, dummzeuch said:

Which one?

I would create my own from the TMS Diagram component.

Edited August 8, 2019 by PeterPanettone

[PeterPanettone 157]

14 hours ago, Uwe Raabe said:

call stack

"call stack" is a term from the IDE's debugging functionality and refers to the "visited" source code lines, I believe.

 

The concept I have called "Flow Diagram" is in practice a sum of all possible call stacks, a diagram showing the complete call tree.

 

Is this definition appropriate? Or how would you name/define the concept?

Edited August 8, 2019 by PeterPanettone

[Sherlock 663]

Call tree sounds about right. But keep recursiveness in mind.

[PeterPanettone 157]

The methodology I have in mind is to take the list of procedures generated by the GExperts Procedure List and convert it into a graphical Call Tree diagram by using the rules of logic.

 

Would you agree with that approach?

Edited August 8, 2019 by PeterPanettone

[Uwe Raabe 2057]

Peganza Pascal Analyzer creates a Call Tree Report. That looks like a perfect input for such a diagram.

[PeterPanettone 157]

7 minutes ago, Uwe Raabe said:

Peganza Pascal Analyzer creates a Call Tree Report. That looks like a perfect input for such a diagram.

Good idea. Thank you!

[PeterPanettone 157]

In the Call Tree Diagram, when the mouse pointer hovers over a diagram item, then the source code documentation of this procedure is shown in a formatted hint:

 

 

 

[PeterPanettone 157]

5 hours ago, Uwe Raabe said:

Peganza Pascal Analyzer creates a Call Tree Report.

This is the Pascal Analyzer 8.1.0.0 Call Tree report for the above example source code:

 

 

However, when using this report, the user would have to buy Pascal Analyzer. So I probably will use the procedure list created by the GExperts procedure list. (Or the one used by the CnWizards procedure list).