spiegel-keyman/linux/mcompile/keymap
2024-07-03 14:10:38 +02:00
..
deadkey.cpp feat(linux): ... and back in 2024-06-26 16:06:42 +02:00
deadkey.h feat(linux): ... and back in 2024-06-26 16:06:42 +02:00
keymap.cpp feat(linux): char-filenames, check parameters in run() 2024-07-01 11:15:14 +02:00
keymap.h feat(linux): more comments for keymap 2 2024-06-27 15:48:01 +02:00
km_types.h feat(linux): ... and back in 2024-06-26 16:06:42 +02:00
mc_import_rules.cpp feat(linux): more comments for keymap 2 2024-06-27 15:48:01 +02:00
mc_import_rules.h feat(linux): ... and back in 2024-06-26 16:06:42 +02:00
mc_kmxfile.cpp feat(linux): char-filenames, check parameters in run() 2024-07-01 11:15:14 +02:00
mc_kmxfile.h feat(linux): char-filenames, check parameters in run() 2024-07-01 11:15:14 +02:00
mcompile.cpp feat(linux): formatting 2024-07-01 12:08:16 +02:00
mcompile.h feat(linux): char-filenames, check parameters in run() 2024-07-01 11:15:14 +02:00
meson.build feat(linux): remove filesystem.h/cpp and move OpenFile() function to mc_kmx_file 2024-06-28 13:59:16 +02:00
README.md feat(linux): ... and back in 2024-06-26 16:06:42 +02:00
u16.cpp feat(linux): remaining comments on u16 2024-07-03 14:10:38 +02:00
u16.h feat(linux): finish up comments on u16 2024-07-01 15:10:55 +02:00

This is a proposal to rewrite mcompile for Linux. For this we need to query the base keyboard data from the Linux platform, then rewriting the keyboard .kmx using the same approach as is done in mcompile for Windows, but working from the data from the x11 keyboard on Linux.

Ideally, we'd rewrite mcompile to be cross-platform (Windows, Linux, macOS), so that the keyboard interrogation would be separated from the .kmx rewriting, at least to some degree. Nevertheless it would probably be easiest to start from a standalone implementation. Sample program that reads US basic keyboard and compares to key value group

Keymap