[awesome bugs] #757 - Image/Drawing System Overhaul With Cairo Bias

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#757 - Image/Drawing System Overhaul With Cairo Bias User who did this - Gregor Best (farhaven) -- I remember a long time ago I used oocairo for drawing on widgets. That was before I added the wra

[awesome bugs] #757 - Image/Drawing System Overhaul With Cairo Bias

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#757 - Image/Drawing System Overhaul With Cairo Bias User who did this - Julien Danjou (jd) -- Anyhow, I think we should not decide blindly to embed our own wrapper. If luacairo is crap, we might j

[awesome bugs] #757 - Image/Drawing System Overhaul With Cairo Bias

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#757 - Image/Drawing System Overhaul With Cairo Bias User who did this - Uli Schlachter (psychon) -- I looked around a little. http://luaforge.net/projects/luacairo/ auto-generated crap that was l

[awesome bugs] #757 - Image/Drawing System Overhaul With Cairo Bias

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#757 - Image/Drawing System Overhaul With Cairo Bias User who did this - Julien Danjou (jd) -- Cairo bindings obviously. Eventually, using some existing binding maybe a big plus… -- More

[awesome bugs] #757 - Image/Drawing System Overhaul With Cairo Bias

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#757 - Image/Drawing System Overhaul With Cairo Bias User who did this - Uli Schlachter (psychon) -- So let's start with a drawing API. How should it look like? Should this be like the current api

[awesome bugs] #798 - handling modal windows

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#798 - handling modal windows User who did this - Uli Schlachter (psychon) -- The gvim "open file" dialog that was mentioned previously has this: $ xprop | egrep 'TRANS|MODA' _NET_WM_STATE(ATOM) =

[awesome bugs] #798 - handling modal windows

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#798 - handling modal windows User who did this - Julien Danjou (jd) -- I don't think this is a problem with modal windows, but rather with windows having the WM_TRANSIENT_FOR property. This one a

[awesome bugs] #798 - handling modal windows

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#798 - handling modal windows User who did this - Uli Schlachter (psychon) -- I don't think that a focusable parent is useful. I just don't know what a good fix would be. If we automatically focus

Re: RFC: Drop support for zaphod mode

On Wed, Aug 18 2010, James Pearson wrote: I use two separate X sessions. If that is not zaphod mode, disregard the rest of this message. If you mean 2 X servers, this is not Zaphod mode indeed. -- Julien Danjou // ᐰhttp://julien.danjou.info -- To unsubscribe, send mail to awesome-devel-

Re: RFC: Drop support for zaphod mode

On Sun, Aug 15, 2010 at 6:14 AM, Uli Schlachter wrote: > Are you using zaphod mode? > I use two separate X sessions. If that is not zaphod mode, disregard the rest of this message. > Why? It was the simplest way I could get two separate desktops (as in, switching tags on one does not affect