Creating an image of an xib(interface builder)

Hi all,
Actually i wanted to create an image of a xib file by the clicking the button present in xib file within the application. The generated image to be stored some where safely(i.e documents folder).
Waiting for the response.
Thanks in Advance.
Radhar.

Hi all,
I got the solution for the above issue. You go through the below link:
https://developer.apple.com/library/ios/#qa/qa2010/qa1703.html

Similar Messages

How do I create an image of our standard MacBook build?

Hi,
I've been set the job of creating a standard image for all our companies MacBooks. We currently have a build process, but this takes several hours for each MacBook and isn't very convienient.
What I would like to do is install all the required software, configure all the settings, then take an image that we can deploy to all subsequent MacBooks.
I know this is a pretty simple procedure for a Windows machine, but from my research, unless I'm missing something blindingly obvious, it doesn't seem to quite as simple on Macs.
All our MacBooks currently run on Mountain Lion 10.8.5, we are unable to upgrade to Mavericks at the moment due to some support issues with disk encryption software.
I am currently using a MacMini with Server installed 10.8.5.
Can someone please offer me some advice?
Cheers
Dunk

If you perceive the Windows procedure to be easy, then the Mac process will be a slice of cake and a bowl or cherries. Cloning OS X is incredibly easy. There are some gotchas when new hardware is released, but in general, it is cake. There are many ways to do this.
The easiest, is a disk image clone. You have already figure out the steps. Build a machine exactly the way you want it. But don't personalize it in any way. Don't bind it to the domain. Don't create user accounts (other than admin), and remember to change the machine name to something the you will remember to change. I tend to use CHANGEME. Once you have the master image, the steps are basically:
1: Boot the master machine to its recovery partition or into target disk mode.
2: Use Disk Utility to create a disk image of the entire drive. Compressed with no encryption is usually effective.
3: Save this to a drive other than the master drive.
4: When the capture is complete, go to the images menu in Disk Utility and run Scan Image for Restore on the disk image you've just created.
5: When done, use that disk image and the Restore tab of Disk Utility to restore back to other machines. Once again, boot to the other machines recovery partition or build yourself a boot service drive.
Now, beyond this, you can get into NetRestore (requires and OS X Server), or tools like JAMF. You need more than 50 Macs for this to be cost effective.
Imaging Macs is cake. New SSD based units can be cloned in less than 10 minutes.
R-
Apple Consultants Network
Apple Professional Services
Author "Mavericks Server – Foundation Services" :: Exclusively available in the Apple iBooks Store

Variables in BPS populating the template built using web interface builder

Hi All,
I have a issue :
I created some variables in bps0 (under a planning area) based on Fiscal Year, Fiscal Year/Period, Posting Period, Cal. Yr /Quarter and Version.
Then I created a template using the web interface builder .
The end user goes and puts the varaibels in the SEM template and that will run the BW queries in BW (ABAP code has been written to popluate the values entered in SEM tempalte in to BW variable screen).
Now the problem is it works well for all values other than for #(not assigned).
What should be done to make it work even for #?
We do not have # as the value in master data for all the above info objects. We have # only for 0version and for the rest I can't even see the master data as it says " master data is not maintained" .
when I come back and look in bps0 then I see that the values entered in the SEM template are getting accumulated in selection conditionds in bps0 (when we click on the variable then when we see the selection conditions there it is getting accumulated)
Can anyone please suggest a solution to make the # (not assigned) work and to clear the selection conditions table after refresh of the SEM template?
Thanks
Sri

Hi
You should create a BEX Web Query and integrate it in the upper level of WEB Layout.
Check this link for a step by step guide about this topic
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/how-to%20guides%20-%20rig%20official/bi/nw04/how%20to%20integrate%20bex%20web%20applications%20into%20bps%20web%20interfaces.doc
Ciao
Andr

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.)

Interface Builder refuses to see "@2x" image files - AGAIN in 5.0

