freenode/#clim - IRC Chatlog
Search
6:25:13
jackdaniel
something what piggybacks on ffi won't become default, so the old rendering code will still be there and it will be default (hopefully it will benefit from loke's refactor too)
6:26:38
jackdaniel
unrelated note: it might be worth considering factoring renderer into a separate library
6:53:11
loke
jackdaniel: I don't know. I've mostly left the old ttf code that way it is, and just adapted it a bit to conform to the new interface between clx and the font renderer
8:10:39
smokeink
loke: I spent many hours trying to make iBus work on my slackware , but my conclusion is that iBus is crapware, it has many idiotic dependencies and it's full of bugs . In the end I managed to compile and install it but it just doesn't want to work with any Chinese table, no matter it's pinyin or something else. Japanese doesn't work either. Russian and English and the other non-table European languages work fine though
8:16:14
smokeink
the crappiest thing I've ever seen in my life is python. iBus depends on python... and all these chinese tables which should just be a single file or something similar, they also depend on obscure python libs such as pyzy - which fail to run because python is split into ver2 and ver3, but both ver2 and 3 (I think) are also split into ucsc4 and ucsc_something else, and they're incompatible as far as parsing unicode is concerned
8:22:14
smokeink
on my system that pyzy fails to run because re.compile(u'[\U00010000-\U0001FFFF]') doesn't work in python2, it works only in python3 . But the lib is written in python2. "It's because Python (for reasons I don't care to look into) made a decision at some point (I guess it made sense at the time?) to have two kinds of unicode handling. This resulted in "narrow" and "wide" builds of Python in the 2.7 series. In Py3, this is distinction is removed."
8:23:00
smokeink
and if I choose to compile the other python2 build, the wide_ version, then all the other software that I have installed and that uses python will break
8:23:59
smokeink
stuff like that has happened to me almost every time I had to deal with software that directly or indirectly depends on python
9:58:55
smokeink
https://www.niksula.hut.fi/~jkirma/books/xlib.pdf does anyone have the example programs for this book ? ftp.uu.net doesn't seem to be working any more
10:20:36
smokeink
first I'm gonna make a helloworld in C that has a textbox and see if the IME interacts with it by default or not (I think it doesn't ) , then I shall see how to integrate the ime with the helloworld, to understand the mechanism
10:22:35
loke
I have another one that tests harfbuzz, but I didn't need much in C. I just quickly moved to CFFI, because in many cases uses C libraries from Lisp is nicer than C :-)
10:27:00
loke
Because I render the glyphs without any alpha channel, but yet it still manages to render the subpixel sampled pixels correctly.
10:27:58
loke
I do have to tell the xrender glyphmap what the background colour for the individual glyph is, so it may use that to determine the alpha to use
12:54:54
loke
smokeink: Oh the Shape extension? Yeah, that one has been around since the early 90's.
12:56:58
loke
smokeink: Yes. First of all, it creates a tiny border around the transparent part. Looks bizarre
12:57:21
loke
Also, it gets confused as to which window is on top, so you end up with the shaped window on top, but you click on it and you select the window below.
13:05:32
loke
smokeink: Your test example, is it supposed to not have any window decoration at all? Not even a bar to move it?
13:07:00
loke
Hmm... wait. It seems to depend on which font I use. There are some fonts that look bad with autohint on
13:08:18
loke
I think the problems are caused by the iwnodw manager when it wants to decorate the window
13:09:30
smokeink
this is going to be a simple example that I'm going to show jackdaniel and then ask him if he can add this to mcclim. Last time when we discussed about custom shaped windows the conclusion was "it's impossible to achieve this in X"
13:10:04
smokeink
so if even gnome did not mess with that simple example, it means it's possible and easy
13:11:07
loke
A pity I wasn't in the channel when that was discussed.I would have immediately asked him to run "oclock" that is surely on his system, and mentioned the Xshape extension. :-)