RE: [Jsdoc-user] some questions regarding jsdoc

[<sch...@ma...>]

> nope, you're totally right. this is kind of a speciality of hop, the
> application server we are using. script files are located in
> directories which determine the prototype (or class) they belong to.
> this way, we can define a method bar() in two (or more) directories,
> say Foo and FooBar, and make them instance methods of different
> prototypes. (it's not really good practice anymore and we are
> currently elaborating on that, anyway).
>
> but i don't want to bother you with such details. it's just that i
> thought it would feel natural if JSDoc was to take the @member tag with
> a higher priority and document a method according to it -- just as it
> takes e.g. @extend simply as is without further checking if there really
> is such a parent class...

Same goes for us, a example:

er have applications in folders organized like:

applications/app/em01/em01.xul
applications/app/em02/em01.js
applications/app/em02/em02.xul
applications/app/em02/em02.js

each xul file has a script tag like <script src=""em01.js" />

while each js page contains our so called controller (getting vars 
fromthe ui and sticking them into apis)

em01.js
function FXPAGE() {

}

FXPAGE.prototype.load() {

}

....

So we could use that too. btw: last tip for own @tags worked well. Greets
Sebastian 
-----------------------------------------------------------------------------
  - Mayflower GmbH - http://www.mayflower.de - E-Mail: in...@ma... -