Open GoogleCodeExporter opened 8 years ago
I'm going to study this to see if it's a good idea or not, but I'm tentatively
accepting it.
Original comment by micmath
on 8 Nov 2008 at 10:18
Original comment by micmath
on 8 Nov 2008 at 10:18
[deleted comment]
What do you do if there are sub-components to this class? I.e., if you want to
document additions to myUtilSet.DOMUtils? The spurious documentation comment
above
doesn't seem to work on something like myUtilSet.DOMUtils. But maybe that's the
wrong form for this sort of thing.
Original comment by rpgold...@gmail.com
on 6 Mar 2009 at 5:45
To get around this limitation I experimented for a bit as I was needing to
overcome the fact that window is not a Built-In Namespace as I was providing so
extension to it. As luck would have it I discovered a work around.
/**
* @namespace
* @name window
* @description supplimental window methods.
*/
// By declaring the namespace above I was able to assign the field below to the
window namespace
/**
* @memberOf window
* @name isinited
* @description holds whether the apicalls can continue when referencing elements.
*/
// Likewise I was able to add a child to the namespace
/**
* @memberOf window
* @namespace
* @description adds queryString as a property of window inspired by Adam Vandenberg
*/
window.queryString = {};
Original comment by abyss...@gmail.com
on 5 Jul 2010 at 12:37
Original issue reported on code.google.com by
lezek...@gmail.com
on 28 Oct 2008 at 3:23