From: D. M. M. <ros...@gm...> - 2009-03-05 20:42:23
|
On Thursday 05 March 2009, Heikki Johannes Junes wrote: > 1) merge tracks which have the same name -- reason: correct way is to > place segments in a single track I agree this hack is no longer needed, and can be removed. There may be cases where the old hack was the only way to accomplish something, but if we run into those, we should try to accommodate those use cases within the new expanding tracks paradigm. > 2) export \midi field -- reason: RG exports also midi; this could be > exported by default, although commented out > > 3) allow point-and-click fixing -- reason: RG is not LilyPond editor; this > could be exported by default, although commented out I no longer remember why I implemented either of those options, and I have no problem removing them. I think while you're cleaning this up, there's probably room to pull everything to the front page, and get rid of the "Advanced Options" tab. While you're at it, "non-printable headers" are another example of legacy cruft. We used to have a really simple and ugly method for creating these, and you improved it a long time ago. You left the old mechanism as "non-printable headers" but I think it is useless, and we can dispose of this now. I propose you remove "non-printable headers" entirely, and replace that with some kind of text edit field where a user can write one single block of comments. We could very likely just ignore any of the old-style headers we encounter in the future, because I doubt anybody has ever used them for anything. If they do, we'll hear about it, and if the need arises, we can import legacy headers into the comment block. What do you think about that proposal? -- D. Michael McIntyre |