| Summary: | Provide a "Run" mode for the launcher | ||
|---|---|---|---|
| Product: | [WebTools] JSDT | Reporter: | Nitin Dahyabhai <thatnitind> |
| Component: | Debug | Assignee: | Project Inbox <jsdt.debug-inbox> |
| Status: | NEW --- | QA Contact: | Michael Rennie <Michael_Rennie> |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | curtis.windatt.public, grant_gayed, thatnitind |
| Version: | 3.3 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
Nitin Dahyabhai
(In reply to comment #0) > A user without knowledge of the underpinnings might not understand why you can > only Debug JavaScript and not Run it. Would it be possible to allow for > scripts to just be Run? Sure, we could have run support. This would be a good chance to implement a system for managing browsers / runtimes that can be used to run or debug JavaScript. Off the top of my head, I envision something like the installed JREs page from JDT, except in this case it would be installed browsers and runtimes. Is that already covered by the Debug mode, or can we scope it down and have something for Juno? (In reply to comment #2) > Is that already covered by the Debug mode, or can we scope it down and have > something for Juno? This is not covered by the debug impls, we would have to add run support separately. |