Re: Do we really offer the future?

[Kieren MacMillan]

Hi Urs,

> I think you could vastly benefit from using openLilyLib's GridLY library.

No doubt true. (I look forward to examining GridLY, when I have a spare moment.)

> Of course thst's only viable for new projects.

We should strive to create tools for which this isn’t [ever] true.  =)

Someone spoke of python being able to translate between parallel and 
non-parallel music. Wouldn’t it be great to have a tool where you could:
    1. Say “Given the current Lilypond file being outputted, show me ‘in 
parallel’ [whatever that means] all the code that’s involved.”
    2. Edit the music "in parallel” [whatever that means].
    3. Say [if necessary] “Return this parallel-edited code back to its 
distributed source location."
Then we’d really be talking.

Perhaps that’s exactly what GridLY does with new [read: properly structured] 
projects…?
But this kind of thing will only be truly game-changing if it works on existing 
projects, with essentially no setup or programmer overhead, and without forcing 
structural requirements onto the user/programmer.

Cheers,
Kieren.
________________________________

Kieren MacMillan, composer
‣ website: www.kierenmacmillan.info
‣ email: address@hidden