Bug 256824 - Improve feedback mechanisms in e4
Summary: Improve feedback mechanisms in e4
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.0   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-11-27 13:37 EST by Eric Moffatt CLA
Modified: 2019-09-06 15:35 EDT (History)
5 users (show)

See Also:


Attachments
OpenGL Investigation (186.29 KB, application/x-zip-compressed)
2008-11-28 15:00 EST, Matthew Bisson CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Eric Moffatt CLA 2008-11-27 13:37:15 EST
e4 is supposed to be 'new'. One of the ways we can accomplish this is through more refined feedback mechanisms (something better that our current blacks boxes).

This defect is to capture input on what techniques we could use and when/where we should consider using them. Matt Bisson has been looking at OpenGL and will post his results here but anyone is welcome to chime in on what they think would be 'cool' (as well as useful...;-).
Comment 1 Eric Moffatt CLA 2008-11-27 13:42:55 EST
Kevin, you might want to pass this around to some of the UI folks you've gathered up during your CSS/Declarative UI threads.

I'd like to make the saying "So cool you'll drool" a reality...
Comment 2 Krzysztof Daniel CLA 2008-11-28 04:57:22 EST
maybe e4 is a good place for bug 249649 attachment 1 [details]?
Comment 3 Matthew Bisson CLA 2008-11-28 15:00:36 EST
Created attachment 119043 [details]
OpenGL Investigation

Here's all the work I've done with OpenGL. The readme.txt file in the root of the project has project-setup settings, and summarizes all the work done, as organized in the java files. The files themselves, where appropriate, explain shortcomings, etc.
Comment 4 Eclipse Webmaster CLA 2019-09-06 15:35:33 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.