User Manual
Window Switch consists of two parts: the server which provides the applications and the client (the applet)
which is used to connect to them.
The client and server may run on the same system.
Applet
The applet can be started from the application/start menu of your operating system, see here for details.(You may want to configure it to auto-start on login, so that you can automatically resume previously connected sessions)
In order to make use of it, you will need to connect it to a server (see below).
You can either install a server on your local machine, on another machine on your local network,
or you can subscribe to a fully serviced account, accessible from anywhere on the Internet.
Servers on your local network should be detected automatically via mDNS, if the applet fails to connect to them, look here.
Once connected, you may choose between many different supported protocols to start new remote desktops and applications, to help you chose the most suitable one, see here.
Server
The server is generally started automatically when starting the client applet.
The server can also be started manually by any user. (running as root is a work in progress and is not currently supported)
Simply open a terminal and run:
winswitch_server
More information on configuring the server can be found here
Starting seamless applications via Window Switch
Only applications started via Window Switch can be manipulated (disconnected, moved around, etc).
Starting sessions via the applet's menu is covered in the quick start guide,
you can also open files via Window Switch directly from your file explorer:
both Microsoft Windows Explorer and Gnome nautilus are supported.
On Unices (Linux, BSDs, etc), if you want all your standard desktop shortcuts to start applications via winswitch, you can modify your desktop shortcuts to use the wrapper script.
You can then use the regular start menu and still get the benefits of winswitch.
Simply replace:
Exec=command_name
With:
Exec=wcw command_name
In the desktop shortcuts (generally located in /usr/share/applications
),
this will start the command via winswitch if it is running, otherwise the command will be started normally.
(in future versions, a tool will be provided to make it easier to manage this sort of configuration)
Starting a full remote desktop session
Full desktop sessions are similar to seamless sessions described above, but the whole session will be contained in a single window showing a complete desktop.
Shadowing an existing session or display
Shadowing allows you to clone an existing session or display onto another machine.
Setting up Sound Forwarding
Sound can be forwarded to and from your locale machine using GStreamer plugins,
see here for details.
(This feature is currently not available on MS Windows, see here for details)
Other Useful Tools and Features
To make the windows follow you around without needing to explicitly tell the software where you are located,
we can use tools such as blueproximity
to receive notification of your changes in location.
There are two utilities which we can trigger to notify Window Switch of your present location:
winswitch_away
: when you may be away from this computer.winswitch_back
: when you are back in front of this computer.
Debugging
On non-Windows platforms, you may also launch the client from the command line:
winswitch_applet
This will print all the standard diagnostic messages to your terminal.
Add "
--debug_mode
" to increase the verbosity.
(do not run the applet as root!)
More info on troubleshooting here.