From: hgfernan@usp.br
To: "Gnu-Win32 Mailing List"<gnu-win32@cygnus.com>,
Brendan Simon <BSimon@randata.com.au>,
vgui-discuss@attila.apana.org.au
Cc: "Fernandes, Hilton" <hgfernan@usp.br>
Subject: RE: Compiling "V" 1.16 - Specific Instructions?
Date: Mon, 29 Dec 1997 20:04:00 -0000 [thread overview]
Message-ID: <9712300407.AA37836@spider.uspnet.usp.br> (raw)
In-Reply-To: <c=AU%a=_%l=MELADMIN-971226012241Z-988@meladmin.randata.com.au>
On 26 Dec 97 at 12:22, Brendan Simon <BSimon@randata.com.au> wrote:
> >
> >> Please be warned that V is mainly a Unix GUI library; its
> >> support to Windows 95/NT is still to be done. People wanting to
> > program for Win95/NT should take a look at wxWindows.
> >> Maybe wxWindows should be added to Cygnus page.
> >
> THIS IS DEFINATELY INCORRECT !!!
>
> V has both X Windows AND MS-Windows support.
Hi, Brendan!
I'm sorry if i was incorrect. I appreciate the V library and its
community, and don't want to be unfair with any of them.
Internet and computing in general changes very quickly, so it's very
easy to have information no longer current.
Maybe you can help enlighten me and this mailing list about V making
the necessary corrections to what i'm going to relate.
I first heard about V in the famous paper by Prof. Wampler, V's
creator, published in C/C++ Users Journal (Aug/96). Prof. Wampler
related that he designed a multiplatform class library and was using
it to teach his students about object-oriented programming and
interface design.
I'm a C++ instructor and i'm constantly embarrassed by the "good" o-o
design principles followed in the construction of MFC. So i was
very interested when i read Prof. Wampler's paper. But prudence
advised me to take some time before jumping into V and preparing
classes to my students. To that purpose i subscribed V mailing list
and read its messages for a while.
From what i could see, in that times (circa 1996) several people
were having problems with V's window implementation. I'm not saying
that V didn't compile, but people related that in some cases V didn't
work correctly under Windows.
Then in several messages, experienced users advised beginners that
they should consider V a Unix-oriented class library. This wasn't
emphatically contested then.
I thought that was still the case when i read V's page: they say
that Windows support is still missing.
Maybe that was just a misunderstood, but i'd like to ask your opinion
about it.
Thank you for the attention,
++Hilton
-------------------
Hilton Fernandes
email: hgfernan@usp.br
www: http://www.lsi.usp.br/~hilton.html (inactive)
M. Sc. Student of Parallel Distributed Applications
at Escola Politecnica (Polytechic School)
University of S. Paulo - Brazil
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
next prev parent reply other threads:[~1997-12-29 20:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-12-25 17:18 Brendan Simon
1997-12-29 20:04 ` hgfernan [this message]
1997-12-30 5:58 ` [VGUI] " msphil
[not found] <349FE59A.2098DF17@cyberramp.net>
1997-12-23 15:07 ` hgfernan
-- strict thread matches above, loose matches on Subject: below --
1997-12-18 16:04 dahms
1997-12-18 11:21 Rick Miller
1997-12-22 18:59 ` hgfernan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9712300407.AA37836@spider.uspnet.usp.br \
--to=hgfernan@usp.br \
--cc=BSimon@randata.com.au \
--cc=gnu-win32@cygnus.com \
--cc=vgui-discuss@attila.apana.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).