Re: GNUstep Cocoa compatibility

[Stefan Urbanek]

Hi,

I am moving this to gnustep-dev...

On 3.3.2006, at 17:47, Adam Fedor wrote:

> On 2006-02-21 08:07:01 -0700 Dmitri Sotnikov  
> <address@hidden> wrote:
>
> > Hi,
> > I understand that both the Cocoa API and GNUstep inherit from the  
> > NeXTSTEP
> > API, having read the documentation at gnustep.org, I notice that
> > it is already possible to cross-compile basic applications between  
> > Cocoa and
> > GNUstep, so I was wondering if it is one of project goals to  
> > eventually
> > have full cocoa compatibility.
>
> You can read here about our mission
>
> http://www.gnustep.org/information/mission.html
>
> Cocoa compatibility is a goal, but one that is almost impossible to  
> fully achieve.

To what exact point it is a goal? What is on "the radar" and  what is  
not?

What are the definitions of sets depicted in the following diagram?

http://stefan.agentfarms.net/Download/GNUstep/DesignNotes/GNUstep% 
20and%20Cocoa.png

Clear definition would help.

For example, I am now developing "on the real thing", but I would  
like to keep GNUstep compatibility. To achieve this, I need a clear  
list of what I can use and what I can not use from Cocoa. That is, I  
need to know, what is planned for gnustep (does not have to be fully  
implemented at this time) and what is not going to be in gnustep in  
any way.

Stefan Urbanek

p.s.: Btw. why is old OpenStep compatibility so important? Is not new  
OpenStep what we define now by defining API that is common for  
GNUstep and Cocoa??
p.p.s: from the mission statement: "We won't remove things, even if  
they have been removed by Apple." why not, regardless of apple? Death  
is so natural to life...
--
http://stefan.agentfarms.net

First they ignore you, then they laugh at you, then they fight you,  
then you win.
- Mahatma Gandhi