Community
Participate
Working Groups
A couple things have changed in the Europa and Ganymede cycle that I think would be useful to percolate to the Java EE perspective in the next release cycle. * Mylyn has been included, and the Task List view is part of the default perspective in the Java distribution * Platform provides a Markers view that captures both Problems and Tasks In addition, the hope is that we get to rename the Mylyn's "Task List" view to "Tasks" in the next release train (history for this is on bug 176986), and we hope to resolve the name clash between "Task markers" and Mylyn's "Tasks". I'll post a screenshot of a suggested perspective layout.
Created attachment 105750 [details] suggested layout
Chuck, Giving this to you for initial input/review. (I am assuming that such a UI change would have to wait until WTP 3.1.)
Bringing to the 3.1 plan.
Kaloyan: do you want a patch?
Yes, please. A patch is welcome. Can you point me to documentation about this Markers view? I am interested about customization capabilities.
Sounds good, I'll plan to provide this patch in the first half of the Galileo cycle. Just let me know if you need it sooner. Regarding the new Markers support, I haven't come across any documentation, but you can explore the UI by opening the Markers view, and explore the API through the code or at: http://help.eclipse.org/stable/nftopic/org.eclipse.platform.doc.isv/reference/api/org/eclipse/ui/views/markers/package-summary.html As you suggest, it could be useful for WTP because it allows the user to put all of the markers relevant to them in a single view. then Mylyn can do things like focusing that view to show only the markers relevant to the active task, helping with the marker overload problem.
Created attachment 112945 [details] suggested layout v2 I attach a suggestion for new layout that extends the one already provided by Mik. The new thing is that I have moved the docking of the Servers view from the bottom side to the left-bottom side - just below the Project Explorer view. My motivation for this change is that whenever the user invokes server operations like start, stop or publish and the server instance dumps something in the system output stream, then the Console view inevitably pops up with bottom docking. This switches the focus from the Servers tab to the Console tab, the user loses the Servers view and is forced to see lots of rapidly changing logs - the "matrix" feeling. By moving the Servers view on the left, we will still have it shown even after the Console view pops up. This way the user can have all the information he would want to see - either the nice looking status in the Servers view or the more comprehensive output in the Console view. Another benefit of having the Servers view on the left below the Project Explorer view is that we have the two views in the Java EE perspective that deal with projects on one and the same side. This looks much more natural and also enables better drag-and-drop experience for the user. There is one small drawback. Docking on the left side allows smaller horizontal space for views. This means that the Servers view needs to be optimized for such orientation. The very minimum would be that the default width of the columns is adapted. Opinions?
Hi Kaloyan, Thanks for cc'ing me. I appreciate the new layout and work being done here, but I think we need to take a look at the Servers view offline (i.e. via a separate bug or investigation) before we move it into a vertical orientation. This view has always been in a wide horizontal space, and in any normal usage the server name and status will be much too long to fit in the small columns that would be available here. If we need a view that would fit here we can discuss, but I don't think it should be part of (or hold up) this perspective reorg.
I agree, Tim. I have created bug 247934 to discuss the possible optimization in the Servers view.
Created attachment 113030 [details] alternative layout First of all, I think it would make a good discussion topic for UI working group. You may get lots of great ideas from such discussion. As for the Servers view location, you need to consider the developer's workflow around information provided from that view. It is unclear if developer actually need to see Servers view all the time and if that is the case, maybe it is better to have Servers view in a "Fast View" mode. Also, I think it would be a big mistake to bring Task List view into a visibility like shown on proposed screenshots. Usually developer don't need to see all tasks after activating some specific one and while working on an active task. Also, it is quite noticeable on attached screenshots, as well as from several Mylyn webinars and screencasts, that with Task List view on the right there is really not enough screen real estate left for the editor in a middle. Given those issues, it seem to make more sense to have Task List view to share a docking spot with some other view, e.g. Project Explorer. For example, see an alternative layout in the attached screenshot. Though that bring up an issue with Mylyn's present UI, that does not allow to see or switch currently active task without bringing the whole Task List view into a visibility. It would be great if Mylyn team could somehow address that.
I might be in the minority on this, but I find that most Eclipse perspectives are far too cluttered to be useful in practice. They are awesome at showcasing all the views, but most people don't have monitors to allow so many views to be shown concurrently. I have a 20" monitor and yet the first thing I do on Java and Java EE perspectives is move the outline view to share space with package explorer and minimize the lower views (problems, servers, console, etc). That allows me to flip between navigating across files and navigating in a file with a quick tab switch while reserving most of the real estate for the source view. The problems and servers views aren't interesting when you are busy writing code and when they are needed, they can slide out at a touch of a button. So how about we put Package Explorer, Outline and Mylyn tasks on the left (sharing the same space), leave the problems and servers on the bottom, and put nothing on the RHS? Regarding Mylyn Tasks view specifically, would referencing the Mylyn view from the Java EE perspective force WTP to take a dependency on Mylyn or can this be done gracefully so that the view is there if Mylyn is present in the install, but WTP and it's perspectives can work without Mylyn?
Created attachment 113238 [details] suggested layout v3 It's nice to have lots of different opinions. I like the Konstantin's idea for simplicity and Eugene's the concept of having rarely used views as fast views. However, I would prefer using "minimized" views instead of "fast" views. For me they looked pretty similar, but "minimized" views have some benefits like: - they (the whole set of views) can be easily unminimized when needed - they are still group by docking side I attach another screenshot. Features: - we have only the Project Explorer and Task List views open by default on LHS sharing the same space. All other views are minimized. - on RHS we have Outline and Snippets minimized. The Snippets view naturally seems to have vertical orientation, so there is no sense to have it at the bottom. Both views deal with the code - now they share one and the same space. - on bottom LHS we have Servers and Data Source Explorer minimized. Both views deal with external resources (servers and DBs), so let them share one and the same space. I still like the idea of having the Servers view and the Console view on different places. - on the bottom side we have all the rest (Markers, Properties, Console, etc.) minimized.
(In reply to comment #10) > First of all, I think it would make a good discussion topic for UI working > group. You may get lots of great ideas from such discussion. I agree. I will try to reserve the Oct 15th slot. (In reply to comment #11) > Regarding Mylyn Tasks view specifically, would referencing the Mylyn view from > the Java EE perspective force WTP to take a dependency on Mylyn or can this be > done gracefully so that the view is there if Mylyn is present in the install, > but WTP and it's perspectives can work without Mylyn? No dependency to Mylyn. There will be a check if the Task List view exists (by ID string).
(In reply to comment #12) I agree with Konstantin's comments that most perspectives are too cluttered, but I think this is too far the other way - seems like it's almost optimized for very low resolution. Having the views out makes them easier to get to, and more importantly easier to find for new users. I'd rather see the frequently used views displayed by default, since users can close/fastview/minimize them once they've seen what's available. Less frequently used views can be minimized or not included at all. FWIW, I only have a 15" screen on my laptop, but I leave the Java perspective close to the defaults. (well, do I drop the font size down one point in all text editors :) )
It has just been confirmed that we will have an UI walk-through on the Java EE perspective tomorrow, Oct 15. Please, feel yourselves invited! Check this page for connection details: http://wiki.eclipse.org/User_Interface_Best_Practices_Working_Group#Meetings I will post the link to the webex session 15 minutes before the meeting.
Webex info: ------------------------------------------------------- To join the online meeting ------------------------------------------------------- 1. Go to https://sap.webex.com/sap/e.php?AT=MI&EventID=94734252 2. Enter your name and email address. 3. Enter the meeting password: eclipseui 4. Click "Join". 5. Follow the instructions that appear on your screen. ------------------------------------------------------- To join the teleconference only ------------------------------------------------------- 866.362.7064 x 892048 See this wiki page for quick preparation: http://wiki.eclipse.org/JavaEE_Perspective_UIWG_Walkthrough There are some screenshot available, too: http://wiki.eclipse.org/UI_Walkthrough_JavaEE_Perspective
Kaloyan: As promised during the UI review, here are the some stats about perspective and view usage: * http://www.tasktop.com/resources/technology/ "How are Java software developers using the Eclipse IDE" * http://www.eclipse.org/org/usagedata/results.php?kind=view&sort=use UI Usage Collector stats
Created attachment 115278 [details] layout for Galileo M3 There was a good attendance on the UI walkthrough and a very valuable feedback. You can see the minutes here: http://wiki.eclipse.org/JavaEE_Perspective_UIWG_Walkthrough In short: we have decided to make the improvements in the Java EE perspective in small steps. For M3: * Replace the Problems and Tasks view with the Markers view. * Introduce the Mylyn's Task List view stacked together with the Outline view. See the attached screenshot.
Created attachment 115921 [details] Patch
Committed to HEAD and released to build. Bug 251195 is already fixed in the Platform, but the I-build is not yet adopted in the WTP build.