This was a problem in Xcode 4.0. Eventually, it was fixed.
Now that Xcode 5.0 is out, it's back to the same problem. And, Xcode 5.0 asks you to convert your XIB files to the new format, so it can screw you up without you even knowing it!
PROBLEM:
The @2x images are NOT visible in interface builder. It cannot be selected from the list. It shows an unknown image (question mark) if you manually type it in...which renders layout design pointless if you need those @2x files.
Many, many, many developers reuse the @2x images in the iPad xib files. Now, all of the images will either be shrunk or stretched from lower-res images...because it REMOVES the @2x extension for any images it finds in a xib file.
SUGGESTIONS in the past:
- Copy your @2x images to ~ipad images, because the framework will automatically use it.
NO. I don't need to up the size of my app significantly with duplicate images.
- Rename the @2x images to something else (e.g. -2x).
NO. Because the framework will no longer auto load them for iPhone retina.
- Just manually name them with the @2x and live with the broken image in IB.
NO. Because most people actually care about the layout.
- Create a separate iPad app.
NO. Because customers shouldn't have to pay twice for the same app for 2 different devices.
- Programmatically change the images to @2x if it's an iPad.
UGH. This is what I've ended up doing, but how ridiculous is that?
Anyone else found a way around this?

NSString* path = [[NSBundle mainBundle] pathForResource:@"imageName" ofType:@"png"];
NSData* data = path ? [NSData dataWithContentsOfFile:path] : nil;
UIImage* img = data ? [UIImage imageWithData:data] : nil;
if( img ) [button setImage:img forState:UIControlStateNormal];
OR
NSString* path = [[NSBundle mainBundle] pathForResource:@"imageName" ofType:@"png"];
UIImage* img = [UIImage imageWithContentsOfFile:path];
if( img ) [button setImage:img forState:UIControlStateNormal];
Both should bypass auto-scaling.

Interface builder is unable to open documents of type iPad XIB

Hi,
I got a application from my teammate, and it is for both iphone and ipad devices (which it is developed under iPhone SDK 3.2).
I have iPhone SDK 3.1.3 installed in my mac book. When i tried to compile the application for iphone simulator i got the following error.
Interface builder is unable to open documents of type iPad XIB.
The above error is for interface builder created for ipad.
My Question is we can't compile the application on iPhone SDK 3.1.3 which the application developed under iPhone SDK 3.2?
Please shed some light of this?
thanks
mindus

Go to your project settings, and delete the line that says Interface Builder Plugin search path or something similar.
the exact line in project.pbxproj is: IBC_PLUGIN_SEARCH_PATHS = "${PROJECT_DIR}/**";

Interface Builder refuses to see "@2x" image files

I'm making some apps with support for all three major iOS platforms: iPhone&Co, iPhone4 and iPad. This support means, naturally, having larger-resolution images for the latter two platforms. Currently I'm making the apps universal, so the same app will run in all of them.
Since most of the double-resolution images of the iPhone4 version of the app can be used as-is in the iPad version (only things like background images have to be made separately for all three types of platform due to differing screen resolutions; the rest can be done with simply laying out the elements appropriately in the iPad as compared to the iPhone4, using the same element images for both), it would be a huge waste of space to make separate images for the iPhone4 and the iPad, when these images would be completely identical. Thus it only makes sense to reuse the same "@2x" images of the iPhone4 on the iPad version of the app.
This worked nicely for a while. However, at some point quite suddenly (I don't really know what happened), Interface Builder started to completely refuse to see any image files with a "@2x" in their name. It won't show them on the drop-down menu where you select an image (eg. for an UIImageView or UIButton), and if you write it manually, it will refuse to show it (only showing the question mark image symbolizing a missing image file). The image will show ok when running the app, but IB simply refuses to acknowledge the existence of such images. If I rename the image such that I remove the "@2x", then IB will accept it, but not if it has those characters.
As said, IB did see the "@2x" images at some point, but for some reason now it doesn't. (This is a bit of a mystery because I don't remember this happening after any kind of SDK upgrade or anything.)
This tells me that this is either 1) a bug in IB, or 2) intentional behavior, and the "@2x" images should not be "abused" in this way to create an iPad version of the app properly.
If hypothesis 2 is correct, then what is the proper way of using the same images in both the iPhone4 and iPad versions of the app? Duplicating the image files would be an enormous waste of space (the apps are quite graphics-heavy).
One "kludge" that comes to mind would be to create soft links for the images so that the iPad versions of the image files would just be soft links to the @2x iPhone4 images. However, I don't know if the bundling mechanism of the iPhone SDK supports soft links, or if it will simply make copies of the images (in which case each such image will end up being stored twice in the bundle).

