Bugzilla – Full Text Bug Listing
| Summary: | Swing: SwingScoutRootFrame should adhere Java LAF | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Adrian Moser <trekking09> |
| Component: | Scout | Assignee: | Claudio Guglielmo <claudio.guglielmo> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | claudio.guglielmo, daniel.wiehl, zimmermann |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
Adrian Moser
to be verified for indigo sr1 scheduled for scout juno release Problem: There is no distinct separation among the different Look And Feels. In practice, if using a L&F other than Rayo or Orson, some widgets (e.g. the header panel) partly look like Rayo, but not like the installed L&F. Solution: Scout should completely adhere the installed L&F. To solve this ticket, some major changes where necessary to the SwingScoutRootFrame, SwingScoutToolBar and its attached controls. Also, all Scout specific icons are moved from the org.eclipse.scout.rt.client Plug-In to the respective UI / L&F Plug-Ins to conform the UI. Changes: - Generally, icons in Scout are strongly referenced by their icon identifier defined in SwingIcons#XX, SwtIcons#XX, RwtIcons#XX or AbtractIcons#XX. - Icons are moved from org.eclipse.scout.rt.client to the respective UI Plug-Ins. The Swing and SWT Plug-In only contain OpenSource specific icons whereas L&F fragments L&F specific ones. - org.eclipse.scout.rt.ui.swing does not contain any Rayo / Orson specific UI definitions anymore. Those are outsourced to the respective L&F Plugins. - ISwingEnvironment is extended to install a custom NavigationWidgetPanel, ViewTabsBar and ToolTabsBar specific to the L&F. The default implementation does not draw these elements anymore, but uses native controls instead. - Added extension point *.scouticons to every UI Plug-in to easily replace Scout default icons like window, tray or navigation icons. - Scout icons which cannot be configured in application (by respective getConfigured method) are fetched by the UI Activator, not the environemnt anymore. Now, Swing and SWT behave the same way. Those icons can be replaced by the *.scouticons extension point. - Rayo and Orson have a different JTextWithFieldTransparentIcon to meet L&F specific requirements. - Rayo and Orson have a different DateField / TimeField to meet L&F specific requirements. - Rayo and Orson have a different ActionInjection / UIDefaultsInjector to meet L&F specific requirements. - Moved and renamed legacy UI classes to org.eclipse.scout.rt.ui.swing.orson as they only belong to Orson L&F. - added icons for Orson L&F to org.eclipse.scout.rt.ui.swing.laf.orson.fragment - added icons for Orson L&F to org.eclipse.scout.rt.ui.swing.laf.rayo.fragment - created Plug-In org.eclipse.scout.rt.ui.swing.orson to meet Orson specific requirements such as actions, formfields and Swing environment. Migration: - Icons as CheckboxYes and CheckboxNo were removed from AbstractIcons. If required, add them to your project specific icons in your client Plug-In. - Product specific icons were removed from Scout UI Plug-Ins and must be installed in project yourself. Thereto, copy icons attached to this mail (window16.png, window32.png, window48.png, window256.png, tray.gif) into your Swing Plugin, e.g. /resources/icons. If folder does not exist yet, create it and register it in build.properties to be exported for production. Open plugin.xml of Swing Plug-In and register those icons in extension org.eclipse.scout.rt.ui.swing.scouticons. - Names of some icons in AbstractIcons were changed to gain consistency in naming: e.g. AbstractIcons.TimeFieldTime -> AbstractIcons.DateFieldTime, AbstractIcons.File -> AbstractIcons.FileChooserFieldFile Fix verified. The root frame now looks well for the different Look&Feels (scout 3.8.0). ticket closed. deliverd as part of eclipse scout 3.8.0 (juno release train) |