tynet-lichat/shirakumo

7:40:30 shinmera |3b|: How do you feel about making the kerning table key on integers instead? Can compute the key via (+ (char-code lhs) (ash (char-code rhs) 21))

7:40:46 shinmera would mean we can do an eql table instead.

7:41:34 shinmera should also mean the keys remain fixnums on 64 bit machines.

8:22:10 selwyn what happened with that clamp to 32 bits thing

8:27:21 shinmera eh?

8:30:33 selwyn we were trying to write a routine to round integers to 32 bits

8:31:09 shinmera ah. nothing.

13:02:39 selwyn i have been asked the following: 'is it a metroidvania or more like something like classic sidescrolling zelda/castlevania?'

13:02:57 shinmera Neither

13:03:35 shinmera It's an open world action RPG without any gatekeeping

14:13:26 selwyn it has been wishlisted

14:13:59 shinmera cool

14:22:57 shinmera Now I just need about 15'000 more and we'll be looking at least somewhat alright.

14:26:01 |3b| shinmera: i'd probably lean towards having that as an option (what is it keyed on currently?

14:26:13 shinmera a cons of the characters.

14:27:20 shinmera My proposition is this: make a KERNING function that takes two CHARACTERs and handle the lookup internally.

14:27:30 shinmera *a KERNING place

14:27:39 shinmera That way it's at least internal.

14:27:44 |3b| yeah, that too

14:28:02 shinmera An option for it would just make things even more of a mess, rather than less :)

14:28:49 |3b| is there a struct or something per character currently?

14:28:59 |3b| ACTION just woke up, so remembering things is too much effort)

14:29:04 shinmera In my PR?

14:29:10 |3b| or in general

14:29:21 shinmera right now each glyph has a plist of properties in a table.

14:29:29 |3b| ok, so there is

14:29:31 shinmera the kerning is a separate table indexed via a cons of the two characters.

14:29:59 |3b| ACTION was just wondering if it would be worthwhile having a flag in that to indicate if a particular char is the first of any kerning pairs

14:30:15 shinmera what would you do with that?

14:30:16 |3b| (for the structs + optimized kerning hash version)

14:30:24 |3b| decide to skip the kerning lookup

14:30:31 shinmera hrm.

14:31:01 shinmera I suppose that could be worth it. Sounds like a micro optimisation though vs changing the table keys to fixnums.

14:31:05 |3b| yeah

14:31:15 shinmera I can add it if you like.

14:32:01 shinmera Anything to procrastinate from having to figure out once again why layouting with labels that have line breaking requires multiple resizes to stabilise to a proper sizing information for the labels :v

14:32:21 shinmera Alt: any takers for that?

14:51:32 shinmera |3b|: Pushed some more stuff to the PR. The writers should be translated now to use the structs, too, and I added the kerning table optimisation.

14:51:48 shinmera there's still some GETFs in the code, around the page table and the sdf info.

15:04:59 shinmera If you like I can turn those into structs, too.

15:05:44 |3b| ACTION will try to take a look at it soon, might be a few days though

15:05:50 shinmera ok.

15:06:00 shinmera Will continue to operate off of my fork for now.

15:58:47 shinmera Of course, even getting a bloody test case together for this stupid Alloy layouting issue is a nightmare

16:00:50 shinmera Hmm, ok. I think I got it. The clip-view seems to be necessary. But why?...

16:02:28 shinmera https://plaster.tymoon.eu/view/3539#3539

16:02:30 shinmera well, no time

16:02:35 shinmera will have to check tomorrow.

16:02:48 shinmera the second block receives a lot of padding for some reason