[Openmcl-devel] undo size

Paul Krueger plkrueger at comcast.net
Tue Jun 14 18:31:06 UTC 2011


This is a really excellent point. The same notion of saved state that exists in IOS apps will be extended to OSX apps. IIRC part of the new features that Ralph mentioned is a sort of automatic time-machine-like capability to capture and preserve persistent document versions for arbitrary amounts of time. I was just reading about some of this the other day (in completely open Apple-approved descriptions of upcoming Lion attributes that are now available on Apple's website). It was also demoed in the keynote speech given at WWDC which is also available online. Obviously I haven't completely integrated it into my thinking yet. 

As Ralph suggested, this may effectively provide the same sort of persistent undo capability that Peter described. What I'm not sure about is whether you can get this behavior on a single local machine (i.e. without iCloud) or whether you have to store your documents in iCloud to get this capability. Given that you can work off-line without a network and then sync with iCloud later, maybe it will be possible to use it on a single platform without every syncing (???). Even if iCloud is completely free as Apple says, I can imagine that it would make some people nervous to store all documents there for security reasons. And there are some limitations on aggregate space used as well. 

Anybody know more that they can discuss?

Paul

On Jun 14, 2011, at 12:46 PM, Raffael Cavallaro wrote:

> 
> On Jun 14, 2011, at 11:41 AM, Paul Krueger wrote:
> 
>> That said, the notion of having an undo state (potentially two stacks for undo and redo actions) persist across boots of the application/system isn't something that NSUndoManager supports natively.
> 
> I also think everyone interested in using CCL to do Mac OS X apps should be aware that, going forward, the combination of auto-save, document versions, and iCloud will be the Apple approved norm. IOW, users will expect to be able to get, from any device (laptop, desktop, iPhone, iPad), the current version of any document (which was autosaved and pushed to the cloud), and on Mac OS X (most relevant to CCL at the moment) all previous autosaved and manually saved versions as well.
> 
> In this context, the whole nature of undo/redo becomes less important as it is local to that invocation of the app on that device only, while autosave and document versions are global - across devices and across application launches, so autosave and document versions, not undo/redo will become the primary means of avoiding data loss, and something users will come to expect.
> 
> warmest regards,
> 
> Ralph
> 
> 
> 
> 
> Raffael Cavallaro
> raffaelcavallaro at me.com
> 
> 
> 
> 
> 
> _______________________________________________
> Openmcl-devel mailing list
> Openmcl-devel at clozure.com
> http://clozure.com/mailman/listinfo/openmcl-devel




More information about the Openmcl-devel mailing list