Awesome desktop environment?

louis058 · 2011-06-15 09:45:00

Is there any desktop environment that encorporates the awesome window manager? Or a tiling window manager?

Jelle · 2011-06-15 10:01:44

Have you tried pytlye(2) with your regular (non-tiling) setup? Not sure how it performs with a full-blown DE, but it works great with Openbox.

louis058 · 2011-06-15 10:10:40

Hmm... Is there any way of incorporating Awesome itself into a DE?

MrMars · 2011-06-15 10:14:12

louis058 wrote:

Hmm... Is there any way of incorporating Awesome itself into a DE?

what exactly you want to have in your DE of awesome?
the tags? the widgets?

I mean, if you use awesome as a floating wm, you maybe won't miss any of the features of others DE.
if you want transparency and shadows, just use xcompmgr or cairo-compmgr, and you're done.

I just don't understand why you would want some awesome features in another De

louis058 · 2011-06-15 11:59:05

MrMars wrote:

louis058 wrote:
Hmm... Is there any way of incorporating Awesome itself into a DE?
what exactly you want to have in your DE of awesome?
the tags? the widgets?
I mean, if you use awesome as a floating wm, you maybe won't miss any of the features of others DE.
if you want transparency and shadows, just use xcompmgr or cairo-compmgr, and you're done.
I just don't understand why you would want some awesome features in another De

Basically just the customization, and the tiling I think. The problem is that by itself, Awesome misses a lot of features, most important for me is a shutdown/reboot utility. The Awesome documentation also doesn't seem to offer a way of integrating with PolicyKit. It would take a lot of work figuring it out by myself when I have zero knowledge of policykit, and little documentation from Awesome itself.

the_isz · 2011-06-15 12:57:03

louis058 wrote:

Basically just the customization, and the tiling I think. The problem is that by itself, Awesome misses a lot of features, most important for me is a shutdown/reboot utility. The Awesome documentation also doesn't seem to offer a way of integrating with PolicyKit. It would take a lot of work figuring it out by myself when I have zero knowledge of policykit, and little documentation from Awesome itself.

It's very easy to add shutdown/reboot menu entries or keybindings to awesome. As
to the PolicyKit stuff: You should more precisely state what you're trying to do
and what doesn't work so people can help you. I can't see how awesome should
have any problems working with PolicyKit.

If you just need the tiling, the already recommened PyTyle is probably the
easiest way to add tiling to an already existing DE. Integrating awesome into a
DE is a tedious task, as is an almost fully-featured DE itself.

Last edited by the_isz (2011-06-15 12:59:03)

ANOKNUSA · 2011-06-15 15:24:13

I agree with the_isz that Awesome is configurable and extensible enough in itself. If you must have a DE, though, there are instructions on the Awesome wiki to do so. Just make sure the DE isn't KDE, as it essentially results in just using KDE programs with Awesome: you must kill Plasma to get Awesome working.

Guff · 2011-06-15 16:08:51

louis058 wrote:

The problem is that by itself, Awesome misses a lot of features, most important for me is a shutdown/reboot utility. The Awesome documentation also doesn't seem to offer a way of integrating with PolicyKit. It would take a lot of work figuring it out by myself when I have zero knowledge of policykit, and little documentation from Awesome itself.

There's actually an example on the awesome wiki.
What I do is different, though:

local lock = "slimlock"
local ck = "dbus-send --system --print-reply --dest=\"org.freedesktop.ConsoleKit\" "
            .. "/org/freedesktop/ConsoleKit/Manager org.freedesktop.ConsoleKit.Manager."
local suspend = "dbus-send --system --print-reply --dest=\"org.freedesktop.UPower\" "
                .. "/org/freedesktop/UPower org.freedesktop.UPower.Suspend"

local logoutmenu = {
    { "Shutdown", ck .. "Stop", freedesktop.utils.lookup_icon({ icon = 'system-shutdown' }) },
    { "Reboot", ck .. "Restart",  freedesktop.utils.lookup_icon({ icon = 'gtk-refresh' }) },
    { "Suspend", suspend, freedesktop.utils.lookup_icon({ icon = 'media-playback-pause' }) },
    { "Lock screen", lock, freedesktop.utils.lookup_icon({ icon = 'system-lock-screen' }) },
    { "Log out", awesome.quit, freedesktop.utils.lookup_icon({ icon = 'system-log-out' }) },
}

Then just add logoutmenu to your myawesomemenu table, and replace lock with whatever screenlocker you use. Or remove the "Lock screen" entry from the table if you don't use one.

If you don't have awesome-freedesktop-git installed, just remove the freedesktop.utils.lookup_icon parts. I just like having icons on everything.

