|
|
| Line 1: |
Line 1: |
| − | {{ScoutPage|cat=Concepts}}
| + | #REDIRECT [[Scout/Concepts/Client_Plug-In#Separation_of_UI_and_GUI]] |
| − | | + | |
| − | Eclipse Scout uses its own component model for the client. This model is do not rely on any UI library. Rendering the GUI using a UI library is part of the framework. A Swing and a SWT GUI implementation are provided.
| + | |
| − | | + | |
| − | | + | |
| − | ==Overview==
| + | |
| − | | + | |
| − | [[Image:Scout gui representation.png]] | + | |
| − | | + | |
| − | This represents how the UI and the GUI of Eclipse Scout and your application based on Eclipse Scout work together. On the left there is the plugin org.eclipse.scout.rt.client (UI) and the plugin org.eclipse.scout.rt.ui.swt (GUI). The UI plugin does not have any dependency to the GUI plugin so that it stays independent. On the right side there are the counterparts of the scout plugins which form your applications client.
| + | |
| − | | + | |
| − | | + | |
| − | ==Example==
| + | |
| − | | + | |
| − | The same application rendered with SWT and Swing
| + | |
| − | | + | |
| − | <gallery>
| + | |
| − | Image:Scout_app_gallery_swt.jpg|SWT GUI
| + | |
| − | Image:Scout_app_gallery_swing.jpg|SWING GUI (Nimbus Look and Feel)
| + | |
| − | </gallery>
| + | |
| − | | + | |
| − | | + | |
| − | ==See also==
| + | |
| − | | + | |
| − | * {{ScoutLink|Concepts|UI Plug-Ins|UI Plug-Ins}}
| + | |
| − | * {{ScoutLink|Concepts|Client Plug-In|Client Plug-In}}
| + | |
