Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 369161 - Proposed UI change for built-in scenario (from previous STEM bug 250135)
Summary: Proposed UI change for built-in scenario (from previous STEM bug 250135)
Status: CLOSED WONTFIX
Alias: None
Product: STEM
Classification: Technology
Component: UI (show other bugs)
Version: 1.3.0   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: 1.3.1   Edit
Assignee: James Kaufman CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-01-19 18:35 EST by Stefan Edlund CLA
Modified: 2012-05-04 12:55 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Stefan Edlund CLA 2012-01-19 18:35:58 EST
250135: This needs discussion.....

Proposed UI change for Built in Scenarios    
    To make the ui more user friendly we could
    1) Eliminate completely the separate view which shows the built in
Scenarios/graphs/models etc
    and instead
    2) Add to the project explorer a default build in project (perhaps called
STEM library) that     contains all the built in graphs and scenarios....

    The advantage to this is the user only will have to learn one single user
interface.
Comment 1 James Kaufman CLA 2012-01-26 11:06:21 EST
Let's discuss this on the weekly call and STEM-DEV too. I like the idea :-)
Comment 2 Stefan Edlund CLA 2012-05-04 12:44:51 EDT
This bug was copied over from 250135 suggested by you Jamie back in 2008. Personally I think keeping the build in objects in separate views the way it is today much more flexible. As an example, if all built in models are in a project folder, you need to scroll down to get to what you need. Then you need to scroll back up again to drag it into your models folder to make a copy. I think we can close this bug.
Comment 3 James Kaufman CLA 2012-05-04 12:53:54 EDT
reassign to jk
Comment 4 James Kaufman CLA 2012-05-04 12:55:01 EDT
This is an old request. Instead we are adding help to the library folders below. They should not be moved to the project explorer but instead we need to make it clearer that they are libraries....
Comment 5 Matthew Davis CLA 2012-05-04 12:55:16 EDT
I agree, although I have a slightly different suggestion for the use of the "Scenarios" view that might be useful.

I find running launching scenarios to be somewhat cumbersome, especially after restarts - having to navigate through the project explorer, expanding trees, etc.  It might be useful to have - in addition to the built-in scenarios - a condensed list of *all* scenarios in the workspace, easily accessible/launchable from the Scenarios view.  They could be top-level items above the built-in scenarios in the tree.  Shouldn't be too difficult to implement if others think this would be useful.