Interface Builder w/ Xcode folder refs

when i set up xcode with folder refs interface builder does not see my images in the dropdown list. i actually have to type out the path and ib will show a broken image. is there anyway to fix this?

Note that *AppleScript Studio* has been deprecated in Snow Leopard - AppleScriptObjC is the new framework. You can still edit Studio projects, but the project templates have been removed and you will need to enable the AppleScript palette - see the release notes.
Assigning a handler (IBaction) to a button (or any object) is pretty easy - create a handler in your script that takes a single parameter and name it with a trailing underscore (the naming conventions are also in the release notes), for example:on doButtonStuff_(sender) it will appear in *Interface Builder* under the *Connections Inspector* for your application delegate - from there you can make a connection from your object to the handler. MacScripter has some tutorials for AppleScriptObjC in Xcode, and I also have a button example project (it's not much of a tutorial, though).

Similar Messages

Trying to create first iPhone app, use Interface Builder or Xcode first?

I'm trying to create my first iPhone App, do I start with Interface Builder or Xcode first? And how do I link the two together?

It's not really that simple -- you'll be working with both. Interface Builder is used to design the GUI (graphical user interface, which consists of the windows and buttons and text fields and so forth, the parts of the application that your user interacts with). Xcode, on the other hand, is used to write the code that tells that GUI what it's supposed to do, and how to do it. So, to answer your question as best I can -- generally, I would imagine you would want to start by creating the basic form of your GUI in Interface Builder and then start coding where appropriate in Xcode, then you'll move back and forth between the two (Xcode and Interface Builder) as needed.
If you're new to programming and want to start with iPhone apps, I recommend picking up a book on the topic (Apress publishing has a book called "Beginning iPhone 3 Development: Exploring the iPhone SDK" that is a good one, and don't forget to take advantage of Apple's iOS Dev Center, which has lots of good documentation on most any topic that will be helpful in supplementing the information in the book you buy -- click [here|http://developer.apple.com/iphone/index.action] to go there).
Keep in mind, however, that trying to learn to program iPhone apps will be difficult (to say the least) if you don't already know Objective-C, and the Apress book I recommended above will not be easy to follow without understanding Objective-C first. Objective-C an object-oriented extension of C, and it is the programming language that is used to develop iOS apps (apps for the iPhone, iPod touch, or iPad). I would definitely recommend learning Objective-C on the Mac before jumping in to iPhone development in specific. Apress has another book called "Learn Objective-C on the Mac" that I would recommend for this.
Furthermore, since Objective-C is an extension of C, you won't have an easy time learning it without a prior understanding of the C programming language. Again, Apress has a book for this, called "Learn C on the Mac."
Put simply, learning to program for the iPhone is not something that comes overnight -- it's a step-by-step process that takes patience, and you have to be willing to go through these steps if you want to learn to program properly for the iPhone.
Step 1 -- learn the C programming language
Step 2 -- learn the Objective-C programming language
Step 3 -- apply your knowledge to developing for iOS (iPhone's operating system) with the Cocoa Touch framework
Anyways, that's just my advice -- I definitely recommend taking the time to do it right and not jumping straight into the deep end, but in the end only you know what works best for you. Also, like I said, I definitely think investing in a book on the subject is worth the time and money, so let me know if you want any other recommendations for books beyond the ones listed above.
Hope this was helpful to you, and best of luck with your journey toward programming for iOS.

Interface builder and xcode

ok, im a complete newbie to xcode and interface builder,
so, wen i try to make a connection for a new outlet and click 'files owner', all it shows is 'delegate', instead of files tat i hav in my resource folder, or the files im supposed to hav, anyone could help me on this? it would be appreciated greatly, thx

Hello joshup7 & welcome to the forums...
Generally speaking, you first need to properly specify items in your templates/code (*.m & *.h files) in Xcode and then they will show up when making connections in IB. Who/what/where/why depends on your specific code, naming conventions, etc.
See this page from Apple:
http://developer.apple.com/iphone/library/documentation/DeveloperTools/Conceptua l/IB_UserGuide/Introduction/Introduction.html
And this sample/tutorial that should cover the basics:
http://www.iphonesdkarticles.com/2008/07/first-iphone-application.html
...see the section on 'Connecting Instance Variables'.

Can I upload apps made with xcode Interface Builder to the App Store

Like my title says Can I upload apps made with xcode Interface Builder to the App Store? I'm currently making an app with the interface builder from xcode and I was wondering if I could upload it like that to the App Store.
Please help me with this.

Hi seba,
In order to be able to submit apps to the App Store, you need these things:
1. An Apple ID
2. Join the Mac developer program ($99) https://developer.apple.com/programs/mac/
Once you've got these, you're free to submit your created applications to the App Store. It should walk you through the process

Create an Xcode / Interface Builder Application Written In AppleScript

Hi.
I've got what's probably a stupid and easy question.
I have some AppleScript programs that I'd like to create custom interfaces for.
I've read about AppleScript Studio.
I've read that to create an Xcode project written in AppleScript, you can just select 'AppleScript Application' from the New Project window.
However, the New Project window that I get looks entirely different (newer) and the closest thing that I can find is 'Cocoa-AppleScript application', which doesn't work.
So, is there a way for me to use Interface Builder and Xcode with my AppleScript programs, short of learning Objective-C and converting everything?
I'm using 10.6.2, Xcode & Interface Builder 3.2.1.
Thanks in advance!

You don't really need to know Objective-C, although it does help a bit with understanding the examples and code snippets in the Cocoa documentation. See my reply to your other topic.

How to instantiate a control in code instead of using Interface Builder ?

I really appreciate the combination of the interface builder and Xcode altogether.
However when I am learning QT, I realize I had been pampered by Apple's Design to a certain extend as I only need to create say a NSLabel instance and use Interface Builder to do the linking and never have to worry about instantiating the Object myself.
But I'm curious, what is the way to instantiate a new hmmm say...NSLabel in the code ?
NSLabel* label = new NSLabel();
Then what ?
What you are seeing here is how QT did it, could anyone create an equivalent in ObjC ? No fancy code please, just bare minimum.
#include <QApplication>
#include <QWidget>
#include <QLabel>
int main (int argc, char * argv [ ])
QApplication app(argc, argv); //NSApplication in ObjC
//These two lines merely created a window and set the title bar text.
QWidget* window = new QWidget();
window->setWindowTitle("Hello World");
QLabel* label = new QLabel(window);//Create a label and inform the it belongs to window.
label->setText("Hello World");
window->show();
return app.exec();
Message was edited by: Bracer Jack

Hi Jack -
I think my best answer will be something of a disappointment, because I don't know how to show a one-to-one correspondence between the code you're working with and a Cocoa program. The main function of a Cocoa GUI program for OS X will look something like this:
#import <Cocoa/Cocoa.h>
int main(int argc, char *argv[])
return NSApplicationMain(argc, (const char **) argv);
As you commented, we could draw a correspondence between the first statements, but after that the functionality of the Cocoa program is going to be spread out in a way that makes for a rather tedious comparison. The only way I know to answer your question in less than 5000 words, is to skip ahead to one of several points in the startup sequence where the programmer can intervene with custom code.
For example, a common way to get control would be to program a custom controller class and add an object of that class to the main nib file which is loaded during the startup sequence. By making a connection to the Application object in that nib file, the custom object could be made the delegate of the Application object, and if we then added a method named applicationDidFinishLaunching, our code would run as soon as the application's run loop was started.
Now I finally have enough context to directly answer your question, so here is the code to create a label and add it to the key window at launch time:
// MyAppController.m
#import "AppController.h"
@implementation AppController
- (void)applicationDidFinishLaunching:(NSNotification *)aNotification {
NSLog(@"applicationDidFinishLaunching");
NSRect frameRect = NSMakeRect(150, 300, 150, 30);
NSTextField *label = [[NSTextField alloc] initWithFrame:frameRect];
[label setEditable:NO];
[label setStringValue:@"Hello World!"];
[label setFont:[NSFont labelFontOfSize:20]];
[label setAlignment:NSCenterTextAlignment];
NSView *contentView = [self.window contentView];
[contentView addSubview:label];
@end
If I needed to develop a worst case scenario for this thread, the next question would be, "Ok sure, but your code still needs a nib to start up. I want to see a Cocoa GUI program that doesn't require any nib".
It turns out that it's quite easy to build a simple iPhone app without any nib, but it's considerably more difficult for an OS X app. If anyone wants to see my nib-less iPhone code, I'll be happy to post it (I think I did post it here once before, and the response was underwhelming). But I've never attempted the much more difficult nib-less OS X app. Just in case you really want to go there, here's a blog that goes into the details: [http://lapcatsoftware.com/blog/2007/07/10/working-without-a-nib-part-5-open-re cent-menu>.
Hope some of the above is helpful!
- Ray

Interface Builder Fold Down Panel?

Hey Thanks to everyone on these forums there a huge help.
I'm trying to recreate the fold down effect that the open file panel has were the panel like folds out of the top of the app. Is there a way I could recreate this in Interface Builder or possible its called something else.
Thanks

yz4now wrote:
What would that animation or effect be called?
Drop-down menu. This is a standard menu example for most routine applications.
Using Xcode, create an new project....Mac OS X Application, Cocoa Application.
Open the 'Resources' folder on the left and double-click on 'MainMenu.xib' to open it in Interface Builder.
Using the MainMenu.xib window in IB, toggle the small triangles on the left to show the items in that menu. From there you will see the contents and the menu. This menu will drop-down in your application to show whatever contents you are working with.

Xcode 4.2.1 crashes when using a QCView in Interface Builder

Hi, I have been trying to use a QCView in one of my projects but I get a crash everytime. I tried loading the QuartzComposerChart sample application but if I compile the project I get a crash, it just seems to crash when it wants to but I was able to get it compiled if I didn't click on the .nib file. It seems to be related to interface builder anyway.
Adding a QCView to a new project results in a .xib file not being able to be saved I get this error
The document “MainMenu.xib” could not be autosaved. -[NSConcreteMapTable state]: unrecognized selector sent to instance 0x402d47420
Heres my crash log:
UNCAUGHT EXCEPTION (NSInvalidArgumentException): -[NSKeyValueUndefinedSetter state]: unrecognized selector sent to instance 0x4026f43a0
UserInfo: (null)
Hints: None
Backtrace:
0 0x00007fff8963726a __exceptionPreprocess (in CoreFoundation)
1 0x00007fff83bb2d5e objc_exception_throw (in libobjc.A.dylib)
2 0x00007fff896c34ce -[NSObject doesNotRecognizeSelector:] (in CoreFoundation)
3 0x00007fff89624133 ___forwarding___ (in CoreFoundation)
4 0x00007fff89623f48 _CF_forwarding_prep_0 (in CoreFoundation)
5 0x00007fff88c829b2 _PatchToComposition (in QuartzComposer)
6 0x00007fff88c5bd47 -[QCPatchController encodeWithCoder:] (in QuartzComposer)
7 0x00007fff8a60559d _encodeObject (in Foundation)
8 0x00007fff8dc72814 -[NSNibConnector encodeWithCoder:] (in AppKit)
9 0x00007fff8dc72599 -[NSNibBindingConnector encodeWithCoder:] (in AppKit)
10 0x00007fff8a60559d _encodeObject (in Foundation)
11 0x00007fff8a60678e -[NSKeyedArchiver _encodeArrayOfObjects:forKey:] (in Foundation)
12 0x00007fff8a606e56 -[NSArray(NSArray) encodeWithCoder:] (in Foundation)
13 0x00007fff8a60559d _encodeObject (in Foundation)
14 0x00007fff8dbe5ab7 -[NSIBObjectData encodeWithCoder:] (in AppKit)
15 0x00007fff8a60559d _encodeObject (in Foundation)
16 0x000000010aaf0938 -[IBCocoaDocument compiledKeyedObjectsData:] (in IDEInterfaceBuilderCocoaIntegration)
17 0x000000010aaf10e0 -[IBCocoaDocument fileWrapperOfType:error:] (in IDEInterfaceBuilderCocoaIntegration)
18 0x00007fff8db59801 -[NSDocument writeToURL:ofType:error:] (in AppKit)
19 0x000000010a681231 -[IBDocument writeToURL:ofType:error:] (in IDEInterfaceBuilderKit)
20 0x00007fff8db58769 -[NSDocument writeToURL:ofType:forSaveOperation:originalContentsURL:error:] (in AppKit)
21 0x000000010a6846ff -[IBDocument writeToURL:ofType:forSaveOperation:originalContentsURL:error:] (in IDEInterfaceBuilderKit)
22 0x00007fff8db58b68 -[NSDocument _writeSafelyToURL:ofType:forSaveOperation:forceTemporaryDirectory:error:] (in AppKit)
23 0x00007fff8db4285d -[NSDocument _writeSafelyToURL:ofType:forSaveOperation:error:] (in AppKit)
24 0x00007fff8db58911 -[NSDocument writeSafelyToURL:ofType:forSaveOperation:error:] (in AppKit)
25 0x0000000107ad664a -[IDEEditorDocument writeSafelyToURL:ofType:forSaveOperation:error:] (in IDEKit)
26 0x00007fff8db61ea7 __-[NSDocument saveToURL:ofType:forSaveOperation:completionHandler:]_block_invoke_8 (in AppKit)
27 0x00007fff8db61327 __-[NSDocument saveToURL:ofType:forSaveOperation:completionHandler:]_block_invoke_14 (in AppKit)
28 0x00007fff8db61c80 __-[NSDocument saveToURL:ofType:forSaveOperation:completionHandler:]_block_invoke_7 (in AppKit)
29 0x00007fff8a7a5a8d -[NSFileCoordinator(NSPrivate) _invokeAccessor:orDont:thenRelinquishAccessClaimForID:] (in Foundation)
30 0x00007fff8a7a8e65 -[NSFileCoordinator(NSPrivate) _coordinateReadingItemAtURL:options:writingItemAtURL:options:error:byAccessor:] (in Foundation)
31 0x00007fff8db5725c -[NSDocument _fileCoordinator:coordinateReadingContentsAndWritingItemAtURL:byAccessor:] (in AppKit)
32 0x00007fff8db45702 __-[NSDocument saveToURL:ofType:forSaveOperation:completionHandler:]_block_invoke_1 (in AppKit)
33 0x00007fff8db5ab75 -[NSDocument performAsynchronousFileAccessUsingBlock:] (in AppKit)
34 0x00007fff8db453af -[NSDocument saveToURL:ofType:forSaveOperation:completionHandler:] (in AppKit)
35 0x0000000107b8b66b -[IDEEditorDocument saveToURL:ofType:forSaveOperation:completionHandler:] (in IDEKit)
36 0x000000010a6811fd -[IBDocument saveToURL:ofType:forSaveOperation:completionHandler:] (in IDEInterfaceBuilderKit)
37 0x00007fff8db46d40 __-[NSDocument autosaveWithImplicitCancellability:completionHandler:]_block_invoke_1 (in AppKit)
38 0x00007fff8db40898 -[NSDocument continueFileAccessUsingBlock:] (in AppKit)
39 0x0000000107b898db -[IDEEditorDocument continueFileAccessUsingBlock:] (in IDEKit)
40 0x00007fff8db40cad __-[NSDocument performAsynchronousFileAccessUsingBlock:]_block_invoke_6 (in AppKit)
41 0x00007fff8db71333 __-[NSDocumentController(NSInternal) _onMainThreadInvokeWorker:]_block_invoke_3 (in AppKit)
42 0x00007fff882cc8ba _dispatch_call_block_and_release (in libdispatch.dylib)
43 0x00007fff882ce72a _dispatch_main_queue_callback_4CF (in libdispatch.dylib)
44 0x00007fff895cc4dc __CFRunLoopRun (in CoreFoundation)
45 0x00007fff895cbae6 CFRunLoopRunSpecific (in CoreFoundation)
46 0x00007fff8c1283d3 RunCurrentEventLoopInMode (in HIToolbox)
47 0x00007fff8c12f63d ReceiveNextEventCommon (in HIToolbox)
48 0x00007fff8c12f4ca BlockUntilNextEventMatchingListInMode (in HIToolbox)
49 0x00007fff8d7a23f1 _DPSNextEvent (in AppKit)
50 0x00007fff8d7a1cf5 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] (in AppKit)
51 0x00007fff8d79e62d -[NSApplication run] (in AppKit)
52 0x00007fff8da1d80c NSApplicationMain (in AppKit)
53 0x0000000107165eec (in Xcode)
54 0x0000000000000002
This also happens when I try loading a composition into a QCView. Does anyone know how to fix this?
Thanks
Ed

Glad you posted... I am getting similar messages in xcode 4.2.1
The document “MainMenu.xib” could not be saved. -[DVTFileSystemVNode state]: unrecognized selector sent to instance 0x40540f920
I didn't make the connection with QCView until I saw your post. I have several .xib in the project with QCViews and all of them have this same problem. .xib files without QCViews in them are fine.
However, my application does not crash, but runs fine. (The xib's and application were written with xcode 3.2, and I can't edit them now in 4.2.1, because I can't save them. )
Any other clues would be welcome.
Thanks
Keith

The Interface Builder won't open in Xcode when I click on MainMenu.xib

I have recently installed Xcode and have been trying to make very simple applications. The youtube videos that I have watched all show someone click the MainMenu.xib file and the Interface Builder opens. I have tried to do this and nothing opens. I am able to open the Interface builder manually but then the application that I make isn't linked and doesn't work.

Hi chris
Your question might be better posted in the Developer section of these forums. It's actually the very last one listed in the scrolling list of "Communities"
Bob

I am new to xCode and SDK Disks. My Interface Builder will not work and 'quit's unexpecteldy'. What can I do? I really want to create an applicaiton. Thanks

Hi, I am a new user to xCode and just recently downloaded a SDK Disk image and also an older version of xCode from the Apple Developer site. I opened the 'Interface Builder' for the first time and it worked. Next, when I tried to open it again (with and without the xCode 'Mainmenu.xib' attachment file from xCode) it kept showing the message "it quit unexpectedly".
I need to create an application for a project I am working on. If anyone who can resolve my problem of why the Interface Builder is not working, that will be great.
If you need additional details (like which versions etc.) please ask, for I am desperate to find an adequate solution to this problem.
Thanks.

If you need additional details (like which versions etc.) please ask, for I am desperate to find an adequate solution to this problem.
Without intending any disrespect, if you had suspected these would be questions and if you're in a hurry for an answer, then why did you exclude the information? And yes, knowing the Mac OS X version (preferably Mac OS X 10.5.8 or 10.6.7) , as well as the Xcode version might shed some light on this. Might. And I'll presume there's a specific reason you downloaded what I will assume is an Xcode3 version.
Was this an existing Xcode project, or did you start with a new project here? If it's an existing project, it could well have a corruption or an incompatibility.
Initially, I'd probably start with a new project, and load in newly-copied source files. On the off chance the project is corrupted.
Failing that, I'd deinstall Xcode using the documented procedures, and would then reload it. If there was an old version of Xcode around on the system, sometimes wonky stuff can happen with an installation.
And FWIW, the Apple Developer Forums and the Apple mailing lists tend to see far more developer-related traffic than do these particular forums. (There's an Xcode users' mailing list around which sees regular traffic, too.)

String windows in Xcode vs interface builder

Dear All,
Doing translation, I used interface builder 3.6 with "string windows" (alt S) to have a list of sting used in the nib file.
I can translate them, and I'm sure that everything is included in my local version.
Now Interface builder is included in Xcode.... How can I get all the string used in a nib file on a list format ????
Tahnk for your help
Bruno

Finally i've got iLocalize for free on the appstore which give me more flexibility, and i use now xCode to clean the interface and do fine tunning.
Bruno

Xcode and Interface Builder

Hello,
I want to make a thing in Interface Builder so that when I click on the About "My Application" menu in the Menu Bar at the top a new window comes up.
What I did, was made a new window (HUB) then, deselected Visible at Launch. I did all the linking stuff with applescript and when I tested (Apple - R) it showed up! Any idea why and how to fix this problem?
Thanks!
P.S. My app is an AppleScript app
And also, if you can, how do you "export" your finished apps from Xcode?

bubblejelly wrote:
I want to make a thing in Interface Builder so that when I click on the About "My Application" menu in the Menu Bar at the top a new window comes up.
Umm, OK. But you should get an "About" window by default without having to do anything. Are you saying you want another window too, or a different window than the default one?
What I did, was made a new window (HUB) then, deselected Visible at Launch. I did all the linking stuff with applescript and when I tested (Apple - R) it showed up! Any idea why and how to fix this problem?
HUB? Not sure what that means.
Did you do the Apple-R in Xcode or in Interface Builder? "Test Interface" (or Apple-R) in Interface Builder is not the same as "Build and Run" (Apple-R) in Xcode. In IB if your "not visible" window is open when you do the Apple-R then it will also be open when the interface test is in progress. None of your AppleScript code gets executed when you're testing in IB.
If you were doing the Apple-R in Xcode then I don't know. Post some of your AppleScript code.
Steve

Make a button do something Xcode/interface builder

How can i make a button placed in interface builder do something

Well, that isn't much better - I am going to guess that your application is for Mac OS X in Objective-C. Since something like a button is pretty basic, you either need some help with Xcode, or a conversion from some other programming language you know, or both.
There is a basic button tutorial here that uses the older Xcode (there shouldn't be much difference), although you should look at getting Xcode 4.2 (free from the AppStore), since that is what is current.
I don't do much in Obj-C so I can't help with good books, but Apple has a few documents on its developer site that should get you started (although most of their documentation has moved on to Xcode 4.

DELETE or make TITLE BAR INVISIBLE in XCODE INTERFACE BUILDER

Im trying to figure out how to make the title menu invisible or to simple delete it all together, it serves no purpose in my app, and i would really like it to be gone, any ideas?

>The only trick is that you have to load the NIB file manually. Here's the code to put up your >dialog:
>
>IBNibRef dialogNibRef = NULL;
>WindowRef windowRef = NULL;
>CFBundleRef bundle = CFBundleGetBundleWithIdentifier(kMyBundleIdentifier);
>CreateNibReferenceWithCFBundle(bundle, kMyNIBName, &dialogNibRef);
>CreateWindowFromNib(dialogNibRef, kMyWindowName, &windowRef);
>DisposeNibReference(dialogNibRef);
>
>Having done this, you can show the window using RunAppModalLoopForWindow.
Could you please explain these steps more in detail Aaron. I've setup a UI using the Interface Builder and have put the above mentioned code into DissolveUIMac.cpp but i am getting the following errors:
error: 'kMyBundleIdentifier' was not declared in this scope
error: expected constructor, destructor, or type conversion before '(' token
error: expected constructor, destructor, or type conversion before '(' token
error: expected constructor, destructor, or type conversion before '(' token

Xcode 3/Interface Builder - Adding classes to NIB file doesn't work

I'm attempting to learn Objective-C and Cocoa GUI through Apple's "Currency Convertor" tutorial. I'm currently at the "Add the ConverterController Class to Your Nib File" step, and I add ConverterController.h to the Interface Builder project (both by Read Class Files and dragging) and... nothing happens. The tutorial clearly states that the class should appear as a new icon in the MainMenu.nib window. I've tried researching this problem, and it appears to be quite common, however every fix isn't really a fix at all. They all involve using the Identity Inspector for something, which appears very complicated, and is otherwise uncovered in the tutorial. It occurs to me that anyone knowing enough to be able to use this fix wouldn't be reading this tutorial, thus making such answers moot. Any help anyone could provide on this issue would be appreciated.

The tutorial you linked to should work fine except that they've just got the illustration (Figure 5-3) in the wrong place.
The placement of that illustration implies that you should see the instance of your class in the MainMenu.nib window right after doing step 2 (where you read your class file). But that's not really true. In reality it's step 3 that gets you the blue box in the MainMenu.nib window and steps 4 and 5 that will transform it from an "Object" into a "ConverterController". Steps 3, 4 and 5 are exactly what Thomvis suggested that you do earlier.
Steve

Interface Builder w/ Xcode folder refs

Similar Messages

Maybe you are looking for