How to define interface builder outlets in Cocoa-Python?

Hi,
I am writing a Cocoa-Python application but I couldn't find a way to define outlets in Python code that I can use in the Interface Builder. Of course I know how to do that in Objective-C and this doc http://developer.apple.com/documentation/Cocoa/Conceptual/RubyPythonCocoa/Articl es/BuildingRubyCocoaAppl.html explains how to create outlets in Ruby, but what about Python?
Thanks in advance,
Ganesh

I found it out myself. You have to write
class MyClass(NSObject):
  outletName = objc.IBOutlet('outletName')
  def foo(self):
    # etc.
Thanks anyway,
Ganesh

Similar Messages

How to define interface of IDOC?

IDoc outbound:
In step 1, a new file is generated with the transferred IDocs by the IDoc Interface. In the second step,
the program ¡°rfcexec¡± (synchronous RFC) with the path to an executable program is called (here:
¡°out.script¡±) and also the path to the IDoc file. ¡°out.script¡± thus contains the path and name of the
file as an input value. In step 3, it therefore calls the external system, which reads the file in step 4.
After successful processing of the IDoc file, the external system must delete the IDoc file. The call
command in ¡°out.script¡± depends on the external system.
I quated this from relative document,I want to know how to define 'rfcexec' and 'out.script' looking forward to ur reply,
best regards

Hi Aparajitha,
Master_idoc_distribute for sending outbound IDOCs.
Thanks,
Anil

How to define Interfaces in SAP PI

HI Experts,
I am kind of very new to SAP PI topic and hear we doing an new SAP implementation project where the existing infrastructure is transformed to SAP.
So , in this process we have analyze the different existing interfaces like which one should pass through PI and which doesn't.
hear my question is how exactly we define the PI interfaces and differentiate them with regular user interfaces and database interfaces.
Thanks,
Kiran

Hi,
>>>hear my question is how exactly we define the PI interfaces and differentiate them with regular user interfaces and database interfaces
you use PI interfaces for connecting one application to another
but please read the basic info on PI first (available on SDN) before asking basic questions
Thank you,
Regards,
Michal Krawczyk

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

How to make a form for input in web interface builder

Hi expert:
How to make a form for input in web interface builder?I have already used it to do PS planning, but I don't know how to draw lines and checkboxes . Thanks in advance.
Allen

WAD:
Open the WAD and create a new template. On the left hand navigation you will have several Web Items available. Under 'Standard' you have 'Analysis' item. Pull that into your template to the right. Under the Properties tab you need to pick the query [form/layout] that you have built in Query Designer.
You will also find other items such as Button group, Checkbox, drop down, list box etc available. Pick and drag into the template whatever it is you require. Lets say you want a button. Under the Properties tab select the 'Command' that you require. You could use standard commands that are available there. You could also define functions and commands that you require.
Query Designer:
Open the QD and drag the characteristics and key figures that you require into the rows and columns of the QD. You would need to specify restrictions under the Filter tab of the QD based on the granularity of data that you require. You would need to remember that the key figures need to be made Input Ready [do this by clicking on KF and on the planning tab select "change by user and planning functions"].
This shouldgive you a start. After you've explored it yourself a bit we can discuss further and I can certainly provide you additional details/material on these areas.
Srikant

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.

How to add interface to customlize MXML Component when use Flex Builder 3?

How to add interface to customlize MXML Component when use
Flex Builder 3?

David,
I don't believe you can add the interface via the creation
dialog in FlexBuilder 3. You can always manually add the
"implements" property to your MXML Component root tag. Something
like this: <mx:VBox implements="com.mycorp.IMyInterface">
If you want autogeneration of the interface, then create an
ActionScript class with that interface and then copy the generated
functions and setter/getters into the script block of your MXML
component.

Interface Builder - Custom images not visible in Cocoa Simulator

I'm very new to this, and just toying around with Interface Builder more than anything at this stage…
Anyway, my problem… I've created some of my own images to place on buttons, etc. I've saved them in PNG format and dragged them into the Resources folder of my Xcode project, so they become available in Interface Builder's media library. I can drag them onto my window just fine, but when I test the UI with the 'Simulate Interface' command, the images disappear completely.
Any ideas?

This was changed in Interface Builder 3.0. Now, you have to click on the "Connections" tab in the object's Info panel. I think it is the 2nd one from the right. You will recognize it because you will see all your outlets. You click the little circle next to the outlet and drag a line over the user interface object to make the connection. Once you do that, there is a bug in Interface Builder that will blank out the info panel. You will have to select some other object to redisplay any information, then click back to your original object. The bindings panel has a similar set of bugs. Suffice to say, Interface Builder 3.0 is a work in progress.
PS - to break a connection, click the little X button next to an outlet name.

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.

How can I access instances from Interface Builder?

Hello!
How can I access instances build from the Interface Builder? For example, i know how to access Controller classes = just setting the class in the view identity. But I am missing some "connection" to my navigation controller. IB uses one, but in my code, i dont have one.
All my xibs file owners have as their identity class a View or TableView Controller. But shouldnt they have a navigation controller as identy if the View or TableView is using a navigation Controller?
thank you..

thank you, .. i know.. the problem is, that i have different xib files, but i am not sure how i can connect them with their navigation controller / tabbarcontroller.
it seems, that
NSLog(@"pushing next view..");
[[self navigationController] pushViewController:nextViewController animated:YES];
is not enough. On the console, i can read pushing next view.. but it doesnt come up to the screen.

Load Class in Interface Builder 3

