Comments on: First package of jsdoc-toolkit-ext

By: Dan

Dan — Tue, 08 Jul 2008 03:38:23 +0000

Hi,

I’ve just checked out the most recent version (on 8th July) including the patches that were submitted on the ext forum – everything gets generated, but nothing gets displayed in the tree.

Looking at the code, it’s trying to load child node data from Docs.classData – in the docs.js file that was output, Docs has no properties, it’s declared like so:

Docs = {};

Any idea what’s gone wrong? The last version I tried worked really well.

Thanks,

Dan

By: Emp1

Emp1 — Sun, 15 Jun 2008 18:35:14 +0000

HI, you are making a great tool.
I still have a problem with template/ext. When i launch the script on windows xp,

java -jar jsrun.jar app/main.js -a -t=templates/ext -r ../JSSSOURCES

Then i get this output:

Plugin Ext installed
num classes: 7

The files are created but they are like this one:
http://emp1.fr/JSSOURCES_api.js.html

My template seams to be good, so what’s wrong please?

By: Christocracy

Christocracy — Tue, 15 Apr 2008 01:14:09 +0000

Hey Cornelius. I've started writing a blog-entry about Jsdoc Toolkit on my blog here

By: Cornelius Weiss

Cornelius Weiss — Wed, 09 Apr 2008 21:19:56 +0000

@Shyru
Which operating system do you use? I have it running under OS X and Solaris w.o problems and without the need of JSDOC.Lang.read_hex() and Dumper.js.

Dumper.js has a license not compatible to the jsrun.jar, so i removed it. But I guess that it’s used in some exception cases.

I always let the svn information in, to allow easy updates.

@dan
yes, the stuff is based on 2.0. I’ll need to take a look how the plugin-manager developed, hopefully I can skip the custiom stuff and only supply a plugin for the official code.

By: Dan

Dan — Tue, 08 Apr 2008 01:41:03 +0000

Works really well – thanks.

Do you have any plans to work with version 2 of the jsdoc-toolkit – the current beta (which looks close to launch) allows plugins which may work well with your solution.

By: Shyru

Shyru — Mon, 07 Apr 2008 16:24:31 +0000

I just tried your release.
This is what I found out:
JSDOC.Lang.read_hex() was a missing function – I copied it from jsdoc-tk 2.0

The publish.js is faulty because it forgets to copy numerous files which are also not available in the template directory. I copied all files from the sample documentation directory, and then it worked.

It is currently not possible to launch jsdoc from outside the jsdoc directory because of path errors. – With jsdoc-tk 1.x this was possible.

The package had all .svn directories included. Hint: (In case you did not just forget) make an svn export before releasing something.

Other than that it works, but shows the known limitations in the output, but I think that is clear, and I will not report the various problems unless desired.

All in all, great work so far, keep it up!! Even with the current flaws it is way better as the default jsdoc templates!