12:59:13lokejackdaniel: Are you there? I have a question w.r.t. xrender... Do we already store a picture representing the entire window? The font renderer (both of them, afaik) allocates its own, which is a bit of a waste.
12:59:53jackdanielthat's one of a few reasons why double buffering is broken
13:01:13lokeI'm creating a new one. (I don't think they use much resources anyway)
13:01:49jackdanielI think that the right approach is to use single (or eventually two) pictures
13:01:59jackdanielwhich will have the size of the entire window
13:02:04jackdanieland remove all the auxiliary ones
13:38:08lokejackdaniel: I was checking how the render backend handles complex shapes, and it uses the PATHS library (part of cl-vectors). I didn' tknow about this library.
13:39:07lokeIt implements the necessary code to break paths and polygons into simples shapes, which is what is needed for xrender as well. I've already gotten the basic line drawing working with xrender, so now I'm looking into leveraing PATHS in the same wasy as the render backend.
13:39:20lokeHow much do you know abou thtis library?
13:41:19jackdanielI've suggested today you should look there
13:42:57jackdanielinstead of copying code over maybe it is possible to reuse render methods? or refactor them into reusable components?
18:37:10ck_jackdaniel: I believe #742 can be closed now; also, #699 needs only a technical writeup and a normalization of the standard width/height values for all panes. Would you like me to put a diff as a comment?
18:40:00jackdanielsure, or you may wrap PR which will supersede this one