On Thu, 2009-02-05 at 20:16 +0100, Vladimir Nadvornik wrote: > It is difficult to pick one method when the requirements are different for > writting to image files or for writting to Geeqie's private data. > > Current configuration allows both these methods and also something inbetween. > But maybe some options could be merged to simplify it.
If it's "things that the user types in which are associated with an image", it should be one way (instant save) or the other (save on request); it doesn't really matter where in the filesystem the data lives. The only question I see here is, "does the user need an opportunity to undo the changes they've just made"? If not, or if there is an "Undo" menu option or button, I would make it "instant save" (under the hood being "almost instant" for performance optimization). If you're talking about metadata changes that result from an "Edit" action or just the caching of internal calculations, it seems clear to me those can go to disk at the earliest opportunity. -B. ------------------------------------------------------------------------------ Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM) software. With Adobe AIR, Ajax developers can use existing skills and code to build responsive, highly engaging applications that combine the power of local resources and data with the reach of the web. Download the Adobe AIR SDK and Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com _______________________________________________ Geeqie-devel mailing list Geeqie-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geeqie-devel
