tree: 78f2ddd29917e49f41c341ad6e9ff215769b9ea5 [path history] [tgz]
  1. .classpath_cocoa
  2. .classpath_gtk
  3. .classpath_gtk_win32
  4. .classpath_win32
  5. .externalToolBuilders/
  6. .gitignore
  7. .project
  8. .settings/
  9. Eclipse SWT AWT/
  10. Eclipse SWT Accessibility/
  11. Eclipse SWT Browser/
  12. Eclipse SWT Custom Widgets/
  13. Eclipse SWT Drag and Drop/
  14. Eclipse SWT OLE Win32/
  15. Eclipse SWT OpenGL/
  16. Eclipse SWT PI/
  17. Eclipse SWT Printing/
  18. Eclipse SWT Program/
  19. Eclipse SWT WebKit/
  20. Eclipse SWT/
  21. META-INF/
  22. Readme.Linux.md
  23. Readme.Win32.md
  24. Readme.macOS.md
  25. Readme.md
  26. about.html
  27. about_files/
  28. build.properties
  29. build.xml
  30. build/
  31. buildFragment.xml
  32. buildInternal.xml
  33. buildSWT.xml
  34. plugin.properties
  35. pom.xml
  36. tasks/
bundles/org.eclipse.swt/Readme.md

org.eclipse.swt

Main plug-in for the SWT user interface library.

Setting the classpath:

To compile this project, you need to set the classpath specific for your operating and windowing system. For this, rename one of the following files to .classpath:

  • .classpath_win32 - Windows
  • .classpath_cocoa - Mac OS X
  • .classpath_gtk - Linux and all Unix variants

Similar class paths renaming should be done for ./examples/org.eclipse.swt.snippets/

To see these files, you may have to remove the filter for “.* resources”:

  • In the Project Explorer: view menu > Customize View... > Filters
  • In the Package Explorer: view menu > Filters...

Dependencies:

  • SWT Binaries
    You also need to clone the binary Git repository: https://git.eclipse.org/r/#/admin/projects/platform/eclipse.platform.swt.binaries
    and import the project for your platform into your workspace.

    Ensure that the fragment matching your windowingSystem.operatingSystem.cpuArchitecture
    (e.g. org.eclipse.swt.gtk.linux.x86_64) is open in your workspace.
    The fragments provide the platform-specific native libraries.

Using Assertions:

Assertions are added to the code. These don't run in production, but they do when:

  • JUnits are ran, they turn on assertions by default.
  • If you run a java run configuration and add ‘-ea’ to the ‘VM Arguments’

Assertions look like:

assert expression ;
assert expression : msg ;

See: https://docs.oracle.com/javase/8/docs/technotes/guides/language/assert.html

More Information:

See the Readme.md in the main directory of the Git repository for this project to learn more about SWT development.