Re: wxWindows and GNOME

Robert Roebling wrote:

> I want GNOME to be able to say: "We give you the choice: you can do
> it the 100% pure GNOME way which means: less overhead, usage of true
> GNOME code everywhere and dependence on the latest GNOME 1.0.13p5 to be
> installed or your program won´t run anywhere; or you can write programs
> that will run with the same source code on just about any platform
> on this planet, even in the very absence of any trace of GNOME, but
> at the prize of using a totally different API".

How does including wxGTK with GNOME make that paragraph any more 
or less true than it was the day the wxGTK port was announced? 
By the same token, now that V has a GTK driver abailable, why 
should one be chosen over the other?

Both of these toolkits are excellent gui abstraction layers, as
evidenced by the fact that they work on the wide variety of 
platforms that they do (windows, macs, half a dozen X widget sets).
Gtk-- shows promise as a thin c++ wrapper around most of GTK, and 
some amount of GNOME as well.  Gtk-- is unique in the aspect that
it only seeks to wrap c++ bindings around the "standard" GTK/GNOME
APIs.  wxWindows and V create a whole new layer of abstraction,
which is necessary to achieve their goal of cross platform portability
using native toolkits.  I beieve GNOME seeks to achieve cross 
platform portability by porting the toolkit.

However, none of these options are, strictly speaking, GNOME, so 
I fail to see the point in distributing any of them as part of GNOME.
They are all "extra" support libs (as is perl/gtk, gnome-objc, etc),
which offer additional language bindings for the developer, and 
extra dependencies for the user... =7

>   Robert
> Robert Roebling <>

-- ebm
|  __                         a.k.a. Eric B. Mitchell |
|  |_) .  _  _|      _|  _    |
|  | \ ( (_ (_| (_| (_| (/_  |
| How's My Programming?   Call:  1 - 800 - DEV - NULL |

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