Comment 1 for bug 868311

I've decided to take a look around Screenlet's code and while I'm not a python expert I figured out the way it loads its Screenlets and I've (manually) done this as a workaround: Instead of loading the Screenlet directly, creat a numbered copy on ~/.screenlets and instead load it. That way we can have "unique" screenlets instead of multiple copies of a single screenlets, each with its own window name (the number).

I'm going to try to implement that in the code, but I'd like to know if that sounds acceptable or too "hackish" (that would solve the positioning problem, though, since I'm now able to use the Place plugin to position each screenlet as I please).