Seems confusing... You know what they say, "The more things change... The more things stay the same" Let's see how long will that last?
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.
Mac OS X Lion Notes: iOS Scroll Bars, Any Corner Resizing, Dock Changes
- Thread starter MacRumors
- Start date
- Sort by reaction score
I agree....I think this is a brilliant way to show what's on and what's off. It's sometimes important to close various programs when using a real resource hog like a 3D rendering program like Vray or Maxwell.
They already did this when the "X" button doesn't actually quit the application.
I can see your point with Network input, but still OS X is getting push notifications (see FaceTime), so I doubt that'll be relevant soon either.
Seeing as the pushes are sometimes delayed, I wonder why Apple is considering double capacity of it's data center?
I actually like the scrollbar change.
In fact I'd like the entire GUI to change, dock including.
Something minimalist like HUD would be nice, except without the current HUD requirements that the window always has to be on top.
Just my opinion though.
In fact I'd like the entire GUI to change, dock including.
Something minimalist like HUD would be nice, except without the current HUD requirements that the window always has to be on top.
Just my opinion though.
I think it's more efficient with respect to RAM/CPU cycles. To the user their is absolutely no difference.
Except MOST (not all) users are barely aware of its existence, and even less are aware of its purpose.
Who gives a crap!
And if you're rendering away, you're gonna know about it realistically. So Cmd-Tab + Cmd-Q it. You're more than likely going to have to look at the window anyway to see if what it is doing is important. The "dot" has added nothing of any use.
If you want it to quick resume, maybe the app with have a "suspend" option, now that would be cool!
we have NO idea how they are really going to implement this. This is apple we are talking about. They will come up with a creative and simple way for all of this to work. Everyone seems to be freaking out and they really don't know what this is going to be like.
Dunno how I feel about the whole "unlit items on Dock" thing. But given how OSX works I bet it won't be a big shift in knowing exactly what my computer's doing.
Now show me a touchscreen iMac and I'm set...
Now show me a touchscreen iMac and I'm set...
When I go to download and update a program it frequently says things like make sure it's not running or when I update many adobe cs programs it wants all my browsers closed, etc. My visual clue is the little light underneath. I can right-click on the icon in the dock and quickly quit. I find it fast and intuitive. Just sayin'.
After seeing the patent for a hinged iMac I'm with you and after using an iPhone the mouse interface just seems so clunky and slow.
It is relevant, for all users. You don't care if your downloads stops? You don't care if photoshop stops processing your image while you surf? When i have applications running, its for a reason.
Sorry but no. Push notification requires an external server to actually be up and responsive for my app to get notification ? I'd rather use the multi-tasking on my OS and pull information at an interval I decided was good.
Why are you people so hellbent on just accepting going backwards like this ? Install OS9 and be done with it.
Except for all the differences I've documented here and that you keep dismissing instead of responding to. Seriously, at least try to make an argument.
Obviously all the users responding to you. For the last 3 pages. Seriously if most users are barely aware of the lights, what are they harming then ? It is a step backwards for us who do use them if you remove them.
Btw, I have an idea. For every poster here claiming that he/she will not upgrade to Lion, based on the features been shown, let's make a list of them and check after Lion ships if they actually do upgrade or not
There are people still running 10.4 believe it or not. There's even people who have not even upgraded to Snow Leopard.
That won't change. Anything that needs to be running will. Anything that does will suspend and you can immediately resume when you want to use it again. I don't know where people think it's going to be slow to resume. It isn't in iOS4.
I think that most people here aren't convinced that the removal of dots from the dock means that we are moving to a cooperative multi-tasking OS as you discuss above.
And if you can't live without the the dots and the changes that come with their removal, then "install Mac OS X 10.6 and be done with it."
GL
Again, I'm not talking about that. Those are two separate issues. I don't know why you think I'm for one way or the other. I'm just trying to explain why this is possibly a good move.
'bout time.
By now we shouldn't have to wait for computers, OSs and programs to "start up" or "shut down". The machines are fast enough to get to an initial usable point within milliseconds; we don't need everything up, configured, and ready to go - we just need access to the first menu(s) & operation ASAP, and let the program leverage user interaction time with under-the-hood configuration and catchup. Only make the user wait if doing what the user wants at that moment requires it.
Word processor? just take me to a file open/create menu, or display where I left off; configure mailmerge or perform pagination if I need it or there's idle time.
Web browser? ditto; don't spend time configuring what isn't needed right now unless there's idle time.
Games? about the only one I can think of where "resume" could often be resource-intensive (loading megabytes of world data), and even there careful coding can make that efficient.
Indeed, get away from the "is/isn't running" paradigm. Just use it; system idle time & unused resources should be applied to making that transition as rapid/transparent as possible. There is value in recognizing what new users don't understand and have to learn: do they really need to learn about X? or should developers take pains to ensure users don't need to know about it?
I'm reminded of one of the new high-end electric cars (Tesla?): there is no more "insert key, start engine" - you just get in the car, and the RFID device knows you have the key so it just starts. Not a big deal, but every special action which can be shaved off the user experience is an improvement (the essence of minimalism).
By now we shouldn't have to wait for computers, OSs and programs to "start up" or "shut down". The machines are fast enough to get to an initial usable point within milliseconds; we don't need everything up, configured, and ready to go - we just need access to the first menu(s) & operation ASAP, and let the program leverage user interaction time with under-the-hood configuration and catchup. Only make the user wait if doing what the user wants at that moment requires it.
Word processor? just take me to a file open/create menu, or display where I left off; configure mailmerge or perform pagination if I need it or there's idle time.
Web browser? ditto; don't spend time configuring what isn't needed right now unless there's idle time.
Games? about the only one I can think of where "resume" could often be resource-intensive (loading megabytes of world data), and even there careful coding can make that efficient.
Indeed, get away from the "is/isn't running" paradigm. Just use it; system idle time & unused resources should be applied to making that transition as rapid/transparent as possible. There is value in recognizing what new users don't understand and have to learn: do they really need to learn about X? or should developers take pains to ensure users don't need to know about it?
I'm reminded of one of the new high-end electric cars (Tesla?): there is no more "insert key, start engine" - you just get in the car, and the RFID device knows you have the key so it just starts. Not a big deal, but every special action which can be shaved off the user experience is an improvement (the essence of minimalism).
How am I dismissing them? If there is absolutely no change to the user in regards to whether it's running or not then how does it matter? If the user is downloading something in the background then that process stays.Except for all the differences I've documented here and that you keep dismissing instead of responding to. Seriously, at least try to make an argument.
If you're talking about the blasted indicator lights, I haven't made my bloody mind up on that issue! I'll have to use it first.
But the dock only tells you that there is an app running. It might have no documents open or one or ten. It tells you nothing of any relevance because clicking on that icon invokes the app, both in you old world and in Lion's new world.
In future you will (all guessing here of course) see what documents you are currently working on (that of course includes the app required for it) and what apps you have most recently used, regardless of their state (window-less in RAM, paged out or suspended). How exactly it will work we don't know, maybe only Mission Control, maybe also CMD-TAB, maybe something else.
The iPad has shown that "always on" visible scroll bars are not necessary. The context of the page is more than enough info to know that there is more to the page above or below. Are there situations where you want to know where you're at in a document? Of course, but it's a very small use case in the grand scheme.
If you don't have an iPad, find one and mess around for a while. Scroll bars just aren't as necessary as we thought.
Similarly, it's not going to just quit itself, is it?
Apps would have to be specifically written for this, as is the case with iOS. And the developers will have control over whether or not an app is not allowed to quit (even allow the user to specify this in the prefs), should the app be aware of this.
You seem to be concentrating your efforts on a more doom and gloom scenario, rather than looking at the most likely outcome, given what is already capable on iOS.
My guess is Safari will be able to remain running until downloads finish and then have the option of suspending.
As for Photoshop, that may catch up and be suspend aware three-years down the line, so it'll just stay in RAM as per the current situation.
Broaden your view a little.
Great example. That's pretty much how I feel. I've noticed ZERO difference in how iOS4 multitasks and my battery life is amazing. It's a win, win.