Last christmas, I gave you^W^W^W I wrote katriawm[1].

 Been  using  it  ever  since. Shortly after, bevelbar[2] came to life,
 accompanied by infofeld[3].

 Still, it's my first WM and there are some  things  that  I  would  do
 differently now. For example:

   -- The  client-server-model  results  in quite some code duplication
      and it makes some things more  complex.  Maybe  I'd  ditch  that.
      Plus,  I  don't use a single tool that makes use of that model --
      with  my  setup,  katriac  only  ever  handles  user  input.  So,
      splitting client and server has little to no real life benefit.

   -- I  would  go for DPI-independant drawing. Yes, I should have seen
      that coming. Even I  get  in  contact  with  monitors  that  have
      high/higher DPI and that makes my WM look tiny. Meh.

   -- I  would probably do font rendering using Cairo/Pango. That pulls
      in some nasty dependencies, but you also get a lot  of  features.
      Proper UTF-8 rendering, for example.

 Nevertheless, I'm very happy with katriawm. DPI issues are probably my
 biggest grudge, but this also affects a lot  of  other  software.  The
 Linux world is not ready for that. :-/


                          ____________________


 For  over  four  years, I did not have to update sgopherd -- the shell
 script which serves this gopher hole. That's  pretty  amazing.  Today,
 though,  I  found  a bug, because Bash changed its behaviour. Oh, well
 ...

 ____________________

 1. https://github.com/vain/katriawm

 2. https://github.com/vain/katriawm

 3. https://github.com/vain/infofeld

You are viewing proxied material from uninformativ.de. The copyright of proxied material belongs to its original authors. Any comments or complaints in relation to proxied material should be directed to the original authors of the content concerned. Please see the disclaimer for more details.