ncurses++ and maintenance thereof

[L. Dee Holtsclaw]

I've been working with the C++ interface classes for the last few days
and it's become apparent that I need some items which the classes do not
provide. Although deriving from a class will solve the difficulties, it
seems grotesquely stupid to override practically every method when
adding a member to the original class would do. Additionally, the
haphazard naming conventions (um, presuming there are any) and spaghetti
organization of the code make perusal difficult and, I'm sure,
maintenance a joy.

So... This brings the following questions:
1. Is anyone maintaining these classes and, if so, how do I contact?
2. Are these classes in enough use to prohibit renaming some members?
3. Is there any reason NOT to use some STL in the implementations?

FYI, Some of the functionality I intend to add:
1. Menu choices displaying details on a "status line" if so allocated
2. Current field details ditto
3. ESC key additionally available to exit-cancel a menu or form
4. Accessing Pad driver outside of Pad's own loop (for an external loop)
5. Swapping in new SLKs for active forms/fields

Already implemented #1 & 4 but it's with non-derived replacement
classes.

Thanks!

Ciao,
Dee
(Lawrence D. Holtsclaw)
Senior Software Engineer
Sunbelt Software Solutions, Inc.
Chattanooga, TN USA

P.S. Is there a FAQ for this list?