On Fri, Jun 4, 2010 at 3:33 AM, Anselm R Garbe wrote:
> There are still plans for this. Unfortunately I became ultra-busy
> during the last year at my day job and wasn't able to achieve the
> suckless goals I hoped for. The drawing abstraction is a higher
> priority though.
>
> I can't promise any
On 3 June 2010 21:28, Thayer Williams wrote:
> On Wed, Jun 17, 2009 at 1:01 AM, Anselm R Garbe wrote:
>> I received my long awaited X200s yesterday, and the dwm development
>> will continue now, first item in the queue is the new multihead
>> support as discussed on IRC a while ago.
>> ...
>> Aft
On Thu, Jun 03, 2010 at 01:28:52PM -0700, Thayer Williams wrote:
On Wed, Jun 17, 2009 at 1:01 AM, Anselm R Garbe wrote:
Hi,
I received my long awaited X200s yesterday, and the dwm development
will continue now, first item in the queue is the new multihead
support as discussed on IRC a while ag
Great!
- Original message -
> On Wed, Jun 17, 2009 at 1:01 AM, Anselm R Garbe
> wrote:
> > Hi,
> >
> > I received my long awaited X200s yesterday, and the dwm development
> > will continue now, first item in the queue is the new multihead
> > support as discussed on IRC a while ago.
> >
On Wed, Jun 17, 2009 at 1:01 AM, Anselm R Garbe wrote:
> Hi,
>
> I received my long awaited X200s yesterday, and the dwm development
> will continue now, first item in the queue is the new multihead
> support as discussed on IRC a while ago.
> ...
> Afterwards the next item will be the interface i
On Mon, Jun 22, 2009 at 3:28 AM, Jack Woehr wrote:
> Enno Boland (Gottox) wrote:
>>
>> 2009/6/21 Uriel :
>>
>>>
>>> Excessive and naive obsession with code reuse is one of the major
>>> sources of gratuitous complexity in the software industry.
>>>
>
> Ooh! Nice. "Having an idea and being able to e
Enno Boland (Gottox) wrote:
2009/6/21 Uriel :
Excessive and naive obsession with code reuse is one of the major
sources of gratuitous complexity in the software industry.
Ooh! Nice. "Having an idea and being able to execute it in code"
is in 75% of cases much more serendipitous than rot
I agree with uriel. In my opinion just seperate the drawing code from
the rest of the code by putting it into its own functions. This should
be sufficient. Please avoid using extra libraries.
2009/6/21 Uriel :
> Well, it might work, but lets say that I'm skeptical.
>
> Also I wonder if the gain of
Well, it might work, but lets say that I'm skeptical.
Also I wonder if the gain of moving the handful of lines of code
involved in drawing dwm's GUI into a library would really be worth it.
Excessive and naive obsession with code reuse is one of the major
sources of gratuitous complexity in the s
On Sun, 21 Jun 2009 17:43:40 +0200
hiro <23h...@googlemail.com> wrote:
> > As said, don't miss that all these efforts will be kept at
> its most minimalist solution.
>
> Easily said...
Easily done...
> > Separating interface and implementation...
>
> Not always sane.
In most cases it is. Figu
> As said, don't miss that all these efforts will be kept at
its most minimalist solution.
Easily said...
> It is the Sensible Solution[tm] to
> do it the way he suggests.
...
> Separating interface and implementation...
Not always sane.
In this case I agree that it's rather not worth it.
If
On Sun, 21 Jun 2009 02:56:46 +0200
Uriel wrote:
> I thought we had agreed against having multiple drawing backends...
> this will add considerable complexity for no gain at all.
you misunderstand. Read Anselms mail. It is the Sensible Solution[tm] to
do it the way he suggests. Separating interfa
2009/6/20 Michael :
> Anselm R Garbe wrote:
>> Afterwards the next item will be the interface integration to enable
>> different drawing backends, which will ease porting to cairo/pango or
>> xft as well. The advantage is, that the same interface will be used in
>> st and dmenu as well. This is bas
On Sat, Jun 20, 2009 at 7:56 PM, Uriel wrote:
> I thought we had agreed against having multiple drawing backends...
> this will add considerable complexity for no gain at all.
>
> uriel
Separating rendering code out hardly creates "no gain at all." Some
of us would like to use dwm with something
I thought we had agreed against having multiple drawing backends...
this will add considerable complexity for no gain at all.
uriel
> Afterwards the next item will be the interface integration to enable
> different drawing backends, which will ease porting to cairo/pango or
> xft as well. The adv
On Sun, Jun 21, 2009 at 02:53:10AM +0400, Michael wrote:
> Anselm R Garbe wrote:
> > Afterwards the next item will be the interface integration to enable
> > different drawing backends, which will ease porting to cairo/pango or
> > xft as well. The advantage is, that the same interface will be used
Anselm R Garbe wrote:
> Afterwards the next item will be the interface integration to enable
> different drawing backends, which will ease porting to cairo/pango or
> xft as well. The advantage is, that the same interface will be used in
> st and dmenu as well. This is basically the remainder of my
On Wed, Jun 17, 2009 at 09:01:27AM +0100, Anselm R Garbe wrote:
> Afterwards the next item will be the interface integration to enable
> different drawing backends, which will ease porting to cairo/pango or
> xft as well. The advantage is, that the same interface will be used in
> st and dmenu as w
On Wed, Jun 17, 2009 at 09:01:27AM +0100, Anselm R Garbe wrote:
> I received my long awaited X200s yesterday, and the dwm development
> will continue now, first item in the queue is the new multihead
> support as discussed on IRC a while ago.
this is a very welcome development :)
the particulars
Hi,
I received my long awaited X200s yesterday, and the dwm development
will continue now, first item in the queue is the new multihead
support as discussed on IRC a while ago.
The basic idea is to use the available Xinerama screens as mutual
exclusive additional tagset for clients, so that each
20 matches
Mail list logo
