I’m going to answer my own question here.
The designerlauncher.desktop file is a file that specifies where an application exists and how a Linux desktop such as Gnome (or other freedesktop.org compliant applications) can start it from an icon. These desktop systems assign icons to applications by registering each application’s “.desktop” file.
There are 2 main locations where the “.desktop” file should be placed in order for this to occur:
- /usr/share/applications => For globally accessible applications by all users
- ~/.local/share/applications => For applications only accessible by the logged in user
Ideally you would place the designer.desktop file in one of those two locations, and place the executables somewhere else (that somewhere being described within the .desktop file). However the designerlauncher.desktop file specifies the location of the executables relative to the location of .desktop file itself. As taken from the .desktop file the app directory is defined as being in a sub-directory within the directory where the .desktop file is located:
Exec=bash -c ‘cd “$(dirname “$1”)/app” && ./designerlauncher.sh &’ . %k
As I didn’t want to:
- Pollute the global applications directory with the designerlauncher executables
- Rewrite the bash script to point to a different location
I simply copied the contents of the tar.gz file to my local applications directory. Given that I extracted the tar.gz file to ~/Downloads directory. I did this by executing the command line:
cp -rp ~/Downloads/designerlauncher/* ~/.local/share/applications
The “r” option means recursive, and the “p” option is to preserve file attributes.
With this done my Debian desktop could find the Designer Launcher application (I may have needed to log out and in again to refresh the desktop).
Ideally the app and runtime directories should not be in the same directory as the .desktop file, but for testing purposes it works for me.
Next step is finding out where the designerlauncher puts the shortcuts for the projects!