Re: iPad keyboards

2013-12-17 Thread Luther Baker
On Thu, Dec 12, 2013 at 3:08 PM, Rick Mann wrote: > > That's good to know; I thought they were requiring iOS 7. > > https://developer.apple.com/news/index.php?id=12172013a#top > Even so, does an iOS 6 SDK-based app not get all iOS 7 styling? I'd try > the experiment myself, but it's a bit of wo

Re: iPad keyboards

2013-12-16 Thread Maxthon Chan
Hangout is code-styled to iOS 7 fashion (pretty much in order to keep in align with their Google+ app which is already using iOS 7 SDK). Those non-iOS 6-look controls are not presented by the app per se. UIAlertView is in SpringBoard.app (it blocks power button and home button) and the cut/copy

Re: iPad keyboards

2013-12-16 Thread Rick Mann
On Dec 12, 2013, at 21:11 , Maxthon Chan wrote: > If you run a stock iOS 6 app on iOS 7 you get most of the UI in iOS 6 style. > As what I said, UIAlertView is not in your app but SpringBoard.app so that > will still get the iOS 7 look, for SpringBoard.app is linked against iOS 7 > SDK. > >

Re: iPad keyboards

2013-12-16 Thread Maxthon Chan
If you run a stock iOS 6 app on iOS 7 you get most of the UI in iOS 6 style. As what I said, UIAlertView is not in your app but SpringBoard.app so that will still get the iOS 7 look, for SpringBoard.app is linked against iOS 7 SDK. If you are styling iOS 6 app in the fashion of iOS 7 app you can

Re: iPad keyboards

2013-12-12 Thread Shawn Erickson
Your app is tagged with the SDK you link against. When running on a later version of the OS then the SDK the app is built with the OS may (and often does) run the application in a compatibility mode in an attempt to avoid causing problems for the app. On Thu, Dec 12, 2013 at 1:08 PM, Rick Mann w

Re: iPad keyboards

2013-12-12 Thread David Duncan
On Dec 12, 2013, at 1:08 PM, Rick Mann wrote: > > On Dec 12, 2013, at 11:58 , Shawn Erickson wrote: > >> We have been submitting and getting approved apps built with Xcode 4.x and >> iOS 6 SDK without issue still. Apple knows the iOS 7 jump is fairly large >> for some apps so hasn't yet been

Re: iPad keyboards

2013-12-12 Thread Rick Mann
On Dec 12, 2013, at 11:58 , Shawn Erickson wrote: > We have been submitting and getting approved apps built with Xcode 4.x and > iOS 6 SDK without issue still. Apple knows the iOS 7 jump is fairly large > for some apps so hasn't yet been forceful but I expect to happen at some > point. That's g

Re: iPad keyboards

2013-12-12 Thread Shawn Erickson
We have been submitting and getting approved apps built with Xcode 4.x and iOS 6 SDK without issue still. Apple knows the iOS 7 jump is fairly large for some apps so hasn't yet been forceful but I expect to happen at some point. On Thu, Dec 12, 2013 at 1:38 AM, Rick Mann wrote: > I thought you

Re: iPad keyboards

2013-12-12 Thread Mike Abdullah
On 12 Dec 2013, at 15:39, Luther Baker wrote: > > > On Dec 12, 2013, at 3:38 AM, Rick Mann wrote: > >> I thought you had to use Xcode 5 to submit now, > > Xcode 5 can build with the 6 SDK. Not without modifying the Xcode package, or other monkeying about with settings. Perhaps you’re thin

Re: iPad keyboards

2013-12-12 Thread Luther Baker
On Dec 12, 2013, at 3:38 AM, Rick Mann wrote: > I thought you had to use Xcode 5 to submit now, Xcode 5 can build with the 6 SDK. > and I thought it had to be linked against iOS 7. Dunno > I'm pretty sure Apple rejected one of my binaries because of that. > Might try to clarify for which

Re: iPad keyboards

