Wednesday, February 24, 2010

Re: omnicompletion for javascript

On Feb 23, 7:19 pm, David Fishburn <dfishburn....@gmail.com> wrote:
> On Tue, Feb 23, 2010 at 4:55 AM, Gareth Oakes <juiceju...@gmail.com> wrote:
> ...
> > There is a custom object model in use on this application platform and
> > I would like to omnicomplete my Javascript objects according to their
> > methods and properties. What is the best way to let omnicomplete
> > recognise my new object structures? (The object definitions are "baked
> > in" to the application, although I do have access to the completion
> > files for Eclipse JSDT).
>
> Hmm, I would be interested in seeing the format of the JSDT files.

Stubs. Generally we've followed the specifications as best as
possible and written skeleton definitions containing their types,
methods, and fields, and just using the same "compiler" on it as if it
were actual source. We're about to rearrange the CVS repository, but
for a few more days you can see our definition of the standard runtime
at
http://dev.eclipse.org/viewcvs/index.cgi/sourceediting/plugins/org.eclipse.wst.jsdt.core/libraries/system.js?root=WebTools_Project&view=markup
.

--
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php

No comments: