Bug 489121 - Consider removal of JSDT package/script explorer
Summary: Consider removal of JSDT package/script explorer
Status: NEW
Alias: None
Product: JSDT
Classification: WebTools
Component: General (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact: Victor Rubezhny CLA
URL:
Whiteboard:
Keywords: usability
Depends on:
Blocks:
 
Reported: 2016-03-07 04:55 EST by Mickael Istria CLA
Modified: 2018-11-22 17:32 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 Mickael Istria CLA 2016-03-07 04:55:25 EST 
As a clone of JDT, JSDT comes with a Package Explorer, rebranded as "Script Explorer". The default perspective does prefer the generic "Project Explorer", and it doesn't seem obvious that this "Script Explorer" has any benefit over "Project Explorer".
Since JSDT is currently moving to a 2.0, wouldn't it be useful to get rid of this "Script Explorer" view?
Comment 1 Eclipse Genie CLA 2016-03-07 05:21:10 EST 
New Gerrit change created: https://git.eclipse.org/r/67887
Comment 2 Gorkem Ercan CLA 2016-03-07 14:03:48 EST 
+1 
We still should check if we are loosing any functionality
Comment 3 Nitin Dahyabhai CLA 2016-03-07 14:55:13 EST 
-1

There would be a definite loss of a JS-centric viewpoint when one first opens JSDT's own perspective. While you can configure the contents of the Project Explorer view, that configuration is common across all perspectives.
Comment 4 Mickael Istria CLA 2016-03-07 15:01:16 EST 
(In reply to Nitin Dahyabhai from comment #3)
> There would be a definite loss of a JS-centric viewpoint when one first
> opens JSDT's own perspective. While you can configure the contents of the
> Project Explorer view, that configuration is common across all perspectives.

Is it an actual use-case you've used/seen? My impression is that the multiplicity of views doing very similar things costs effort for not much value, and actually drive users to an impression of mess/inconsistency/excess of choice/lack of guidance.
Comment 5 Gautier de SAINT MARTIN LACAZE CLA 2016-03-08 19:15:29 EST 
As a user of Eclipse for Java and JavaScript, I prefer to use the Project Explorer. 
In fact because I have Java and JavaScript in the same projects, I use the Java Perspective with Project Explorer View.
Comment 6 Gorkem Ercan CLA 2016-03-17 14:44:39 EDT 
I think the preferences on JavaScript>Appearance is broken for Package Explorer and somewhat works for Script Explorer.
Comment 7 Mickael Istria CLA 2017-12-15 04:48:26 EST 
@Nitin: what's the delta between rendering of a JS project in Project Explorer and JSDT's Package Explorer?
Comment 8 Nitin Dahyabhai CLA 2018-01-23 02:21:58 EST 
(In reply to Mickael Istria from comment #7)
> @Nitin: what's the delta between rendering of a JS project in Project
> Explorer and JSDT's Package Explorer?

As small as possible. The difference is that the Script Explorer starts with a narrow focus on the workspace aimed at the perspective of a JavaScript developer, rather than burying its contents amid every other content providers'.