freenode/#clim - IRC Chatlog
Search
4:52:51
loke
Oh, and one last thing: The width is always computed from the text content of course. This is all about the height (i.e. the ascent and descent)
4:58:50
jackdaniel
(that means, that font-text-extents misses font-left and font-right, because left/right bearings should be taken into account too
4:59:23
jackdaniel
luckily it is an internal itnerface, so there is no controversy with adding more values
5:49:50
jackdaniel
another finding: our text-style-to-x-font is redundant with (standard) text-style-mapping
5:51:56
loke
Speaking of FONT-TEXT-EXTENTS. I have no idea what the purpose of the eigth and ninth values are supposed to be. If I recall correctly, no code uses them.
5:53:37
jackdaniel
text direction should be implied by the advance-width/advance-height, eventually by toward-x toward-y (i.e for vertical text with "normally" oriented glyphs)
5:54:06
loke
If the new truetype renderer can get the extents correct (needs to be pixel perfrect) I'll be happy to try to adapt Climaxima to be able to use it.
5:55:11
loke
The other feature that should be standardised is a way to install custom fonts. Climaxima ships with its own fonts, and there needs to be a way to tell CLIM to use it.
16:20:58
slyrus1
Oh, hey! I finally figured out what causes the caught STYLE-WARNING cannot find type for specializer ... when executing SB-PCL:SPECIALIZER-TYPE-SPECIFIER...
16:32:22
slyrus1
so this happens when we define a presentation method (in this case it's present) on a presentation-type that doesn't correspond to a CLOS class. So... the question is do we fix the warning or the code that generates the warning?