[ Let's concentrate on what needs to be done with Tumbler. ] ext Damien Lespiau <[email protected]> writes:
> The XFCE repository seems to always have been the "upstream" version. Yes, I agree with that. >> I can't say yet how to proceed, but would you be happy if we merge >> the XFCE and the Maemo code bases, call that 0.2, and agree on the >> canonical place to release it from? > > The current version breaks the specified use of a thumbnailing service > and thus breaks the applications that depend on it. Ok, understood. I didn't see how incompatible the two tumbler versions are. Here is a revised plan, then: - We remove tumbler 0.1.12 from MeeGo again. This might 'inconvenience' some apps that expect 0.1.12. - XFCE makes a 0.2 release, maybe identical to 0.1.6. - Nokia merges XFCE 0.2 into its Tumbler tree, makes it compatible with the thumbnailing spec, and releases 0.2-meego1. This goes into MeeGo. Making it compatible means that we lose a lot of performance, hence... - ...we try to amend the spec to get that lost performance back. Once done and all clients in MeeGo have been updated, MeeGo Handheld is tuned for higher performance. The performance motivated deviations from the spec are: - Using JPEG instead of PNG for the thumbnail image format. JPEG is usually smaller and we have better optimized code for loading and saving it. Generating both PNG and JPEG would be spec compliant but very wasteful. - Not storing meta data inside the thumbnail image itself. This is harder for JPEGs and slow in any case. This is most important for time stamps, which is done by setting the mtime of the file instead of putting a Thumb::MTime tag into the image. - The predefined thumbnail sizes are not appropriate for our devices and we need to be more flexible. (I think the 0.3 version of the spec that I just found also moves in that direction.) _______________________________________________ MeeGo-packaging mailing list [email protected] http://lists.meego.com/listinfo/meego-packaging