Screenshot:

bohoomil · 2011-06-15 16:51:54

To tile, or to click... That's a great question. ;o)

There are things like bluetile, designed specifically for Gnome and based on Xmonad, or one can always try and install Docky or AWM (or any other clickable dock with panel features) inside, say, AwesomeWM. I tried them both before eventually moving straight to pure tiling policies, and using keyboard shortcuts that do exactly the same job as the couple of icons appeared to be a much more sensible (and convenient) solution. Of course, Awesome allows for a lot more -- see above. There are plenty of options to choose from. : )

Last edited by bohoomil (2011-06-15 16:52:50)

louis058 · 2011-06-15 17:59:02

Guff wrote:

louis058 wrote:
The problem is that by itself, Awesome misses a lot of features, most important for me is a shutdown/reboot utility. The Awesome documentation also doesn't seem to offer a way of integrating with PolicyKit. It would take a lot of work figuring it out by myself when I have zero knowledge of policykit, and little documentation from Awesome itself.
There's actually an example on the awesome wiki.
What I do is different, though:
local lock = "slimlock"
local ck = "dbus-send --system --print-reply --dest=\"org.freedesktop.ConsoleKit\" "
            .. "/org/freedesktop/ConsoleKit/Manager org.freedesktop.ConsoleKit.Manager."
local suspend = "dbus-send --system --print-reply --dest=\"org.freedesktop.UPower\" "
                .. "/org/freedesktop/UPower org.freedesktop.UPower.Suspend"

local logoutmenu = {
    { "Shutdown", ck .. "Stop", freedesktop.utils.lookup_icon({ icon = 'system-shutdown' }) },
    { "Reboot", ck .. "Restart",  freedesktop.utils.lookup_icon({ icon = 'gtk-refresh' }) },
    { "Suspend", suspend, freedesktop.utils.lookup_icon({ icon = 'media-playback-pause' }) },
    { "Lock screen", lock, freedesktop.utils.lookup_icon({ icon = 'system-lock-screen' }) },
    { "Log out", awesome.quit, freedesktop.utils.lookup_icon({ icon = 'system-log-out' }) },
}
Then just add logoutmenu to your myawesomemenu table, and replace lock with whatever screenlocker you use. Or remove the "Lock screen" entry from the table if you don't use one.
If you don't have awesome-freedesktop-git installed, just remove the freedesktop.utils.lookup_icon parts. I just like having icons on everything.
Screenshot: http://ompldr.org/tOTJ0Ng

This is the exact tutorial that I found on the wiki for implementing a shutdown menu. I may be wrong though, but I assumed that it needed a password to be used since it uses gksu.

Sorry everyone, I just went and assumed doing it with policykit would be difficult, since there aren't any tutorials for it. I shall look into it by myself.

Guff · 2011-06-15 18:30:23

louis058 wrote:

This is the exact tutorial that I found on the wiki for implementing a shutdown menu. I may be wrong though, but I assumed that it needed a password to be used since it uses gksu.
Sorry everyone, I just went and assumed doing it with policykit would be difficult, since there aren't any tutorials for it. I shall look into it by myself.

gksu will require a password.

The commands used in my thing are all passwordless, though.

ANOKNUSA · 2011-06-15 21:14:03

gksu is just a front-end for su or sudo, which are typically required for simple shutdown without Policykit. visudo will let you change that behavior easily enough (I don't like messing around with polkit settings unless I really need to). Awesome isn't intended to make things exceptionally easy by doing everything behind the scenes without user input; if it were, it would be a full DE rather than a stand-alone WM. As Guff demonstrates, Awesome offers users plenty of freedom for configuring their systems as they see fit.

Arch Linux

#1 2011-06-15 09:45:00

Awesome desktop environment?

#2 2011-06-15 10:01:44

Re: Awesome desktop environment?

#3 2011-06-15 10:10:40

Re: Awesome desktop environment?

#4 2011-06-15 10:14:12

Re: Awesome desktop environment?

#5 2011-06-15 11:59:05

Re: Awesome desktop environment?

#6 2011-06-15 12:57:03

Re: Awesome desktop environment?

#7 2011-06-15 15:24:13

Re: Awesome desktop environment?

#8 2011-06-15 16:08:51

Re: Awesome desktop environment?

#9 2011-06-15 16:51:54

Re: Awesome desktop environment?

#10 2011-06-15 17:59:02

Re: Awesome desktop environment?

#11 2011-06-15 18:30:23

Re: Awesome desktop environment?

#12 2011-06-15 21:14:03

Re: Awesome desktop environment?

Board footer