On Wed, Oct 24, 2012 at 11:22 AM, Raphael Plasson <[email protected]>wrote:
> 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!
