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 128383 - Ability to test .js files in browser
Summary: Ability to test .js files in browser
Status: NEW
Alias: None
Product: javascript
Classification: Unclassified
Component: Editor (show other bugs)
Version: 6.x
Hardware: All All
: P2 blocker (vote)
Assignee: Petr Pisl
Depends on:
Reported: 2008-02-26 00:45 UTC by _ tboudreau
Modified: 2014-01-16 10:30 UTC (History)
0 users

See Also:
Exception Reporter:


Note You need to log in before you can comment on or make changes to this bug.
Description _ tboudreau 2008-02-26 00:45:43 UTC
If we are targetting JavaScript developers, one thing they will often need to do is test code in a browser.  It might be useful to be able to generate some 
dummy HTML that invokes the script (there are some common patterns, and probably finding something that calls Document.write() is a clue, but we can 
always generate a skeleton and ask the user).

I would imagine particularly in the case of JSPs and similar which embed Javascript this would be useful, as the user probably does not want to redeploy a web 
app to test changes.
Comment 1 Torbjorn Norbye 2008-02-26 01:12:52 UTC
This feature will have to be done by each project type, as it depends a lot upon the surrounding project context I
think. E.g. hook the Shift-F6 action up to something useful for JavaScript files. (For Ruby on Rails projects, we
already do similar things based on the filetype -- e.g. for rakefiles run rake, for migration files run db:migrate rake
targets, for tests execute the test runner, for controllers and views compute the relevant URL and show the browser on
that URL).

For Javascript perhaps a simple start is locating some file in the project that includes the JavaScript and showing that
file's url (generating a preview if necesary; e.g. in Creator we had Preview In Browser for certain types of JSP files.)