Re: Cocotron

[Gregory John Casamento]

Actually, after a second look the nib does contain the connections.   I'm not 
sure why I didn't see them at first.

From looking at the decoding logic, there are keys missing in classes such as 
NSCell and others.   The nib decoding isn't complete and the encoding is not 
present.

GJC
 
--
Gregory Casamento
## GNUstep Chief Maintainer

----- Original Message ----
From: Renaud Molla <renaud.molla@wanadoo.fr>
To: discuss-gnustep@gnu.org
Sent: Tuesday, December 26, 2006 5:22:01 AM
Subject: Re: Cocotron

First of all,
I join the cocotron thread after several posts and may say things  
already said in previous messages.

I tried the cocotron textedit example, and to be true, i first  
thought this was an hoax since I downloaded it and it worked as is.
So i changed the NIB with Interface Builder to check this was really  
true, addes a Label and A button,
and it worked, so i guess claims that they're experiencing nib  
reading problems can't be totally true.

What stroke me (positively) is that their example worked after  
unzipping, nothing more to do.
The application integrates well within the OS look and feel, i mean,  
I'm a mac os x user and really like
the top menu bar and the floating menu concept of openstep, but to  
most windows or other APIs (gtk/kde/etc...)
with menus right below the title bar, the menus are rather reluctant.  
(what a pity however).

I think it really is straightforward to see that cocotron and gnustep  
do not share the same goals.
They must have common "subprojects" in order to comply with the  
OpenStep specifications,
but it is clear that the end user/deployment philosophy is not the same.

Renaud.



_______________________________________________
Discuss-gnustep mailing list
Discuss-gnustep@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnustep