Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 356618 - Consider revamping the 'Scripts' node.
Summary: Consider revamping the 'Scripts' node.
Status: NEW
Alias: None
Product: JSDT
Classification: WebTools
Component: Debug (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: Future   Edit
Assignee: Project Inbox CLA
QA Contact: Michael Rennie CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-09-02 11:42 EDT by Michael Rennie CLA
Modified: 2012-03-01 14:12 EST (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Rennie CLA 2011-09-02 11:42:39 EDT 
Currently the 'Scripts' node falls below the debug target for any one given launch, which is ok in the single context (thread) debug scenario, but as soon as you start working with multiple contexts, is is almost impossible to sort out what script belongs to what context (thread).

Perhaps we should look at a different solution:

1. we could could have a 'Scripts' node per context (thread)
2. we could re-organize the 'Scripts' node (somehow)