I am new to Xcode development. When I first opened Xcode 4.2, there were different types of applications we can build (Master Detail, Page Based, Single View, Tabbed, Utility, Empty Application) using Xcode.
I am somewhat confused about how different they are from each other. I did some search but so far I am not able to understand their basic difference. How would I know which application to select to start developing my own application.
If someone can explain their difference and usage to me in layman terms.
Thanks.
Those are different starter template's provided along with Xcode. You may decide not to you use any of the templates and go with an empty project.
Below is the brief overview of each of the templates.
Master Detail - Template which has pre-created Parent-child views with navigation controller, typically for iPad for different orientation.
Page based - Similar to iBooks app.
Single View - Starter template with a single view. you can add multiple view whenever required.
Tabbed application - View controller with tab bar at the bottom of the screen.
I hope you got the idea. In my opinion, as a starter, you should go with creating a single view based application.
Good luck.
Related
I have a single-view application open. I need to have two storyboard views (UIViewControllers), because one is a Table View, but when one of the Table View elements is selected it brings up another screen with a normal UIViewController. Is there any way of creating a second storyboard view (UIViewController)?
Of course! Those templates Xcode provides are in no way "set-in-stone". When Xcode created your Single-View Template, it just gave you a base for creating something more. You can create additional classes, view controllers, views, and resources (other than what Xcode starts you off with in a few ways).
To add another View Controller to your Storyboard, just drag and drop one from the Object Library:
It seems like you do not have a basic understanding of using or developing with Xcode. I would recommend reading over all of Apple's documentation on Xcode before going any further. The Building A User Interface section may be of particular interest to you.
I have recently noticed something odd with Display Suite. I am rather new to Drupal so if its something on my mistake please do not make fun of me.
But I have noticed that no new custom display settings (view nodes are being added to either node or field collection) previously it worked perfectly but now if I create a new view mode and attaching it to the node / field collection it seems it does not apply to it.
See the photos attached. Any suggestion?
http://oi59.tinypic.com/727fqp.jpg
http://oi59.tinypic.com/jb44cj.jpg
P.S. I have cleared drupal cache but it still keeps not working.
Thanks in advance
Fist I'd say that if you're a new user to Drupal, using Display Suite is really jumping into the deep end. It's a really powerful module and creating View Modes is just the tip of the iceberg of what it can do. Second, when you create a new View Mode, you're doing it for an Entity (such as Content Types, Users, Comments, File - but not so much a single node, nor a field). You can find more info on what View Modes and entities are here. You don't need Display Suite to activate other View Modes but if all you're wanting to do is create a custom view mode, the lightweight module to use for that is Entity View Mode. Lullabot does a nice job of explaining this module here.
Anyhow, modules aside, note that the controls for turning View Modes on and off are only found on the 'Default' view mode for a given content type, ie: when on the Manage Display page of whatever content type you're working with, at the top right under the main tabs, you'll see your activated view modes. If you select 'Default' then you will see the control to turn on/off other view modes.
Now, maybe you're wondering how do you see what a particular View Mode looks. To do this, you're best off using Views as it ties in nicely with View Modes.
Hope that helps.
I'm have done some development on iOS using Storyboards. Now I'm building on app for Mac OS X and it seems that an equivalent for Storyboards does not exists.
For instance, I'm need to build some kind of wizard, which contains four different windows or views (step 1 to 4).
Currently I've created one Window xib (the standard MainMenu.xib), containing a window with the first view, and three other custom views. Using this approach, I can create outlets and actions, making me able to change the contentView of my window, e.g. when clicking an button. This seems as a fair solution, and my views are all grouped cleanly inside a single xib. But this also cause that the logic for all the view should be handled by the same File's Owner, right? For instance saving the settings on each step and controlling the interaction between the different views.
How is the preferred way to handle a situation like this? Should I instead create four different windows, and maybe in four different xib-files? If you know an sample project somewhere from the internet showing how to handle multiple windows, please give me a hint.
You can make use of the NSViewController class for this purpose. Each view controller will be responsible of loading a xib associated with it and all logic associated with the views can go inside the controllers (Same as in iOS). The MainMenu.xib can now load appropriate views after initialising the required view controllers.
Here is a sample app for your reference.
https://developer.apple.com/library/mac/samplecode/ViewController/Introduction/Intro.html
In xcode, go to File->New->New File
Add an objective C class and set it to subclass of "NSViewController".
This will itself create yourController.h, yourController.m and yourController.xib.
Now you can keep your view and its controller class seperate.
Hi all
I am a newby app developer infact I am still in high school, I am making a radio app and I have made the channel list using interface builder (mainwindow.xib in xcode) now I want to be able to click on a link/button in the main window and that take me too a new page in the app where I can have a play button and maybe a symbol etc. I know it is probably a trivial question but I am stumped, but how do I go about doing this if someone could place it out in step by step or even a few screenshots it really would be apreciated?
Many Thanks in advance
David
So, basically you want to be able to use a UIButton to take you to an entirely new view controller? Well, for your particular case, I'd recommend trying a Tab bar controller. When you create a new application, it gives you an option for what type of template you want, and Tab bar controller is one of them. This creates a black bar across the bottom that lets you cycle between several different independent view controllers. Just create a new tab bar application, and copy/paste your existing code into one of the views, then use the other one(s) to do whatever else you have in mind. Hope this helps!
I am a software developer working with different ERPs based on different platforms. Java is one of them. I've decided to learn Eclipse RCP. I am trying to understand the basics of Eclipse RCP regarding its views and editors concept.
Working with other platforms I don't care how to make a form in GUI. All the forms in my application can show data say from a DB or save this data back into the DB. And I don't care if a form shows the list of entities or a detailed info about an entity.
Here, in Eclipse RCP, I see that a form can reside in a view or in an editor. What is the difference between them? I would like to hear these differences from a business point of view, please. Or maybe these differences can be explained only in terms like "editor cannot have its own toolbar"? I would like to understand the purposes or common usages as a user not as a developer.
Thank you.
The wiki has a goof FAQ on this topic
There is generally only one instance of a given view per workbench page, but there can be several instances of the same type of editor.
Editors can appear in only one region of the page, whereas views can be moved to any part of the page and minimized as fast views.
Editors can be in a dirty state, meaning that their contents are unsaved and will be lost if the editor is closed without saving.
Views have a local toolbar, whereas editors contribute buttons to the global toolbar.
Editors can be associated with a file name or an extension, and this association can be changed by users.
Some advanced use are mentioned
here, about the ability to reuse an editor for several types of file.
or there, for linking to an editor
Views can have a different organization than editor: see fast view.
In broad terms:
Use editors for the main editable "documents".
Document lifecycle (open/dirty/save/close) fits neatly with editors.
Use all sorts of rich controls, hyperlinks, etc. It doesn't have to be a text editor.
Use views to provide optional supplementary analysis/manipulation of the document in the current editor.
Use views for other (often cross-document) navigation, analysis, search results, etc.