In fact, it seems that what LilyPond can embed in its markup is eps, rather than .png images. So we should pick up the .eps output when we create a thumbnail for use on a title page/thematic index or whatever. I am not quite sure how to handle this - perhaps actually read it in and store it with the .denemo file (if it is wanted, of course). No real reason to link this very tightly in with thumbnails, although the application I have in mind it would be precisely the thumbnail that I would want to place on the cover of the printed work.
Richard On Sat, 2011-05-21 at 20:30 +0100, Richard Shann wrote: > It looks like it won't be too arduous to create thumbnails according to > the gnome (and kde?) standard. Glib has a function > g_compute_checksum_for_string () > which you use on the URI of the .denemo file. (e.g. > "file:///home/jbloggs/mydenemofiles/mygreatwork.denemo") and with this > as the file name you store a .png in ~/.thumbnails/normal of size > 128x128 pixels. > We would want the .png to be basically something created by denemo's > print excerpt on the first three measures or so - a script could make an > intelligent choice of how much to include so that the thumbnail was > enough to identify the piece (we may need the larger sized thumbnails > that the standard allows). (The \incipit in LilyPond is not this BTW). > > This would have a nice consequence that folk using gnome (and kde?) > would see these thumbnails in their file browsers when looking at > their .denemo files. > > There is then the job of displaying them in the denemo file selectors as > you move down a list of .denemo files. Volunteers, as usual, always > welcome:) > > Richard > > > > _______________________________________________ > Denemo-devel mailing list > [email protected] > https://lists.gnu.org/mailman/listinfo/denemo-devel _______________________________________________ Denemo-devel mailing list [email protected] https://lists.gnu.org/mailman/listinfo/denemo-devel
