Developer forums (C::B DEVELOPMENT STRICTLY!) > Plugins development
Doxygen plugin
codeur:
--- Quote from: Cryogen on March 11, 2010, 08:56:31 am ---
Today's excitement :D :
Released version 1.0.14 of DoxyBlocks
-...
--- End quote ---
I notice furious activity still going on SourceForge since, with version 15 in SVN.
Many thank.
MortenMacFly:
--- Quote from: Cryogen on March 11, 2010, 09:27:29 pm ---
--- Quote ---Drop the .mo files into $SHARE/codeblocks/locale/lang_CODE and Code::Blocks will use them.
--- End quote ---
still correct?
--- End quote ---
Yes, that is correct. And yes: This directory does not exist in the nightlies.
Cryogen:
--- Quote from: MortenMacFly on March 12, 2010, 09:23:14 am ---
--- Quote from: Cryogen on March 11, 2010, 09:27:29 pm ---
--- Quote ---Drop the .mo files into $SHARE/codeblocks/locale/lang_CODE and Code::Blocks will use them.
--- End quote ---
still correct?
--- End quote ---
Yes, that is correct. And yes: This directory does not exist in the nightlies.
--- End quote ---
OK, thanks. Or the SVN repo, apparently, where I would have thought you'd expect to see the directory and a usage note, or something, no? I've never used a nightly build.
Could I also ask that you go back and answer the various other questions that I'm awaiting answers for? I know you've probably got 50 other things to think about here but I really need some answers.
E.g.
The whole Linux plug-in thing.
The problem with the toolbar crashing C::B when no editors are open.
Your project patch.
The other localisation questions.
Many thanks.
Cryogen:
Hi Guys,
Released version 1.1.79 of DoxyBlocks
-Added: The toolbar and menu are now disabled when all projects are closed and re-enabled when a project is opened.
-Fixed: The wxSmith block was being lost from the .cbp when saving during project closure. Reworked how config is saved.
I also spent some time looking into automating the documentation of a file and found that it was not practical as things stand. There is currently no way to differentiate adequately between a function declaration and a function call, or stop it trying to document every macro declaration or other entry that looks like a documentable entity in the file. Better regexes would go some way towards improving things but it's always going to be a mixed bag. Since, other than when retrofitting existing code, we are encouraging people to document code as it's written, I don't see this as a big issue and that's where I'm going to leave it for now.
codeur:
--- Quote from: Cryogen on March 16, 2010, 08:04:01 pm --- Hi Guys,
... automating the documentation of a file and found that it was not practical as things stand. ...
--- End quote ---
Agreed. I use CB in an educational setting and would look pretty dimly at per-file documentation automation. It would mess up already written function banner comments and would encourage the poor practice of "commenting when all is done". I am glad you don't consider it anymore.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version