Re: Revised version of waveform renderer on Rietveld that uses glpk

[Graham Percival]

On Fri, Jul 02, 2010 at 04:54:11PM +0200, David Kastrup wrote:
> There is no documentation as far as I can see,

Our stated (albeit probably only on the mailing list) policy is
that new features don't need docs from the programmers; as long as
there's sufficient regtest(s) and the programmer talks to the doc
people, we can the docs up to other people.

Admittedly, this was back when I was doing docs full-time and we
were desperate for more programming effort, so it might be time to
review that policy.

> It seems nice to be able to add this sort of thing to Lilypond, but I
> think it rather strongly demonstrates Lilypond's lack of modularity:
> this sort of thing should sit in a separate directory and be loaded
> on-demand under user control without needing any resident code parts
> when people don't use it.

If it was all done in scheme, this would be easy.  :)

I haven't looked at the patch, but I'm guessing that the
non-modularized parts is the interaction with glpk.  Is there any
way that scheme could call a natively-install glpk library (i.e.
not the -devel version) ?  That might make this feature
modularizable, and incidently might even allow it to get into
2.14.

Alternatively, is glpk *actually* needed?  The output looks like a
waveform to me[1], and surely scheme is capable of calcuating
such things.

[1] I didn't realize how stupid that sounded until after I wrote
it.

Cheers,
- Graham