Lacking encoding, perhaps. Lacking key elements of nib decoding doesn't make sense at all. Their example may work, but I have a feeling that many, more complex apps, won't. GJC
-- Gregory Casamento ## GNUstep Chief Maintainer ----- Original Message ---- From: Renaud Molla <[EMAIL PROTECTED]> To: Gregory John Casamento <[EMAIL PROTECTED]>; discuss-gnustep@gnu.org Sent: Tuesday, December 26, 2006 10:52:25 AM Subject: Re: Cocotron These lacks seem somewhat "logical" within their goal that seems to be enabling cross compilations from Mac OS X to Windows, and the use of OS X tools to create software. On Dec 26, 2006, at 4:47 PM, Gregory John Casamento wrote: > 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 <[EMAIL PROTECTED]> > 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 > > > > ---------------------------------------------------------------------- > ----------------- > Orange vous informe que cet e-mail a ete controle par l'anti-virus > mail. > Aucun virus connu a ce jour par nos services n'a ete detecte. > > > _______________________________________________ Discuss-gnustep mailing list Discuss-gnustep@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnustep _______________________________________________ Discuss-gnustep mailing list Discuss-gnustep@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnustep
