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