Aaargh! I promised myself I wouldn't continue with this pointless discussion, but I can't resist having one more go.
Quote:
Originally Posted by PatNY
I am not asking you to show which apps used S&S.
|
What were you asking for here, then:
Quote:
|
Just name a widely used consumer app that was scalable prior to iOS6
|
Moving on from that, however ...
Quote:
|
I am asking you to prove that there were easy and practical methods to scale iOS apps before iOS6. It should be an easy thing to do -- if in fact that were the case.
|
If you want evidence that it exists and is easy to use, just look at the developer docs for how it's used, and judge its ease of use for yourself. Or, if you have access to a Mac, or know someone who does, download Xcode and try it out (it's free, and you can knock up a simple S&S UI that scales in a few minutes). I completely agree its usefulness is limited to certain types of UI, but it would be a mistake to underestimate the importance of those types.
If you want evidence that developers were using it, just google for "Xcode springs and struts". You'll find thousands of discussions amongst developers using it.
Having said that, I don't know why I'm bothering to try convince you of this point - it's irrelevant to my argument. I only stepped into this discussion to correct the misinformation that Apple are currently held back by an inability for iOS to scale interfaces. What it did in an OS two generations out of date is not relevant to that point. Feel free to continue to believe whatever you want about springs and struts - I'm not really bothered.
Quote:
|
Again, we are not talking esoteric private apps shared among a few people.
|
By "private" do you mean not available to the public via the app store? It would be a mistake to assume that all such apps are only available to a few people. They can have wide distribution, and are an area that is important to Apple.
Quote:
|
This is not too different from my original claim -- the only difference being the time frame in question.
|
The time frame is, however, a crucial difference. In a thread about the
current state of affairs for Apple, it seems perfectly reasonable for me to have pointed out that a limitation you claimed currently applied to iOS hasn't applied for at least the last two generations.
Apologies to anyone still listening for dragging this out further, and for allowing myself to be dragged down irrelevant side alleys. I really will try and resist the temptation to carry on, unless something new is added to the argument.
/JB