WarpRulez wrote:
If I rename the image such that I remove the "@2x", then IB will accept it, but not if it has those characters.
I guess I don't understand why you want a solution when you've found one already.
Just use ".2x" or "-2x" or whatever.
Report the bug, use your workaround and move on.

Interface Builder does not open when I click Mainwindow.xib file on Monotouch.

I did a lot research about it, What the most of view say it is because of the iOS SDK, not because of the MonoTouch, they say that iOS SDK provides the Interface Builder? Any suggestions? Thanks in advance. iOS SDK Version 4.3.

Does Monotouch work within Xcode? I'm not sure what it is. If so then Interface Builder does not open a separate window in Xcode 4. When you first go to your .xib, you must select your "Window" to see the window. Otherwise you get an empty grid. Here's an image with the "Window" selected. I have it set for Mac applications not iOS but what you have should look similar.

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.

When I click on the xib file interface builder doesn't open, I have the newest version downloaded from the app store

as the title says when I click on the .xib on the left hand nothing happens I just get the iphone screen and checkered background no interface builder.

Interface Builder is no longer a separate application. All editing functions are now integrated into Xcode 4.
Xcode 4 User Guide
Xcode Basics Help
Xcode 4 Transition Guide

Set background image in the Interface builder

Hi,
Is there a way to set a background image for a View controller through the Interface builder? I'm using story boards.
If not please tell me how to do that programatically. I need to set this background image for all my UIs.
Thanks

Remember that the client is running from a browser. You need to have the file be available to the browser and that means having it be served by the web server. Place the image file in a directory available to the web server and map that directory to a virtual web server directory and specify it with a url relative to the web server root: /images/your_image.gif

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.

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

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.

Creating an attribute editor like panel from Interface Builder

The Attributes Inspector from Interface Builder presents the user with a great set of options that are neatly organized in folding panels. I really want to do something like this for a project I'm working on to help organize a large set of options that I plan on presenting to the end user.
Only problem is I have no idea what this widget is called or even if its available from Cocoa. I thought it was a NSRuleEditor but I've seen no examples so I'm not sure. So if someone could help point me in the right direction that would be awesome. If you know of an example project in the Examples folder that would be even better. Thanks a lot.

The IB toolpanel is just built out of stock IB parts but there are quite a few of them. As far as I can tell it's just an NSPanel with a toolbar at the top and then at least one NSSplitView with an NSScrollView inserted into it.
To add something like this to your project - although I would recommend starting simpler for learning - simply drag an NSPanel into your IB window and then drag an NSScrollView on top of it and it will fill the NSPanel and you can modify it from there. You can also drag an NSScrollView directly into your nib and work on it and then drop it on the NSPanel if you want. This might make the process easier/more clear for you. If you put an NSTextView into the window it will automatically show and hide scrollbars depending on content unless you tell it otherwise.
Custom views can be confusing but since NSPanels can be made to show themselves as soon as a program launches (I think this is their default state) your content should show up automatically which makes it easier than creating regular windows and then worrying about showing their contents.
Do this help?
=Tod

Creating an image of an xib(interface builder)

Similar Messages

Maybe you are looking for