As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 9 years ago.
I usually used to do every thing programmatically, what I mean is I am not using the Interface builder instead I do every thing in the code, like UIButton or UITableView, etc..
So can anyone tell me what is the best for programming iOS, or does that make any difference on the application performance or any thing else?
I am new to programming so I wanna hear that from someone in the field, I searched in Google but I couldn't find a clear answer.
Thanks.
The advantage of using IB is that it allows you make interface really quickly without checking a hundred times that a label should be moved up or down by pixel or two. But when you use IB you can't inherit nib files so if you have a lot of common interface features in several view controllers across your app you probably should use just code.
You really should separate your views from the code. This is what for Interface Builder was made for.
It builds xml files, apart from your application logic, so when you'll need to change anything in design you won't have to touch your code, and mess anything by mistake.
All modern program designs separate view from business logic: MVC, MVVM, MVP and so on. It is considered the best pattern for programming.
Related
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 9 years ago.
I'm trying to create an application for the iPad but I would like to create a user interface with different styles and controls to those offered in xcode. I would like to create something with an interface like StumblUpon, Flipboard or any other applications that you can see over here http://www.iospirations.com/. I don't know if those kind of interfaces are created with custom controls or some kind of library. If any of you can give some pointers or directions for things to read or try I'll be very grateful. I don't think i can build an interface like those just dragging the standard controls...so that's why I'm completely lost here.
Thanks for your time!
It really depends on what you want to build specifically. You might customise some standard components using UIAppearance Proxy:
http://developer.apple.com/library/ios/#documentation/uikit/reference/UIAppearance_Protocol/Reference/Reference.html
and some other components you would build from scratch, perhaps by stacking up several views and moving them around programmatically, with custom backing classes and logic. Move them around using UIView animations, or apply transforms to them using C drawing.
Another option might be to look at if there is any open-source components on GitHub that you could use/customize. iCarousel is a good example of this, take a look through the source code.
https://github.com/nicklockwood/iCarousel
Your question is very general, the bottom line is if you want a custom component you need to build it from scratch. I'd advise against doing too much of this, as it makes your code harder to maintain, harder to to keep inline with iOS updates, and usually includes doing loads of work to achieve roughly the same function that Apple gives you for free
Another good resource (not free though) - http://www.appdesignvault.com
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
From the UIWebView, The UIWebView class should not be subclassed.
I just want to know why. There is no more detail about this.
Because I met a memory out issue in my project, which create one extended UIWebView, which could cause memory out issue. Otherwise, just create the UIWebView instance will not cause the issue.
That is why I want to address this problem and try to analyze more.
Thanks for the guy to give some comments in terms of the design pattern with MVC.
I hope to close this once get some comments for memory management.
Thanks,
iOS development works on MVC concept and V part which is View should be as generic as possible. If you write a custom view, when the model changes the view has to change as well. It becomes interlinked..This means the view cannot be reused, especially when a new UI comes out..Better to put the code in the controller portion...Key: Keep the view as generic as possible..
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
So I have built an iPhone application using built in SDK controls, just wondering how I could make better looking applications like the ones displayed on http://pttrns.com/
Directions to books or tutorials would be grateful as well as any tips.
Take a look at Scoutzie. It's a website for finding mobile designers and design ideas.
Learn the art of graphics design, build your image assets, and stich them onto your views. You can do this a plethora of ways, not the least of which is custom drawing, image views, pattern colours... Alternatively, you can hire a designer like most of us do. :)
Point is, good iPhone interfaces are usually skinned by designers, or developers with design experience.
Look at good apps and try to recreate the experience. When the UI Layout etc is good, there really is not much left thanlearn how to create sophisticated animations and learn photoshop!
In addition, apple has several guides in the UI topic. Look around in the dev center, there is much to discover!
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 9 years ago.
Kind of a noob question, but is there a good way to search for custom controls/objects/frameworks? I was able to stumble upon the Three20 framework and some other things like custom progress bar views and other custom views...but I just kinda 'happened' upon them. Is there any standard place where people post their stuff besides doing a github-wide search?
For UI elements, check out Cocoa Controls. I unfortunately don't know of any other centralized repositories for categories etc. All the useful stuff I've stumbled across came from github, stackoverflow, and/or repeated google searches.
I would recommend staying away from Three20, though. Having used it on some large projects in the past, the framework tended get in the way more than it helped IMHO. Their drawing libraries have some nice conveniences, but it's a lot of bloat to add to your project if you just want a single UI element that the framework provides.
One good site that has aggregated a lot of these is http://cocoacontrols.com/
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
I am new to iOS development and am trying to figure out how it is MVC.
I see how there are controllers that produce views.
However, where are the models that represent data? I just see iOS development as controllers that "delegate" (I still don't see what that çlearly means.) functionality to each other.
iOS development done the right way is a great example of true MVC programming. If you really want to see this in action, check out Stanford's iTunes U videos.
The model for iOS will be either a CoreData store, a manually built class, etc. The ViewController is the controller and the View will be the nib or storyboard scene that contains the UI elements and is wired up to the VC.
There is a summary of MVC in the Core Competencies Guide
And there is a more detailed description in the Cocoa Fundamentals Guide
Simply put - MVC in Cocoa means that views don't get their data directly from the model objects, and model objects don't update their state directly from the views. There is always a controller in the middle that is mediating the communication.
In simply words you create views and code separately. Then you link them between themselves using class name, variables and methods. Likewise for program data.
But it is too basic question. You can learn it from the first pages of all the books about objective-c