I have another issue related to Views, and i've ended up here dealing with Views and Windows in general. My understanding of all the fundamentals of iPhone development has been turned upside down.
Can somebody explain, or point to a reference, the difference between these 2 templates?
Ex: My app doesnt show a Window in the Interface Builder. Should I have one? When should i have one and when should I not?
The Window-based Application template provides just an application delegate and a window.
A View-based application will start you off with an application delegate and a window, as well as a view.
Your application doesn't show a Window because the view that you are (most likely) viewing and editing now is loaded by the Window, which is in a separate XIB.
Related
I'm trying to recreate the Camera.app buttons and interface from iOS in my own, custom camera application built on GPUFilter. Specifically talking about the Flash, Options, and front vs back camera button toggle that are across the top of the app:
Curious to know if these are built into Storyboards as UI objects or if there's another easy way to recreate these without totally reprogramming. I'm also interested in using the overlay table view that they use (in picture above) for options.
Thanks!
You can using AVCamCaptureManager and AVCamRecorder classes. Apple has a demo program build on its developer site here.
I want to create a new navigation based application that needs to be work with only i pad?How can i do that.when i start the navigation based iphone application and then try to upgrade the target to ipad.then there is two target files,and two main window xibs ,it is confusing me ,i need this application to be work only in ipad.i changed the device family to ipad?thsese are the steps done by me
1)created a new navigation based application in 3.2 with core data enabled.
2)upgraded the target to ipad(not universal only ipad)
3) changed the device family to ipad.
But this will give me two targets and two set of zib files,what to do?
is it enough? can anybody give the exact steps in achieving this?
As you've said, change the Targeted Device Family to iPad is enough.
If you still not feeling comfortable with the iPhone's files (main window xib for example), you can just delete them.
Start with a single view template, then embed the initial view controller in a navigation controller. But you don't see many iPad native full screen navigation based apps. A split view is more usual.
I've been following an excellent guide on how to create basic custom table cells and populate them via a plist. The problem i've run into is the guide is written for iPhone, and i'm developing an app on iPad, one of the key issues is when creating the project, the guide uses a Navigation based template for iPhone, where iPad isn't selectable. Later on the guide it says to add outputs to this controller.
I tried following the guide using a Window based template for iPad, but have run into some problems when connecting the output. In particular where I add my 'customTableViewCell' outlet to the 'RootViewController' (which is a UITableController) - in my iPad project, it's just a 'UIViewController'
Is there an easy was to solve this? or is developing it on iPad a totally different tutorial?
thanks.
On the iPad, the Split-View format is really for navigation. It has a root view controller that is a tableview. You might have good luck starting with that template.
In the Interface Builder, you can add UITableView by dragging it onto the view.
I have an iPhone app that I want to change into an iPad app. I do not want to make it universal. The result should be an iPad only app. The main problem I see is converting all of my .xib files. I realize that I will have to change some things around manually, but I would like as much as possible (including all of the painstakingly made connections in IB) to carry over. Also, if there are unlikely places where I need to change settings, please give me a hint to that as well. Thanks!
Xcode has a convert option. It gives you the choice between a new app or a universal one.
This will convert all your NIBs, but quite how useful that is will depend on how thorough you've been with the sizing options in Interface Builder. For me is mostly worked. A couple of minor tweaks for a couple of views and a complete rewrite for some others.
Of course you'll also have to work with view controllers that "manually" build the view.
The gotchas I found were around orientations (iPad apps should work in all four orientations) and with the screen size. There are also some oddities with the keyboard and modal views if you have any of those (there are a few kinds of modal view, and the keyboard does not always dismiss). As ever when you're making automated changes, testing is key.
The full process took me a lot longer than I was expecting.
Few thoughts for changing iPhone app to iPad app.
Xcode has the provision to change the current iPhone app to iPad app by using "Upgrade current target for iPad" menu command.
http://www.enscand.com/roller/enscand/entry/ready_for_ipad
resize all current view to the ipad size 768*1024(portrait) and then resize all the subviews respectively. the connections doesn't get lost by doing this.
I am developing web application for iphone. Is it possible to implement Tab bar controller in dashcode.
Is there is any option available for implementing tab bar using dashcode for developing web application.
Thanks
mindus
you probably could do it in dashcode but there are no library items that let you do it out of the box as it were. i think also that the limited real estate when Dashcode is targeting iPhone apps is such that you probably would not use tabs as a standard method of navigation and this may be the reason for it's absence. However if doing browsers and possibly iPad (which does not seem to be catered for in Dashcode at all) then this wouldn't be the case.
Quickly looking at Sencha Touch and Sproutcore touch i cannot see any tabbed paradigms. Which again is i suspect due to the nature of the Touch method of navigating where the vertical table view tend to be the norm.
To do it in dash code would be simple enough as you could simply use JavaScript + css to implement the tabs.