KLL 0.4 or 0.5?

[nyarly]

Is there a timeline on 0.4? I'm anxious especially to do some of the timing stuff - I'd like to program certain keys only to trigger on their own (Enter most specifically), and I hear good things about tap keys...

[haata]

I hope to start working on it again soon. I'm been pre-occupied getting my testing infrastructure working for force curves (super close, but I keep finding bugs...).

I'm probably 1/3 done with 0.4 (and 0.5) implementation of KLL. The parser is finished, now I'm working on code generation and firmware (firmware is the easy part lol).

[imbriaco]

@haata Any chance you might have an even alpha-quality branch kicking around that people could help test? I'm keen to use some of the newer KLL features like state scheduling for tap keys.

Thanks for KLL, I've quickly become a huge fan of the simplicity!

[haata]

@imbriaco About a month ago I started on a full rewrite of the compiler. It was one of those...you know...I hate everything moments.
Making really good progress, nearly at feature parity with the old compiler, and have started adding the KLL 0.4 and 0.5 features. The new design makes it way easier to extend the language, so future updates should proceed more quickly as well.

I'll definitely let you know when I have some sort of alpha-branch ready. Please bug me every couple of weeks (just in case I forget). At this current rate, I'm probably a couple weeks away.

[pystub]

🐛
It just doesn't feel the same after having used tap/hold Ctrl.

[imbriaco]

@haata Bugging you as requested! ;)

[haata]

Thanks!
Some non-working keyboard bugs have been distracting me. I hope to work on this some more this weekend.

[bwright86]

I am just getting into KLL, and was curious what version of the spec you are using today.

Is there an obvious place in the files that specify v0.3/v0.4/v0.5?

[haata]

The code that's running today is still 0.3d.

I have been integrating 0.5c into the ktype branch (though it's not ready to be used yet). The new compiler has been written, I just have to finalize the code-generation (which means I'm working on the firmware code now).

Anyone who wants to watch my progress, these are the branches that matter:

• https://github.com/kiibohd/controller/tree/ktype
• https://github.com/kiibohd/kll/tree/dev
• https://github.com/kiibohd/kll-spec/tree/0.5

[typorian]

I did a pull on the ergodox infinity firmware today and some message about kll 0.5 went by, does that mean that it is now usable for the infinity ergodox? I am still waiting for momentary layer switches (because they are awesome)

[nyarly]

So, is 0.5 just basically dead? Seems like latest commit there is over a year ago, and I don't see progress on the other branches there.

Is QMK supported on the Ergodox Infinity? I've been switching layouts between keyboards for more than a year now, and I'd like to just standardize. There's a lot to like about KLL in principle, but if there's no progress coming, I don't want to hold out that hope.

[typorian]

All I can tell you so far, qmk does compile for the infinity ergodox, I have no Idea on how to flash it though and if there is any support for the lcd at all.

[dmgm]

Progress in the form of commits still seems slow. Probably not dead. Hataa said in another issue thread he was working on it, but looks like 2016 was the year for KLL inspiration. @haata do you still want to be bugged about this?

https://github.com/kiibohd/kll-spec/commits?author=haata

[haata]

Yep! Progress is slow on my side mostly because I work on a ton of different things (and have a full-time job too). State scheduling is actually gating Animation trigger support so I'm hoping to be working on it in the next few weeks.

…

On Thu, May 10, 2018 at 6:35 PM dmgm ***@***.***> wrote: Progress in the form of commits still seems slow. Probably not dead. Hataa said in another issue thread he was working on it, but looks like 2016 was the year for KLL inspiration. @haata <https://github.com/haata> do you still want to be bugged about this? https://github.com/kiibohd/kll-spec/commits?author=haata — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#6 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AABbqRzBqTCSnJueaGnM6kiMFquBdNWvks5txOrygaJpZM4H0x9l> .

[kluelogic]

Does KLL compiler already support animation trigger like this? I saw some code was generated, but it seems linked animation does not work.

A[test1] <= loops:1, framedelay:1;
A[test1, 1] <= P[6](255);

A[test2] <= loops:1, framedelay:1;
A[test2, 1] <= P[13](255);

U"RGui"      : A[test1](start); # this works
A[test1](D)  : A[test2](start); # this doesn't work

[haata]

Not quite yet. Most of the code is there I just haven't enabled it yet (I had it enabled, but then a bunch of other stuff broke...).
My guess that state scheduling for triggers will be ready in the next week or two.

[kluelogic]

It's good to know. Thanks for the info!