Using Interface Builder to Inspect a New Object?

I am having a major frustration following a Stanford demo on using Interface Builder. The demo shows how to create a simple slider object with a value. But when the demo pulls up the Inspector Window to examine the new Object, in the Stanford demo the inspector window has panes for CLASS ACTIONS and CLASS OUTLETS, whereas my inspector window, identical in every other respect to the demo window, doesn't have these two panes. Help!!!!!!!!!

The first lecture gives information about joining the developer program and there are forums similar to this at their website. You can also find forums on private sites on the web that are following the courses and have their own forums for asking questions like this.
Try one of those paths and you should find more help than on here. This is just end users helping end users not delopers.
Jason

Similar Messages

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

Looking for simple sample of iphone apps without using Interface Builder

I successfully went through the 'iphone app tutorial' and used Interface Builder, but now want to try creating apps without it.
The UI Catalog sample is too complex, but didn't see anything that just had a view and a button or label.
Ideally I want code that doesn't require any IB usage, but I can't tell if that is possible yet...
Anyone have a link to an easy sample?
Or has anyone created a test app themselves and wouldn't mind posting?
I took a stab at creating one and posted it on the "101" forum, but it would be hard for somebody to try and figure out what I was attempting
Thx for any links/___sbsstatic___/migration-images/migration-img-not-avail.png
ps
I really need a good book, especially "cookbook" style

hey dear
I have one solution of your problem
just go to in iphone developer search for FAQ
In faq their is one section how to use prohramming in this you can see
the how to ceate label,button etc.
after that simply add the view or remove theview.

Using interface builder to create a table view and add a cell

So I am using interface builder to make a table view. Should be easy. I drag a table view controller to my view, then it seems I should be able to drag a table view cell to the table view but it won't let me drop it down. If I do it in the documents window it just replaces the table view with a cell. Seems like this shouldn't be hard, but it's one of those things that should take 2 seconds but I have been messing with it for hours. It seems like most of the examples I have looked at in the same code don't use iB so I haven't found a good reference. If somebody can point me in the write direction let me know.

I struggled a bit too. Here's what I did on my recently completed app. I used IB to create the basic view and add the table. That's it. Then ensure your UIViewController based class implements the UITableViewDelegate and UITableViewDataSource protocols. Your cells will come from those methods, not anything you do in IB.
If you're creating a set of screens that just have tables that allow you to navigate up and down through the data then IB isn't worth using at all.
Just have your views extends UITableViewController and follow some of the supplied table based example apps.
I rewrote my first app 3 times as I slowly figured all of this out.
Hope that helps.

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.

Not using interface builder??

Hi all,
I'm new to Cocoa & Xcode and have noticed some examples (both Apples documentation & samples and some third party samples) that you can create your views, navigation controllers etc programatically and not use IB.
I'm wondering if some experienced cocoa & xcode progranners can let me know if their is anything I should be aware of before choosing a certain workflow method.
For instance a simple iphone app might have
1. Splash or Intro screen
2. Main menu + possible sub menus
3. Main app
4. Additional prefs or info screens
Is there any point to using IB if all I do is setup my initial window and UIView for the intro in IB and then all subsequent class files don't use IB?
Thanks for any pointers!
Message was edited by: david_lister

You can definitely mix methods. Use IB for situations where you are doing a lot of layout or connections, or just if you are more comfortable with it. Use code if the view is simple, or you are more comfortable with that. If you use IB, you will want to split your xib files up so the app doesn't have to load one big file.

Use String Variable in New Object Creation

Thanks to those who review and respond. I am new to Java, so please be patient with my terminoloy mistakes and fumblings. I am reading in a file and I want to create a new object based on specific field (car for example). As you will notice I grab field 8 here label sIID.
String sIID = dts.group(8);
BTW this regex grouping works fine. The problem is seen when I try to use the sIID variable in my new object creation process.
DateParse sIID = new DateParse();
My IDE is reporting "Variable sIID is already defined in the scope"
Is this possible? The assumption is that the sIID will have different value during the processing of the file. For example, car could mean truck, sedan, etc with operators like color, number of doors, mileage, top speed, etc.

