On Sat, Feb 28, 2009 at 01:16:06PM +0100, Klaus Post wrote: > On Sat, Feb 28, 2009 at 12:47 PM, Gianluca Sforna <[email protected]> wrote: > > > With enough time to code, nothing is impossible but I am not sure that > > is an optimal solution. > > In fact, what a user want is to load a file; if we can use N different > > libraries because that way we can cover more formats, that is good but > > IMHO it should be done without user intervention. > > > > I don't think I'm going to be impressed by a workflow like: > > > > 1. open file -> fail -> change library in menu -> goto 1 > > As Anders wrote, RS already HAS already implemented a plugin structure > for loader plugins, it is already implemented, and will be in the next > version of RS. > > Loaders are internally prioritized, so if plugin A cannot decode the > image, it silently moves on to the next plugin in the list. It > actually works very nicely. There is no need for user intervention, as > fallback is silent. The only issue we are working at, is to avoid the > filesystem re-loading the image data for each plugin, but other than > that it, it works very nice.
Is that worth optimizing? Wouldn't the image data be kept in the filesystem cache by the OS? Regards, -- Krzysztof Kościuszkiewicz Skype: dr.vee, Gadu: 111851, Jabber: [email protected] "Simplicity is the ultimate sophistication" -- Leonardo da Vinci _______________________________________________ Rawstudio-dev mailing list [email protected] http://rawstudio.org/cgi-bin/mailman/listinfo/rawstudio-dev
