From: Tee Y Teoh <tee_yong.teoh@alcatel.com>
To: egcs@cygnus.com
Cc: sourcenav@sources.redhat.com
Subject: Re: silly question : how long would it take to make SN Gnome-complian t?
Date: Tue, 19 Sep 2000 06:32:00 -0000 [thread overview]
Message-ID: <39C76ABA.387D5BC7@alcatel.com> (raw)
In-Reply-To: <39C765A4.4403EC37@redhat.com>
Ian Roxborough wrote:
> Maintain two UIs, one GTK compliant, one for the rest
> of the work, just won't fly.
What about porting to wxWindows ? wxWindows is support on MS-Windows, Unix/Motif,
Unix/GTK, and Mac (with work going on for OS/2). wxWindows is written in C++
and has a Python binding. See http://www.wxwindows.org/ for more info.
Regards
Tee Teoh
next prev parent reply other threads:[~2000-09-19 6:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-19 3:11 William Gacquer
2000-09-19 3:34 ` silly question : how long would it take to make SN Gnome-comp lian t? Bruce Stephens
2000-09-19 6:10 ` silly question : how long would it take to make SN Gnome-complian t? Ian Roxborough
2000-09-19 6:32 ` Tee Y Teoh [this message]
2000-09-19 6:44 ` Bruce Stephens
2000-09-19 11:54 ` silly question : how long would it take to make SN Gnome-compliant? Ben Elliston
2000-09-24 17:59 ` silly question : how long would it take to make SN Gnome-complian t? Mo DeJong
2000-09-24 17:46 ` silly question : how long would it take to make SN Gnome-comp lian t? Mo DeJong
-- strict thread matches above, loose matches on Subject: below --
2000-09-25 0:47 silly question : how long would it take to make SN Gnome-complian t? William Gacquer
2000-09-19 7:42 William Gacquer
2000-09-19 6:44 William Gacquer
2000-09-19 7:05 ` Ian Roxborough
2000-09-19 2:44 silly question : how long would it take to make SN Gnome-compliant? William Gacquer
2000-09-19 2:56 ` silly question : how long would it take to make SN Gnome-complian t? Bruce Stephens
2000-09-19 3:15 ` Florent Pillet
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=39C76ABA.387D5BC7@alcatel.com \
--to=tee_yong.teoh@alcatel.com \
--cc=egcs@cygnus.com \
--cc=sourcenav@sources.redhat.com \
/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).