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.
Will the OS X Lion autosave feature work for Microsoft Office?
- Thread starter Nosrettap
- Start date
- Sort by reaction score
MS will have to release an update if they want those products to take advantage of those features in Lion.
Major software companies are already working on it.
Most of the major software developers like Microsoft and Adobe are already working on including autosave and versions in their products.
Most of the major software developers like Microsoft and Adobe are already working on including autosave and versions in their products.
It really depends on how difficult integrating the feature will be.
Easy: will be seen in a update to Office 2011.
Difficult: wait for Office 2013-2014.
Easy: will be seen in a update to Office 2011.
Difficult: wait for Office 2013-2014.
Probably just Office 2011. They'd want to sell current versions of their software not support an older version with feature updates.
Yeah, it's gonna have to be a case by case scenario on their end. They'll probably roll out an update, or if they were smart, wait to integrate it with the next release to make some more profit and include the autosave, fullscreen, etc.
Has anyone noticed that it seems to run a little slower? Maybe my hardware is just getting older....
Has anyone noticed that it seems to run a little slower? Maybe my hardware is just getting older....
I'd imagine that they eventually would since, if I'm not mistaken, MS Office is a popular suit on OS X so it would seem likely that they'd put the effort in to use the autosave feature.
The rub that I can foresee however is that because the feature has to be implemented on the end of the app developer, I can imagine some developers opting not to include this feature either due to design philosophy, effort etc. Whilst some others will opt to include the feature, the result being an inconsistent behaviour when opening apps.
An example of what I mean would be how for example 'maximizing' apps in OS X is pretty inconsistent, some will fill the screen whilst others will follow Apple's philosophy of expanding to the point where there are no scroll bars etc, and also again, with the close button. Some applications exit when you press it, whilst others simply hide.
It's this inconsistency that I find annoying. Nothing terribly bad but annoying no less. And I can kind of see it as an inevitability when it comes to the autosave feature.
The rub that I can foresee however is that because the feature has to be implemented on the end of the app developer, I can imagine some developers opting not to include this feature either due to design philosophy, effort etc. Whilst some others will opt to include the feature, the result being an inconsistent behaviour when opening apps.
An example of what I mean would be how for example 'maximizing' apps in OS X is pretty inconsistent, some will fill the screen whilst others will follow Apple's philosophy of expanding to the point where there are no scroll bars etc, and also again, with the close button. Some applications exit when you press it, whilst others simply hide.
It's this inconsistency that I find annoying. Nothing terribly bad but annoying no less. And I can kind of see it as an inevitability when it comes to the autosave feature.