Community
Participate
Working Groups
Created attachment 133966 [details] screenshot See the attached screenshot. The WebContent folder of the Dynamic Web Project is decorated with the JavaScript decorator. The project structure has also the "JavaScript Resources" library node. The projects on the screenshot do not have the JavaScript Toolkit facet installed.
Are you sure the facet or nature is not installed? Also, the WebContent folder is now a JavaScript source folder by default so that its contents are properly indexed. We're still looking at the common navigator contributions with an eye on how to properly represent all of this to the user.
Categorizing JSDT bugzillas for planning purposes.
Renaming the bug to better reflect plan: 1) Deprecate/hide Script Explorer in favor of the Project Explorer by default. 2) Stop interfering with the display of non-JS files. Never interfere with the display of folders. 3) Make JS files on our include path optionally expandable to show their structure 4) Remove the flat/hierarchical layout offering from JSDT. 5) Reorganize the contents of the "JavaScript Resources" node in a similar manner to what's been done for "Java Resources". 6) Correct status line labels when a JS element is selected, e.g. a verbose Library "description" should not precede the element's identifier.
Created attachment 161534 [details] Not a complete solution, but a good start. This patch does the following: 1. Sets WebContent as a source by default 2. Sets the default view in JavaScript Perspective to be the Project Explorer. 3. Removes the UI associated with source folders and packages. The JavaScript Resources node remains.
*** Bug 248779 has been marked as a duplicate of this bug. ***
Sounds like more than "clean up" ... all important. Thanks.
Fixed, except item 4 was made to work, and for item 6, which is still a problem and typified by bug 285758 and deferred to 3.3.
Closing. 1) Deprecate/hide Script Explorer in favor of the Project Explorer by default. Done. 2) Stop interfering with the display of non-JS files. Never interfere with the display of folders. Done. 3) Make JS files on our include path optionally expandable to show their structure Done. 4) Remove the flat/hierarchical layout offering from JSDT. Reimplemented "hierarchical" layout as "Groups". 5) Reorganize the contents of the "JavaScript Resources" node in a similar manner to what's been done for "Java Resources". Source entries from the project Include Path now visible. 6) Correct status line labels when a JS element is selected, e.g. a verbose Library "description" should not precede the element's identifier. Deferred to bug 285758.
