Doxygen plugin

[codeur]

Patch #3127 was applied on 8 February. I built and tested the new version (1.7.655).
The repair is only partial and the issue is not fixed.
DoxyBlocks still does not properly handle output documents located elsewhere than in the doxygen folder (even when the doxyfile is in that "other" output folder).

[Cryogen]

Is this one still problematic?

Yes. It does not apply at all. :-(

Hey - this is already applied ! :-)

Yes and no. I see the problem. For some reason, the second version of the patch missed a bunch of stuff. Something seems to be going on with patch creation in Tortoise. I'll upload take 3. Ergh.

[Cryogen]

Patch #3127 was applied on 8 February. I built and tested the new version (1.7.655).
The repair is only partial and the issue is not fixed.

Yes. See the previous response

DoxyBlocks still does not properly handle output documents located elsewhere than in the doxygen folder (even when the doxyfile is in that "other" output folder).

That will improve somewhat once we get all the changes in place, however, you might reconsider your use of the word "properly". As explained in detail below, it still won't do exactly what you're after as it wasn't designed to do so. I don't consider your approach "proper" use of doxygen but I respect your right to do things as you wish. I always try and build in maximum flexibility, this ain't Microsoft, but I don't have the time to address your request in full at present. Feel free to improve things.

Cheers.

[codeur]

Patch #3127 was applied on 8 February. I built and tested the new version (1.7.655).
The repair is only partial and the issue is not fixed.

Yes. See the previous response
... however, you might reconsider your use of the word "properly". As explained in detail below, it still won't do exactly what you're after as it wasn't designed to do so.

I understand Gary. I have read your previous posts and for me "properly" for now includes the restriction that we need to have the doxyfile inside the output documentation folder. I'll live with this minor constraint for now.
As you suggest I will indeed hop on board in a few months when I have a bit of time. I'll then provide patches to enable those few refinements that are not yet in by then, like the possibility of having separate doxygen setup and output documentation folders.
That's not a worry.

DoxyBlocks is great and a huge help as it is. It has been used a lot around here and is VERY useful in educational environments. Programming students who would normally skip all documentation get into the habit of documenting their code thanks to it and to you. Have a look at the latest version of CodeBlocks-EP if you have the time.

[Cryogen]

 Hi Codeur,

Thanks, that's great. I'm happy to look at improving things when I get the time, as well. I think it will require a revision of all of the path management code as it wasn't written with that in mind. It shouldn't be an earth-shattering change, though, it just needs some time.

CodeBlocks-EP is very cool. I will do that. :-)

Cheers.

[youarefunny]

I noticed that this plug-in creates the doxygen config file as 'doxyfile' instead of doxygens default 'Doxyfile'.  Could this be changed please.

Oh, pan by the way great plug-in

I can see the future of this plug-in extracting the documentation and having fly-outs as you highlight a function in auto-complete and by right clicking on things.  Keep up the good work.

[ptDev]

I can see the future of this plug-in extracting the documentation and having fly-outs as you highlight a function in auto-complete and by right clicking on things.  Keep up the good work.

The best way to implement this would be allowing CodeCompletion to parse doxygen documentation.

[oBFusCATed]

Or provide some hooks to enable different styles of documentation...

[MortenMacFly]

...I got another feature request:
Doxygen (while compiling) complains about missing documentation like missing variables or wrong spelled variables. It would be nice to have a log window where these messages are piped into and where you can click on the messages and jump to the line in the file (similar like the build log).

[oBFusCATed]

Why not use the build log directly, there are too many logs already:)

[killerbot]

before I forget, in on e of the last changes something got broken, with respect to output directory or position position of the cbp file or the doxygen file. It used to work before, now it no longer works. Gonna try to post a little project here, showcasing the failure this evening,

[killerbot]

here's a project that now fail with the doxygen plugin, where it used to work in the past.

----------------------------------------------------------------------------------------------------
Extracting documentation for Test.
DoxyBlocks is working, please wait a few moments...
Writing doxyfile...
Failed. /home/killerbot/Projects/Test/Project/doxygen/doxyfile was not created.

Done.

Note that the "doxygen" directory is created

[gd_on]

Here is a small Hello standard program. Results with Doxybloacks are not those I expect.

cbp file is inside a make folder. main.c and version.h are in src.
Autoversioning plugin finds correctly version.h, but Doxyblocks when configured to use it, does not seem to find version.h. More, it tries to locate it at a wrong place.
svn 7141, Win XP, SP3.

And in the result, version.h is in the file list, but not main.c (totally different problem here ?).

Bug or I'm missing something ?

Gd_on

[Derjik]

Hello again,

I hope this is the appropriate thread to talk about eventual (small) "issues" with DoxyBlocks... if not, I'm really sorry, and I understand my post could be deleted.

So:
As i said in this thread, I'm running C::B 12.11 on Windows 7 Pro and while "everything's fine" with DoxyWizard itself for extracting the documentation, the "Extract Documentation" item from DoxyBlocks doesn't seem to do anything...
It just creates a small doxyfile if no existing one is found, else it "detects" it, but doesn't extract anything. (and the doxyfile I use in my currect projet is valid, as DoxyWizard managed to extract the documentation).

So this isn't a "harmful" problem, but I like the idea of "just using a keyboard shortcut" whenever I want to extract (or "update") my documentation... and I don't know what I'm doing wrong with DoxyBlocks.
Any help welcome, so thanks by advance, and sorry if I'm not in the right thread :|


EDIT: As I said in the other topic, we found more details on this problem: The "Extract Documentation" feature cannot handle special characters in the working path (and I'm working under "Mes Documents", so the blank caused the trouble for me...).
I don't know if we can call it "a bug", but... it's said.

[Joerg]

Hi,
I would like to suggest another template for block comments without the trailing stars:

Code Select Expand


/** \brief

\param
\param
\return

*/

It's easier to edit, as long as C::B does not fill in the stars, as eclipse is doing ;-)