Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
Is it possible to make either a jailbreak app/tweak or regular app that could display two times on the status bar on iPhone? Is such a thing possible and / or that's already developed?
I have a very special friend in another country and sometimes I forget what time it is there. Having to check the time on the clock app is a pain, especially when talking on the phone. I can't imagine a simple clock could use many system resources.
Is it possible to make either a jailbreak app/tweak or regular app that could display two times on the status bar on iPhone?
Definitely, most likely using MobileSubstrate. What I can imagine as a solution is roughly:
You hook into one of SpringBoard's initialization methods.
You create an UILabel and add it to the status bar as a subview using the addSubview: method.
You spawn a timer (use NSTimer, Grand Central Dispatch or whatever suits you) to update the text of the label every minute or so. You can use NSDate and perhaps NSLocale (I don't have the docs in front of me right now) to find out the local time of another country.
This is is why Apple hasn't already done this. They have way to many icons that can appear up at once. Adding another time would take away precious space for these other icons. When I max out the bar it bumps other icons off, like right now I have music playing but the "Play Button" Icon got bumped off by the "Navigator" Icon.
Check out this site, it shows you most of the icons if they haven't added any more in the iOS 6.
https://sites.google.com/site/appleclubfhs/support/advice-and-articles/understanding-ios-menu-symbols
Your going to have to go with jailbreaking probably or hard programming, because the status bar is basically apart of the iPhone screen.
Best of luck!
Related
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 12 months ago.
Improve this question
I am building a flutter app where i use some flutter-animations tag like hero tag which is useful to take a picture from one screen to another using smooth animation. Now i wonder, when we see animations which are not like an image to shows in just one go but it shows in frame by frame and for every frame flutter change it's state then it must be slow down the performance of app in my opinon. What you say sir?
Yes. But by that same logic, showing anything on the screen also slows the app down. Why even have an image at all? Why not just display an empty screen?
So clearly, the real question is: is the tradeoff worth it, does it make your app drop below 60 fps or whatever you are targeting? Does adding an animation make your app easier to use and more polished? In almost all cases, the answer is yes, adding animations is well worth it.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
Is it better to build separate views for the different screen sizes for the height of the iPhone. Or is it better to creat a #define IS_IPHONE5 and adjust the view's code based on the hight of the phone? Any other ideas would be appreciated.
Have you thought about using Auto Layout? It's the Apple-recommended way to do this.
You can find some posts online bashing Auto Layout. You shouldn't be discouraged by them, because from what I've seen they can mostly be divided into 2 groups:
incorrect understanding of Auto Layout by the authors,
poor Auto Layout implementation in Interface Builder in Xcode 4 (it's gotten a lot better in Xcode 5).
Using Auto layout is great option. Other then this you should create different views and use them depending on device and screen.
Creating different views for the different device screen resolutions is not a good idea. You should try to avoid constants when it comes to screen dimensions. If Apple decided to bring out a 6" phablet tomorrow with a different resolution you'd have to update your app and create an entirely new view for that resolution.
If you no longer have to support iOS5 then you should definitely go for auto layout. Take a look at this Ray Wenderlich tutorial to better understand auto layout:
http://www.raywenderlich.com/20881/beginning-auto-layout-part-1-of-2
If you still need to support iOS5 then go with auto-resizing masks (the above tutorial also explains auto-resizing in short), it has its limits but you can correct this in viewDidLayoutSubviews in UIViewControllers and layoutSubviews in UIViews.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 3 years ago.
Improve this question
I'm making an iPhone app that primarily focuses on loading webpages in UIWebviews. To show the user that the web page is currently loading, I'd like the screen to display a loading animation while the page loads, similar to the eBay app:
How can I do this? Or, at least, what UIWebView methods could I use to tell me if the page is loading and that there is internet connection (so it's not blindly trying to load forever).
You can use MBProgressHUD, a open source component which will do a lot of the work for you.
You'll need to create a delegate of the UIWebView and respond to the didStartLoading and didFinishLoading messages (that's when you'll show an hide the progress view).
A simple way is just having it there until you need it and setting the alpha from 0 to 1.
You would just need a gray thing (or whatever that thing is) and a activity indicator.
You could also dig into the alerts section in apple but I think the above is easier.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
I know that it's trivial to add a red number badge to an app's icon on the home screen. What's the best way to get a badge that looks like this within my app? There are some classes I've found online that can do this, such as MKNumberBadgeView, but none that I've found look completely right. Facebook, for example, implements red badges within the app perfectly as far as I can see. Did they just build their own badges by trial and error? Any suggestions would be appreciated.
Thanks,
Luke
Where do you want the badge? The standard badge can trivially be added to a UITabBarItem through the badgeValue property. It is documented here.
I am using this by Sascha Paulus -
http://www.spaulus.com/2011/04/custombadge-2-0-retina-ready-scalable-light-reflex/?lang=en
Which is a class that you can drop into your project, easy enough to customize for the appearance you are looking for. I had a slight issue with the placement of the number within the red badge so I shifted it slightly. Other than that, all good.
This one looks 100% like the Apple one and it's also completely customizable: https://github.com/JaviSoto/JSBadgeView
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 5 years ago.
Improve this question
Apple requires you to make your app work nicely, whether iAds are available or not, which makes perfect sense. What I'm wondering about is the transition between those two states.
Should I create a view that has a space for an iAd and push it to the screen. If no iAds are available, I then have to remove the ADBannerView once the view is shown.
Or, should I create a view that has no space for an iAd in the first place and create such a space whenever an iAd finished loading?
Apple seems to use the first scenario. But I find it visually more appealing when the Ads slide in, once they are loaded rather than sliding out a failed ad. What do you think? Is there any reason not to go for the second scenario?
The second approach seems reasonable and more pleasing. It comes with a cost on the implementation / design side. If this doesn't matter, go for it.