Hello,
i am trying to get started with Cocoa after having worked a while with Xcode & smaller AppleScript based projects.
As my idea was to create a menubar-based (NSStatusItem) service app for myself i started with this tutorial:
http://files.semaja2.net/NSStatusItem%20-%20ObjC.html
Unfortunaly it seems like there was a change in Interface Builder regarding loading Classes from Version 2 to IB version 3
The tutorial tells me to (about the middle of the tutorial):
Rename the “NSMenu1” to “StatusItem”, following this in “Interface Builder” >>choose from the menu “Classes > Read Files..” now select the AppController.h >>file, Once the file has been read it should change out project view to “Classes” >>from here find the AppController item and right click on it and select >>“Instantiate AppController”:
I was able to follow the tutorial until there without problems but it looks like the Classes-Tab is gone in IB 3.x.
So i feel somehow unable to finish this small tutorial.
how would i do this step in Interface Builder 3.x ?
Any help is heavily appreciated.
Best regards
fidel

fidel-castro wrote:
I was able to follow the tutorial until there without problems but it looks like the Classes-Tab is gone in IB 3.x.
So i feel somehow unable to finish this small tutorial.
how would i do this step in Interface Builder 3.x ?
You're right, this has changed. I'm currently using IB 3.1.1 but I believe the changes appeared in IB 3.
Once you've done the "Read class files" and selected your AppController.h file IB should know about your class.
In order to instantiate your AppController in IB first go to the Library window and find the "NSObject" (it will appear as a blue cube). Drag one of these NSObject's from the Library window and drop it into your MainMenu.xib window along with the other icons that appear there (File's Owner, First Responder, Application... etc).
Now you will have created an instance of an NSObject in your MainMenu.xib file. And, since your AppController class is a subclass of NSObject (and IB knows this since you've had it read in your AppController.h file) you can now change this NSObject instance into an instance of your AppController.
Select the NSObject icon in the MainMenu.xib window then go to IB's Inspector window and click on the next to last icon in the top tool bar. This should change the Inspector window's title bar to say "Object Identity" and the Class Identity in the first text field should be set to NSObject. You should be able to type "AppController" into this field (or click the popup and it should show up in the popup list. Once you've done this it will transform the NSObject instance into an AppController instance.
You'll see another slight difference between IB 3.x and the tutorial when you do the <Control>-Drag between items to connect up the outlets and actions. Instead of finalizing the connections in the Inspector window like the tutorial says you'll get a small popup window right next to the item you're connecting to that will list the available outlets/actions you can connect to. Simply click the one you want. You can still double-check your connections in the inspector window though.
Steve

Can I no longer browse classes in interface builder?

in tiger, I used to be able to browse classes in interface builder, and from their I could create subclasses, and create actions and outlets. then I could create files for the classes from the classes menu. then when I went back to xcode I would have empty class file templates that I could then write the methods for.
also, I could easily instantiate my class via the classes menu.
alas, now I cannot find these features. have they dissappeared entirely? is there an equivilant way to do this?

I found that disturbing too...
However the system changed completely. You can no longer define the super-class directly in Interface Build, however you can still define classes there with IBOutlets and IBActions.
First, to instantiate a blue cube as a custom object, simply drag a blue cube from the Library windows inside : Library --> Cocoa --> Objects & Controllers --> Controllers.
To set the class, go in Identity inspector (CMD + 6) here you'll be able to define the class name, its outlets and its actions, you can even define the action argument type (sender) here, however, weirdly, they took the ability to add the colon directly at the of the method name, so you'll have to add it yourself.
However, Apple documentation advise you to add methods and outlets directly in Xcode and not in IB, "Whenever you want to create a new controller class, or add an outlet or action to an existing class, do it in Xcode."
Indeed, if IB is opened at the same time, it will update the class's outlets and actions directly, Xcode and IB are more binded together than before.
Message was edited by: PsychoH13

Interface Builder Library?

Is there a library of additional items which can be imported into Interface Builder, either from Apple, third-party, or open-source projects?
Apple provides all the basic elements, but either I haven't learned how to take full advantage of advanced use of the existing items, or some other common items are missing. I would think with the insurgence of new developers and platforms, specifically the iPhone and Cocoa Touch, there might be additional packages or libraries available.
For instance, I like the revolving picker, but for something a little less flashy, a simple pop-up list similar to a web-based select, would be a great little item, allowing for single or multi-item selections.
I'm sure I'm not the first or only developer interested in being to re-use well crafted elements.
Another example is the info light or info dark UIButton. Since I didn't feel comfortable crafting my own programmatically, I put an info light button in my xib file, and programmatically put an opaque circular graphic right over the info graphic, userInteractionEnabled=NO, and voila, functionally the same, but the screen presence is different.
Having a larger library seems like just the thing.
Are there any out there?

Have you looked over Adding Custom Objects to the Library in the Interface Builder User Guide? That feature doesn't provide everything you're asking for, but it might come in handy.
It might be good to remember that IB doesn't create objects, and the xib file doesn't include instructions on how to create an object. IB just specifies an object which must already be defined somewhere. So any 3rd party icon library would not only need to have an API for IB, it would also need to include a framework or static library to actually create the new objects represented by the icons.
Another point to remember is that the appearance of an object in IB doesn't determine what an object's class will be at runtime. That's determined by the Class you specify in the Identity Inspector. So if you have a custom class in your own library, you can use that class in IB by dragging an "Object" (cube) icon into a window, then setting that icon's identity to the custom class.
Hope some of the above is useful to you!
\- Ray

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.

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

How to define interface builder outlets in Cocoa-Python?

Similar Messages

Maybe you are looking for