Dunst: Refactoring x11

Created on 9 Jan 2018  ·  4Comments  ·  Source: dunst-project/dunst

For scheduled refactoring of the X11 code, what should we pay attention to?

@tsipinakis please add your thoughts here, too!

graphics refactor

Most helpful comment

Implementing the transparency for the separators would be great!

All 4 comments

Single windows per notifications would be amazing, I would love to have different notifications size's based on the width needed for that notification, and not get resized when the bigger one comes along.

add ability to center the notifications

I wouldn't put that in the X11 refactor that falls more into the settings redesign (#336 ), the implementation part of it is pretty straight-forward.


We should also look for:

  • Separate X11 with the rest of the codebase as much as possible (_eyeing those xctx accesses in notification.c_).

  • Decoupling X11 API calls from the pango/cairo drawing functions

I wouldn't put that in the X11 refactor that falls more into the settings redesign (#336 ), the implementation part of it is pretty straight-forward.

Well, however we should look forward to refactor it in a way, that we can adapt such changes later very easy.

IMHO we should actually now decide, where we want to head for with the graphics stack. This avoids double work.

Implementing the transparency for the separators would be great!

Was this page helpful?
0 / 5 - 0 ratings