2013-12-12 Thread Maxthon Chan
Seem to me that Xcode 4.6.3 and iOS 6 SDK is still working, from my friends. On Dec 12, 2013, at 15:25, Maxthon Chan wrote: > Well on OS X Mavericks I have > /System/Library/Frameworks/Foundation.framework/Version/C/Foundation - and I > can assume tat versions A are from NeXTSTEP (possibly use

Re: iPad keyboards

2013-12-12 Thread Rick Mann
I thought you had to use Xcode 5 to submit now, and I thought it had to be linked against iOS 7. I'm pretty sure Apple rejected one of my binaries because of that. On Dec 12, 2013, at 01:34 , Kyle Sluder wrote: >> On Dec 11, 2013, at 9:49 PM, Rick Mann wrote: > >> >> They released the lates

Re: iPad keyboards

2013-12-12 Thread Kyle Sluder
> On Dec 11, 2013, at 9:49 PM, Rick Mann wrote: > > They released the latest version of their app Nov 19. They would've had to > build against the iOS 7 SDK. As far as I know, Apple is still accepting binaries linked against the iOS 6 SDK. --Kyle Sluder _

Re: iPad keyboards

2013-12-11 Thread Maxthon Chan
Well on OS X Mavericks I have /System/Library/Frameworks/Foundation.framework/Version/C/Foundation - and I can assume tat versions A are from NeXTSTEP (possibly used in early PPC OS X too) Also, I distribute my CGIKit framework in two versions, version F and G - versions F and G have different

Re: iPad keyboards

2013-12-11 Thread Greg Parker
On Dec 11, 2013, at 10:46 PM, Maxthon Chan wrote: > Bad example - you should use the example between NeXTSTEP/Mach and OS X, > which the identical technology, library versioning, is used. (People do you > still remember that OS X derived from NeXTSTEP, to the extent that OS X 10.0 > have versio

Re: iPad keyboards

2013-12-11 Thread Maxthon Chan
There are situations that new frameworks failed to support old code and debugging may be impossible, especially games. Apple will not prevent them from being released. (Some apps are known to be linked against ancient SDKs like iOS 4 SDK when released) On Dec 12, 2013, at 14:46, Rick Mann wrot

Re: iPad keyboards

2013-12-11 Thread Maxthon Chan
Bad example - you should use the example between NeXTSTEP/Mach and OS X, which the identical technology, library versioning, is used. (People do you still remember that OS X derived from NeXTSTEP, to the extent that OS X 10.0 have version number 4.0, picking up where NeXTSTEP left off, and this

Re: iPad keyboards

2013-12-11 Thread Rick Mann
Right, so how were they able to release an app 11/19 without using the iOS 7 sdk? I doubt they submitted it long before that. Sent from my iPhone On Dec 11, 2013, at 22:04, Luther Baker wrote: > Technically, an iPad running iOS7 can run apps in iOS6 compatibility mode. > > The keyboard is a

Re: iPad keyboards

2013-12-11 Thread Luther Baker
Technically, an iPad running iOS7 can run apps in iOS6 compatibility mode. The keyboard is a dead giveaway. It is similar to an original OSX upgrade from OS9, where some OS9 apps could run within OSX under an OS9 compatibility mode. Or think of it like running a windows app in Parallels on a Mac.

Re: iPad keyboards

2013-12-11 Thread Rick Mann
They released the latest version of their app Nov 19. They would've had to build against the iOS 7 SDK. So, how do they get that look? On Dec 11, 2013, at 21:47 , Maxthon Chan wrote: > The other way around - they styled their UI in iOS 7 fashion but used iOS 6 > SDK. It is actually quite simpl

Re: iPad keyboards

2013-12-11 Thread Maxthon Chan
The other way around - they styled their UI in iOS 7 fashion but used iOS 6 SDK. It is actually quite simple if you ignore the blur effect. And I used to do that as well - when I worked for a game company and designed a UIKit-only game imitating iOS 7 looks on iOS 6 SDK. On Dec 12, 2013, at 13:

Re: iPad keyboards

2013-12-11 Thread Rick Mann
I'm running iOS 7. You're saying they styled their own keyboard to look like the iOS 6 keyboard? It's a pretty good imitation. On Dec 11, 2013, at 21:29 , Maxthon Chan wrote: > They simulated iOS 7 looks using iOS 6 SDK. It is not that difficult by using > appearance proxy. > > On Dec 12, 201

Re: iPad keyboards

2013-12-11 Thread Maxthon Chan
They simulated iOS 7 looks using iOS 6 SDK. It is not that difficult by using appearance proxy. On Dec 12, 2013, at 13:26, Rick Mann wrote: > Why does the Google Hangouts app on iPad, on iOS 7, have a nice-looking iOS-6 > style keyboard? Other UI in the app looks like iOS 7 UI. > > Hangouts:

iPad keyboards

2013-12-11 Thread Rick Mann
Why does the Google Hangouts app on iPad, on iOS 7, have a nice-looking iOS-6 style keyboard? Other UI in the app looks like iOS 7 UI. Hangouts: http://cl.ly/image/1U2T1e1y1G15 Safari: http://cl.ly/image/2C1B2r2n2J3J -- Rick signature.asc Description: Message signed with OpenPGP using GP