I asked in the linux-usb mailing list (question, see one of the relevant answers (from Alan Stern). In short: not possible. Using a USB hub it’s then maybe possible -some models only-. The answer includes a link to a small program to try to disable the port. I could disable the port, but the device had still power.

I still didn’t want to give up. I remembered that I bought, 2 years ago, a USB relay. Actually that one could be used it says with 220VAC/10A, so I could power on a heating or some big device.

I did a bit of very bad-done hardware work: I “broke” a USB cable, got the red inner-cable to pass through the relay. Then using one USB port I control the relay and I can switch on and off the other USB device like I wanted initially.

As you can see in the photo I broke too much the shield -because a confussion not directly related with the project-. Still, it works well with my dumb device and other devices.

Una de les “practiques” que vaig fer va ser el Joc de la Vida de Conwall (Wikipedia-en , Wikipedia-ca). És un joc per 0 jugadors (no s’interactua un cop està funcionant), l’estat inicial del taulell va evolucionant seguint unes regles.

Ho vaig fer, el taulell va evolucionar, vaig pensar “que guai” i ja va estar, o poc més.

Ara, amb Viquipèdia, es poden veure figures que fan coses pel taulell. Que es mouen, que commuten estats, etc. etc.

El passat Python Code Dojo va ser el problema a resoldre més votat. Vaig pensar “vaja, ja l’he fet, tampoc era tan divertit”. Però gràcies a Wikipedia doncs vaig descobrir coses i va ser més divertit.

Els codi font de diferents grups del Python Dojo es pot trobar a github.

Qui hagués tingut Viquipèdia a la joventut. Segur que tot el que hi ha allà es pot trobar a altres llocs (evidentment) però és tant fàcil anar i llegir fàcilment…

De Catux només va venir en Fran. Divendres a la nit miràvem quin autobús / tramvia agafar, a quina hora, etc.

Vaig revisar la línia d’autobús i vaig mirar els horaris (recordo que el tramvia passava cada… 40 minuts?). Total, el què no vàrem revisar és a quina hora començava el Fosdem. El Fran va dir, crec, a les 9:30 (o potser les 9?). Total, vàrem arribar allà ven d’hora. Però el Fosdem començava a les 10:30!

Així que vaig fer la meva donació al Fosdem, la que et donen una camiseta. Tinc la donació número… 2!:

Gràcies Fran! ens vàrem llevar d’hora, però vàrem tenir la segona camiseta, veure els llibres d’OReilly amb calma, esmorzar tranquil·lament, planificar les conferències…

Fosdem: fins l’any vinent!

Normalment surto de cada Fosdem amb una llista de projectes, programes, coses a mirar que tardo uns quants dies…

Si algú ve i vol saludar que avisi. Companys de Catux també venen.

On the last hack weekend I did a screensaver using Python, which one is integrated with KDE. Probably with some small changes would work in other systems.

In this entry I’ll cover the basic of the screensavers in KDE (how to integrate the new screensaver in KDE), and how KDE interacts with the screensaver. You should know a little bit of Python and Pygame, but if you don’t know you can still understand the code and do the same using other systems.

The code is in Git. Or if you want the quick example look here.

How to add a new screensaver in the screensavers list from the system

In KDE, in Settings, Display icon, screensavers: there is a list of screensavers (if you don’t have any you can install the packages kde-window-manager and kscreensaver-xsavers).

If you want to add a new screensaver there, you can create a file in the directory /usr/share/kde4/services/ScreenSavers , My new file is named “Mendeley.desktop” where you can follow the same structure than other entries there. My one looks like:

[Desktop Entry]
Exec=mendeley.kss
Icon=preferences-desktop-screensaver
Type=Service
X-KDE-ServiceTypes=ScreenSaver
Actions=Setup;InWindow;Root;
# X-KDE-Category=Miscellaneous
Name=Mendeley
Name[ca]=Mendeley

[Desktop Action Root]
Exec=mendeley.kss -root
Name=Display in Root Window
Name[ca]=Mostra a la finestra arrel
NoDisplay=true

See the different sections: Desktop Entry is a general one, defining which actions that particular screensaver can do (in the example: all of them: setup, preview -InWindow- and the real screensaver thing -root).

In each action it defines which the parameters will be passed to the binary. They can be changed, I’ve used the same than other screensavers.

In the above case, it says that when mendeley screensaver will be called in preview mode (or test mode) it will pass the parameter -window-id and then the window id. In execution mode it will pass only -root parameter, and in setup mode -setup.

In our case, mendeley.kss is just a Python file (the extension .kss is to use the same extensions than other screensavers, could be whatever we want).

The mendeley.kss should be in some directory in the path of the current user (else, the full path could be also used).

Preview / test mode: window-id parameter

Pygame, by default, uses SDL as an output. And SDL reads an environment variable (SDL_WINDOWID), if the variable exists uses that window to pain the things. Else SDL creates a new window, as it usually happens.

The basic code to handle the test and the preview mode would be like:


#!/usr/bin/python

import os
import pygame

if sys.argv[1] == “-window-id”:
    os.environ['SDL_WINDOWID'] = sys.argv[2]

    pygame.init()
self.window = pygame.display.set_mode((0,0)) # auto-resize

From here on we would just write standard Python using Pygame.

Root window: the real case

In case that the screensaver executable receives -root parameter, we need to search the root window of the current desktop.

As a first approach (that doesn’t work here), this could be found using xprop -root and then getting the “window id” from the output of the command. But we will find that when KDE is trying to use the screensaver, nothing will appear on the screen (as a note, here is where I spent quite a long time to understand what was happening…).

What we need to do is search for the virtual root window. This is a window that we need to use. This virtual root window is a window child of the root window and that one of the properties is __SWM_ROOT. Code to do this can be found in git.

What the code does is to get all the children of the real root window, iterate over them and search which one contains __SWM_VROOT. Then returns the window id of the window that contains __SWM_VROOT.

The first version of the screensaver used a small C executable with some code borrowed from xscreensaver project that was doing the same using C libraries (libx11). I thought that would be more clear, Pythonic and easier to understand if I would implement it using xwininfo and xprop. If somebody knows a way to get the same result using just Python (without external calls) feel free to commend or mail me.

The code in mendeley.kss (which is the main Python file) to get the Virtual Root Window is like:

if sys.argv[1] == "-root":
    windowid = virtualroot.getVirtualRootWindow()
    os.environ['SDL_WINDOWID'] = windowid


Instead of using the window-id that KDE provides us: searches for the windowid of the virtual root window and uses it.

Configuration

Maybe we would like to have a setup dialog for our new shiny screensaver. In that case (already specified in the .desktop file) KDE will launch the executable with the option -setup. I did something very simple as a proof of concept: I just launch a Qt dialog where the user can change some values, and the values are saved in a .py file. The main screensaver file just imports that .py file. Don’t do the same into the wild!

The code to do this (including the Qt code, etc.) can be found in the file mendeleyScreensaverSetup.py.

Exiting

When the user moves the mouse (or after writing the password): the KDE screensaver system will kill send a SIGTERM to the screensaver. In the handle_input of the screensaver code we can do:


def handle_input(self,events):
for event in events:
# SIGTERM is handled by SDL and received a QUIT event
if event.type == QUIT:
    sys.exit(0)


All together now…

All the code for the Mendeley screensaver can be found in git.

I’ve done a reduced version without mainly any logic (only a text is displayed) so you could create your own screensaver from there on. See the code.

In my system, when the screensaver is printing something to the standard output, this is saved in the file ~/.xsession-errors .

What about other desktop systems? (or operating systems?)

Screensavers in Gnome? Maybe just xscreensaver? Or even on Mac OS X? Microsoft Windows? I haven’t done it, but as far as I’ve seen in Google the principles are quite similar. Good luck, comment here if you do. And perhaps I’ll do some other article about how to do screensavers in the other systems.

Here I found some information regarding Microsoft Windows (I haven’t tested): http://archives.seul.org/pygame/users/Mar-2003/msg00162.html

Conclusion

Doing screensaver using Python and Pygame is easy (when you have the basic) and can be very fun. And leave a quite big potential there: would you like your screensaver to do some network connections and show webpages? Or perhaps take photos of your desk? Or maybe a clock with how long you haven’t been there? Or show randomly your last git messages? everything can be done, it’s just Python code.

Also, thanks to Mendeley to organise the hackdays / hackweekends. It’s fun, you learn, you code for fun… without thinking too much about maintenance or other constraints. We did a blog post with some screenshots of some hacks.

Also, if you have some idea for some hackday: tell me. It’s usually more fun to do something that could potentially be useful (like an amazing screensaver ) than something not so terribly useful.

If you are curious what the Mendeley screensaver does: it connects to Mendeley using the Open-API, fetches some stats, shows on the screen using a black background and green fixed-width font, with a scrolling up. It also shows a random paper from your library and a random paper from the Mendeley catalog.