Timeline for Get current Virtual Desktop - number/name/tag/id?
Current License: CC BY-SA 3.0
13 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 13, 2011 at 12:59 | comment | added | sr_ | added an answer with a little additional information :) | |
| Nov 13, 2011 at 12:59 | answer | added | sr_ | timeline score: 2 | |
| Nov 11, 2011 at 22:57 | comment | added | Grzegorz Wierzowiecki | @sr_ arbtt is a great tool :D. Why haven't you put it as separate answer, but as comment? - it deserves it :) (and points). I'have to check out it's sources carefully :). | |
| Oct 31, 2011 at 20:24 | answer | added | Gilles 'SO- stop being evil' | timeline score: 5 | |
| Oct 30, 2011 at 8:09 | comment | added | sr_ | A similar project that might be interesting to you is arbtt: "arbtt is a background daemon that stores which windows are open, which one has the focus and how long since your last action (and possibly more sources later), and stores this. It is also a program that will, based on expressive rules you specify, derive what you were doing, and what for." | |
| Oct 29, 2011 at 22:36 | comment | added | Grzegorz Wierzowiecki | Hello, @Celeb your comments inspired me to write more about my motivations putting me into this question. As you guessed, I'd like to monitor. Because monitor is not oriented to receive "well structured data", but "any structured data" in order to do some mining on that, I am open for paradigm differences. I just would like to reason about user task according to his/her current behaviour. Current desktop configuration (like selected virtual desktop ,tag or sth) is great source of informatino what is beeing done at moment. For example: I named my VD's for this purpose. | |
| Oct 29, 2011 at 22:30 | history | edited | Grzegorz Wierzowiecki | CC BY-SA 3.0 | added 1324 characters in body; edited title |
| Oct 29, 2011 at 22:12 | comment | added | Caleb | As far as your program is concerned, Window Managers should be left to their job however they want their job to be done, meddling with the WM from inside a program is not welcome. If you are trying to add functionality / behavior to a WM or write some kind of window controller / monitor, this will need to be done specific to each different WM and use the WM's own API, whatever that is. | |
| Oct 29, 2011 at 22:10 | comment | added | Caleb | Of that list, I know awesome is going to play a different game. That's why I use and is the one that specifically handles VD's using an entirely different paradigm. I think xmonad and dwm are much like it. They are known as dynamic or framework managers and don't have the kind of desktop paradigm that Gnome/KDE based WM's typically do. You can probably come up with something that works across stock Gnome/KDE/XFCE ... however I would seriously question whether you are on the right track at all. It sounds like you are trying to work this problem backwards. | |
| Oct 29, 2011 at 21:13 | comment | added | Grzegorz Wierzowiecki | Thanks @Celeb , I hope you don't mind, I've changed a little bit problem statement, according to your comment. Thanks for pointing me - I hope - on right way. :) | |
| Oct 29, 2011 at 21:12 | history | edited | Grzegorz Wierzowiecki | CC BY-SA 3.0 | added 254 characters in body |
| Oct 29, 2011 at 19:38 | comment | added | Caleb | A general solution to this is not going to be possible. For example the Desktop Environment I use doesn't use VD's at all, it uses tags that can be mixed and matched at any given moment. There are ways that will span a few DE's, but don't expect full coverage. | |
| Oct 29, 2011 at 19:34 | history | asked | Grzegorz Wierzowiecki | CC BY-SA 3.0 |