Re animation disabling - have you given TinkerTool a look? It has a fairly good set of controls for overriding at least some animations:
Doesn't do anything about automatic program quitting or launching, though. The script I wrote wiill shut down a Mac and purge the 'automatically load programs when logging in' history, and it can easily be modified to do that on reboot as well - but it assumes a normal shutdown. If you have to force a reboot, it won't work.
Yes. And some of the other tools as well.
If Apple doesn't offer switches (remember the menu flashes of 1, 2 or 3 in OS 7?), then you have to wait for someone else to figure out how to override it, or spend the time yourself.
Using a few tools and terminal settings, I've turned off most of what I can turn off. Now, I'm looking to disable the auto quit and disable the bouncy (elastic) NSScrollViews in every app.
Re: Is it possible to disable the auto quit of preview and other apps?
Maybe you should be posting in the developers forum then. And why would people gripe when the vast majority are having no problems with Lion
Wait, so bugs aren't really bugs unless they impact 100% of the userbase?
You're kidding, right?
Zav - if you haven't looked at ReSpaceApp, it might be worth exploring as well, for dealing with the Mission Control animations and so on:
I've set up its transitions to work with ctrl-option-arrow, since I can't seem to turn off the ctrl-arrow desktop switching that Mission Control uses, but with ReSpaceApp's setting to turn animated transitions off when it switches desktops, I've got none of the zoomy flying animations any more.
It interacts a little oddly with Mission Control, doesn't replace or override it, and installs in the /Applications folder. As a third-party utility might constitute a hack, but I've seen worse.
Whilst the discussion of historical Mac users vs windows converts/recent Mac users is interesting, the issue here is an OS the previously gave the user maximum flexibility is now implementing options that hinder user preferences and efficiency, which is bad. I am a windows convert from 4-5 years ago, and I initially found the need to quit apps strange, but quickly came to see the wisdom of that feature in OS X.
Claiming the logic that if a user closes the last window he must want to close the app is short-sighted and basically a Windo$e-type mentality. And the main reason I hate this feature, apart from the fact I am used the need to user-quit, is efficiency. Why, you ask? Because I use various apps from time to time during my computer usage, and I want the apps to respond instantly (or almost) - why else have quad-core processors, 4 GB of RAM and SS drives? When apps auto-quit (e.g. Preview), I then later double-click an image or PDF and the icon sits there bouncing 4-5 times until the file opens. That is utter BS - when apps don't quit, they respond immediately when a user needs them.
This is why the Auto-Quit feature from Apple $uck$ big-time, and why it better get removed or as a minimum have a global user-selected preferens or command-line on/off hack (like forcing the /User/Library folder to reappear - I bet the same genius that came up with that "feature" also siggested auto-quitting apps!).
I don't see it as short sighted or A Windo$s type mentality. When I'm done using a program there is NO Good Reason to leave it open. And Apple agrees with me because in Lion it will eventually be closed by the OS. I see No wisdom in leaving programs open when you know you are done using them.
Well with my 1.5+ year old i5 Windows desktop with an SSD and 16GBs of RAM all programs open in about 2-7 second, Photoshop taking the longest. The reason it take a Mac longer to open programs is the way OS X is, even with fast drives (SS) it still loads programs slower then a Windows computer.
The reason for Auto quitting apps is to free up system resources so new apps that you need to run have those resources.
But I'm NOT done with the program. The OS just wants to think I am.
This is why auto quit *****. The app is still runing, yet without the GUI.
I use the GUI all the time to open apps. It's not saving much of anything, let alone memory and the app is still running, the GUI's just disabled.
You're not freeing up much if any resources. We're talking about 10 MB in the case ot TextEdit - and I have 16 GB on my machine.
If they want to free up resources, they could issue a purge terminal command on Safari, which will return up to several gigabytes of memory.
And you're also wrong. If you've read Apple's developer docs, it states why. It's to allow "faster relaunch" of the app. Well why quit it in the first place if it's to only aid in relaunching it again?