I am developing an iOS app in iOS 7 that requires me to display a particular time.
Though this is not a programming question exactly, can anyone suggest me the component that allows me to display the time in a nice analog clock?
Did you search Cocoa Controls for example? This is the pleace where you can find lots of cocoa visual components like clocks.
Related
I'm beginning some OS X development, I am reasonably accomplished with objective C and UIKIT.
There doesn't seem to be as much online about moving from iOS development to OS X as I thought there would be!
Anyway, I found a decent tutorial over a Ray Wenderlich, that basically explained the differences, (multiple NSWindows, then add to them NSViewControllers etc)
What I would like to do is make a little app that shows info in the status bar (beside the Wifi icon etc)
Basically all it does is have an NSStatusitem that has it's title set with info I want shown (e.g. current song title)
I've got one going and it's working ok so to my question:
I've got Application is agent (UIElement) (so I cannot see a dock icon or menubar)
The code for my little app all resides in the app delegate, now from iOS dev i'm sure this is not the right place for this code, but since the app is a just a status bar item, that has it's title updated I don't think I need a UIViewController etc....
Where should my apps logic go?
Anything online to transition from iOS to OS X?
As you dont have much work with NSWindows and NSViews, you surely dont need NSWindowController or NSViewController.
And I think for this kind of app even your AppDelegate class is enough and best place to put all your logic.
If you have some models then you can break your code upto that, and use it in the AppDelegate itself.
Transition from iOS to OSX.
If you are good in Objective-C then you dont have to worry about few more Cocoa-Controls especially GUI levels, you have full support of Documentation.
Switching between iOS to OSX, vice-versa is not to difficult, but yes if you end up with system level then you need to interact with OSX too.
As stated earlier, if you know Objective-C well, then you should not face major problems. However, there are some differences. I found these following documents helpful:
About Developing for Mac
Migrating from Cocoa Touch
I've finished up my first iOS 5 app (and only third iOS app overall) and I'm wondering if anyone out there has any recommendations for adding that touch of class, polish, professionalism, etc. to a plain-vanilla iOS app. I've taken a look at an iOS 5 appearance tutorial but I don't find it extremely helpful. What do you do to add polish to your UI? For example, do you add a logo view in your UINavigationBar? Do you create custom UIKit control backgrounds/images? Do you remove rounded edges from controls? I would especially appreciate any input related to how you use the new Appearance options in iOS 5 to accomplish your UIX goals.
For inspiration, look at the apps featured by Apple in the App store. Maybe hire an artist or designer familiar with iOS devices and their users (if you are not one yourself). There seem to be lots of creative ways to potentially "delight" the user, customize things for your specific app's purpose or customer base, but still stay within the spirit of the HIG.
I have a native objective c ios application that I would like to convert to run on my Mac. How could I begin such a journey? Is there a way to run a native objective c ios app on a mac without ios simulator? Or some sort of in place framework I can use?
Although your logic code will be fairly portable, there is no quick way to port an app from iOS to OS X. The only way to do this is to create a new app from the Xcode template and move your code accordingly.
Remember, the View paradigm in OS X is completely different than iOS (i.e. UITableView vs. NSTableView). How will you handle user input? Is a series of tableviews the best way or would an NSBrowser work better?
There are many things to consider and at the end of the day you'll need to account for that when creating your new app.
You are going to have to re-implement the GUI in App kit, App Kit uses a lot of the same design patterns as UIKit, delegation, datasources, view controllers, View hierarchy with views having a bounds and a frame, responder chain, Nib files, if you are competent with iOS programming you will pick up Mac OS X very quickly. If your application is structured with good business logic separation from your GUI, you will be able to use all your model classes with little or no modification. Foundation Kit, Core Data and others are on both platforms and they are very similar, it is usually the case that the iOS versions have reduced API and so going other direction, Mac OS X to iOS, can require some work, for example iOS does not have NSXMLDocument classes.
I have implemented iphone application using Titanium..But I want to convert in to android application.
Is it possible doing small chnges?
There are changes, but not major changes. Here is what i would do in my case?
Understand How iPhone works and Android works. Compare them in terms
of working model and OS Architecture. This will purely give you more idea on how to make an real Android App... else you would end up cloning your iPhone feel to Android again.
List out all the components i have used in iPhone and check out the
similar component available for me to replace. { For instance,
TableView has a delete option for iPhone and not for Android }
I would remove the back button implemented in iPhone and check how i
can move between windows with the Android BackKey.
Styles and Animation i have used in iPhone will not be the same for
Android. I think they don't have full supported ones too.
For example: style:Titanium.UI.iPhone.ActivityIndicatorStyle.BIG,
maybe you experience some performance differences depending on your implementation since the javascript engine is not the same. if so, you maybe need to restructure your app to ensure a performance enhancement.
Developing for the iPhone has been my first experience with objective-c and first in-depth experience with xcode. How difficult would it be to port an openGLES iPhone app to the OSX desktop using openGL? I am not asking about user interface - obviously there is no equivalent to cocoa touch UI on the desktop. I am asking specifically about the app delegate and openGLES layers. Are there any major hurdles? Is it as straight forward as simply creating a new app delegate in a project of type cocoa?
I've started looking into just the same thing, and it appears that OpenGL-heavy applications would be among the easiest to backport to the Mac. Pretty much everything in OpenGL ES is present in OpenGL on the desktop (with the exception of some of the fixed-point stuff), so that code can stay the same.
The way that OpenGL is handled on the iPhone is via a Core Animation layer (CAEAGLLayer), rather than a specific view. Therefore, you should be able to transfer that across to a Leopard-based desktop application, although you'll need to convert all references to EAGL classes to their OpenGL equivalent (EAGLContext to NSOpenGLContext, for example). You could render into a CAOpenGLLayer that's displayed by itself, or use that layer to back a custom NSView.
The fundamental structure of a desktop Cocoa application will be different than a Cocoa Touch one, but you should be able to start from one of the Xcode templates and add back in your components from the Cocoa Touch application.
Again, I haven't yet done this for my application, but it looks reasonably straightforward.