Remote Systems
v6.4.1

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

Interface Summary
ISystemFilterWizard  
ISystemNewFilterWizardConfigurator Much of the new filter wizard is configurable, especially with respect to translated strings.
SystemFilterNewFilterPoolWizardMainPageInterface Interface for new Filter wizard main page classes
SystemFilterPoolWizardInterface An interface for filter pool wizards to implement
 

Class Summary
SystemChangeFilterDialog A dialog that allows the user to change a filter.
SystemFilterNewFilterPoolWizard Wizard for creating a new system filter pool.
SystemFilterNewFilterPoolWizardDefaultMainPage Default main page of the "New Filter Pool" wizard.
SystemFilterPoolWizardDialog Extends WizardDialog to support ability to pass data in from the common wizard action class, and get data out.
SystemFilterWizardDialog Extends WizardDialog to support ability to pass data in from the common wizard action class, and get data out.
SystemFilterWorkWithFilterPoolsDialog Dialog for working with filter pools.
SystemNewFilterWizard Base Wizard for users to define a new system filter.
SystemNewFilterWizardConfigurator Much of the new filter wizard is configurable, especially with respect to translated strings.
SystemNewFilterWizardInfoPage Third page of the New Filter wizard that simply shows information
SystemNewFilterWizardMainPage Main page of the abstract "New Filter" wizard.
SystemNewFilterWizardNamePage Second page of the New Filter wizard that prompts for the name of the filter.
SystemUnNamedFilterDialog A dialog that prompts the user for a single filter string, but not for the purpose of creating a named filter.
 


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.