Bug 72661 - Helper classes for AbstractTextSearchViewPage should be API
Summary: Helper classes for AbstractTextSearchViewPage should be API
Status: ASSIGNED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Search (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform-Search-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: api
Depends on:
Blocks:
 
Reported: 2004-08-26 04:44 EDT by Markus Keller CLA
Modified: 2019-09-06 16:13 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Markus Keller CLA 2004-08-26 04:44:46 EDT
Implementors of AbstractTextSearchResult have to implement
elementsChanged(Object[] objects). The element changes must be reflected in the
search result viewer. This functionality is currently internal, but should be
abstracted into API classes to avoid code duplication.

The API classes should provide the necessary implementation for displaying
AbstractTextSearchResults (leaving domain specific methods abstract).

TextSearchTableContentProvider, JavaSearchContentProvider, FileContentProvider,
and their subclasses should be structured like this:

TextSearchContentProvider
    (new; out of JavaSearchContentProvider, FileContentProvider)
+ TextSearchTableContentProvider
      (new; out of existing TextSearchTableCP, JavaSearchTableCP, FileTableCP)
+ TextSearchTreeContentProvider
      (new; out of FileTreeContentProvider, LevelTreeContentProvider)
Comment 1 Markus Keller CLA 2004-08-26 04:48:15 EDT
Oops, I meant:
"Implementors of *AbstractTextSearchViewPage* ..."
Comment 2 Eclipse Webmaster CLA 2019-09-06 16:13:46 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.