Hi all,
I updated my code, taking into account all comments I did get so far, except
the comments about the (code) comment
My code comment will be extended in a later stage.
You can find the work so far at:
https://github.com/de-wolff/lilypond/tree/musicxml
It is already generating useable mus
> -Oorspronkelijk bericht-
> Van: Thomas Morley
> Verzonden: Sunday, November 17, 2019 7:38 PM
> Aan: lilyp...@de-wolff.org
> CC: David Kastrup ; Urs Liska ;
> lilypond-devel
> Onderwerp: Re: Working on issue 665, how to proceed?
>
> Am So., 17. Nov
Thomas Morley writes:
> Am So., 17. Nov. 2019 um 18:13 Uhr schrieb :
>>
>> > -Oorspronkelijk bericht-
>> > Van: David Kastrup
>> > > I did use a lot of define-method, as it is easy this way to be type
>> > > save.
>> >
>> > I don't think the cost justifies the effort here. Scheme is not
Am So., 17. Nov. 2019 um 18:13 Uhr schrieb :
>
> > -Oorspronkelijk bericht-
> > Van: David Kastrup
> > > I did use a lot of define-method, as it is easy this way to be type
> > > save.
> >
> > I don't think the cost justifies the effort here. Scheme is not intended
> > as a
> > "type saf
> -Oorspronkelijk bericht-
> Van: David Kastrup
> Verzonden: Sunday, November 17, 2019 5:20 PM
> Aan: lilyp...@de-wolff.org
> CC: 'Thomas Morley' ; 'Urs Liska'
> ; 'lilypond-devel'
> Onderwerp: Re: Working on issue 665, how to proceed
writes:
>> -Oorspronkelijk bericht-
>> Van: Thomas Morley
>>
>> You use (oop goops).
>> Is there need for it? This is a question not a hidden request!
>> Speaking only for myself, I'm not familar with it. So reviewing your code
>> will be
>> difficult for me.
>> We don't use it much so
> -Oorspronkelijk bericht-
> Van: Thomas Morley
> Verzonden: Sunday, November 17, 2019 3:44 PM
> Aan: lilyp...@de-wolff.org
> CC: Jacques Menu ; Urs Liska
> ; lilypond-devel
> Onderwerp: Re: Working on issue 665, how to proceed?
>
> Am So., 17. Nov
Am So., 17. Nov. 2019 um 15:44 Uhr schrieb Thomas Morley
:
> And there is musicxml.ly and xml-library.scm as well.
Please always obtain a 80-characters-line-width.
In musicxml.ly you give an optional string?-argument and convert to
symbol later, why not directly?
I'd use `format´ instead of strin
Am So., 17. Nov. 2019 um 14:08 Uhr schrieb :
>
> I followed your suggestion and added a the filename to the output, also now
> it is possible to use no header.
Thanks.
> Further the resulting filename is defined in the musicxml.ly, and is
> .xml if the function is called with a music expression
Liska ;
lilypond-devel
Onderwerp: Re: Working on issue 665, how to proceed?
Am So., 17. Nov. 2019 um 11:49 Uhr schrieb mailto:lilyp...@de-wolff.org> >:
When I use your example on 2.19, I get the same error
When I add
\header {}
to it, it creates a file named test.xml
I trie
Am So., 17. Nov. 2019 um 11:49 Uhr schrieb :
>
> When I use your example on 2.19, I get the same error
>
> When I add
> \header {}
> to it, it creates a file named test.xml
>
I tried this. At first attempt I've got:
While evaluating arguments to music->musicxml in expression
(music->musicxml scor
Hello Jaap & Harm & Urs,
> Le 17 nov. 2019 à 10:29, Thomas Morley a écrit :
>
> Hi Jaap,
>
>
> Am Sa., 16. Nov. 2019 um 01:23 Uhr schrieb :
>>
>> In the last weeks I did write a start of a lilypond -> musicxml solution.
>
> Many thanks working on it.
>
> I think Jacques Menu does a lot with
> -Original Message-
> From: Thomas Morley
> Sent: Sunday, November 17, 2019 10:29 AM
> To: lilyp...@de-wolff.org; Jacques Menu ; Urs Liska
>
> Cc: lilypond-devel
> Subject: Re: Working on issue 665, how to proceed?
>
> Hi Jaap,
>
>
> Am Sa.
Hi Jaap,
Am Sa., 16. Nov. 2019 um 01:23 Uhr schrieb :
>
> In the last weeks I did write a start of a lilypond -> musicxml solution.
Many thanks working on it.
I think Jacques Menu does a lot with musicxml.
Also, I seem to remember there was some experimental work in Frescobaldi.
I may be wrong
working on this - hope it all goes well!
Trevor
-- Original Message --
From: lilyp...@de-wolff.org
To: "'Trevor'"
Sent: 16/11/2019 16:53:36
Subject: RE: Working on issue 665, how to proceed?
I already have an sourceforge account: my username is de-wolff
Jaap
My sourceforge account name is: de-wolff
> -Original Message-
> From: Trevor
> Sent: Saturday, November 16, 2019 3:44 PM
> To: lilyp...@de-wolff.org; lilypond-devel@gnu.org
> Subject: Re: Working on issue 665, how to proceed?
>
> lilyp...@de-wolff.org wrote 15/11/20
lilyp...@de-wolff.org wrote 15/11/2019 23:31:33
Subject: Working on issue 665, how to proceed?
Hi Jaap
You wrote
In the last weeks I did write a start of a lilypond -> musicxml solution.
As this is an (old) issue, there is need to put this in lilypond, but how?
What level of quality
In the last weeks I did write a start of a lilypond -> musicxml solution.
What I have written so far is creating musicxml files which contains all
partials time signatures, keys, notes, slurs, ties, staffs and staff
grouping, as well as support for most accidentals, barlines, lyrics, beams,
tup
Am 16.10.2012 02:44, schrieb David Kastrup:
> Most of the things that would count as simplifications are so because
> they drop details used for distinguishing things told to the computer.
> Where those distinctions are distinctions between non-sensical
> directions and potentially useful directio
On Tue, Oct 16, 2012 at 2:44 AM, David Kastrup wrote:
> [...]
> A coherent set of choices governed by a particular patterning may be
> called "design". Letting choices be made individually by a democratic
> process will favor varying concepts of simplicity on a detail level
> while breaking the a
Joram Berger writes:
> sorry for joining the discussion too late (I joined the mailinglist just
> now).
There is all the time of the world for this discussion now.
> In short: I would be very fond of a syntax like (no # or')
> \set context.property = 0.3
> \unset context.property
> and a unific
eems that we have to agree to disagree, not finding a solution
>> right now. The question is how to proceed.
>>
>> My suggestion is to stop the discussion now and to let David work as
>> he thinks is best, bringing lilypond into a shape which makes it
>> easier to modify la
PS
David, i apologize for discussing this topic too stubbornly.
PS2
I have also noticed that sometimes i miss parts of the discussion, for
example i forgot to read comments in the tracker issue. I apologize
for that, and i want to assure everyone that i don't mean to ignore
anyone deliberatly.
a
; him to see that everybody picks his code and suggestion into pieces
> without being able to actually contribute code. In other words, we
> have one musician and a lot of conductors.
>
> It seems that we have to agree to disagree, not finding a solution
> right now. The qu
being able to actually contribute code. In other words, we
have one musician and a lot of conductors.
It seems that we have to agree to disagree, not finding a solution
right now. The question is how to proceed.
My suggestion is to stop the discussion now and to let David work as
he thinks is
25 matches
Mail list logo
