• 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: newbie alert: i'm confused: The XCode Quick Tour Guide
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: newbie alert: i'm confused: The XCode Quick Tour Guide


  • Subject: Re: newbie alert: i'm confused: The XCode Quick Tour Guide
  • From: Quincey Morris <email@hidden>
  • Date: Sat, 9 Feb 2008 01:09:15 -0800


On Feb 8, 2008, at 23:47, George Greene wrote:

Now the question. How did you know to do that? I mean what should I be reading in-order to learn how to do that.

Well, as far as that goes, you're the victim of the documentation being out of date, temporarily.



I tried:
1). creating the project
2). opening the nib file
3). dragging an Custom View object into the main nib window
4). writing the .h and .m by using interface builders File > Write Class Files...
they were create but not seen by XCode.
5). i read in the Class, well i thought by using File > Read Class Files...
but the files still did not show up in XCode. ( .h and .m file) i could see the h. and .m folders in the
project's folder using the finder, but not in XCode's Project Interface.


you mention there are probably other ways, yours seem to be the right way to think about though.
was i anywhere close to having a working solution... was there someway to get XCode to read in those files?

I haven't used Write Class Files in 3.0. You used to get a dialog asking if you wanted to add the files to the project, and you can still get that result manually (drag the files from the finder into the project window).


The problem with Write Class Files is that you'd probably only want to ever do it once. After that, if you'd added source code to the files manually, you wouldn't want to define new outlets or actions in IB and trust IB to preserve what you'd added.

The problem with Read Class Files is that if the class isn't in your project (the files aren't in the project window) IB doesn't seem to pay any attention to the files' contents -- since the class isn't in your project. (doh!)

In 3.0, the IB and PB applications are tightly integrated, so I'm not sure there's ever a reason to use Read Class Files any more.

_______________________________________________

Cocoa-dev mailing list (email@hidden)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


References: 
 >newbie alert: i'm confused: The XCode Quick Tour Guide (From: George Greene <email@hidden>)
 >Re: newbie alert: i'm confused: The XCode Quick Tour Guide (From: Quincey Morris <email@hidden>)
 >Re: newbie alert: i'm confused: The XCode Quick Tour Guide (From: George Greene <email@hidden>)

  • Prev by Date: Re: CoreData: Save password securly
  • Next by Date: Clicking in an attributed TextField
  • Previous by thread: Re: newbie alert: i'm confused: The XCode Quick Tour Guide
  • Next by thread: wired things about NSApp Modal
  • Index(es):
    • Date
    • Thread