Lucamar, thank you for clear question.
Perfect in plans not always perfect in life.
Preferably - set expectations: What(general), work amount, intensity, time limit, conditions.
As far as I imagine now:
WHAT:
1. OSS-GPL(?1,2,3?)
2. Bring it to the level of library, that makes possible visual code manipulation. At procedures ( like low level ~DFD)
Work amount: detailed visual diagram of:
a) parser(! ultimate, adapt from FPC, help needed: with it many other possibilities are open, including parse to graphml, or other DIA or other. Without it - nothing will work )
b) Graphing library primitive ( probably - from Edson's / Laz-model works)
c) Data structure + Code-Graph junction
d) integration to Lazarus.
1+d - Help Ultimately needed!! - not able to go through the whole code/compatibility of FPC, Lazarus. So actually - the help from IDE/FPC developers will be required (actually - I'm not so expertized to judge.) But anyway - the general (just concept) scope of FPC source usage(!) and integration(?) will be neede at the very beginning.
intensity
Initially 3h/24x10d, on the run - at least 4..5h/7dx6mon.
CONDITIONS:
0. Community will state they're interests for milestones
1. My side: set some kind of startup... go from diagram scope to questions.
2. start dialogue and see the outcome
// 0.-1.-2. -- 4--7 days. if this starts with success - further planning possible.
3. Update agreement.
4. quit / proceed
With respect,
Researching.