«

As soon as my sourceforge.net project gets approved, I am going to
build a ncurses port to win32 bindable to sockets, e.g. allowing
VT100/ANSI terminals and the creation of simple terminal servers using
the ncurses API for the UI. I plan to initially support only a subset
of the ncurses lib, leaving the lib open to expansion/completion.

Please stop me if I am going to reinvent the wheel, and tell me if
there are any libraries of this kind.

1. No, I don't want to use cygwin
2. Yes, I know pdcurses, it is great and I plan to use it for normal
ncurses consoles but I need a socket-bound vt100 terminal library...

Thank you!

--
Daniele C.

"Daniele C." <> writes:
> As soon as my sourceforge.net project gets approved, I am going to
> build a ncurses port to win32 bindable to sockets, e.g. allowing
> VT100/ANSI terminals and the creation of simple terminal servers using
> the ncurses API for the UI. I plan to initially support only a subset
> of the ncurses lib, leaving the lib open to expansion/completion.
>
> Please stop me if I am going to reinvent the wheel, and tell me if
> there are any libraries of this kind.

Sorry, this is the wrong place to ask. Try a Windows programming
newsgroup, possibly comp.os.ms-windows.programmer.win32. (Or a Google
search.)

--
Keith Thompson (The_Other_Keith) kst- <http://www.ghoti.net/~kst>
San Diego Supercomputer Center <*> <http://users.sdsc.edu/~kst>
We must do something. This is something. Therefore, we must do this.

In article <>, Keith Thompson <kst-
> writes
>"Daniele C." <> writes:
>> As soon as my sourceforge.net project gets approved, I am going to
>> build a ncurses port to win32 bindable to sockets, e.g. allowing
>> VT100/ANSI terminals and the creation of simple terminal servers using
>> the ncurses API for the UI. I plan to initially support only a subset
>> of the ncurses lib, leaving the lib open to expansion/completion.
>>
>> Please stop me if I am going to reinvent the wheel, and tell me if
>> there are any libraries of this kind.
>
>Sorry, this is the wrong place to ask. Try a Windows programming
>newsgroup, possibly comp.os.ms-windows.programmer.win32. (Or a Google
>search.)

This has bugger all to do with windows. Curses is a portable screen
handling system for terminal windows. I have used the same curses
library on an Atari ST, Dos, Win9* (in a dos window) MAC and various
unix. It is a portable system.

This is precisely the place to talk about the majority of the code for a
curses library. The only difference for the many dozens of terminal
types are the escape sequences. These are usually held in a text file so
you can swap terminal types easily.

Very little of this will be windows or any other OS specific

--
\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\
\/\/\/\/\ Chris Hills Staffs England /\/\/\/\/
/\/\/ www.phaedsys.org \/\/\
\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/

Chris Hills wrote:
> In article <>, Keith Thompson <kst-
> > writes
>> "Daniele C." <> writes:
>>> As soon as my sourceforge.net project gets approved, I am going to
>>> build a ncurses port to win32 bindable to sockets, e.g. allowing
>>> VT100/ANSI terminals and the creation of simple terminal servers using
>>> the ncurses API for the UI. I plan to initially support only a subset
>>> of the ncurses lib, leaving the lib open to expansion/completion.
>>>
>>> Please stop me if I am going to reinvent the wheel, and tell me if
>>> there are any libraries of this kind.
>> Sorry, this is the wrong place to ask. Try a Windows programming
>> newsgroup, possibly comp.os.ms-windows.programmer.win32. (Or a Google
>> search.)
>
> This has bugger all to do with windows. Curses is a portable screen
> handling system for terminal windows. I have used the same curses
> library on an Atari ST, Dos, Win9* (in a dos window) MAC and various
> unix. It is a portable system.
>
The OP is trying to *implement* a networked ncurses on a particular
platform. This is going to involve OS or library-specific stuff, unless you
believe in magic.

> This is precisely the place to talk about the majority of the code for a
> curses library. The only difference for the many dozens of terminal
> types are the escape sequences. These are usually held in a text file so
> you can swap terminal types easily.
>
> Very little of this will be windows or any other OS specific
>
Very little of this will be C specific too, and that's what this newsgroup
is about. There are no questions about the C language here. If there are
questions about what's portable and what's not, that would be another matter.

S.

