Blacken need not tie itself to Curses behavior

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Notice that other similar libraries distance themselves from Curses.
2. Notice that Blacken 1.0 tries to mimic the Curses API.
3. Suspect that makes Blacken harder to use than other APIs.

What is the expected output? What do you see instead?

Most of the curses-like functions are implemented using simpler calls.

Split out the Curses-like functions to an overlay that rests on top of a 
simpler terminal interface.

Original issue reported on code.google.com by yam...@gmail.com on 1 Aug 2012 at 7:41

[GoogleCodeExporter]

This is particularly the case with the whole concept of the "update cursor" 
then -- because you want them to be separate -- you have this whole weird 
"separate cursor" thing and functions which either use the visible cursor 
position or the update cursor position, etc.

It's much simpler to drop it. The curses-like interface has a unified 
update/visible cursor, and the non-curses interface only has a visible cursor 
(without an implied update location except when explicit getstring calls are 
made).

Original comment by yam...@gmail.com on 1 Aug 2012 at 7:44

• Changed state: Verified