Developer forums (C::B DEVELOPMENT STRICTLY!) > Plugins development
NEW PLUGIN: Code Browser
Joren7:
Hi guys, I have used CodeBlocks from 2005, and my attention goes to something missing...a Code Browser plugin!
I'm thinking of a plugin that draw some diagrams (maybe UML) of the code (function or methods) that you are browsing...
As example, think that you want to know which methods are called inside a function, or maybe only in a part of it...
Or maybe you want to know all the part of the code that access a particular variables...
This is my idea...I think it could be useful for everyone.
When I code I write many papers with UML diagrams, either to project or to undestand some part that I am working to.
When I have to modify something, I begin studying the code and drawing diagrams using pen and paper...
What do you think about it?
Let me know if it is something useless...
Thank's to all!
/Joren
JGM:
Is a great idea :D
It will help some of us that are lost in road.
lubos:
i would love you for that plugin :P
rickg22:
Actually making a UML diagram from CodeCompletion is pretty straightforward since you already have the tokens at hand. Now, the HARD PART would be to add / edit methods from UML and generate the C++ code, because our parser isn't C++ complete. But yeah, it would still be useful to look at the UML.
Joren7:
Well...my idea is to develop a plugin that might you select what to see using these tokens...
Say that you want to know what methods are called from within another method. You choose the start method, and then click on an hypotetic menu voice "code flows". Then it will appear a diagram of what functions are called...
This is the starting point, the road continue with another function like "variable access", in which you see a diagram with all the pieces of code
that use the selected variables...this is my idea...
I'll hope to begin soon the development, now I begin the project phase!
Where do you suggest me to start with? The tokens of the code completion may be a good start...
Navigation
[0] Message Index
[#] Next page
Go to full version