termbox2 and the future of ex_termbox

[zachallaun]

Hi all! @mhanberg and I had a brief conversation about porting this library to use termbox2 and we wanted to solicit input.

In addition to some useful enhancements over termbox, the primary motivation of moving to termbox2 is that it is actively maintained. (Indeed, the termbox readme currently points to termbox2 as a preferred choice for new projects.)

There are a few of options for how to proceed:

• If @ndreynolds has interest, I believe it would be possible to update this project to use termbox2 without breaking backwards compatibility.
• This project could be forked as ex_termbox2 and maintained independently. If this occurred, a separate discussion could be had about maintaining API compatibility, which might allow Ratatouille to easily switch to it if desired at any point.

I'm eager to hear any thoughts, suggestions, or alternatives from anyone interested!

[slondr]

@zachallaun / @mhanberg I think this project is unmaintained, there's an open PR which fixes a deterministic build failure that hasn't been merged for many months.

I'd be interested in contributing to a fork which targets termbox2, if one exists or will exist.

Termbox2 is very nice, Elixir is very nice, I'd love to see a library which lets you combine them with minimal client effort out of the box.

[katafrakt]

@zachallaun does the fork exist? I was about to try to do that on my own, but decided to check the issues first 😉

[YurkoHoshko]

I have posted my WIP PR that moves over to Termbox2 in case you are interested. Very rough, but seems to work: #15