@elextr: thanks for the response, better late than never 😁

Actually I stopped working on this for two reasons:

• the Geany code is not easy to extend
• it would make more sense to put the workbench plugin in the cascade before the project so that projects can inherit workbench global build settings. Putting it on top of everything wouldn't make sense

IMHO the not GUI related part in Geany could need a complete re-write and it would be cool to have some of these features/properties:

• any caller can create it's own source
• it should have a name so we do not get linker issues (meaning it should be dynamic)
• the caller can specify at which position to insert his source in the sources cascade (by name, e.g. before "project")
• the cascade of build sources could be configurable (maybe with some kind of sanity check)
• it would be cool to see a graphic display of the cascade to find the place where a value comes from (for debugging, for users who are stuck understanding why they don't get the expected value). This could maybe be a dynamically generated SVG image

Just some ideas 😃 I guess this would break compatibility to other plugins so I did not even start working on it (also I did not find much references to the build data in Geany-Plugins but maybe there are some in external plugins repos).

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.