On Jun 3, 2011, at 6:48 PM, Ken Shmidheiser wrote:

Brian wrote:

Developing an FB-style BASIC that uses Cocoa is undoubtedly difficult. While it may not be desirable, anything in a Cocoa nib can be written in Objective-C code, so Cocoa nibs per se are not a technical obstacle.

In response to Brian's thoughts, I simply cite the first note on this page:


Yes, thanks Ken. Point well taken and already understood.  However, it doesn’t contradict my point: it is technically *possible* to write Objective-C code for anything in a Cocoa nib. The link to the Apple page is advice and direction for application developers. I’m looking at it from a system perspective and what it takes to allow FB to work with Cocoa. Clearly, an Objective-C/Xcode programmer should always be using nibs for UI apps but I’m talking about tools for FB programmers. Maybe it is possible to write code that reads a Cocoa nib and outputs Objective-C. This kind of scenario allows the user to work with the nib. Yes, there are all sorts of issues with this concept ( how to connect outlets and actions being one of them ).

The majority ( and probably more like 90%+ ) of FB users need a high level interface to APIs and (IMO) will not make the transition to being an Xcode/Objective-C/Cocoa programmer. Xcode/Objective-C/Cocoa is difficult and complex for the casual/hobbyist programmer ( or part-time programmer who uses FB to supplement their work assignments ) and is clearly oriented to knowledgeable/dedicated professional programmers.

As noted in a prior post, another procedural Mac BASIC was able to incorporate Cocoa. The link has a crude and unimpressive demo built from approximately 30 lines of Blitz Max code. Run the executable through LegacyAPISurvey and it will show ZERO legacy APIs used. This is because their GUI module uses Cocoa.


Brian S

To unsubscribe, e-mail: fbcocoa-unsubscribe@... For additional commands, e-mail: fbcocoa-help@...