On Monday 04 June 2007, Chris Cannam wrote: > Are they? I haven't noticed that myself, but if you two have, such a > change would be fine with me.
I vote for using PDF. It seems to be a lot more stable. Especially just now. I don't think PDF will have a negative impact on anyone. > If Xdialog isn't available, it doesn't complain, it just doesn't show > progress. That is intentional (if not necessarily wise). Right, I remember now. The progress dialog is kind of useless anyway, really. There are many cases that produce usable output with hundreds of warnings, and I had to put in some ugly hack to make it continue in spite of thinking all was lost. It almost always does produce something, in spite of these errors. > I think we've mentioned this before, but I do think that now would be a > good time to switch to using Lilypond for the "native" printing > implementation. That is, make both "Print..." and "Print Preview..." go > through Lilypond, and then perhaps add a draft-print function (or option on > the print dialog) to allow you to use native printing if you really want > to. Or, alternatively, remove the native printing code completely. I'd be inclined to remove the native printing code and force a dependency on LilyPond for printing. The results are so much better, and "draft" implies something quick and dirty, which is most definitely not the case with my printer. Native printing is so abysmally slow it's not even funny. However, if there is no longer any way to print Rosegarden's own on-screen interpretation of the state of things, it immediately renders the micro-positioning feature completely useless. (From my perspective, it already *is* largely useless, since I only print via LilyPond, and it's not exportable. I mostly use it to reposition LilyPond export tags so they are out of my way.) There may be other casualties. There is a problem with stem directions for sure. Our stem directions are only exported explicitly if they are not computed automatically, but we make different choices from LilyPond in certain edge cases, and this impacts slur direction in particular. Say I have flipped a slur, which *is* exported, but that flip presupposes an alternate stem direction from what LilyPond chooses; the result is a slur that's obviously flipped the wrong way on the printed page. Anyway, I'm generally in favor of making the move, with some concerns. -- D. Michael McIntyre ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Rosegarden-devel mailing list [email protected] - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
