SwingOSC

Note: this project is basically abandoned. The reason being that SuperCollider now has a better supported cross-platform GUI library, and furthermore that I use a different SuperCollider client now. The project was just recently updated to make sure it still compiles. It may still be useful where you have to run older SuperCollider versions or want a remote GUI server. I am unsure whether it still runs under SuperCollider v3.6.x or newer.

statement

SwingOSC is an OpenSoundControl (OSC) server intended for scripting Java(tm), such as to create graphical user interfaces with AWT or Swing classes. It uses the reflection and beans mechanisms to dynamically create instances of Java classes and control them. A separate set of SuperCollider language classes is included to allow the building of GUIs from within sclang.

SwingOSC is (C)opyright by 2005-2016 Hanns Holger. All rights reserved. It is released under the GNU General Public License.

SwingOSC version 0.70 is intended to be used with SuperCollider 3.5.1 or higher.

security note

SwingOSC uses UDP and TCP network protocols. It allows to create and execute almost any kind of java code on your machine. Therefore, running SwingOSC in a network that can be accessed from outside is a severe security problem, allowing hijacking, information retrieval and massive damage on your machine. You have been warned!

It is strongly advised to launch SwingOSC with the -L option which limits communication to the local computer. Alternatively, make sure your firewall settings are appropriate.

requirements

SwingOSC is written in Java and requires a Java runtime environment (JRE) version 1.6 or better. SwingOSC should work with Oracle Java or OpenJDK. You can verify your current Java version by opening a terminal and executing the command java -version.

installation

Installing SuperCollider classes: please refer to the separate file SuperCollider/README.md. Also see file INSTALL_LINUX on Linux.

contributing

Please see the file CONTRIBUTING.md

launching the server

Note: Typically you will launch SwingOSC from sclang, using SwingOSC.default.boot. The following section describes how to launch SwingOSC from a terminal and the types of switches accepted.

Open a terminal and cd into the SwingOSC folder. Either run the default script by typing sh SwingOSC_TCP.ext (where ext is .command on OS X, .sh on Linux, and .bat on Windows), or launch with custom options:

java [java-VM-options] -jar SwingOSC.jar [swing-osc-options]

where the VM options are:

• -Dswing.defaultlaf=<LookAndFeelClassName>: specifies a custom look-and-feel class. e.g. com.birosoft.liquid.LiquidLookAndFeel. Note that the widgets are now optimised for Nimbus, so it is recommended to just use the -nimbus switch instead.
• -Xdock:icon=application.icns : (Mac OS only) uses a prettier icon for display in the dock and programme switching screen.
• -Xdock:name=SwingOSC : (Mac OS only) uses an alternative name in the screen bar and dock

and the SwingOSC options are:

• -t <port> (recommended) : uses the given TCP port for message reception. The SuperCollider classes assume that you use port 57111!
• -u <port> : uses the given UDP port for message reception. if absent, an arbitrary free port will be picked.
• -L (recommended) : uses loopback address ("127.0.0.1") for communication. if absent, the local host's IP address is used. when your computer is connected to a network and SwingOSC needs only be accessed from the local computer, make sure you use this option to minimize the security issue mentioned above.
• -i : runs Swing initialization upon startup. On Mac OS, a terminal app becomes a GUI app with screen menu bar and icon in the Dock, as soon as an AWT or Swing component is created. This initialization can be enforced by using this option.
• -h <host:port> (recommended) : sends a [ /swing, "hello", <swingHost>, <swingPort>, <swingProtocol> ] message to the given UDP socket. this kind of manual "bonjour" is used by the SuperCollider classes to detect the startup of the SwingOSC server.
• --nimbus (recommended) : enforces the use of the Nimbus look and feel. Requires Apple Java 6, Oracle Java 6, or OpenJDK 7 or newer.

If you wish to include custom Java classes or libraries, you can either

• use the /classes OSC command (see OSC reference for details).

• include them in the SwingOSC.jar file

• add them to the java class path, as shown in the following example which adds the freetts speech libraries (assuming they have been copied to the lib folder):

  java -cp SwingOSC.jar:lib/freetts.jar:lib/jsapi.jar de.sciss.swingosc.SwingOSC [swing-osc-options]

compilation from source

SwingOSC now builds with sbt. Includes is a little helper bash script sbt by Paul Philips (license)which will download the sbt launcher to the SwingOSC directory if not yet present, and then invoke it.

You can also install sbt as explained on the sbt website.

To compile and assemble SwingOSC, run ./sbt assembly-devel. The final fully self-contained jar file will be SwingOSC.jar in the base directory. Make sure you adjust your SwingOSC.program settings in SuperCollider accordingly.

To package distribution zip files in the dist directory, run ./sbt package-dist.

The project now includes all the JXBrowser library components. In lib you find two license keys jxbrowser_development_license_for_swingosc.jar and jxbrowser_runtime_license_for_swingosc.jar. If creating a binary artifact of SwingOSC, only the runtime key may be distributed, and the development key must not be included.

download

• The source code and issue tracker can be found at github.com/Sciss/SwingOSC.