Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "CDT/Obsolete/ScannerDiscovery61/Design"
< CDT | Obsolete | ScannerDiscovery61
(→Diagrams) |
(→Diagram) |
||
Line 2: | Line 2: | ||
AG: I think that this (initial) design possibly can satisfy the [[CDT/ScannerDiscovery61/UseCases | use cases]]. This does not map well into existing scanner discovery complexity. Somebody educate me on what my model is missing! | AG: I think that this (initial) design possibly can satisfy the [[CDT/ScannerDiscovery61/UseCases | use cases]]. This does not map well into existing scanner discovery complexity. Somebody educate me on what my model is missing! | ||
[[Image:ScannerDiscoveryClassDiagram.png]] | [[Image:ScannerDiscoveryClassDiagram.png]] | ||
+ | |||
+ | === Extension Point === | ||
+ | For example like that: | ||
+ | [[Image:LanguageSettingsContributor.png]] | ||
=== Screenshot === | === Screenshot === |
Revision as of 13:36, 26 October 2009
Contents
Diagram
AG: I think that this (initial) design possibly can satisfy the use cases. This does not map well into existing scanner discovery complexity. Somebody educate me on what my model is missing!
Extension Point
Screenshot
AG: This is how project properties settings scanner discovery tab might've looked. The page is possibly too overloaded though.
Data
AG: Here is how the data supporting this design might've been saved in .cpoject: