Decoupling?

[dotmilk]

In the original issue, decoupling was mentioned. Has work begun on that? I have a little bit of time, and have been reading the codebase, but have yet to really find where the 'ncurses' like stuff ends and the gui / widget api begins.

If you could point me to a couple lines of code where the lowest level use of the ncurses like library written is used by the gui api, I would like to help with the decoupling.

[piranna]

In the original issue, decoupling was mentioned. Has work begun on that? I have a little bit of time, and have been reading the codebase, but have yet to really find where the 'ncurses' like stuff ends and the gui / widget api begins. Decoupling has not started, so you are free for that :-) I find codebase splitted on three diferent layers: widgets (like textarea or terminal, mostly at the 'widgets' folder), core widgets (like screen or box) and low level (ncurses like). If you could point me to a couple lines of code where the lowest level use of the ncurses like library written is used by the gui api, I would like to help with the decoupling. Instead of going directly to the low level APIs (splitted between tput.js and the screen widget, so this one would need to be splitted itself, and also ideally define an AbstractScreen or SubScreen class too), I would go top-to-bottom, starting by moving out first the widgets with external dependencies like terminal and the high level ones. This will reduce the code a lot and just left to decide what remaining parts are low level or core ones (or could be moved to the high level widgets...).