#avr Logs

Jan 22 2021

08:08 AM rue_bed2: hmm, I wonder how you low level code for dual core
09:34 AM vmt: rue_bed2: there's a designated core that starts executing at reset, and you'll wake up the other one with it, well... if you want to
06:25 PM vmt: LeoNerd: hey, you had that term key lib right?
06:25 PM LeoNerd: ... maaaybe?
06:26 PM vmt: :) i checked your site and you've merged it into the other project, yeah?
06:26 PM LeoNerd: Not exactly
06:26 PM vmt: no?
06:26 PM LeoNerd: I said that it ought to be. I haven't got around to it yet
06:26 PM LeoNerd: ETIME
06:28 PM vmt: heh, i guess what i'm asking here is, is that is there something majorly unimplemented in it, whether it has any deps and if an up-to-date standalone version is available?
06:28 PM LeoNerd: Unsure quite if I can parse the question. Can you reword it?
06:29 PM vmt: right, well for one, is it small, or do i have to expect to link against ICU or something?
06:30 PM LeoNerd: The "it" is now vague. Which of my libraries are you talking about?
06:30 PM vmt: libtermkey i believe it's called?
06:30 PM LeoNerd: Right. Then, no .. it's quite small. But I wouldn't recommend writing new applications using it
06:31 PM LeoNerd: The entire /design/ is wrong
06:31 PM LeoNerd: I'd suggest using libtickit... which currently /happens/ to use libtermkey internally, which becomes my problem to fix
06:32 PM vmt: the thing is libtickit is pretty much a whole input/output thing on its own and i've got all of the output and polling in the architecture already
06:32 PM LeoNerd: Right.
06:32 PM LeoNerd: So here's the thing - you can't understand keys read /from/ the terminal, without talking /to/ the terminal
06:32 PM LeoNerd: libtermkey never got around to doing that
06:32 PM LeoNerd: There's lots of things it can't do. can't ever do
06:33 PM LeoNerd: libtickit will be able to do much more things, nicer, better, because it is able to send as well as receive
06:35 PM vmt: yeah... i've got a basic system in place but special keys with all the fucking colors-in-the-rainbow-terminals it starts to make me quite sad
06:35 PM LeoNerd: Imean ultimately I can't stop you doing whatever you want.. I'm just pointing out that eventually I will kill it, because it is massively inflexible with what it can do
06:36 PM LeoNerd: E.g it cannot handle copy/paste to the terminal
06:36 PM vmt: yeah, i guess this was what i was after
06:36 PM vmt: thanks
06:36 PM LeoNerd: So if you're going to adopt /something/ you might as well adopt the thing I'm not going to kill.. rather than the one I am :)
06:36 PM vmt: heh
06:37 PM vmt: perhaps... i'll just extend my system a bit further then and whoever doesn't use the terms i support can fuck off
06:38 PM LeoNerd: entirely up to you
06:38 PM LeoNerd: Though if you don't want to use it I'd at least be interested to hear /why/, ... in case there's some basic problem that means nobody else is ever going to use it but I'll never know...
06:39 PM vmt: no, i think it's really great if you're looking for a solution out-of-the-box that just works, for both input and output, though i haven't tested it but i'll take your word for it
06:40 PM vmt: not sure if you've got some evloop in it for a really simple solution or if you provide your own
06:41 PM LeoNerd: I provide a basic one and hooks to attach your own
06:41 PM LeoNerd: and a couple of examples showing glib and libuv
06:42 PM vmt: i haven't dug through that much foss stuff, but what's curious to me is the project structure
06:42 PM vmt: namely the existence of t/ and contents thereof
06:42 PM LeoNerd: t/ contains tests
06:43 PM LeoNerd: See the CODE-MAP file. That's docs to explain what is where.
06:43 PM LeoNerd: I really wish more folks wrote those :(
06:44 PM vmt: oh damn, i've never come across a CODE-MAP file either, didn't come across my mind to take a look
06:44 PM vmt: i really wish more people would write one too. that's a definite +1
06:45 PM LeoNerd: Yeah.. I'm sure someone else somewhere does that too, but the specific idea/name I did think of myself. I hope I am not unique, but it's rare I ever see one
06:45 PM vmt: perhaps it'd be a good idea to add a mention of it directly in the readme
06:46 PM LeoNerd: hmm.. perhaps