At 1228229037 time_t, Lluis wrote:
> I've been wanting for days to post some ideas to modularize customizability in
> awesome. My proposal consists of two main ideas:
That's a good idea, we probably missed so module to handle some common
aspect that are widely used by many users.
> To that extent
Hi all!
El Mon, Dec 01, 2008 at 05:08:42PM +0100, Julien Danjou ens deleit� amb les
seg�ents paraules:
[...]
> What you want to achieve is to build another layer between awesome and
> the final configuration file.
Nice! Somebody else opened the box for me :)
I've been wanting for days to post s
At 1228146547 time_t, Andreas Klöckner wrote:
> You can (and probably should) even support both points of view: Keep the
> current default config, but add enough hooks that I can dofile() just one
> thing at the end to make my wishes happen. Then everybody is free to hack the
> default, or, as I
On Montag 01 Dezember 2008, Julien Danjou wrote:
> Hi,
>
> I think Maarten well answered your question.
>
> At 1228087684 time_t, Andreas Klöckner wrote:
> > a) Don't break APIs. Ever. Pretty please. Breaking people's work
> > environment is a complete no-no. If you have to, do so extremely gently,
Hi,
I think Maarten well answered your question.
At 1228087684 time_t, Andreas Klöckner wrote:
> a) Don't break APIs. Ever. Pretty please. Breaking people's work environment
> is a complete no-no. If you have to, do so extremely gently, and with plenty
> of documentation on how to adapt. Rememb
Forgot to send to list as well.
Original Message
Subject:Re: config file maintenance
Date: Mon, 01 Dec 2008 01:02:36 +0100
From: Maarten Maathuis <[EMAIL PROTECTED]>
To: Andreas Klöckner <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
Hi all,
I think that awesome has quite a significant problem with config file
maintainability. Here's the story, conveniently from my point of view:
So, I discover awesome, find it likewise, hack my config file to pieces, use
it for a few months and am happy. Then I upgrade from 3.0 to 3.1rc3,
