I’d recommend posting your question on the YUIDoc forum — that’s a better place to get specific questions answered.

http://yuilibrary.com/forum/viewforum.php?f=26

-Eric

var somevariable=true;

function foo(a1,a2)
{
some code;
}
Can please anyone guide me on this ,how to generate a YUI doc without using class tag

Thanks for the feedback. I’d love to see you post this feedback to the YUI Doc discussion forum –

http://yuilibrary.com/forum/viewforum.php?f=26

That would be the best place to have a conversation about the features you’re discussing and the suggestions you’re making for improving the tool.

Regards,
Eric

I have a couple of questions/issues regarding YUI Doc…
I am a little unclear of the expected relationships between source files, modules and namespaces. Is it expected that there is a 1:1 relationship between source file & module? Would the namespaces used in a module be the exclusive property of that module?

I have also experimented by defining some submodules, but the result was not as I expected. I would expect the submodules to be displayed in a hierarchy in the navigator, but they were presented in the body of the module page.

I am in the process of converting from jsdoc toolkit … I miss a few features from this tool, specifically @link to arbitrarily link to a documented artifact from the description.

There was also an error when I tried to document static members of a constructor (‘@class’). Is this not good?

Overall I am very impressed. I would have liked navigation based on namespace, as this is the way my existing code is structured … with a moderately long namespace the class references in the navigator overflow the default space allowed. Wouldn’t it be better to have some sort of expandable tree navigation based on distinct namespaces, with just the bare class names as leaves?

here’s a fork of yuidoc that can be installed with easy_install:
http://github.com/dinoboff/yuidoc/tree/master