Re: XML idea

[Nicola Pero]

> It would be nice if the PortabilityKit team finished some of the classes
> that are semi-portable between GNUstep and Cocoa (such as the
> NSDocument architecture, for example). 
> Do the PortabilityKit team plan to submit fixes for classes already in
> GNUstep?

If what they want to achieve is easy portability, it would be criminal if
they didn't finish the unfinished classes in GNUstep :-)

 
> From the other side, I think GNUstep should remove 
> poorly-designed / unfinished classes (like NSToolBar and NSDrawer)
> and let the PortabilityKit team implement them.

Why don't they just finish those classes and contribute them to GNUstep ?

It's easy to make everyone happy with stuff like NSToolBar.  We put an
implementation in gnustep-gui.  If you are an OpenStep purist and don't
want to use it, you don't use it - you can ignore it.  If you are an
Apple-compatible guy and want to use it, you use it.  I don't see why we
should remove NSToolBar from gnustep-gui.  The problem arises when adding
Apple compatibility pollutes or confuses the original OpenStep classes
(then, we need a "superior workaround").  Adding an additional separate
class does not.