Bug 144663 - [Viewers] Information Infrastructure for Viewers
Summary: [Viewers] Information Infrastructure for Viewers
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.2   Edit
Hardware: PC All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-05-31 09:38 EDT by Thomas Schindl CLA
Modified: 2019-09-06 16:18 EDT (History)
0 users

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 Thomas Schindl CLA 2006-05-31 09:38:26 EDT 
At the moment the viewer doesn't inform users about structural changes:
- viewer#add()
- viewer#remove()
- viewer#refresh()
...

Wouldn't it be possible to add something like PropertyChange support to the viewer which informs the user about those events?
Comment 1 Boris Bokowski CLA 2006-05-31 13:37:27 EDT 
Do you have use cases where this support would help?
Comment 2 Thomas Schindl CLA 2006-05-31 13:44:35 EDT 
Yeah. One of them has been questioned on the newsgroup e.g. if you want to recheck all checkboxes when you refresh the table.
 
But there are much more e.g. if you have two completely seperate components and one of them wants to be notified if the model is refreshed, an item is added to the viewer, or it wants to veto against a add/refresh/remove operation, ... .

I know that you could also solve those problems by e.g. sub-classing but that's not really nice.

(In reply to comment #1)
> Do you have use cases where this support would help?
>
Comment 3 Boris Bokowski CLA 2009-11-26 09:47:26 EST 
Hitesh is now responsible for watching bugs in the [Viewers] component area.
Comment 4 Eclipse Webmaster CLA 2019-09-06 16:18:37 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.