Check http://www.eclipsecon.org/2011/sessions/?page=sessions&id=2187 for information on how to add an infer engine (yes, the AST gives you access to the code and the parser the comments) and how to contribute a provider to look up your documentation and format it for viewing.
Yes, check the slides of http://www.eclipsecon.org/2011/sessions/?page=sessions&id=2187 , although you can't change the actual parser without forking (JSDoc comments are the only ones stored on the AST directly). You'll want to add an infer engine that processes your JSDuck comments as well as a documentation provider to help show them to the user.
Yes, check the slides of http://www.eclipsecon.org/2011/sessions/?page=sessions&id=2187 , although you can't change the actual parser without forking (JSDoc comments are the only ones stored on the AST directly). You'll want to add an infer engine that processes your JSDuck comments as well as a documentation provider to help show them to the user.
Check http://www.eclipsecon.org/2011/sessions/?page=sessions&id=2187 for information on how to add an infer engine (yes, the AST gives you access to the code and the parser the comments) and how to contribute a provider to look up your documentation and format it for viewing.
--
---
Nitin Dahyabhai
Eclipse WTP, IBM
Yes, check the slides of http://www.eclipsecon.org/2011/sessions/?page=sessions&id=2187 , although you can't change the actual parser without forking (JSDoc comments are the only ones stored on the AST directly). You'll want to add an infer engine that processes your JSDuck comments as well as a documentation provider to help show them to the user.
Check http://www.eclipsecon.org/2011/sessions/?page=sessions&id=2187 for information on how to add an infer engine (yes, the AST gives you access to the code and the parser the comments) and how to contribute a provider to look up your documentation and format it for viewing.
--
---
Nitin Dahyabhai
Eclipse WTP, IBM
Yes, check the slides of http://www.eclipsecon.org/2011/sessions/?page=sessions&id=2187 , although you can't change the actual parser without forking (JSDoc comments are the only ones stored on the AST directly). You'll want to add an infer engine that processes your JSDuck comments as well as a documentation provider to help show them to the user.
--
---
Nitin Dahyabhai
Eclipse WTP, IBM
Yes, check the slides of http://www.eclipsecon.org/2011/sessions/?page=sessions&id=2187 , although you can't change the actual parser without forking (JSDoc comments are the only ones stored on the AST directly). You'll want to add an infer engine that processes your JSDuck comments as well as a documentation provider to help show them to the user.
--
---
Nitin Dahyabhai
Eclipse WTP, IBM
Check http://www.eclipsecon.org/2011/sessions/?page=sessions&id=2187 for information on how to add an infer engine (yes, the AST gives you access to the code and the parser the comments) and how to contribute a provider to look up your documentation and format it for viewing.
--
---
Nitin Dahyabhai
Eclipse WTP, IBM
Yes, check the slides of http://www.eclipsecon.org/2011/sessions/?page=sessions&id=2187 , although you can't change the actual parser without forking (JSDoc comments are the only ones stored on the AST directly). You'll want to add an infer engine that processes your JSDuck comments as well as a documentation provider to help show them to the user.
--
---
Nitin Dahyabhai
Eclipse WTP, IBM
Yes, check the slides of http://www.eclipsecon.org/2011/sessions/?page=sessions&id=2187 , although you can't change the actual parser without forking (JSDoc comments are the only ones stored on the AST directly). You'll want to add an infer engine that processes your JSDuck comments as well as a documentation provider to help show them to the user.
--
---
Nitin Dahyabhai
Eclipse WTP, IBM
Yes, check the slides of http://www.eclipsecon.org/2011/sessions/?page=sessions&id=2187 , although you can't change the actual parser without forking (JSDoc comments are the only ones stored on the AST directly). You'll want to add an infer engine that processes your JSDuck comments as well as a documentation provider to help show them to the user.
--
---
Nitin Dahyabhai
Eclipse WTP, IBM
Check http://www.eclipsecon.org/2011/sessions/?page=sessions&id=2187 for information on how to add an infer engine (yes, the AST gives you access to the code and the parser the comments) and how to contribute a provider to look up your documentation and format it for viewing.
--
---
Nitin Dahyabhai
Eclipse WTP, IBM
Yes, check the slides of http://www.eclipsecon.org/2011/sessions/?page=sessions&id=2187 , although you can't change the actual parser without forking (JSDoc comments are the only ones stored on the AST directly). You'll want to add an infer engine that processes your JSDuck comments as well as a documentation provider to help show them to the user.
--
---
Nitin Dahyabhai
Eclipse WTP, IBM
Yes, check the slides of http://www.eclipsecon.org/2011/sessions/?page=sessions&id=2187 , although you can't change the actual parser without forking (JSDoc comments are the only ones stored on the AST directly). You'll want to add an infer engine that processes your JSDuck comments as well as a documentation provider to help show them to the user.
--
---
Nitin Dahyabhai
Eclipse WTP, IBM
Yes, check the slides of http://www.eclipsecon.org/2011/sessions/?page=sessions&id=2187 , although you can't change the actual parser without forking (JSDoc comments are the only ones stored on the AST directly). You'll want to add an infer engine that processes your JSDuck comments as well as a documentation provider to help show them to the user.
--
---
Nitin Dahyabhai
Eclipse WTP, IBM
Check http://www.eclipsecon.org/2011/sessions/?page=sessions&id=2187 for information on how to add an infer engine (yes, the AST gives you access to the code and the parser the comments) and how to contribute a provider to look up your documentation and format it for viewing.
--
---
Nitin Dahyabhai
Eclipse WTP, IBM
Yes, check the slides of http://www.eclipsecon.org/2011/sessions/?page=sessions&id=2187 , although you can't change the actual parser without forking (JSDoc comments are the only ones stored on the AST directly). You'll want to add an infer engine that processes your JSDuck comments as well as a documentation provider to help show them to the user.
--
---
Nitin Dahyabhai
Eclipse WTP, IBM
Yes, check the slides of http://www.eclipsecon.org/2011/sessions/?page=sessions&id=2187 , although you can't change the actual parser without forking (JSDoc comments are the only ones stored on the AST directly). You'll want to add an infer engine that processes your JSDuck comments as well as a documentation provider to help show them to the user.
--
---
Nitin Dahyabhai
Eclipse WTP, IBM
Yes, check the slides of http://www.eclipsecon.org/2011/sessions/?page=sessions&id=2187 , although you can't change the actual parser without forking (JSDoc comments are the only ones stored on the AST directly). You'll want to add an infer engine that processes your JSDuck comments as well as a documentation provider to help show them to the user.
--
---
Nitin Dahyabhai
Eclipse WTP, IBM
Check http://www.eclipsecon.org/2011/sessions/?page=sessions&id=2187 for information on how to add an infer engine (yes, the AST gives you access to the code and the parser the comments) and how to contribute a provider to look up your documentation and format it for viewing.
--
---
Nitin Dahyabhai
Eclipse WTP, IBM
Yes, check the slides of http://www.eclipsecon.org/2011/sessions/?page=sessions&id=2187 , although you can't change the actual parser without forking (JSDoc comments are the only ones stored on the AST directly). You'll want to add an infer engine that processes your JSDuck comments as well as a documentation provider to help show them to the user.
--
---
Nitin Dahyabhai
Eclipse WTP, IBM
Yes, check the slides of http://www.eclipsecon.org/2011/sessions/?page=sessions&id=2187 , although you can't change the actual parser without forking (JSDoc comments are the only ones stored on the AST directly). You'll want to add an infer engine that processes your JSDuck comments as well as a documentation provider to help show them to the user.
--
---
Nitin Dahyabhai
Eclipse WTP, IBM
Yes, check the slides of http://www.eclipsecon.org/2011/sessions/?page=sessions&id=2187 , although you can't change the actual parser without forking (JSDoc comments are the only ones stored on the AST directly). You'll want to add an infer engine that processes your JSDuck comments as well as a documentation provider to help show them to the user.
--
---
Nitin Dahyabhai
Eclipse WTP, IBM
Check http://www.eclipsecon.org/2011/sessions/?page=sessions&id=2187 for information on how to add an infer engine (yes, the AST gives you access to the code and the parser the comments) and how to contribute a provider to look up your documentation and format it for viewing.
--
---
Nitin Dahyabhai
Eclipse WTP, IBM
Yes, check the slides of http://www.eclipsecon.org/2011/sessions/?page=sessions&id=2187 , although you can't change the actual parser without forking (JSDoc comments are the only ones stored on the AST directly). You'll want to add an infer engine that processes your JSDuck comments as well as a documentation provider to help show them to the user.
--
---
Nitin Dahyabhai
Eclipse WTP, IBM
Yes, check the slides of http://www.eclipsecon.org/2011/sessions/?page=sessions&id=2187 , although you can't change the actual parser without forking (JSDoc comments are the only ones stored on the AST directly). You'll want to add an infer engine that processes your JSDuck comments as well as a documentation provider to help show them to the user.
--
---
Nitin Dahyabhai
Eclipse WTP, IBM
Yes, check the slides of http://www.eclipsecon.org/2011/sessions/?page=sessions&id=2187 , although you can't change the actual parser without forking (JSDoc comments are the only ones stored on the AST directly). You'll want to add an infer engine that processes your JSDuck comments as well as a documentation provider to help show them to the user.
--
---
Nitin Dahyabhai
Eclipse WTP, IBM
Check http://www.eclipsecon.org/2011/sessions/?page=sessions&id=2187 for information on how to add an infer engine (yes, the AST gives you access to the code and the parser the comments) and how to contribute a provider to look up your documentation and format it for viewing.
--
---
Nitin Dahyabhai
Eclipse WTP, IBM
Yes, check the slides of http://www.eclipsecon.org/2011/sessions/?page=sessions&id=2187 , although you can't change the actual parser without forking (JSDoc comments are the only ones stored on the AST directly). You'll want to add an infer engine that processes your JSDuck comments as well as a documentation provider to help show them to the user.
--
---
Nitin Dahyabhai
Eclipse WTP, IBM
Yes, check the slides of http://www.eclipsecon.org/2011/sessions/?page=sessions&id=2187 , although you can't change the actual parser without forking (JSDoc comments are the only ones stored on the AST directly). You'll want to add an infer engine that processes your JSDuck comments as well as a documentation provider to help show them to the user.
--
---
Nitin Dahyabhai
Eclipse WTP, IBM
Yes, check the slides of http://www.eclipsecon.org/2011/sessions/?page=sessions&id=2187 , although you can't change the actual parser without forking (JSDoc comments are the only ones stored on the AST directly). You'll want to add an infer engine that processes your JSDuck comments as well as a documentation provider to help show them to the user.
--
---
Nitin Dahyabhai
Eclipse WTP, IBM
Check http://www.eclipsecon.org/2011/sessions/?page=sessions&id=2187 for information on how to add an infer engine (yes, the AST gives you access to the code and the parser the comments) and how to contribute a provider to look up your documentation and format it for viewing.
--
---
Nitin Dahyabhai
Eclipse WTP, IBM
Yes, check the slides of http://www.eclipsecon.org/2011/sessions/?page=sessions&id=2187 , although you can't change the actual parser without forking (JSDoc comments are the only ones stored on the AST directly). You'll want to add an infer engine that processes your JSDuck comments as well as a documentation provider to help show them to the user.
--
---
Nitin Dahyabhai
Eclipse WTP, IBM
Yes, check the slides of http://www.eclipsecon.org/2011/sessions/?page=sessions&id=2187 , although you can't change the actual parser without forking (JSDoc comments are the only ones stored on the AST directly). You'll want to add an infer engine that processes your JSDuck comments as well as a documentation provider to help show them to the user.
--
---
Nitin Dahyabhai
Eclipse WTP, IBM
Yes, check the slides of http://www.eclipsecon.org/2011/sessions/?page=sessions&id=2187 , although you can't change the actual parser without forking (JSDoc comments are the only ones stored on the AST directly). You'll want to add an infer engine that processes your JSDuck comments as well as a documentation provider to help show them to the user.
--
---
Nitin Dahyabhai
Eclipse WTP, IBM
Check http://www.eclipsecon.org/2011/sessions/?page=sessions&id=2187 for information on how to add an infer engine (yes, the AST gives you access to the code and the parser the comments) and how to contribute a provider to look up your documentation and format it for viewing.
--
---
Nitin Dahyabhai
Eclipse WTP, IBM
Yes, check the slides of http://www.eclipsecon.org/2011/sessions/?page=sessions&id=2187 , although you can't change the actual parser without forking (JSDoc comments are the only ones stored on the AST directly). You'll want to add an infer engine that processes your JSDuck comments as well as a documentation provider to help show them to the user.
--
---
Nitin Dahyabhai
Eclipse WTP, IBM
Yes, check the slides of http://www.eclipsecon.org/2011/sessions/?page=sessions&id=2187 , although you can't change the actual parser without forking (JSDoc comments are the only ones stored on the AST directly). You'll want to add an infer engine that processes your JSDuck comments as well as a documentation provider to help show them to the user.
--
---
Nitin Dahyabhai
Eclipse WTP, IBM