On Fri, Sep 05, 2008 at 11:47:45AM -0300, Erik Garrison wrote: > The current patchset guarantees that [journal previews] will exist > provided the user intentionally saves their work, or properly closes > the activity.
IMO this is the key factor in deciding how much compromise is too much: the compromise being between, on the one hand, a real-time-updated thumbnail of activity if it's currently running; on the other hand, no thumbnail it all. The factors each solution would be judged by include performance, decrease (from the ideal) in usefulness, activity code / API complexity. The two competing compromises, that lie just astride some key boundary in the solution space, seem to me to be: 1) saving (the thumbnail preview, but also I imagine the actual application state as well) just often enough that the user will never be surprised that, when resuming, the state isn't as they last left it; and 2) saving only as often as the user explicity asks to save (and at application shutdown, if possible - currently, this means the app has to be visible) Your patch does #2, I believe. > Can these be implemented and tested quickly? If not perhaps we should > implement this patch and reintroduce the current functionality when > these features are complete. FWIW, I think that the features being sacrificed are not used often enough to justify the loss in performance. > Erik Martin
pgpeGLEkAQaiz.pgp
Description: PGP signature
_______________________________________________ Sugar mailing list [email protected] http://lists.laptop.org/listinfo/sugar
