dozydolphin/worksets

Worksets is a GUI application that helps you to quickly launch and arrange multiple applications in your desktop environment to support a specific workflow. Built for Unity 7 (R.I.P) and X11. Licensed under the GNU General Public License v3 or later.

worksets's Issues

KeyError: 'XDG_CURRENT_DESKTOP'

I believe I installed all of the dependencies and ran the pip3 installer but when I try and run the program I get this error.

Traceback (most recent call last):
File "/home/weggingt/.local/bin/worksets", line 7, in
from worksets.main import run
File "/home/weggingt/.local/lib/python3.5/site-packages/worksets/main.py", line 61, in
run()
File "/home/weggingt/.local/lib/python3.5/site-packages/worksets/main.py", line 54, in run
main = Main()
File "/home/weggingt/.local/lib/python3.5/site-packages/worksets/main.py", line 46, in init
wm = Wm(publisher)
File "/home/weggingt/.local/lib/python3.5/site-packages/worksets/system/wm.py", line 32, in init
desktop_env = os.environ['XDG_CURRENT_DESKTOP'].lower()
File "/usr/lib/python3.5/os.py", line 725, in getitem
raise KeyError(key) from None
KeyError: 'XDG_CURRENT_DESKTOP'

What can I do to resolve this?

Add desktop file to distribution

Problem: At the moment worksets can only be launched from the command line.

Solution
Create a desktop file to be distributed to /usr/share/applications directory if global install, or in ~/.local/share/applications if local (user) install. Needs changes in setup.py and possible MANIFEST.in

Create unit test for wm.py and all *wms

Problem: No unit test exists

wm.py initiates relevant wms and works as an interface for them for the rest of the application.
Solution:
Create unit tests that tests the wm.py itself and the ability to easily add new *wms to be tested through it.

Setup basics for unit testing

Not much to add... no unit tests working at the moment.

Setup so that going forward, unit-tests can be easily added.

Preferably a build integration as well

Desktop Environment not supported. (using Unity7)

Hi,
I'd really like to use your tool!

Unfortunately I'm getting the following:

You seem to be running the Unity:Unity7 desktop environment. Unfortunately, at the moment only the Unity desktop environment is supported.

Desktop: Unity:Unity7
Session: ubuntu

Distributor ID: Ubuntu
Description: Ubuntu 17.04
Release: 17.04
Codename: zesty

Ability to change sleep interval (waiting for the window to load) for individual applications with sane defaults

At the moment a 1 second delay is used for all applications to account for some applications taking longer to load before being able to grab the window and move it. It feels slow for fast loading apps, and can not possibly account for all cases.

The idea is to create a sane default for all applications (0.6 seems to be working for most applications), and then add the ability to change this number in an advanced section of the appdialog (should not be visible initially).

In this way users won't have to worry about it until it's a problem and they can then gradually up the wait time until the problem goes away.

A beautiful icon (in 3 versions: normal(?), dark and light monochrome)

Problem
At the moment my very very limited skills have been applied to Inkscape to hack something together

Solution
A kind competent soul creates an icon that:

• Illustrates the use case of worksets in the very limited amount of pixels available in the system tray
• Creates it in 3 versions: normal(?), dark and light monochrome
  If the icon scales well or a beautified version could be made for the apllication drawer that would just be awesome!

Add support for GNOME Shell (X11)

Although GNOME Shell might not be the obvious choice, since Worksets is built on the Qt framework, Ubuntu's choice to move from Unity to Gnome makes it the ideal candidate to support next (and it has all dependencies in the repositories as well).

system/
wm.py: Add conditional check to enable load of GnomeshellWm()

gnomeshellwm.py: A copy of unitywm.py is a good starting point. Changes should mostly revolve around the difference in the (wmctrl) reporting of desktops from the two DE's.

Where Unity works with one giant desktop and multiple viewports, gnomeshell adheres to listing single desktops.

If the basis on the unity desktop (and unitywm), proves to make this change problematic it might be a better solution to refactor the rest of Worksets and the unitywm, since I think that is the DE that doesn't adhere to the guidelines for EWMH/NetWM.