Developer forums (C::B DEVELOPMENT STRICTLY!) > Plugins development
Doxygen plugin
MortenMacFly:
--- Quote from: codeur on March 29, 2010, 07:45:19 am ---For those people, it would be a pain if they had to set their preferences according to their in-house standards again every time they start a new project. Could ALL the commenting style preferences last used be stored and become the new default commenting style preferences when a new, not yet commented project is started?
--- End quote ---
I was thinking about that myself. My idea would be to have a template file which is read on startup rather than hard-coded internally. This file you could load and parse the buffer for certain tokens to replace - similar as we do it with the default code or C::B's HTML startup page, for example.
So something like this:
--- Code: ---PROJECT_NAME = Code::Blocks
--- End code ---
would become:
--- Code: ---PROJECT_NAME = $(project_name)
--- End code ---
This is very flexible as you could use macro replacements in addition for updating flags. Besides you can easily upgrade any flags needed in the UI (for easier access) by just another macro (replacement) in the template file. Users familiar with environment variables could make use of this, too without needing to compile the plugin. Just edit the template,. setup an envvar and you are done. :-) Surely the settings applied using DoxyBlocks directly should always supersede.
Furthermore an update of doxygens default config file would be as simple as updating this single file... etc... I hope you get my point.
Cryogen:
Hi Guys,
--- Quote from: MortenMacFly on March 29, 2010, 08:06:24 am ---
--- Quote from: codeur on March 29, 2010, 07:45:19 am ---For those people, it would be a pain if they had to set their preferences according to their in-house standards again every time they start a new project. Could ALL the commenting style preferences last used be stored and become the new default commenting style preferences when a new, not yet commented project is started?
--- End quote ---
I was thinking about that myself. My idea would be to have a template file which is read on startup rather than hard-coded internally. This file you could load and parse the buffer for certain tokens to replace - similar as we do it with the default code or C::B's HTML startup page, for example.
--- End quote ---
Interesting point. I can see that it would be useful to be able to apply a default configuration set, yes. The idea of being able to use macros in the default config also sounds good. I'll look at it.
Thanks,
Gary.
Cryogen:
Hey Codeur,
--- Quote from: codeur on March 29, 2010, 07:45:19 am ---As I start using DoxyBlocks in a few projects myself prior to the big release, I am going to dribble in a few issues as I encounter them. Starting now:
And a minor one:
The prototype: int yes( const char *question );
generates: ----- * @param *question constchar ----- for the parameter.
The prototype: bool yes( const string &question );
generates: ----- * @param &question conststring ----- for the parameter.
Can this be easily fixed?
--- End quote ---
Fixed? Yes. Easily? No. ;-)
It will require further tinkering with the regexes, at which I'm no expert, but I will see what I can come up with. It should parse multiple args correctly.
Thanks.
Cryogen:
--- Quote from: MortenMacFly on March 29, 2010, 07:16:19 am ---
--- Quote from: Cryogen on March 28, 2010, 07:30:51 am ---Released version 1.4.366 of DoxyBlocks
--- End quote ---
BTW: You should add a virtual target named "All" to your project files that would compile the main target. This would ensure that when compiling the C::B workspace (where all projects / target belong also to the virtual target "all") you plugin gets compiled, too. I just realised that. Have a look at other plugins if in doubt.
--- End quote ---
Yup, missed that. Done, thanks.
Cryogen:
Hi Guys,
Released version 1.5.440 of DoxyBlocks
-Added: Virtual target "All", for consistency.
-Updated: Menu text so that only the first word is capitalised, as per the existing convention.
-Added: New functionality to save and load a configuration template. Requested by Codeur.
Codeur, have a play with this. It saves the file, DoxyBlocks.ini, in C::B's global config directory, which should be C:\Users\<USER>\AppData\Roaming\codeblocks on Windows.
Cheers.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version