From: "David Botton" <David@Botton.com>
To: <comp.lang.ada@ada.eu.org>
Subject: Re: GUI development: Windex vs. GTK vs. Anything else
Date: Tue, 2 Jan 2001 17:18:31 -0500
Date: 2001-01-02T17:18:31-05:00 [thread overview]
Message-ID: <00d901c07509$f0e886a0$f8ffa8c0@dbdell2000> (raw)
In-Reply-To: t54gaub18soia8@corp.supernews.com
Your multi-platform choices are GtkAda (www.adapower.com/gtkada) or TASH
(www.adatcl.com). Both have GUI builders (TASH has more the one). Both
Modified GPL.
For Win32 development your best bets are CLAW (www.rrsoftware.com) or
GWindows (www.adapower.com/gwindows), with GWindows having a Modified GPL
lic.
What sort of specialized GUI work are you referring to?
David Botton
----- Original Message -----
From: "Jesse Farmer" <tujuggernaut@gmx.net>
> Sub. says most of it.
> I'm looking for opinions on what to use for developing a GUI for an
> application that is intended to be developed across Win, Mac, and Linux
> platforms. This application will quite likely need some specialized gui
> work, so standard widgets won't get it entirely done.
>
> Best approach? Use api bindings like Windex and the respective binding
for
> Mac, and Xwindows-gnome stuff?
> Or try using GTK since it is supported across all of those platforms?
>
> It should be obvious that the application in question is being coded in
Ada.
> Windows in the primary development target, all others are secondary
> concerns.
>
> Any advice would be welcome!
> -Jesse Farmer
next prev parent reply other threads:[~2001-01-02 22:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-02 20:58 GUI development: Windex vs. GTK vs. Anything else Jesse Farmer
2001-01-02 22:18 ` David Botton [this message]
2001-01-02 23:01 ` Ted Dennison
2001-01-08 12:26 ` charlet
2001-01-02 22:30 ` r_srinivasan
2001-01-03 2:20 ` tmoran
2001-01-02 22:31 ` John English
2001-01-03 0:24 ` Jesse Farmer
2001-01-03 1:07 ` David Botton
2001-01-03 2:20 ` tmoran
2001-01-03 22:54 ` Jesse Farmer
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox