Re: What should titlebars be like?
Hello, A question to everyone: does anybody know where GTK themes store their titlebar icons? I think it would way better to use those icons for theme consistency. I searched around for theme and icon theme folders and couldn't find icons like minimize/maximize but they must be somewhere. Kind regards, -- Alexander Yakushev The problem with object-oriented languages is they've got all this implicit environment that they carry around with them. You wanted a banana but what you got was a gorilla holding the banana and the entire jungle. -- Joe Armstrong -- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
Re: What should titlebars be like?
I'm in with the congratulations to you, Uli, awesome work! Are these titlebars wiboxes? And, just an idea, can one dynamically toggle the visibility of it so that I can kind of dynamically add and remove them to show me properties like CPU-Usage of it's client in it if I need to see this (despite the fact that this PID-Stuff isn't implemented, was just an idea coming up in my mind because I love awesome being hackable^^)? Greetings Manuel -- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
Re: What should titlebars be like?
Hi, On 25.10.2012 19:20, Manuel Kasser wrote: Are these titlebars wiboxes? No. They are drawables (I'm running out of names for things that you can draw to). First I refactored the current drawin-code (There are no wiboxes on the C side in git/master, wiboxes are drawins + lots of lua code). This created a new class drawable. Then I made titlebars be drawables, too. So: Titlebars aren't wiboxes, but you can put any kind of widget in them. :-) And, just an idea, can one dynamically toggle the visibility of it so that I can kind of dynamically add and remove them to show me properties like CPU-Usage of it's client in it if I need to see this Yes you can. Dunno if the current code makes this possible nicely, but you can just change a titlebars' height to 0 and that is handled as remove the titlebar. The harder part is recalculating the titlebar height for restoring it. (despite the fact that this PID-Stuff isn't implemented, was just an idea coming up in my mind because I love awesome being hackable^^)? The pid of a window is accessible as c.pid since ages. That is also available in awesome 3.4 (of course only if the client sets a _NET_WM_PID property on its window). Cheers, Uli -- Why make things difficult, when it is possible to make them cryptic and totally illogical, with just a little bit more effort? -- A. P. J. -- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
Re: What should titlebars be like?
Am 25.10.2012, 21:42, schrieb Uli Schlachter: The pid of a window is accessible as c.pid since ages. That is also available in awesome 3.4 (of course only if the client sets a _NET_WM_PID property on its window). You're right, I just misinterpreted something I read, I checked this, completely my mistake. Thanks again for all the infos! Cheers Manuel -- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
Re: What should titlebars be like?
Something that just came into my mind: a are the widgets of a titlebar/drawable at height 0 inactive or do they still perform their job and I just don't see them? -- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
Re: What should titlebars be like?
On 25.10.2012 21:49, Manuel Kasser wrote: Something that just came into my mind: a are the widgets of a titlebar/drawable at height 0 inactive or do they still perform their job and I just don't see them? What do you mean with perform their job? Their job is to display something and they cannot display anything when their is no space. However, I'm unsure if their drawing function might still be called randomly, but I guess not. Cheers, Uli -- For saving the Earth.. and eating cheesecake! -- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
Re: What should titlebars be like?
Thanks for the prompt answer! On 25.10.2012, 22:02, Uli Schlachter wrote: What do you mean with perform their job? Their job is to display something and they cannot display anything when their is no space. A CPU-Widget for example has do check on CPU usage periodically (1/s usually if I programmed it), which would be unnecessary if it isn't displayed (in case of CPU-widgets that would be no big problem, but I know me and I have no idea what crazy stuff I would try out in the titlebar...^^). And I think there might be some cases in which the widget might be better stopped if it isn't necessary. The question if such a widget should be in a titlebar is another one, of course. ;) Cheers Manuel -- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
Re: What should titlebars be like? (was: Release next major version - how bad could it be?)
They should at a minimum be like they are now. Provide the ability to: - move a window by dragging the titlebar - toggle float - close - maximize Buttons less used by me, maybe just as important to other users - ontop - sticky -- Adrian C. (anrxc) | anrxc..sysphere.org | PGP ID: D20A0618 PGP FP: 02A5 628A D8EE 2A93 996E 929F D5CB 31B7 D20A 0618 -- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
Re: What should titlebars be like?
I'm in a lack of words to congratulate and thanks Uli. I guess we all feel something similar. Thank you Uli!
Re: What should titlebars be like?
Hello, I think that the most important point is to have titlebars that are as flexible as possible, so that one can put whatever he wants in it (hell, this is the point to work with a WM that can be configured with code: to be able to hack it, right ? :D). Typically, I am not really interested in classic titlebars. However, it would be really nice to be able to add information about the _process_ running in the window. Imagine to have dynamic monitoring of per process memory, CPU, disk, net, etc. use in each window, so that you can directly see what is going on in each window. All these informations are here to be read (directly from /proc, but some tools are always pre-digesting the data, e.g. prstat). It is easy to get the primary PID of the process in the window (at least via xprop, but I assume this can be accessed directly from awesome, right ?). It may be more tricky to get global statistic about the activity of the process with all its children, but probably doable (best way to get all relevant child PIDs seems to be pslist). It would be: 1) nice 2) useful 3) geeky 4) unique to awesome (?? at least I have never seen this before.) What do you think? Raphaël -- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
Re: What should titlebars be like?
On Wed, Oct 24, 2012 at 11:22 AM, Raphael Plasson rplas...@gmail.comwrote: Hello, I think that the most important point is to have titlebars that are as flexible as possible, so that one can put whatever he wants in it (hell, this is the point to work with a WM that can be configured with code: to be able to hack it, right ? :D). Typically, I am not really interested in classic titlebars. However, it would be really nice to be able to add information about the _process_ running in the window. Imagine to have dynamic monitoring of per process memory, CPU, disk, net, etc. use in each window, so that you can directly see what is going on in each window. All these informations are here to be read (directly from /proc, but some tools are always pre-digesting the data, e.g. prstat). It is easy to get the primary PID of the process in the window (at least via xprop, but I assume this can be accessed directly from awesome, right ?). It may be more tricky to get global statistic about the activity of the process with all its children, but probably doable (best way to get all relevant child PIDs seems to be pslist). It would be: 1) nice 2) useful 3) geeky 4) unique to awesome (?? at least I have never seen this before.) What do you think? Raphaël AWESOME idea. Expose the client's pid so we can add nice little nifties related only to that client to the titlebar! OMG, awesome is evolving fast these days!
Re: What should titlebars be like?
Am 22.10.2012 03:05, schrieb Claudio Roberto França Pereira: I'm all in for titlebars as wiiboxes. It's the best solution in my opinion, as it enables full customization of the titlebar. Current layouts fully support the known widgets disposition in common WM's titlebars; widgets in a wiibox also support mouse actions. I second this! Would be the most flexible option. -- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
Re: What should titlebars be like? (was: Release next major version - how bad could it be?)
I mostly use titlebars to move and resize (tiled) windows with only the mouse (i.e. without a modifier). Cheers, Miles -- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
Re: What should titlebars be like?
Uli Schlachter wrote: On 14.10.2012 16:12, Alexander Yakushev wrote: [...] In order to start writing real titlebar widgets first we should decide what for people want titlebars in first place. Minimize/maximize/close buttons? Moving/resizing windows by titlebar? Something else, more tiling related? This is a question to those who want titlebars in Awesome. Ping? No one wants titlebars? Or do you just want empty titlebars? That'd be easy to implement... Well, my main use for titlebars is as a visual indicator of the status of the window. I.e: - Is the window active? (different titlebar color for active and inactive window) - Is the window maximized? (icon) - Is the window floating? (icon) - Is the window sticky? (icon) - ... The icons could be buttons instead of simply indicators, but my main use for them is the feedback they provide. Of course if they could be completely customizable, so much the better. But that would probably be a lot more complicated to implement... Jerome -- mailto:jeber...@free.fr http://jeberger.free.fr Jabber: jeber...@jabber.fr signature.asc Description: OpenPGP digital signature
RE: What should titlebars be like? (was: Release next major version - how bad could it be?)
The contents for me would be... High Priority: Name Close, Medium Priority: Maximize Minimize, Low Priority: Icon. Indication of mode of the window would probably be nice as well (Medium). While mouse click on the window with a key press can achieve the same purpose, clicking on the titlebar to drag a floating window is my most common action. Regards Dave David Sorkovsky +61 468 478 438 Date: Sun, 21 Oct 2012 20:47:16 +0200 From: psyc...@znc.in To: awesome@naquadah.org Subject: What should titlebars be like? (was: Release next major version - how bad could it be?) On 14.10.2012 16:12, Alexander Yakushev wrote: [...] In order to start writing real titlebar widgets first we should decide what for people want titlebars in first place. Minimize/maximize/close buttons? Moving/resizing windows by titlebar? Something else, more tiling related? This is a question to those who want titlebars in Awesome. Ping? No one wants titlebars? Or do you just want empty titlebars? That'd be easy to implement... Uli -- my $key = \x49\x03\x93\x08\x19\x94\x96\x94\x28\x93\x83\x04\x68\x28\xa8\xf5. \x0a\xb9\x94\x02\x45\x81\x93\x1f\xbc\xd7\xf3\xad\x93\xf5\x32\x93; my $cipher = Crypt::Rijndael-new( $key, Crypt::Rijndael::MODE_ECB() ); my $plain = $ciper-decrypt($daten); -- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
Re: What should titlebars be like? (was: Release next major version - how bad could it be?)
I'm all in for titlebars as wiiboxes. It's the best solution in my opinion, as it enables full customization of the titlebar. Current layouts fully support the known widgets disposition in common WM's titlebars; widgets in a wiibox also support mouse actions.
Re: What should titlebars be like?
On Sun, Oct 21, 2012 at 5:12 PM, Jérôme M. Berger jeber...@free.frwrote: Well, my main use for titlebars is as a visual indicator of the status of the window. I.e: - Is the window active? (different titlebar color for active and inactive window) - Is the window maximized? (icon) - Is the window floating? (icon) - Is the window sticky? (icon) The ability to toggle a window between floating and tiled, maybe even a way to send a application to a different tag, yes I know all this can be done via the keyboard but if your hand is already on the mouse this should be very useful.