Thanks for the reply. I have include similar and much shorter code for the sake of brevity.
My problems are centered around the x variable/object below. Ideally this would translate to three objects PersonA, PersonB, etc that I could reference later in the code as PersonA.newname if I wanted to. Hopefully this makes sense.
public class TestingObjects {
public static void main(String[] argv) {
       String [] names;
       names = new String[3];
       names[0] = "PersonA";
       names[1] = "PersonB";
       names[2] = "PersonC";
       for (String x:names) {
         PN x = new PN(); // <- Problem
         x.name = x;
         x.SayName();
        System.out.println(x.newname);
public class PN {
       String name;
       String newname;
public String SayName() {
       newname = "Name = " + name;
       System.out.println(name);
      return newname;
}

Interface Builder Assertion Failure at initialization/startup

Interface Builder appears to be unusable...
I get four (4) alert messages at the start of running Interface Builder:
====
Interface Builder encountered an internal logic error. Choose "Continue" to continue running Interface Builder in an inconsistent state. Choose "Crash" to halt Interface Builder and file a bug with Crash Reporter. Choosing "Crash" will result in the loss of all unsaved data.
====
Selecting (Show Details) I get:
====
Assertion Message: Interface Builder encountered an error communicating with the iPhone Simulator. If you choose to file a crash report or radar for this issue, please check Console.app for crash reports for "Interface Builder Cocoa Touch Tool" and include their content in your crash report.
IBUIViewImageRequester failed to rasterize a UILabel, UIButton, UITextField, and UISegmentedControl.
Exception name: NSInternalInconsistencyException
Exception reason: [NOTE: this exception originated in the server.]
Invalid parameter not satisfying: font != nil
Exception backtrace:
0. CoreFoundation 0x30279dfb [NSException initWithName:reason:userInfo:]
1. libobjc.A.dylib 0x92750e3b objcexceptionthrow
2. CoreFoundation 0x3028e5fb CFReadStreamGetBuffer
3. Foundation 0x305b0594 [NSAssertionHandler handleFailureInMethod:object:file:lineNumber:description:]
4. UIKit 0x309fe074 [UILabel setFont:]
5. UIKit 0x309fec08 [UILabel _commonInit]
6. UIKit 0x309fd13c [UILabel initWithFrame:]
7. Interface Builder Cocoa Touch Tool 0x00008655 [UIView initWithMarshalledValues:orderedKeys:marshallerClassNames:andMarshallerInstanti ationContexts:globalMarshallingContext:]
8. Interface Builder Cocoa Touch Tool 0x0000b307 [IBCocoaTouchToolObjectPackage dealloc]
9. Interface Builder Cocoa Touch Tool 0x0000b80f [IBCocoaTouchToolObjectPackage initWithData:]
10. Interface Builder Cocoa Touch Tool 0x0000a5a1 [IBCocoaTouchToolObjectPackage dealloc]
11. Interface Builder Cocoa Touch Tool 0x00002c74 [IBCocoaTouchTool produceImageForRequest:]
12. Interface Builder Cocoa Touch Tool 0x00002445 [IBCocoaTouchTool produceImagesForRequests:]
13. CoreFoundation 0x3024a10d CF_forwarding_prep0
14. CoreFoundation 0x30249ff8 [NSInvocation invoke]
15. CoreFoundation 0x3026eaf8 [NSInvocation invokeWithTarget:]
16. CoreFoundation 0x3026e094 [NSDate initWithTimeIntervalSinceNow:]
17. CoreFoundation 0x3024a0a2 CF_forwarding_prep0
18. CoreFoundation 0x3024a10d CF_forwarding_prep0
19. CoreFoundation 0x30249ff8 [NSInvocation invoke]
20. Foundation 0x3053e15d [NSConnection dispatchInvocation:]
21. Foundation 0x3053c307 [NSConnection handleRequest:sequence:]
22. Foundation 0x3053ba13 [NSConnection handlePortCoder:]
23. Foundation 0x3053b5be [NSConcretePortCoder dispatch]
24. Foundation 0x3053ae33 [NSDOStreamData bytes]
25. CoreFoundation 0x30246e79 CFRunLoopRemoveObserver
26. CoreFoundation 0x30245560 CFRunLoopRunSpecific
27. CoreFoundation 0x30244628 CFRunLoopRunInMode
28. Foundation 0x30535525 [NSRunLoop runMode:beforeDate:]
29. Interface Builder Cocoa Touch Tool 0x000020af [IBCocoaTouchTool startServingForPortName:]
30. Interface Builder Cocoa Touch Tool 0x00002e77 [IBCocoaTouchTool produceImageForRequest:]
Exception info:{
Backtrace:
0. Interface Builder 0x00004d29 [IBApplication handleAssertion:inFile:onLine:]
1. IBCocoaTouchPlugin 0x16622659 [IBAssertionShim reportMarshallingFailure:]
2. Foundation 0x9002b9bc [NSRunLoop getCFRunLoop]
3. CoreFoundation 0x93ac9595 CFRunLoopRunSpecific
4. CoreFoundation 0x93ac9c78 CFRunLoopRunInMode
5. HIToolbox 0x91f3428c BlockUntilNextEventMatchingListInMode
6. HIToolbox 0x91f33fde BlockUntilNextEventMatchingListInMode
7. HIToolbox 0x91f33f19 BlockUntilNextEventMatchingListInMode
8. AppKit 0x906e4d0d _DPSNextEvent
9. AppKit 0x906e45c0 [NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:]
10. Interface Builder 0x0000276b [IBApplication nextEventMatchingMask:untilDate:inMode:dequeue:]
11. AppKit 0x9092192b [NSApplication _realDoModalLoop:peek:]
12. AppKit 0x9091c069 [NSApplication runModalForWindow:]
13. InterfaceBuilderKit 0x00382511 [IBDetailedAlert runModal]
14. Interface Builder 0x00004dd6 [IBApplication handleAssertion:inFile:onLine:]
15. IBCocoaTouchPlugin 0x16622659 [IBAssertionShim reportMarshallingFailure:]
16. Foundation 0x9002b9bc [NSRunLoop getCFRunLoop]
17. CoreFoundation 0x93ac9595 CFRunLoopRunSpecific
18. CoreFoundation 0x93ac9c78 CFRunLoopRunInMode
19. HIToolbox 0x91f3428c BlockUntilNextEventMatchingListInMode
20. HIToolbox 0x91f33fde BlockUntilNextEventMatchingListInMode
21. HIToolbox 0x91f33f19 BlockUntilNextEventMatchingListInMode
22. AppKit 0x906e4d0d _DPSNextEvent
23. AppKit 0x906e45c0 [NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:]
24. Interface Builder 0x0000276b [IBApplication nextEventMatchingMask:untilDate:inMode:dequeue:]
25. AppKit 0x9092192b [NSApplication _realDoModalLoop:peek:]
26. AppKit 0x9091c069 [NSApplication runModalForWindow:]
27. InterfaceBuilderKit 0x00382511 [IBDetailedAlert runModal]
28. Interface Builder 0x00004dd6 [IBApplication handleAssertion:inFile:onLine:]
29. IBCocoaTouchPlugin 0x16622659 [IBAssertionShim reportMarshallingFailure:]
30. Foundation 0x9002b9bc [NSRunLoop getCFRunLoop]
31. CoreFoundation 0x93ac9595 CFRunLoopRunSpecific
32. CoreFoundation 0x93ac9c78 CFRunLoopRunInMode
33. HIToolbox 0x91f3428c BlockUntilNextEventMatchingListInMode
34. HIToolbox 0x91f33fde BlockUntilNextEventMatchingListInMode
35. HIToolbox 0x91f33f19 BlockUntilNextEventMatchingListInMode
36. AppKit 0x906e4d0d _DPSNextEvent
37. AppKit 0x906e45c0 [NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:]
38. Interface Builder 0x0000276b [IBApplication nextEventMatchingMask:untilDate:inMode:dequeue:]
39. AppKit 0x9092192b [NSApplication _realDoModalLoop:peek:]
40. AppKit 0x9091c069 [NSApplication runModalForWindow:]
41. InterfaceBuilderKit 0x00382511 [IBDetailedAlert runModal]
42. Interface Builder 0x00004dd6 [IBApplication handleAssertion:inFile:onLine:]
43. IBCocoaTouchPlugin 0x16622659 [IBAssertionShim reportMarshallingFailure:]
44. Foundation 0x9002b9bc [NSRunLoop getCFRunLoop]
45. CoreFoundation 0x93ac9595 CFRunLoopRunSpecific
46. CoreFoundation 0x93ac9c78 CFRunLoopRunInMode
47. HIToolbox 0x91f3428c BlockUntilNextEventMatchingListInMode
48. HIToolbox 0x91f33fde BlockUntilNextEventMatchingListInMode
49. HIToolbox 0x91f33f19 BlockUntilNextEventMatchingListInMode
50. AppKit 0x906e4d0d _DPSNextEvent
51. AppKit 0x906e45c0 [NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:]
52. Interface Builder 0x0000276b [IBApplication nextEventMatchingMask:untilDate:inMode:dequeue:]
53. AppKit 0x906dd5fb [NSApplication run]
54. AppKit 0x906aa834 NSApplicationMain
55. Interface Builder 0x00004eca [IBApplication changeInspectorMode:]
====
If I press (Continue) and then try to create any fields which need text, such as a label or button, I get the exact same alert window, and nothing "appears to work" as far as getting past this.
Some background...
I have no problems like this on my PPC development platform, just on my Intel-based system.
Configuration:
Intel hardware, 1.6 Ghz, 2GB, Mac OS/X 10.5.7
Originally I installed the the devtools from: xcode3122621developerdvd.dmg
and the 2.0 or 2.1 iPhone SDK, but never used Interface Builder (long story)
When the final SDK for 3.0 came out, I installed that from:
iphonesdk_3.0_leopard_9m2736final.dmg
A few days ago, I said, OK, enough reading, I'm ready to start on my application, and fired up Xcode, created a new project and double-clicked on the .xib file to build my interface.
That's when I first saw this problem... and now I'm stuck.
What I've done since...
#1) Deleted prefs for Interface Builder (ibtool), and XCode
retried... same error
#2) wiped /developer clean and resinsatlled from iphonesdk_3.0_leopard_9m2736final.dmg
retried... same error
retried #1, retried, same error
#3) ran /Volumes/Olórin/Developer/Library/uninstall-devtools --mode=all
rebooted
checked international to make sure US/English was selected
repaired disk permissions
rebooted
verified, no prefs files in ~/Library/Preferences or /Library/Preferences
retried... same error
HELP!!!

! ! ! - O M G - ! ! !
{quote:title=reststop wrote:}
#3) ran /Volumes/Olórin/Developer/Library/uninstall-devtools --mode=all
{quote}
I was about to post a reply which included the entire crash log for details... and saw this line:
7/21/09 12:44:16 AM [0x0-0x28028].com.apple.InterfaceBuilder3[269] Couldn't read font cache (file://localhost/Volumes/Olo%C3%83%C3%85rin/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator3.0. sdk/System/Library/.lilid/.lili).
The file is there, so why can't it read it... uh oh, not exactly
... I typed /Olórin/ not /Olo%C3%83%C3%83rin/
Apparently somewhere internal to Interface Builder, when it translates characters, it does it TWICE,
so instead of 'ó' (that's 'option-e o', we have 'o%C3%83%C3%83' which may have worked if it had
only been '%C3%83', without the extra o, or the extra %C3%83.
I am so glad I found this, but I'm furious at Apple for making me rebuild my development system 3 times!
...someone really needs to do better QA on a product used by so many users.
I changed the name of my disk from Olórin to Olorin and Interface Builder works fine!
The PROBLEM all along was the name of my development disk ! ! !
Someone at Apple, please NOTE!
Someone please tell me how to report this, and maybe get Apple to hire me even if just for better QA!
-Carl

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.

Error when using Form Builder

When using Form Builder to create a new form from TEMPLATE.fmb, there is an error like this:
FRM-18108:Failed to load the following objects:
Source Module:APPSTAND
Source object:STANDARD_PC_AND_VA
Source Module:APPSTAND
Source object:STANDARD_TOOLBAR
Source Module:APPSTAND
Source object:STANDARD_CALENDAR
Then, I found an file incuding the error message in the directory where I placed the TEMPLATE.fmb and APPSTAND.fmb.
Here is the main point:
FRM-30064: Unable to parse statement select timezone_code,name
,to_char(trunc(gmt_offset),'S09') || ':' || to_char(abs(gmt_offset - trunc(gmt_offset))
*60,'FM900') offset
,decode(daylight_savings_flag,'Y','*',null) dst_flag
from fnd_timezones_vl
where enabled_flag = 'Y'
order by gmt_offset.
ORA-00942: table or view does not exist
Record Group TIMEZONES
Form: STANDARD_OBJECTS
FRM-30085: Unable to adjust form for output.
How can I fix this error?
Thanks a lot,
Mike Cui
PS: I have intalled the Oracle EBS VIS, and the OS is WinXP(ZHS).

Yes, that's right.
I have fixed this error.
At the same time, I found a bug when installing Oracle EBS DEMO. That is,
FORM60_PATH in HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE,is $AU_TOP\11.5.0\resource;$AU_TOP\11.5.0\form\us; But another one in HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\HOME2 is $AU_TOP\11.5.0\resource;$AU_TOP\11.5.0\plsql. I think the second one is the working path used by Form Builder. Correcting it to be same with the first one will be OK. Or you can change all of them to your own working path.
PS: Form builder is installed in the server PC which I only have:)
Message was edited by:
Mike Cui

[Help] Error when using Form Builder

When using Form Builder to create a new form from TEMPLATE.fmb, there is an error like this:
FRM-18108:Failed to load the following objects:
Source Module:APPSTAND
Source object:STANDARD_PC_AND_VA
Source Module:APPSTAND
Source object:STANDARD_TOOLBAR
Source Module:APPSTAND
Source object:STANDARD_CALENDAR
Then, I found an file incuding the error message in the directory where I placed the TEMPLATE.fmb and APPSTAND.fmb.
Here is the main point:
FRM-30064: Unable to parse statement select timezone_code,name
,to_char(trunc(gmt_offset),'S09') || ':' || to_char(abs(gmt_offset - trunc(gmt_offset))
*60,'FM900') offset
,decode(daylight_savings_flag,'Y','*',null) dst_flag
from fnd_timezones_vl
where enabled_flag = 'Y'
order by gmt_offset.
ORA-00942: table or view does not exist
Record Group TIMEZONES
Form: STANDARD_OBJECTS
FRM-30085: Unable to adjust form for output.
How can I fix this error?
Thanks a lot,
Mike Cui
PS: I have intalled the Oracle EBS VIS, and the OS is WinXP(ZHS).

You have to connect with a database user who has right to select on the table.

SDK Beta 7 - Interface Builder Keeps Crashing

I am running 10.5.3 on a MBP. I was previously running Beta 4 with no problems.
After installing SDK Beta 7 I can no longer use Interface Builder. As soon as I scroll the library scrollbar and reach the datepicker object the IB application beachballs indefinitely. This also happens if I double-click a .xib file in Xcode - IB just hangs.
I have repaired permissions, removed the dev-tools and re-installed them and rebooted several times but the problem persists.
Is anyone else experiencing this problem? How can I fix it?
Thanks,

lots of people with similar problem --- http://discussions.apple.com/thread.jspa?threadID=1538812&tstart=0
any hints?

How do you make a tool bar on interface builder

I don't know how to make a toolbar (for example: like the one safari) using interface builder.

Might start here:
http://developer.apple.com/iphone/library/documentation/UserExperience/Conceptua l/MobileHIG/SystemProvided/SystemProvided.html
In IB, you'll want to look over the objects in the libary pane/window. These are drag/drop into whatever view you're working, etc. Wiring them up of course depends on usage.
Apple's 'UICatalog' is another good reference that you can get your hands into and push around for protos and ideas.

Interface Builder Binding leads to death

I have an Array Controller which is updating an NSMutableArray. The NSMutableArray is made up of an Object called Power which has several NSString objects (each synchronized). One of these is called name.
When the user hits an "Import" button, the program reads a file and creates Power objects, adding them to the Array Controller. When it finishes adding Powers it prints them all to console (in this way I know they are all properly formed).
I am attempting to bind the strings of the Power objects to an NSTableView using Interface Builder. I've done more or less the exact same thing in a few other programs with no troubles. However, this time, I can only bind one of the columns successfully.
If I bind any column to the string "name" of the Power objects in the Array Controller, it displays the names just fine. If I try binding any column to any of the other strings, it results in a program crash at runtime (which is being hooked by gdb, but I do not know how to use it).
Does anybody know what might cause this? Why does one NSString bind perfectly to a column when others don't and each object has every field populated?

Can I ask what is your cell/column/table progression?

Yet another cocoa without interface builder post

I am sure its been brought up before. I would like to know if its possible to write Cocoa apps without Xcode, Interface Builder, or NIB files in general; another words, write Cocoa programs programmatically using ONLY Objective C. Before you ask me why I would want to do such a thing and that I am crazy, please hear me out.
I come from a Win32 background, and my primary languages are C and C++. I am getting used to Objective C (though I wish I could use C++ to program in Cocoa). I picked up a copy of Cocoa(R) Programming for Mac(R) OS X (3rd Edition) by Aaron Hillegass, and have been trying to learn cocoa from it for the last few months. Basically, I am having big trouble wrapping my mind around cocoa via the very conceptual high level approach this book takes. I can not for the life of me begin to understand this whole making connections with interface builder.
I do NOT plan to write production applications in cocoa by hand, but if I could just write a few trivial applications in cocoa by hand without interface builder or nib files, perhaps when I do use interface builder, I won't have such a hard time understanding whats going on.
Thanks in advance for the help.

__mikem wrote:
I am sure its been brought up before.
I don't care. Your question isn't about learning how to program and learning via the iPhone SDK. I'll do anything I can for you
I would like to know if its possible to write Cocoa apps without Xcode, Interface Builder, or NIB files in general; another words, write Cocoa programs programmatically using ONLY Objective C.
Certainly. You can write command-line Cocoa apps. Xcode is just an IDE like Visual Studio.
Before you ask me why I would want to do such a thing and that I am crazy, please hear me out.
I come from a Win32 background, and my primary languages are C and C++. I am getting used to Objective C (though I wish I could use C++ to program in Cocoa). I picked up a copy of Cocoa(R) Programming for Mac(R) OS X (3rd Edition) by Aaron Hillegass, and have been trying to learn cocoa from it for the last few months. Basically, I am having big trouble wrapping my mind around cocoa via the very conceptual high level approach this book takes. I can not for the life of me begin to understand this whole making connections with interface builder.
You specifically asked to avoid the topic, but I'm sure there are several of us who are really tired of iPhone questions who would be happy to try our hand at explaining the User Interface architecture in Cocoa - if you want to try.
I do NOT plan to write production applications in cocoa by hand, but if I could just write a few trivial applications in cocoa by hand without interface builder or nib files, perhaps when I do use interface builder, I won't have such a hard time understanding whats going on.
You can write Objective-C programs using whatever editor and IDE/makefile you want. You can even work with all the non-UI parts of Cocoa to get a feel of how it works. Technically, you could write code using only Carbon and never use Objective-C, but that is really a dead-end.
A good idea might be start looking at doing writing MacOS X kernel extensions. You should still use Xcode, but only as an IDE. The code would all be C++ (or a subset thereof) with no user interface or NIB files. Realistically, that is probably harder than learning Interface Builder, but it is probably the most productive path available to you for developing MacOS X and avoiding Interface Builder.

Using Interface Builder to Inspect a New Object?

Similar Messages

Maybe you are looking for