[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Update on community bonding phase: Plans on refactoring ftinspect
From: |
Charlie Jiang |
Subject: |
Re: Update on community bonding phase: Plans on refactoring ftinspect |
Date: |
Thu, 9 Jun 2022 16:29:03 +0800 |
User-agent: |
Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.9.1 |
Hi Werner,
[Charlie, please subscribe to the 'freetype-devel' mailing list.]
But I can still manage my subscription status on
https://lists.nongnu.org/ . Is my subscription accidentally dropped?
I don't know. What would be the advantage of having everything in a
single file?
IMO, those widgets could be considered "auxiliary components", and are
pretty far from the core logic. Therefore, it should be made less "loud"
(it's 8 source files out of 23 in total - more than 1/3 !)
If you finish editing the control file, you press a button in
`ttfautohintGUI` to regenerate the output font. `ftinspect` should
notice the update file and automatically update its display.
I see.
Well, the coding style of `ftinspect` is*far* more standard than the
FreeType library itself:-)
I will try to imitate it at my best. I'm using the .clang-format file
from FreeType project - should I do that?
Please note that we (roughly) use the 'GNU style for ChangeLog files'
for writing commit messages. You are normally on the safe side if you
imitate the commit message format I use for my commits.
Will definitely do that.
Cheers,
Charlie