LesterCricket
About
- Username
- LesterCricket
- Joined
- Visits
- 0
- Last Active
- Roles
- member
- Points
- 7
- Badges
- 0
- Posts
- 7
Reactions
-
Apple's cross-platform app solution likely to debut in 2019, report says
Soli? Do you listen to me? An app that doesn’t support @3x gets rejected. Admittley I have seen some rogue apps slip through. You can also tell when a UIAlertView pops up. i.e. “This app want to access your photos because...” Like I said yesterday we are on a different page clearly. My point was that @2x apps are NOT upscaled to suit a @3x resolution display. All artwork provided to the app is created at the theoretical resolution of 1242 x 2208 and then it is rendered down to 1080 x 1920. All UI elements created by code use points not pixels and are multiplied by the scale of the screen at @3x in perfect, shape and crisp form - and then in turn downscaled to meet the real pixel count. They are NOT upscaled. You might be talking about apps that haven’t been updated in a while (abandonware) or apps that slipped through on a Monday morning/Friday afternoon/4th July? Who knows? Please stop insulting my intelligence. I have expressed that we might be talking about different things? But you continue to rant about the same point that we may not be talking about. Can you show a little flexibility and realise we might both be right/wrong depending on the motivation of our comments? The reason I pulled you in the first place was because you went off-topic (like usual) and in this case something that I have a passion for and care about, whilst you mooch about looking at your stock options?Soli said:
A developer in 2018 that still doesn't optimize for the 5.5" iPhone. The horrible aesthetics and extra thick status bar don't bother you, your employer/clients? That's, um, amazing. I mean, I know you exist—hence my original post—I just didn't think anyone was proud of it.LesterCricket said:
Are you stupid Soli? A developer writes code for iOS (when referring to user space, rather than unit space) we refer to the devices screen size as if all devices were running a non-retina @1x screen. Geometry concerns itself with the real scale of the device, it doesn’t mean that the GPU renders offscreen context at that smaller size and then “upscales it”. Just stop it because you are wrong. If I don’t get any of this stuff my apps would be rejected - as yes as you hoped (for what ever reason) I have infact read the HIG. Why do you think you know my job better than me? How arrogant.Soli said:
The link you supplied even proves you wrong. How can you be developer and not know this?LesterCricket said:
All I can do to contribute to your comment, is say that it’s wrong. I’m really, really sorry but you investor guys are sooooo wrong. You don’t get “this stuff” and to be fair - you shouldn’t have to.mike eggleston said:
Whoa whoa whoa... Lets bring sanity back to this conversation. And I will quote directly from the horse's mouth: Apple.LesterCricket said:
Like I said, I think we are running a different conversation here. I am going to just leave this at this: It’s labour day here in Spain and I am going to take a beer or two, but quickly - I don’t fully understand what you are getting at. Maybe you mean when a partially blind, plus user selects the assessability “zoom” option that renders the “4.7”” version of an app to a 5.5” screen? In that case what do you expect? On the other hand (and something you misunderstand about the 4.7” screen) there isn’t a single app on the App Store designed (pixel wise) for the 4.7” screen. The truth is that all 4.7” devices run an upscaled 4” app. The only devices that run upscaled artwork/res are the 4.7” devices. Stop trying to be so clever. You never know when it will make you look stupid.
@2x is for Retina Display (iPhone 4 - iPhone 8; not Plus variant, and iPads with Retina Display)
@3x is for Retina HD Display (iPhone 6 Plus, iPhone 7 Plus, iPhone 8 Plus, and iPhone X)
Apple automatically upscales for devices of varying screen resolutions, depending on which model it is.
Links:
https://developer.apple.com/library/content/qa/qa1686/_index.html
https://developer.apple.com/ios/human-interface-guidelines/icons-and-images/image-size-and-resolution/
So, are we done here with the whole resolution debate? Because that has NOTHING to do with Marzipan (or whatever code name it is now). The idea of unifying the codebases such that you can use the same APIs regardless of whether your are developing for iOS or macOS has already been out in the wild, and no one even paid the slightest bit of attention.
For example: They have been converting their main classes from NS* variants to just the name (NSString to String, NSNumber to Number, etc). They would have had to known that the only difference there needs to be between the iOS Screen elements (UIButton for example) and a macOS one (NSButton in the same example) is styling. But the main functionality of it (did it get pressed, what is its target, the title of the button) can be very much universal.
The obvious boons for developers out there is now we can potentially write even more reusable code, across the entire Apple ecosystem. The other main benefit is the reduction of potential bugs in their code-base. In all, this will be a huge benefit to the customer!
But you are wrong. Please just let an arm64/Intel fantasy article be just that. End-of. Rather you want to taint it with your uniformed position just like Soli (you are backing-him-up) and neither of you know what you are talking about. If you want to get defensive, why don’t we just put a pin in it and “iCal” this conversation?
-
Apple's cross-platform app solution likely to debut in 2019, report says
Are you stupid Soli? A developer writes code for iOS (when referring to user space, rather than unit space) we refer to the devices screen size as if all devices were running a non-retina @1x screen. Geometry concerns itself with the real scale of the device, it doesn’t mean that the GPU renders offscreen context at that smaller size and then “upscales it”. Just stop it because you are wrong. If I don’t get any of this stuff my apps would be rejected - as yes as you hoped (for what ever reason) I have infact read the HIG. Why do you think you know my job better than me? How arrogant.Soli said:
The link you supplied even proves you wrong. How can you be developer and not know this?LesterCricket said:
All I can do to contribute to your comment, is say that it’s wrong. I’m really, really sorry but you investor guys are sooooo wrong. You don’t get “this stuff” and to be fair - you shouldn’t have to.mike eggleston said:
Whoa whoa whoa... Lets bring sanity back to this conversation. And I will quote directly from the horse's mouth: Apple.LesterCricket said:
Like I said, I think we are running a different conversation here. I am going to just leave this at this: It’s labour day here in Spain and I am going to take a beer or two, but quickly - I don’t fully understand what you are getting at. Maybe you mean when a partially blind, plus user selects the assessability “zoom” option that renders the “4.7”” version of an app to a 5.5” screen? In that case what do you expect? On the other hand (and something you misunderstand about the 4.7” screen) there isn’t a single app on the App Store designed (pixel wise) for the 4.7” screen. The truth is that all 4.7” devices run an upscaled 4” app. The only devices that run upscaled artwork/res are the 4.7” devices. Stop trying to be so clever. You never know when it will make you look stupid.
@2x is for Retina Display (iPhone 4 - iPhone 8; not Plus variant, and iPads with Retina Display)
@3x is for Retina HD Display (iPhone 6 Plus, iPhone 7 Plus, iPhone 8 Plus, and iPhone X)
Apple automatically upscales for devices of varying screen resolutions, depending on which model it is.
Links:
https://developer.apple.com/library/content/qa/qa1686/_index.html
https://developer.apple.com/ios/human-interface-guidelines/icons-and-images/image-size-and-resolution/
So, are we done here with the whole resolution debate? Because that has NOTHING to do with Marzipan (or whatever code name it is now). The idea of unifying the codebases such that you can use the same APIs regardless of whether your are developing for iOS or macOS has already been out in the wild, and no one even paid the slightest bit of attention.
For example: They have been converting their main classes from NS* variants to just the name (NSString to String, NSNumber to Number, etc). They would have had to known that the only difference there needs to be between the iOS Screen elements (UIButton for example) and a macOS one (NSButton in the same example) is styling. But the main functionality of it (did it get pressed, what is its target, the title of the button) can be very much universal.
The obvious boons for developers out there is now we can potentially write even more reusable code, across the entire Apple ecosystem. The other main benefit is the reduction of potential bugs in their code-base. In all, this will be a huge benefit to the customer!
But you are wrong. Please just let an arm64/Intel fantasy article be just that. End-of. Rather you want to taint it with your uniformed position just like Soli (you are backing-him-up) and neither of you know what you are talking about. If you want to get defensive, why don’t we just put a pin in it and “iCal” this conversation?
