Re: GNUstep on MS Windows

[Pascal J . Bourguignon]

Helge Hess writes:
> a) cross-CPU, like NeXTstep for i386, SPARC, HP and m68k
> b) cross-OS, like X11 on Windows, Linux and MacOSX
> c) cross-UI, like SWT using gtk+ on Linux and Win-UI on Windows
> 
> IMHO GNUstep/AppKit on Windows is pretty useless. OpenStep is the wrong 
> technology to do option c) above. It can do a) and b), but a) doesn't 
> solve the Windows issue and b) provides little value.

What  do you  mean exactly  by  "GNUstep/AppKit on  Windows is  pretty
useless"?

I thought that it was clear that an implementation of the OpenStep API
on MS-Window would open markets to GNUstep and MacOSX developers, this
would not be useless.

Why do you think that "OpenStep is the wrong technology to do option c)"?

It seems  to me that it has  been designed and a  sufficient number of
implementation have been made to implement this cross-UI. OpenStep ran
on Solaris, and on MS-Windows-NT, and  now runs on MacOSX and on Linux
or other unix with GNUstep. 


I guess  that you're saying that  since GNUstep is  drawing itself its
widgets, it can't provide cross-UI.

But it seems  to me that the drawing code  is rather well encapsulated
(in a  few drawing methods of  a little number  of graphical classes),
and  that it should  be possible  to either  fork a  theme, or  to use
MS-Windows widgets to do the actual drawing.

-- 
__Pascal_Bourguignon__                          http://www.informatimago.com/
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Living free in Alaska or in Siberia, a grizzli's life expectancy is 35 years,
but no more than 8 years in captivity.           http://www.theadvocates.org/