jGrouseDoc 1.6 released

[denis.r...@gmail.com]

Hi,

jGrouseDoc 1.6 was finally released.
The biggest enhancement in the new version is support for complex
parameters and return types, via @... tag.
Also a number of nasty bugs have been fixed (thanks a lot to people
who reported and fixed them!), here is the full list:

46 'item' undefined in navTree.js
47 After {@link foor bar} the first following space is eaten in
output.
48 NullPointerException in jgrouse.jgdoc.DocManager.resolveLink
49 add support for specification of components of complex parameter
51 The Chinese Simple characters comments will be garbled in the
generated Docs
52 Index error in IE 6
53 Namespaces will join to first line on the Index page in IE
55 search box appears blank in "noframe" theme in IE6
56 Sometimes search box hides the search input in "noframe" theme in
IE6
57 In certain cases after search IE forwards browser to incorrect
location
58 navTree.html doesn't show the first member of GLOBAL namespace
59 trim leading spaces preceding * in the beginning of a line
60 link names could collide with window's members and break javascript
in IE
61 IE does not handle correctly "\n" character in search "summary"
element

[Jim]

Hey Denis,

I got slammed, and have only just now upgraded to 1.6 from 1.0. Just
wanted to note that all the changes look really great and I'm really
appreciative.

I was thinking about IDE support ... if only Adobe's JSEclipse plug-in,
for example, allowed for custom extensions -- they currently have
JSDoc(JavaDoc) tags built in (syntax highlighting and auto-completion).
I posted on their forums about being able to extend the documentation
keyword set, but never got a response, and it's a closed source project
that I'm not sure they're even active on anymore. Oh well.

Jim

[denis.r...@gmail.com]

Hey Jim,

Good that you liked it. That's the best reward an author could get. If
you want more goodies, try the version in SVN - it has accelerated
XSLT task and simplified way to document variables, functions, etc.

It seems that JSEclipse indeed has a way to upload an XML to extend
their code completion functionality - it appears in their help.

I am ready to add an export in their format, but the format itself is
not quite clear to me.
If you could investigate that format then we could work together on
the JSEclipse renderer.

Technically speaking, Aptana has a way to extend their code completion
via XML or JSON file. If there would be a demand, then creating a
renderer for Aptana should not be an issue

Regards
Denis