[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: ncurses++ and maintenance thereof

From: Thomas Dickey
Subject: Re: ncurses++ and maintenance thereof
Date: Thu, 24 Oct 2002 19:16:53 -0400
User-agent: Mutt/1.3.27i

On Thu, Oct 24, 2002 at 04:56:05PM -0400, L. Dee Holtsclaw wrote:
> 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?

I make occasional bug-fixes.  The classes as they exist now are mostly
Juergen's work.

> 2. Are these classes in enough use to prohibit renaming some members?

I don't know.

> 3. Is there any reason NOT to use some STL in the implementations?

perhaps not.
> 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?

not exactly.  I maintain an FAQ but it's focused on the ncurses library.

Thomas E. Dickey <address@hidden>

reply via email to

[Prev in Thread] Current Thread [Next in Thread]