dunst icon indicating copy to clipboard operation
dunst copied to clipboard

Refactoring x11

Open bebehei opened this issue 7 years ago • 4 comments

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


@tsipinakis please add your thoughts here, too!

bebehei avatar Jan 09 '18 04:01 bebehei

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.

bondzula avatar Jan 12 '18 08:01 bondzula

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

tsipinakis avatar Jan 12 '18 11:01 tsipinakis

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.

bebehei avatar Jan 12 '18 17:01 bebehei

Implementing the transparency for the separators would be great!

samirettali avatar Feb 02 '18 01:02 samirettali

tracking this in #1018

bynect avatar Apr 18 '24 09:04 bynect