Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Apple Seeds iOS 7.1 Beta 2 to Developers [Updated]
- Thread starter MacRumors
- Start date
- Sort by reaction score
It's because that site is crap. It tries and load a crap ton of videos on page load.
Yeah, the screenshot is fairly terrible.
But if there's anybody who doesn't understand the user interface elements, it's Apple.
http://uxcritique.tumblr.com
and
http://sloppyui.tumblr.com
Do you really want to tell me that people get confused because of the lack of buttons? Sure there are things that can be done better, but ios 7 lays the foundation for a new, refreshing design. I don't necessarily agree with all points made in that website. People nowadays know where to find the interface elements. They know where a button is and where not. I find the new design much better, but of course there is always room for improvement.
neat "Car display" settings... 
Now, i need a supported vehicle i can afford.
Just as long as Apple fixes their own Camera app, i don't care what else is busted...
I can make the camera app crash in view coming from the multi-task switch where the its using the rear camera. (the whole app freezes, and happens all the time), until you switch off/switch on iPhone again...
Really annoying. I dunno which is worse, this or the constant "beach balls' in Macericks.
Now, i need a supported vehicle i can afford.
Just as long as Apple fixes their own Camera app, i don't care what else is busted...
I can make the camera app crash in view coming from the multi-task switch where the its using the rear camera. (the whole app freezes, and happens all the time), until you switch off/switch on iPhone again...
Really annoying. I dunno which is worse, this or the constant "beach balls' in Macericks.
I've specifically mentioned UIWebView used by both Safari and 3rd party apps. The reason for this is simple: before loading an arbitrary Web page, you in no way can have the slightest idea how much RAM it'll be allocated: 5 Mbytes or 200 Mbytes. In other types of memory allocations where you do know how much memory you'll allocate for yourself, there's no such problems as you can query the system before the allocation whether you have the necessary RAM.
For example, an excerpt for a large-scale (in cases, several hundreds of Mbytes) memory allocation - in this case, from my OS X code creating the necessary backend tables for my path finding algorithm:
BOOL **alreadyCheckedEdgePairsCArr = malloc(arrSize *sizeof(BOOL *));
for (int i=0; i<arrSize; ++i) {
alreadyCheckedEdgePairsCArr = malloc(arrSize*sizeof(BOOL));
for (int j=0; j<arrSize; ++j) {
alreadyCheckedEdgePairsCArr[j] = NO;
}
}
Before this, it's very easy to test whether you do have the memory because you do know how much you'll allocate. Not so with UIWebView.
This makes it almost impossible to write a UIWebView-based Web browser in iOS that can both make every single byte used and be absolutely crash-free. You either are cautious and, if you see you have less than 100Mbyte RAM free, you either start killing background tabs (as is generally done by Safari - hence the need to reload them all) or frequently crash. There simply isn't another way - you cannot rely on the standard applicationDidReceiveMemoryWarning being called back as it, generally, won't be called back and if it did, you still couldn't cancel page loading.
You may be able to do that with a linear bitmap and use eight times less memory just for the BOOLs, and also skip 8 bytes * arraySize used up for pointers.
I still have the black keyboard when I open the "Search iPhone" feature. 4S here.
Anyone else have this issue?
I think they just removed the option for the black keyboard from the accessibility preferences. Apart from that the keyboard still exists.
Button Shapes - yet another accessibility option that should be default!
Hopefully the will brush up how they look...
On beta 2, Safari is now much better. I can't speak for crashes yet, but it will not reload tabs until you have 6 or more going, and even then it doesn't reload every one of them. Before it was more like 3 tabs and it would reload. A definite improvement. Also, switching between tabs is much, dare I say it?, snappier.
----------
I completely agree. It's a jarring bouncing effect that is really annoying. My guess is, that will not last long, I hope.
That wouldn't matter, would it? Anyway, my friend doesn't have iOS at all. Yet.
I forgot to add mine to my dev account and got the activation error. I then went and added it and turned my iPad off and on, and went through. I would try deleting the UDID and adding it back. If that doesn't work, time to call Apple.
They won't. Jony treats it as a personal insult that there are millions of people complaining about his new text-based "buttons".
So many people complained about the new text-based buttons that Jony decided, "They want buttons? I'll give them buttons so awful that they'll hate them and will go back to using my non-button buttons."
- Buttons that are flat and borderless (a gray blob that makes poor contrast text scenarios no better - e.g., yellow on white is now yellow on light gray).
- Underlined text in some cases (why?).
- Not enough space between the button edges and the text in some cases.
- It gets treated as an assist for handicapped people (to turn it on, you have to go through the "Accessibility" settings).
Then there's the dark keyboard option. Again, treated as a handicapped issue. And I don't want just a dark keyboard. I want an option to replace all of the overuse of white backgrounds with a black or dark gray background.
Last edited:
Why would that be a bug?
Because it didn't happen to me in any of the iOS 7 betas, current release versions and beta 1. I remember a cool keyboard animation in the iOS 7 betas that was labeled a bug and changed in later betas.
Not sure if this has been mentioned yet, but Notification Center now shows your next event rather than showing what's happening for the next six hours.
Just a warning to non-devs who might install this:
Apple is enforcing registration of the device with beta 2!! I updated and suddenly was told I had to register the iPad in the developer portal to activate.
I did (we have an account through work) and was able to activate, but to those who are not developers you might be SOL updating to beta 2!
So don't update to Beta 2 if you don't have your device registered with a dev account. I for one think it's pretty damn sneaky for Apple to let people install Beta 1 but then enforce this on Beta 2.
Nothing happen to me. And updated fine