This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 98954 - Linked javascripts snipets are not included to the javascript parser
Summary: Linked javascripts snipets are not included to the javascript parser
Status: NEW
Alias: None
Product: obsolete
Classification: Unclassified
Component: languages (show other bugs)
Version: 6.x
Hardware: All All
: P1 blocker (vote)
Assignee: issues@obsolete
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-03-26 12:27 UTC by Lukasz Grela
Modified: 2009-03-25 15:39 UTC (History)
2 users (show)

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Lukasz Grela 2007-03-26 12:27:58 UTC
Refers to embeded js.
such instruction <script src="newJavaScriptMethod.js"> should afect on cc list,
add all java object to cc list( In inteliJ by default all js objects from pure
js files are available in cc for all html files).
Comment 1 Lukasz Grela 2007-03-27 12:15:00 UTC
changing status whiteboard
Comment 2 Marek Fukala 2007-03-30 12:53:08 UTC
The problem is now that Schliemann doesn't provide any API which I could use to
specify what external sources should be included into the parser input. 

It could be solved by a special callback from NBS file, something like

AST {
    library:org.netbeans.modules.html.editor.HTML.processLibraries;
}

the code would get the root ASTNode and would parse the linked files and add
their ASTNodes into the AST tree of the edited file.

Or, it would be probably enought just to provide list of included files by an
SPI so the client would implement something like this:

public interface LibraryQuery {
    public String[] getLibraryNames();
}

and S. would parse them together with the edited document.

Reassigning to languages/engine.
Comment 3 Jan Jancura 2007-03-30 14:21:53 UTC
Yes. Context for CC (and all other features) is current file.
=> Feature
We are thinking about this feature for nb6.0...