Allow global tags to passed from the commandline about jsdoc-toolkit

[GoogleCodeExporter]

This looks useful, Vince. Thanks for that! I'll apply your patch and give it a 
try!

Original comment by micmath on 23 Sep 2007 at 7:11

• Changed state: Accepted
• Added labels: Priority-Low, Type-Enhancement
• Removed labels: Priority-Medium, Type-Defect

[GoogleCodeExporter]

The patch for Util.js seems to be empty? I assume the idea is to make multiple
options with the same name into an array? Which seems like a good idea. I think 
I can
swing that myself.

Original comment by micmath on 23 Sep 2007 at 8:30

• Changed state: Started

[GoogleCodeExporter]

Committed in revision 244 but with some changes:

in the template, to access a global variable defined on the command line, use 
this
syntax...

Project name: {+JsDoc.DEFINE.project||''+}

Original comment by micmath on 23 Sep 2007 at 9:45

• Changed state: Fixed

[GoogleCodeExporter]

That works too, here is my original patches

Original comment by vinces1979 on 23 Sep 2007 at 5:10

Attachments:

• patches.tgz

[GoogleCodeExporter]

I've decided to generalise this, rather than treating -D as a special case. You 
can
now display (or otherwise use) any commandline option in your template, by 
refering
to the JsDoc.opt object. So the above would now become:

-D="project:Testing Project"

and

{+JsDoc.opt.D.project+}

But, to het the name of the template, you could similarly use:

{+JsDoc.opt.t+}

Original comment by micmath on 23 Sep 2007 at 7:18

[GoogleCodeExporter]

So they D still exists and can have multiple vars passed in?

Original comment by [email protected] on 23 Sep 2007 at 7:24

[GoogleCodeExporter]

Ok, -D is a little special because it splits up the values like "name: the 
value",
but otherwise you can actually now treat any commandline option as an array by
calling getOptions() like so:

JsDoc.opt = Util.getOptions(arguments, {'o':'justOnes', 'm[]':'many'});

The new '[]' bit tells the option parser to always force that option into an 
array.
So in the case of many -o options (for example) the last -o overwrites any 
before it,
but in the case of -m (for example) the value will always be an array, and will
contain every -m value.

And yes, -D is in the latest commit, and you can have many -D="keyName1:some 
value"
-D="keyName2:some other value"options and you should read them from within a 
template
like so:

{+JsDoc.opt.D.keyName1+} and {+JsDoc.opt.D.keyName2+}

Original comment by micmath on 23 Sep 2007 at 8:00