Welcome to awesome bug tracking system.

FS#614 - Split/merge awful and beautiful

Attached to Project: awesome
Opened by Julien Danjou (jd) - Thursday, 03 September 2009, 13:43 GMT
Last edited by Julien Danjou (jd) - Monday, 07 September 2009, 10:59 GMT
Task Type Evolution Request
Category Lua libraries → awful
Status New
Assigned To No-one
Operating System All
Severity Low
Priority Normal
Reported Version git/master
Due in Version 4.0
Due Date Undecided
Percent Complete 0%
Votes 0
Private No


awful depends on beautiful. Stop that.

Discussion can happen here about this topic. :)
This task depends upon

Comment by Gregor Best (farhaven) - Thursday, 03 September 2009, 13:49 GMT
What about completely integrating beautiful into awful? I.e. only provide the original beautiful as a wrapper around the awful functions for the sake of not breaking api and removing it later on.
Comment by Uli Schlachter (psychon) - Thursday, 03 September 2009, 13:52 GMT
List of awful modules that require() beautiful and what they use it for: - Menu height, font, text color
awful.prompt - font and text color
awful.titlebar - color fonts and images
awful.widget.layoutbox - images
awful.widget.taglist - lots of stuff (booleans, images, colors, fonts)
awful.widget.tasklist - same as taglist

(invaders and naughty dont count)

Comment by Uli Schlachter (psychon) - Thursday, 03 September 2009, 13:56 GMT
Oh, and another idea:

beautiful already depends on awful(.util), so we could add something like awful.theme which can be set by external stuff. (awful.theme = beautiful.get(), beautiful would do this automatically after loading a theme)
That way we wouldn't lose any features, but the dependency on beautiful is removed.

Comment by Julien Danjou (jd) - Thursday, 03 September 2009, 13:56 GMT
@farhaven: I think this is the correct solution after all.