|
|
|
Comments formatted with // should also be revealed with Ctrl-Q. Example:
///////////////////////////////////////////////////////////////////////////////
// Empties an html SELECT menu, and repopulates it using the name/value
// pairs in the oOptions collection/array.
//
// Parameters:
// oOptions: any object collection or array of objects, where the i-th OPTION
// tag would be (as a string): "<OPTION VALUE='" + oOptions[i][lbl]
// + "'>" + oOptions[i][val] = "</OPTION>".
// lbl, val: see oOptions
// selectTag: a js object representing a SELECT menu. For example, for
// <SELECT id="123"> you would pass in ${"123"} (using prototype).
// noneLabel,
// noneValue: If oOptions is empty, then the select menu is populated
// with a single <OPTION> tag whose value is noneValue, and whose
// content is noneLabel.
//
// Example use with prototype Ajax:
// onComplete: function(req) {
// populateSelectTag(eval(req), "commodityName", "commodityId", selectTag, "None", "0" )
// }
// 11/2/2006 rb
///////////////////////////////////////////////////////////////////////////////
function foo( oOptions, lbl, val, selectTag, noneLabel, noneValue) { ... }
The Ctr-Q /** */ support has an inconsistency when used on methods declared on an object:
See attached screenshot. Please, create separate JIRA bug request, and if possible, js code fragment
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Another suggestion: ability to generate javadocs site from such javascript as well (I think there's a tool that does this already, though I can't remember its name).