On Thu, Dec 10, 2009 at 11:55:12AM +0100, Joachim Breitner wrote:
Am Donnerstag, den 10.12.2009, 00:07 +0100 schrieb Jan Vornberger:
It also starts the helper applications and displays some start-up information.
Any chance to have this bit of code in the module that exports bluetimeConfig, e.g. as bluetileStartup.
From Bluetile's perspective xmonad and xmonad-contrib are libraries. If I understand you correctly, you are asking if all pieces of Bluetile can be moved somewhere into those libraries, so that the original Bluetile executable can be reconstructed with a simple recipe from the libraries alone. I see how that would make it possible to build everything from Debian's xmonad source packages, but I find it a little like craming things into
I fear that's not easily possible. This code uses things like 'getBinDir' provided by cabal to determine where it has been installed and find the helper applications. If it would be moved to xmonad-contrib, those calls would return the information for xmonad-contrib instead. Bluetile's main also does things like argument parsing and some extra code for proper restarting is required, because xmonad normally calls out to the binary 'xmonad' which obviously isn't want I want in this case. With some hacking it might be possible to move all this to some module called BluetileMain in xmonad-contrib. But I'm not really sure I want to go down this path, to be honest. places where they shouldn't be. Like moving all pieces of xterm into libncurses to be able to build both from just ncurses - to name a random example. Or do you feel this analogy doesn't hold here? Maybe because Bluetile is such a small program and mostly just uses xmonad and xmonad-contrib for the heavy lifting? But still, Bluetile is more then just bluetileConfig, even if just for technical reasons. Regards! Jan