In article <4470488c$0$31642$>, Skarmander
<> writes
>Chris Hills wrote:
>> In article <>, Keith Thompson <kst-
>> > writes
>>> "Daniele C." <> writes:
>>>> As soon as my sourceforge.net project gets approved, I am going to
>>>> build a ncurses port to win32 bindable to sockets, e.g. allowing
>>>> VT100/ANSI terminals and the creation of simple terminal servers using
>>>> the ncurses API for the UI. I plan to initially support only a subset
>>>> of the ncurses lib, leaving the lib open to expansion/completion.
>>>>
>>>> Please stop me if I am going to reinvent the wheel, and tell me if
>>>> there are any libraries of this kind.
>>> Sorry, this is the wrong place to ask. Try a Windows programming
>>> newsgroup, possibly comp.os.ms-windows.programmer.win32. (Or a Google
>>> search.)
>>
>> This has bugger all to do with windows. Curses is a portable screen
>> handling system for terminal windows. I have used the same curses
>> library on an Atari ST, Dos, Win9* (in a dos window) MAC and various
>> unix. It is a portable system.
>>
>The OP is trying to *implement* a networked ncurses on a particular
>platform. This is going to involve OS or library-specific stuff, unless you
>believe in magic.

SO there will be some OS specific parts of the code. The majority will
not be. Unless this NG is ONLY for pure portable ISO C99 code. As the NG
is not for that he can post here.

>> This is precisely the place to talk about the majority of the code for a
>> curses library. The only difference for the many dozens of terminal
>> types are the escape sequences. These are usually held in a text file so
>> you can swap terminal types easily.
>>
>> Very little of this will be windows or any other OS specific
>>
>Very little of this will be C specific too, and that's what this newsgroup
>is about.

It's written in C which is what this NG is about.

> There are no questions about the C language here. If there are
>questions about what's portable and what's not, that would be another matter.

Wrong. but you are entitled to your opinion.


--
\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\
\/\/\/\/\ Chris Hills Staffs England /\/\/\/\/
/\/\/ www.phaedsys.org \/\/\
\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/

Chris Hills <> writes:
> In article <>, Keith Thompson <kst-
> > writes
>>"Daniele C." <> writes:
>>> As soon as my sourceforge.net project gets approved, I am going to
>>> build a ncurses port to win32 bindable to sockets, e.g. allowing
>>> VT100/ANSI terminals and the creation of simple terminal servers using
>>> the ncurses API for the UI. I plan to initially support only a subset
>>> of the ncurses lib, leaving the lib open to expansion/completion.
>>>
>>> Please stop me if I am going to reinvent the wheel, and tell me if
>>> there are any libraries of this kind.
>>
>>Sorry, this is the wrong place to ask. Try a Windows programming
>>newsgroup, possibly comp.os.ms-windows.programmer.win32. (Or a Google
>>search.)
>
> This has bugger all to do with windows. Curses is a portable screen
> handling system for terminal windows. I have used the same curses
> library on an Atari ST, Dos, Win9* (in a dos window) MAC and various
> unix. It is a portable system.
>
> This is precisely the place to talk about the majority of the code for a
> curses library. The only difference for the many dozens of terminal
> types are the escape sequences. These are usually held in a text file so
> you can swap terminal types easily.
>
> Very little of this will be windows or any other OS specific

He wasn't asking about the code. He wasn't asking how to implement
anything. He was asking whether anyone else had already implemented
such a library *for win32*. That's not a C question.

The Linux kernel is written in C; that doesn't make a question about
porting it to some specific platform topical here. Ditto for any of
the thousands of other software packages implemented in C.

--
Keith Thompson (The_Other_Keith) kst- <http://www.ghoti.net/~kst>
San Diego Supercomputer Center <*> <http://users.sdsc.edu/~kst>
We must do something. This is something. Therefore, we must do this.

