Community
Participate
Working Groups
While we currently use the suffix .ui to depict SWT, JFace, as well as Eclipse Workbench UI dependencies, it could make sense to differentiate this on a more fine-grained level. E.g., Cloudio.UI and Zest.UI contain JFace-related parts that do not depend on the Eclipse Workbench UI. It would IMHO make sense to factor out these parts into own bundles, using the following naming conventions: - .swt where only SWT-dependencies exist - .jface where SWT-/JFace-dependencies exist - .ui where SWT-/JFace-/UI-dependencies exist Actually, the GEF4 Geometry.Convert.SWT already uses this convention (and violates our current naming conventions, because it uses SWT instead of UI).
Factoring out SWT-/JFace-related parts could make sense for Cloudio (bug #468707) and Zest (bug #470636). FX.UI should be renamed to FX.SWT if applying the new conventions.
(In reply to Alexander Nyßen from comment #1) > Factoring out SWT-/JFace-related parts could make sense for Cloudio (bug > #468707) and Zest (bug #470636). > > FX.UI should be renamed to FX.SWT if applying the new conventions. If we move the cell editor, color pickers, and dialogs from MVC.FX.UI to FX.UI (as outlined in bug #471154), the FX.UI bundle should keep its name or be split into FX.SWT and FX.JFace accordingly.
Completed the splitting of FX.UI into FX.SWT and FX.JFace as part of bug #471154. What remains is the refactoring of Zest.FX.UI and Cloudio.UI. After these have been completed, the overview diagram in the wiki doc needs to be adjusted.
Updated wiki documentation of FX and MVC bundles accordingly. Resolving as fixed in 3.11.0 M2.