Re: Custom keyboard source samples (was: Re: Windows keyboard restrictions)

From: Marcel Schneider <>
Date: Tue, 18 Aug 2015 11:42:01 +0200 (CEST)

On 18 Aug 2015 at 10:09, Philippe Verdy wrote:

> it helps if hou reduce the processor frequency (if you don't have a tool fir that, use the energy control panel and set the power profile to max energy saving) just before clicking the button to build the package.

That's a very good idea. I've currently throttled down the CPU to half performance (my computer being a netbook, and the processor stays heating around it). This is very important to note for users of desktop machines working at high performance. One really needs to slow down for this operation.

> i don't know why these c source files need to be deleted so fast when they could just remain in the same folder as the saved.klc file.

That's an—again, very good—question, and I often asked it to myself. Short answer is: There's no need. Long answer is: As it results from decrypting* the blog, Michael Scott Kaplan, the author of MSKLC, tried to meet at maximum the users' needs* and what users were expected to wish to have on their keyboard, and to create a smooth UI with maximum security.* Well, editing oneself the C source and the header file is about the opposite. So Michael didn't want to have his users bother with (which would have inevitably occurred if he put the files into the scope of the end-user). Now once they're meant to stay hidden, the best is to delete them right after use but nevertheless, a long time I couldn't help thinking something I won't post here anymore because it's about software policies.*

> nlte that the tool builds several packages for several processor types, not just amd64.

I'd to choose one folder. amd64 comes first in alphabet, and it comes third in the MSKLC build process so that we've enough time to switch back to the explorer window where the desired files are awaited.

* Like many other people wished that MSKLC support chained dead keys, I often wished that Windows support chained dead keys (like GNU/Linux), thinking that it doesn't, given that MSKLC doesn't offer this option. When I learned that Windows does, I deduced that MSKLC is purposely restricted to prevent the users from making any "too useful" keyboard layouts, until thanks to Doug Ewell drawing our attention to it, I learned the existence of Michael Kaplan's blog, and finally found this blog post on it:
I still wonder why one should not like to type two dead keys to get double-diacriticized letters, but I agree that the new way of typing text is with combining diacritics.

Now I see that it would have been enough to type "who is the author of MSKLC" into the Bing search bar to learn the name in the second result, and the story on his own blog as the fifth result...
I've missed that! October 2013 was before the time I began to really bother with keyboard layouts. But it was the time I should have begun to.

Sorry, Michael!

Received on Tue Aug 18 2015 - 04:43:12 CDT

This archive was generated by hypermail 2.2.0 : Tue Aug 18 2015 - 04:43:12 CDT