"Chris Hills" <> wrote
> In article Skarmander <> writes
>>Chris Hills wrote:
>>> In article <>, Keith Thompson <kst-
>>> > writes
>>>> "Daniele C." <> writes:
>>>>> As soon as my sourceforge.net project gets approved, I am going to
>>>>> build a ncurses port to win32 bindable to sockets, e.g. allowing
>>>>> VT100/ANSI terminals and the creation of simple terminal servers using
>>>>> the ncurses API for the UI. I plan to initially support only a subset
>>>>> of the ncurses lib, leaving the lib open to expansion/completion.
>>>>>
>>>>> Please stop me if I am going to reinvent the wheel, and tell me if
>>>>> there are any libraries of this kind.
>>>> Sorry, this is the wrong place to ask. Try a Windows programming
>>>> newsgroup, possibly comp.os.ms-windows.programmer.win32. (Or a Google
>>>> search.)
>>>
>>> This has bugger all to do with windows. Curses is a portable screen
>>> handling system for terminal windows. I have used the same curses
>>> library on an Atari ST, Dos, Win9* (in a dos window) MAC and various
>>> unix. It is a portable system.
>>>
>>The OP is trying to *implement* a networked ncurses on a particular
>>platform. This is going to involve OS or library-specific stuff, unless
>>you
>>believe in magic.
>
> SO there will be some OS specific parts of the code. The majority will
> not be. Unless this NG is ONLY for pure portable ISO C99 code. As the NG
> is not for that he can post here.
>
And if I write a knitting program, probably the stitch database and most of
the logic will be implemented in portable ANSI C, with only a minor
Windows-specific user interface.
Does that make the knitting / crotchet debate topical here?
>
> It's written in C which is what this NG is about.
>
The difference is that a curses library is something that programmers use.
There is a case for including it in the standard library, though in fact the
ANSI library has no such functions.
>
>> There are no questions about the C language here. If there are
>>questions about what's portable and what's not, that would be another
>>matter.
>
> Wrong. but you are entitled to your opinion.
>
We could allow it, but it would be expanding the scope of the group. I've no
use for a curses system, for instance. If I need a non-stream user interface
I'll use a windowing library, or html forms, or Java.
--
Buy my book 12 Common Atheist Arguments (refuted)
$1.25 download or $7.20 paper, available www.lulu.com/bgy1mm

In article <>, Malcolm
<> writes
>"Chris Hills" <> wrote
>> In article Skarmander <> writes
>>>Chris Hills wrote:
>>
>>> There are no questions about the C language here. If there are
>>>questions about what's portable and what's not, that would be another
>>>matter.
>>
>> Wrong. but you are entitled to your opinion.
>>
>We could allow it,

You can not dis-allow it. You can have no say in the matter. I refer you
to the charter.

--
\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\
\/\/\/\/\ Chris Hills Staffs England /\/\/\/\/
/\/\/ www.phaedsys.org \/\/\
\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/

Chris Hills <> writes:
> In article <>, Malcolm
> <> writes
>>"Chris Hills" <> wrote
>>> In article Skarmander <> writes
>>>>Chris Hills wrote:
>>>
>>>> There are no questions about the C language here. If there are
>>>>questions about what's portable and what's not, that would be another
>>>>matter.
>>>
>>> Wrong. but you are entitled to your opinion.
>>>
>>We could allow it,
>
> You can not dis-allow it. You can have no say in the matter. I refer you
> to the charter.

We certainly do have a say in the matter; we just don't have an
effective enforcement mechanism.

It seems clear to me that any answer to the OP's actual question would
not be based on a knowledge of the C programming language.

--
Keith Thompson (The_Other_Keith) kst- <http://www.ghoti.net/~kst>
San Diego Supercomputer Center <*> <http://users.sdsc.edu/~kst>
We must do something. This is something. Therefore, we must do this.

On 2006-05-22, Keith Thompson <kst-> wrote:
> Chris Hills <> writes:
>> In article <>, Malcolm
>> <> writes
>>>"Chris Hills" <> wrote
>>>> In article Skarmander <> writes
>>>>>Chris Hills wrote:
>>>>
>>>>> There are no questions about the C language here. If there are
>>>>>questions about what's portable and what's not, that would be another
>>>>>matter.
>>>>
>>>> Wrong. but you are entitled to your opinion.
>>>>
>>>We could allow it,
>>
>> You can not dis-allow it. You can have no say in the matter. I refer you
>> to the charter.
>
> We certainly do have a say in the matter; we just don't have an
> effective enforcement mechanism.

The problem is that it's not clear what authority your opinion on what
was the pre-existing "scope of the group" which "allowing" this would be
"expanding" is based on.

> It seems clear to me that any answer to the OP's actual question would
> not be based on a knowledge of the C programming language.