Re: [sc-users] gnustep?

["Vytautas Jancauskas" <unaudio@xxxxxxxxx>]

Porting from Cocoa or OPENSTEP (NS*) to GNUstep

Porting from Cocoa or OPENSTEP to GNUstep has different aspects. First there is the compatibility of the basic Foundation Kit and Application Kit. We support a lot of classes, but not all of them and the same is true for specific methods, specifically newly introduced classes and methods in Cocoa may still be missing as GNUstep started out aiming at OpenStep compatibility.

Second you have all the additional frameworks and libraries programmers on Mac OS X take for granted, for some of them free replacements exists, for most they are still missing. Mac OS X developers should try and avoid CoreFoundation as this will complicate your dependency situation on non-Mac hosts, even if that part of CoreFoundation has actually been ported. GNUstep Base and the FoundationKit offer many parts of the CoreFoundation functionality in a natural Objective-C manner. To be a bit more specific:

• don't use Core* (CoreFoundation, CoreSound, CoreAnimation, ...)
• don't use KeyChain
• don't use Carbon
• don't use Quartz
• don't use QuickTime
• don't use WebKit (GCC 4.1 and up support ObjC++, but currently, there exists no WebKit port for GNUstep)
• don't use altivec features or the vecLib.framework (a collection of functions for vector manipulation, an Apple specific extension)
• don't use anything else we do not provide

If you committed none of these portability evils, the rest is relatively straightforward:

1. Write a new GNUstep make file for the project (very easy, still there is currently no automatic way to do so).
2. Make sure the Nib files are readable by GNUstep.
   1. When saving a NIB file in project builder, ensure that "10.2 or later" format is selected. Also, ensure that "Use text archive format" is NOT checked, as this created problems.
   2. Another option is to load them into Gorm and convert them into .gorm files. If they're from OPENSTEP or Mac OS X 10.1 or earlier, see below.
3. Provide an Info.plist.

From their wiki i think

On Sat, Dec 27, 2008 at 11:17 AM, Vytautas Jancauskas <unaudio@xxxxxxxxx> wrote:

http://www.gnustep.org/resources/documentation/Developer/Gui/Reference/NSView.html
I have no idea what so ever about gnustep or osx programming but i was under impression that porting from osx to gnustep is extremely easy since they are pretty much the same API is that not so?

On Thu, Dec 25, 2008 at 1:34 PM, blackrain <blackrain.sc@gmail.com> wrote:

all of sc's gui views are drawn controls on top of a NSView placed on
a window; except for the scrollers.
porting the code to gnustep, or any other gui toolkit implies a full
implementation of the views hierarchy and widgets.

cheers,

x

On Wed, Dec 24, 2008 at 4:26 PM, Vytautas Jancauskas <unaudio@xxxxxxxxx> wrote:
> Was it ever tried porting the GUI part of supercollider to gnustep? If so
> with what results if not why?
>

_______________________________________________
sc-users mailing list

info (subscription, etc.): http://www.beast.bham.ac.uk/research/sc_mailing_lists.shtml
archive: https://listarc.bham.ac.uk/marchives/sc-users/
search: https://listarc.bham.ac.uk/lists/sc-users/search/