• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: NSView Names
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: NSView Names


  • Subject: Re: NSView Names
  • From: Graeme Hiebert <email@hidden>
  • Date: Thu, 28 Feb 2002 17:24:01 -0800

On Thursday, February 28, 2002, at 09:36 AM, Matt Neuburg wrote:

As a REALbasic user who is switching to Cocoa, I like almost everything
about Cocoa better than REALbasic. This is the rare exception. In REALbasic
every object in the "physical" part of the IDE (the equivalent of IB) has a
global name, and this name is accessible from the "code" part (the
equivalent of PB). In other words, it works more like AppleScript Studio.

How do you handle things like documents, where there may be multiple copies of a window open at a time? (I'm curious about the answers both for RealBASIC and AS Studio. I've played with the Studio, but haven't been able to figure out how to have different "instances" of a script, each with its own set of properties.)

<snip>
This business of shuttling back and forth between PB and IB drawing
connections and inserting outlet accessors drives me nuts; because of it,
it takes much longer to write a simple Cocoa app than the equivalent simple
REALbasic app, as audience members saw when I demonstrated both in my talk
at Macworld Expo last month.

You really only have to shuffle back and forth that much. You can add all of your outlets and actions in IB, and then do a "Create Files" (under the "Classes" menu) when your class is selected. It will bring up FileMerge to let you merge the changes into your document, then you can go back and add the actual code.

It would be great to have an easier way to
close the gap between PB code and IB names. Perhaps this could be an
NSBundle method, e.g. objectWithName:nibNamed: or something. m.

It certainly would be useful. I'd love to see better access to the nib file in general, to the point of being able to dissect and create them programmatically. It would be really cool to be able to make tools to "import" user interfaces from other systems, like RealBASIC, Delphi and Gorm.

-g
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.

References: 
 >Re: NSView Names (From: Matt Neuburg <email@hidden>)

  • Prev by Date: Re: Multiple Line Help Tags
  • Next by Date: Sheet!
  • Previous by thread: Re: NSView Names
  • Next by thread: Re: NSView Names
  • Index(es):
    • Date
    • Thread