Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "EMF Compare/Specifications/DefaultMatchEngineConfiguration"
(→Detailed Specification) |
(→Detailed Specification) |
||
Line 33: | Line 33: | ||
Solution 1: | Solution 1: | ||
+ | [[File:DefaultMatchEngineNotSelectedSol1.png]] | ||
Solution 2: | Solution 2: | ||
+ | |||
+ | [[File:DefaultMatchEngineNotSelectedSol2.png]] |
Revision as of 12:51, 18 February 2014
Contents
Evolution Specification: UI configuration of DefaultMatchEngine
Current status is DRAFT
Preamble
Summary: Define the way user shall can configure Default Match Engine.
_Relevant tickets_
Introduction
Default Match Engine can be configured with one parameter: UseIdentifiers which define if whether or not IDs shall be used.
Detailed Specification
To configure this the system shall provide an User Interface. The user shall be able to use this interface to modify at runtime the UseIdentifier parameter. The way the interface is provided shall be generic to be reusable for other match IMatchEngine.
In the case of the DefaultMatchEngine the interface shall look like this.
When the DefaultMatchEnfineFactory is selected:
When the another MatchEngine is selected (with no configuration):
Solution 1:
Solution 2: