di0ib/kll
Archived
1
0
Fork 0
Code Releases Activity
KLL Compiler
This repo is archived. You can view files and clone it, but cannot push or open issues or pull requests.
94 Commits 3 Branches 0 Tags 292 KiB
Python 97.5%
C 2.5%
d7b7752dc1
Go to file
Jacob Alexander d7b7752dc1 Updating Lexer to KLL 0.5c 
- Added syntax check unit-test
- Added none emitter (for syntax validation check)
- Added KLL 0.5c example expressions
- Added Travis-CI test for syntax check
- Cleaned up README
2016-10-09 20:02:31 -07:00
backends Updating KLL to generate _KLL defines for upcoming firmware update 2016-05-08 17:49:05 -07:00
common Updating Lexer to KLL 0.5c 2016-10-09 20:02:31 -07:00
emitters Updating Lexer to KLL 0.5c 2016-10-09 20:02:31 -07:00
examples Updating Lexer to KLL 0.5c 2016-10-09 20:02:31 -07:00
funcparserlib KLL Compiler Re-Write 2016-09-01 23:48:13 -07:00
kll_lib KLL Compiler Re-Write 2016-09-01 23:48:13 -07:00
layouts Typo in Programmer's Dvorak 2016-08-06 20:50:00 -07:00
templates Initial pixel hard-coded template 2016-09-18 00:49:55 -07:00
tests Updating Lexer to KLL 0.5c 2016-10-09 20:02:31 -07:00
.gitignore Adding support for "Soft Replace" kll 0.3c 2015-09-30 00:04:30 -07:00
.travis.yml Updating Lexer to KLL 0.5c 2016-10-09 20:02:31 -07:00
kll Updating Lexer to KLL 0.5c 2016-10-09 20:02:31 -07:00
kll.py Adding support for pixelmap output and backporting features to 0.3d 2016-09-11 12:40:10 -07:00
LICENSE
README.markdown Updating Lexer to KLL 0.5c 2016-10-09 20:02:31 -07:00

README.markdown

kll - keyboard layout language

https://travis-ci.org/kiibohd/kll

Visit our IRC channel

If you're trying to compile keyboard firmware, you want THIS

KLL Compiler

Most current version of the KLL Spec.

Uses funcparserlib

Usage

General Usage

kll <kll files>

Kiibohd Controller Usage

kll.py <misc kll files> --config <config/capability kll files> --base <basemap kll files) --default <default layer kll files> --partial <partial layer 1 kll files> --partial <partial layer 2 kll files>

See kll --help for the most up to date documentation

Unit Tests

Unit tests can be found in the tests directory. They are run by Travis-CI, but can be useful when testing your own changes.

Remember to add new tests when adding new features/changes.

Patches/Features/Backends

Completely welcome :D