Remote Systems
v6.4.1

Package com.ibm.etools.systems.filters.ui

Interface Summary
ISystemChangeFilterPaneEditPaneSupplier The SystemChangeFilterPane class is used in both SystemChangeFilterDialog and in SystemChangeFilterPropertyPage.
ISystemFilterStringEditPaneListener This listener interface is implemented by any code desired to be kept aware of all user changes to a filter string in the SystemFilterStringEditPane.
SystemFilterDialogInterface Common interface for dialogs or wizards that work with filters.
SystemFilterPoolDialogInterface Common interface for dialogs or wizards that work with filter pools.
SystemFilterPoolManagerUIProvider  
 

Class Summary
SystemChangeFilterPane Since we have decided to allow the same editing in both the Change Filter dialog and the Properties page, we have to abstract the meat of the change filter dialog into a re-usable composite.
SystemFilterDialogInputs A class capturing the attributes commonly needed by dialogs that work with filters.
SystemFilterDialogOutputs A class capturing the attributes commonly returned by dialogs that work with filters.
SystemFilterPoolDialogInputs A class capturing the attributes commonly needed by dialogs that work with filter pools.
SystemFilterPoolDialogOutputs A class capturing the attributes commonly returned by dialogs that work with filter pools.
SystemFilterStringEditPane This class prompts the user to create or edit the contents of a single filter string.
SystemFilterUIHelpers  
SystemFilterWorkWithFilterPoolsTreeViewer This subclass of the standard JFace tree viewer is used to show a tree view of filter pools within filterpool managers, for a work-with experience.
 


Remote Systems
v6.4.1

Copyright © 2005 IBM Corp. All Rights Reserved.

Note: This documentation is for part of an interim API that is still under development and expected to change significantly before reaching stability. It is being made available at this early stage to solicit feedback from pioneering adopters on the understanding that any code that uses this API will almost certainly be broken (repeatedly) as the API evolves.