Re: 30 day webathon for kickstarter support (issue 6068045)
I like the content of the announcement. I still don't like the idea of manually editing index.html. I was expecting/hoping for something like Documentation/web/twits.txt: - The Ensemble 101 is going on a European tour where they'll sing music typeset using LilyPond. Click a target=\_blank\ \href=\http://www.ensemble101.fr\;here/a to learn more! - The Birmingham Amateur Theatre is presenting Penzance Pirates, starring our documentation editor Trevor Daniels as the talking lion![1] - Project manager Graham Percival has successfully defended his PhD thesis. Only two days of edits left to go before he hands in the final version![2] - Valentin is trying soy milk with his cereal. Still on the fence about it.[3] - and then the javascript would parse that file. I'm not picky about the file format (it could be each line is a separate announcement; lines can be up to 256 chars long since that's probably easier to handle in javascript). [1] this is (probably) not true. [3] this is (definitely) not true. [2] joke blantly stolen from Canadian politics. Also, probably not true. - Graham On Wed, Apr 25, 2012 at 11:28:59AM +, m...@mikesolomon.org wrote: Why wouldn't this be a general solution? I think that anyone who wants to add an announcement would have to: a) Add an entry to the array. b) Build the website and make sure that their entry fits. Also, in the most recent patchset I've changed my text to get rid of the kickstarter bit. I'll change the issue names as well. http://codereview.appspot.com/6068045/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Macro for(UP_and_DOWN) and 3 similar. (issue 2491) (issue 6109046)
On 26 avr. 2012, at 07:28, Graham Percival wrote: Well, right now we have nobody running the automated tests to check that new patches are ok. So there will be no patches accepted to lilypond. I have a meeting in mid-May w/ the University of Paris VIII. They're donating a computer to LilyPond and I'll set patchy up on it. Cheers, MS ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Macro for(UP_and_DOWN) and 3 similar. (issue 2491) (issue 6109046)
Hello, On 26 April 2012 07:55, m...@apollinemike.com m...@apollinemike.com wrote: On 26 avr. 2012, at 07:28, Graham Percival wrote: Well, right now we have nobody running the automated tests to check that new patches are ok. So there will be no patches accepted to lilypond. I have a meeting in mid-May w/ the University of Paris VIII. They're donating a computer to LilyPond and I'll set patchy up on it. While you can set up and cron patchy-merge-staging, patchy-test-patches still needs 'human' interaction (reg tests). Perhaps this computer could be better spent doing other LP related things Donate cycles for devs for instance via SSH - David might be appreciative of that. I've run patchy-test just now for the three patches outstanding this morning. It's no a big deal, I've just never got round to running the patchy-test scripts (well since the scripts were very first created when I had trouble understanding them), so don't worry about patches David now, I'll pick up the slack here. Patchy-merge already runs on my box pretty seamlessly and I can run patchy-test over coffee most mornings now I know what is involved. I'll also look at updating the CG instructions because while it is relatively simple, a non-dev like me always has trouble, initially, getting all my ducks in a row with regard to setting up LP source code, getting patchy downloaded and configured and then running her. Regards James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Macro for(UP_and_DOWN) and 3 similar. (issue 2491) (issue 6109046)
On 26 avr. 2012, at 09:05, James wrote: Hello, On 26 April 2012 07:55, m...@apollinemike.com m...@apollinemike.com wrote: On 26 avr. 2012, at 07:28, Graham Percival wrote: Well, right now we have nobody running the automated tests to check that new patches are ok. So there will be no patches accepted to lilypond. I have a meeting in mid-May w/ the University of Paris VIII. They're donating a computer to LilyPond and I'll set patchy up on it. One thing I'm gonna try to do on that machine is have each index.html generated by a regtest comparison (along with the log/png/jpg/etc files) upload to a folder on mikesolomon.org. These can hang out indefinitely and an automatic e-mail can be sent to the list w/ an alert that patchset X is up for viewing on site Y. Cheers, MS ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: 30 day webathon for kickstarter support (issue 6068045)
Graham Percival wrote Thursday, April 26, 2012 7:07 AM The Birmingham Amateur Theatre is presenting Penzance Pirates, starring our documentation editor Trevor Daniels as the talking lion![1] [1] this is (probably) not true. Amazingly, there's an element of truth in it. Read Bicester for Birmingham, though. I'm nearing the end of typesetting a new vocal score for a musical pantomime based on Sullivan's music from the Savoy operas. It has 19 musical numbers, all with original words. It will be performed next November. Oh, and it has a talking dragon rather than a lion, but probably not played by me, although I have played Samuel twice in Pirates. Trevor ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: What's with the test-patches volunteers?
Graham Percival gra...@percival-music.ca writes: On Wed, Apr 25, 2012 at 03:06:00PM +0200, David Kastrup wrote: Graham Percival gra...@percival-music.ca writes: I agree. Given your limited computing power, you are the very last person who should be running Patchy. It is not just my computing resources that make me unsuitable. I was tactfully not mentioning the other part. :) you'll see that I am also damaging the project by alienating new contributors. Actually, we _should_ be alienating new contributors. At least, new programming contributors. Anything else is dishonest and unfair to them. I disagree that alienating them as a purpose would be either honest or fair. The point is more like _warning_ them. Something like: Large companies tend to be organized like termite colonies: everything revolves around the master mind who, with a body inflated a thousandfold, can no longer leave the building and is catered for by layers of personnel who deal with the outer world, bring food and only escalate problems they don't know how to deal with themselves. The outer layer tends to have no clue whatsoever, but is polite and encouraging, so that the customer (the most common problem) figures out himself what was wrong, without feeling all too bad about possibly aggravating or abusing the support person. Now we are more organized like bees. The queens are actually distinguished by being the ones able to sting more than once. And you don't need to consult multiple layers to get an escalation to qualified personnel. You'll likely get an escalation before asking for it. Well, you may have been asking for it, but not necessarily on purpose. I am not good at this, I am afraid. Somebody else better explain that. (we still need more admin people, though, in order to smooth out the process of programming such that we can eventually be fair to new programmers) What's being unfair? Everybody gets the same treatment. Except, of course, that they don't have the option to just bypass procedures and push. So in order to stop damaging the project, I will stop doing any reviews except on patches of myself: I am getting paid for work on LilyPond, and it would not be conscionable for me to forego those parts of general work required to let my own work go forward. Please keep on reviewing -- at least, review to the extent of you haven't fixed everything. or problems in x, y, and z. I'm not asking you to give any details, I'm not asking you to repeat yourself, and I'm certainly not asking you to be nice to patch submitters. But we really need to stop questionable patches getting into lilypond -- you know this even better than I. I am afraid that you overestimate what I have been doing. I've been running test-patches and looking at pretty pictures. The only advantage I have over a trained monkey that I may be saying no more often than merely this looks fishy, and that I may be saying this looks fishy more often than thinking something to be totally irrelevant. It's my job to think ahead of people. I told Janek in January that he should not try to recruit anybody unless he was going to take care of them, because it would end badly. I disagree. The problem is more that it would _start_ badly. Now if you take a look at our code base and documentation, it is pretty much unavoidable that it starts badly with regard to being in smooth sailing waters concerning technical matters. And it is going to last a few years. So if you are easily frustrated, you are not likely to stay around all that long. If you are not easily frustrated, you have a chance to stick around until you start seeing some good things not just in the program itself, but also in other developers, and even in some of our procedures and infrastructure. -- David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Macro for(UP_and_DOWN) and 3 similar. (issue 2491) (issue 6109046)
On Thu, Apr 26, 2012 at 08:05:53AM +0100, James wrote: Hello, On 26 April 2012 07:55, m...@apollinemike.com m...@apollinemike.com wrote: I have a meeting in mid-May w/ the University of Paris VIII. They're donating a computer to LilyPond and I'll set patchy up on it. While you can set up and cron patchy-merge-staging, patchy-test-patches still needs 'human' interaction (reg tests). Yes, although that could be worked around. For example, the server could generate the comparisons, then make them available on the web. When somebody (ideally a bug squad member in this scenario) wants to check patches, they go that url, check the images, then click yes, no changes. Emails with those urls would be sent to the lilypond-auto mailing list so that anybody could deal with them. I was actually thinking about such a system when I first set up Patchy, with particular reference to me going on vacation with only a netbook (or tablet) but leaving my desktop computer to do all that heavy lifting. Perhaps this computer could be better spent doing other LP related things Donate cycles for devs for instance via SSH - David might be appreciative of that. That's an option. I've run patchy-test just now for the three patches outstanding this morning. It's no a big deal, That's yet another egg in the James-basket. :( I'll also look at updating the CG instructions because while it is relatively simple, a non-dev like me always has trouble, initially, getting all my ducks in a row with regard to setting up LP source code, getting patchy downloaded and configured and then running her. That would be great. I also seriously wish that you'd take on an assistant -- either for doc editor or general admin. We need to get more people involved in keeping the project running, to spread the load so nobody gets overwhelmed. - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Macro for(UP_and_DOWN) and 3 similar. (issue 2491) (issue 6109046)
m...@apollinemike.com m...@apollinemike.com writes: On 26 avr. 2012, at 09:05, James wrote: Hello, On 26 April 2012 07:55, m...@apollinemike.com m...@apollinemike.com wrote: On 26 avr. 2012, at 07:28, Graham Percival wrote: Well, right now we have nobody running the automated tests to check that new patches are ok. So there will be no patches accepted to lilypond. I have a meeting in mid-May w/ the University of Paris VIII. They're donating a computer to LilyPond and I'll set patchy up on it. One thing I'm gonna try to do on that machine is have each index.html generated by a regtest comparison (along with the log/png/jpg/etc files) upload to a folder on mikesolomon.org. These can hang out indefinitely and an automatic e-mail can be sent to the list w/ an alert that patchset X is up for viewing on site Y. They make sense only with the accompanying files. I _am_ currently archiving test baselines (if you set LILYPOND_BASELINES to the name of an existing directory, this will happen when creating baselines) as part of speeding up the procedures. Those need to be cleaned up regularly since: total 769011712 153796608 baseline-57c0a284da0de2f89674bfa1cbae8159944b8f5a.tar.gz 153792512 baseline-98c77cfcf941179ec011ca0e0ada02e35ccf4d0c.tar.gz 153800704 baseline-dac45a9c828751fad2eed3ef8c9d756affbb5cb6.tar.gz 153804800 baseline-9830313f5f1f76df8b46bdeffe716fd5b2d6f331.tar.gz 153817088 baseline-bf2c7f09ff00e6c59877eff5ba5f880299ed95bf.tar.gz -- David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: What's with the test-patches volunteers?
On Thu, Apr 26, 2012 at 10:07:32AM +0200, David Kastrup wrote: I am afraid that you overestimate what I have been doing. I've been running test-patches and looking at pretty pictures. You've done more than that; you occasionally say this looks like a silly design or why not do XYZ instead. You say that quite often after patches are accepted and you're trying to work on that area of code, but you still catch some of those problems during the review. That's what I'm asking you to do. I'm not asking you to look at the pretty pictures; don't look at any patch until somebody has signed off on those pretty pictures. That was the whole point of Patchy, after all! I don't want to waste developers' time by looking at patches which have easily-found problems like regtest comparisons. But after that's done -- after a patch has passed Patchy and is on a countdown -- then please look at the patch, and ask yourself if I had to fix a bug or add a feature to this part of the code base, would that change make my work easier or harder?. - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Rename translation branch
2012/4/24 David Kastrup d...@gnu.org: Francisco Vila paconet@gmail.com writes: 2012/4/24 Francisco Vila paconet@gmail.com: 2012/4/24 David Kastrup d...@gnu.org: No objections then? Please go ahead. Thanks! I can take care of related docs. Patch for the rename in docs and lily-git.tcl I will apply the patch into translation branch because it is trivial. The docs talk an awful lot about pushing to _master_. While that has nothing to do with the rename, it might be worth fixing nevertheless. I agree, I am working on it. -- Francisco Vila. Badajoz (Spain) www.paconet.org , www.csmbadajoz.com ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Macro for(UP_and_DOWN) and 3 similar. (issue 2491) (issue 6109046)
Graham Percival gra...@percival-music.ca writes: On Thu, Apr 26, 2012 at 08:05:53AM +0100, James wrote: Hello, On 26 April 2012 07:55, m...@apollinemike.com m...@apollinemike.com wrote: I have a meeting in mid-May w/ the University of Paris VIII. They're donating a computer to LilyPond and I'll set patchy up on it. Perhaps this computer could be better spent doing other LP related things Donate cycles for devs for instance via SSH - David might be appreciative of that. That's an option. The one thing that in my processing power frames takes enough processing hunger to seriously offset the ssh hassle is making releases, and that is something I am not eager to have to start doing, anyway. It might be helpful to have things like test-patches available as a sort of web service: Lukasz mentioned that it ran something like 2 hours on his virtualized setup, and if we offer something like lily-dev as a virtual work environment for the hoi polloi, having well-powered web services for the worst aspects of performance eating during development would be nice. -- David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Macro for(UP_and_DOWN) and 3 similar. (issue 2491) (issue 6109046)
Mike, On 26 April 2012 08:51, m...@apollinemike.com m...@apollinemike.com wrote: On 26 avr. 2012, at 09:05, James wrote: Hello, On 26 April 2012 07:55, m...@apollinemike.com m...@apollinemike.com wrote: On 26 avr. 2012, at 07:28, Graham Percival wrote: Well, right now we have nobody running the automated tests to check that new patches are ok. So there will be no patches accepted to lilypond. I have a meeting in mid-May w/ the University of Paris VIII. They're donating a computer to LilyPond and I'll set patchy up on it. One thing I'm gonna try to do on that machine is have each index.html generated by a regtest comparison (along with the log/png/jpg/etc files) upload to a folder on mikesolomon.org. These can hang out indefinitely and an automatic e-mail can be sent to the list w/ an alert that patchset X is up for viewing on site Y. Still requires 'someone' to 'do' something and then say 'LGTM' and I don't know what the feed back has been with regard to the http://lilypond.org/doc/v2.15/Documentation/contributor/grand-regression-test-checking.html is this just not the same thing in essence? What about GUB? Might that be a (more) worthwhile 'project' for a machine like this? I've never tried to use GUB myself, but it seems to be something we could perhaps run nightly builds on. James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Staging/Master Merge - James' Patchy
lilypond.patchy.jl...@gmail.com writes: Begin LilyPond compile, commit: bf2c7f09ff00e6c59877eff5ba5f880299ed95bf Success:./autogen.sh --noconfigure Success:../configure --disable-optimising Success:nice make clean -j7 CPU_COUNT=7 Success:nice make -j7 CPU_COUNT=7 Success:nice make test-baseline -j7 CPU_COUNT=7 *** FAILED STEP *** patch /home/james/patchy/issue6109058_1.diff Success:nice make test-clean -j7 CPU_COUNT=7 Success:nice make clean *** FAILED STEP *** patch --reverse /home/james/patchy/issue6109058_1.diff Begin LilyPond compile, commit: bf2c7f09ff00e6c59877eff5ba5f880299ed95bf We really should get rid of that reverse patch nonsense. Instead, nuke the build directory and start from scratch. Graham wanted to avoid that because it would lose the test-baseline, but if one creates a LILYPOND_BASELINES environment variable pointing to an outside directory, make test-baseline will put a tarball there (and back again) without the need to recompile anything. -- David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: 30 day webathon for kickstarter support (issue 6068045)
I heart this response. =) K. On 2012-Apr-26, at 03:54, Trevor Daniels wrote: Graham Percival wrote Thursday, April 26, 2012 7:07 AM The Birmingham Amateur Theatre is presenting Penzance Pirates, starring our documentation editor Trevor Daniels as the talking lion![1] [1] this is (probably) not true. Amazingly, there's an element of truth in it. Read Bicester for Birmingham, though. I'm nearing the end of typesetting a new vocal score for a musical pantomime based on Sullivan's music from the Savoy operas. It has 19 musical numbers, all with original words. It will be performed next November. Oh, and it has a talking dragon rather than a lion, but probably not played by me, although I have played Samuel twice in Pirates. Trevor ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Kicking off GSoC
Hi Mike, Carl all! On Thu, Apr 26, 2012 at 7:58 AM, m...@mikesolomon.org m...@mikesolomon.org wrote: Hey Janek! Congrats again on getting accepted for GSoC. Reading the mentoring guide, there are a lot of getting to know you and the project bits that we've already done, so we can more or less get right to work. A few things: 3) It'd be good to have one long meeting to kick off the project. If you could factor that into your timeline, I can carve out the time needed for that. Ideally, we'd go over each issue and identify a code-map so that you hit the ground running. Definitely a good idea! Shall we skype? 1) Could you send me the finalized version of your timeline? There's an unexpected problem: i caught some virus and i'm getting ill. It's too early to say whether i'll be able to do some serious work in the next week or i'll have to stay in bed, which is extremely unfortunate since i have a short holiday on my university and it would be perfect to use it for GSoC... :( If i'll stay usable, here's the plan: Till sunday i'll be drawing an outline of the architecture myself, reading relevant code and writing down any questions related to general design. In the next week, we'd discuss general architecture design; list object properties and methods that need to be created. Determine how to harvest information about horizontal spacing and what changes in horizontal spacing engine will be necessary. (May 1-4 would be a good time for the high-octane meeting on chat, if i stay usable). The rest of the plan stays unchanged - i guess it'd be hard to make corrections before our chat. 2) I'm assuming that midterm reports are due for me when they're due for you, but could you double check on that? That's what GSoC FAQ says: July 9:19:00 UTCMentors and students can begin submitting mid-term evaluations. It's possible that Google will ask mentors for some initial opinions about thier students when the community bonding period ends and first payments are issued (~20 May). I'm sure GNU admin will kepp you informed. P.S. I'm starting off by ccing LilyDevel for all my GSoC communication in case others want to chime in. If for whatever reason people on the list or you don't want this, I can just e-mail you directly w/o ccing the list. I'm fine with ccing - the more transparency the better. Putting GSOC into subject should be enough to allow other to filter it, i think. cheers, Janek ...and wish me good health. oh my God... ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: GSoC
Hi Janek, i'd vote for having Extenders added by default, without the need to write them explicitly in ly code. Yes, but with an \autoExtendersOff option! :) Thanks, Kieren. ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Lilypond patchy and other Lilypond problems
Wooow, a lot of emails were posted in the last 24 hours :) I'll try to comment all your important thoughts, but it's possible that I miss one or two... Anyway: On 26 April 2012 07:28, Graham Percival gra...@percival-music.ca wrote: Some people encourage new contributors. I encourage new contributors who want to work on administrative tasks. I try to discourage new programmers, precisely because they almost always end up in situations like yours. My situation isn't bad - it's more or less ok. I had had some minor problems and a little argue with David, because I didn't know that patchy is run for each patch set. Now I know it, my patch LGT patchy and we have a new patchy runner - James. I can continue on developing and patches will continue to be assessed. That's great, don't you think? :) Last January, I warned him that he should not try to recruit any new programmers unless he was willing to mentor them because it is very difficult for new programmers to get started. I think you have seen that my prediction was correct. I'm not an experienced developer, but I have a slight feeling that you are a bit exaggerating. If I'm wrong, correct me :) On 26 April 2012 08:55, m...@apollinemike.com m...@apollinemike.com wrote: I have a meeting in mid-May w/ the University of Paris VIII. They're donating a computer to LilyPond and I'll set patchy up on it. Wow, that's really, really nice. Why do they do so? Maybe my university could make a similar donation...? On 26 April 2012 09:05, James pkx1...@gmail.com wrote: I've run patchy-test just now for the three patches outstanding this morning. It's no a big deal, I've just never got round to running the patchy-test scripts (well since the scripts were very first created when I had trouble understanding them), so don't worry about patches David now, I'll pick up the slack here. Thanks, James! That's really great! :) Mike, Graham and David wrote about more or less automatic running of tests and presenting only the results, possibly on an unused computer. I realised that I have a server on Dreamhost that probably could be such a computer - there is unlimited disk space and unlimited bandwidth (to some extend, I guess, but that will be enough for us). Now I'm trying to compile Lilypond on it - there are some libraries missing, I'm in progress of figuring out whether I can install it locally (it's a shared server, not a private one, so I don't have root on it). If yes and lilypond compiles, we could automatically pull git repo, run tests on it, pack the results and send an email with a link to them. There is Apache, PHP, MySQL there, so if you would like to do a website to present results directly on the server, it's possible :) By now I'm trying to run successfully ./configure for guile - it requires some additional libraries, which require some other etc. On 26 April 2012 11:43, James pkx1...@gmail.com wrote: Still requires 'someone' to 'do' something and then say 'LGTM' and I don't know what the feed back has been with regard to the http://lilypond.org/doc/v2.15/Documentation/contributor/grand-regression-test-checking.html is this just not the same thing in essence? Woow, what's that: http://www.philholmes.net/lilypond/regtests/ for? Is it for rating regression tests or for rating that particular result of a particular test run? Łukasz ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Doc: LM - Use Homophonic instead of Monophonic (issue 6107045)
Reviewers: dak, Graham Percival,
Message:
committer James Lowe pkx1...@gmail.com
Thu, 26 Apr 2012 18:48:33 + (19:48 +0100)
commit 6b9b2c2e3e701852485c24bc71f404effc6d83ec
Thanks.
James
http://codereview.appspot.com/6107045/diff/1/Documentation/learning/fundamental.itely
File Documentation/learning/fundamental.itely (right):
http://codereview.appspot.com/6107045/diff/1/Documentation/learning/fundamental.itely#newcode1045
Documentation/learning/fundamental.itely:1045: % The following notes are
homophonic
On 2012/04/23 03:37:53, Graham Percival wrote:
On 2012/04/22 16:16:00, dak wrote:
I don't have a better suggestion right now, but _notes_ are always
mono/homophonic.
This section is homophonic ?
Done.
Description:
Doc: LM - Use Homophonic instead of Monophonic
Issue 2488
Some confusion on the term 'monophonic'
(currently used as distinct from 'polyphonic')
Changed three cases it occurs.
One removed completely - just keep the reference to a 'single voice'.
Other two changed to 'Homophonic'.
Please review this at http://codereview.appspot.com/6107045/
Affected files:
M Documentation/learning/fundamental.itely
Index: Documentation/learning/fundamental.itely
diff --git a/Documentation/learning/fundamental.itely
b/Documentation/learning/fundamental.itely
index
847c8489e750718470c5e6d6a4af6f3f8bb514ba..8d9ba6421b65bcc11795e584848312b0440f97be
100644
--- a/Documentation/learning/fundamental.itely
+++ b/Documentation/learning/fundamental.itely
@@ -578,10 +578,10 @@ In fact, a Voice layer or context is the only one
which can contain
music. If a Voice context is not explicitly declared one is created
automatically, as we saw at the beginning of this chapter. Some
instruments such as an Oboe can play only one note at a time. Music
-written for such instruments is monophonic and requires just a single
-voice. Instruments which can play more than one note at a time like
-the piano will often require multiple voices to encode the different
-concurrent notes and rhythms they are capable of playing.
+written for such instruments requires just a single voice. Instruments
+which can play more than one note at a time like the piano will often
+require multiple voices to encode the different concurrent notes and
+rhythms they are capable of playing.
A single voice can contain many notes in a chord, of course,
so when exactly are multiple voices needed? Look first at
@@ -616,7 +616,7 @@ The fragments must also be separated with double
backward slashes,
@code{\\}, to place them in separate voices. Without these, the
notes would be entered into a single voice, which would usually
cause errors. This technique is particularly suited to pieces of
-music which are largely monophonic with occasional short sections
+music which are largely homophonic with occasional short sections
of polyphony.
Here's how we split the chords above into two voices and add both
@@ -1042,7 +1042,7 @@ permitting a phrasing slur to be drawn over them.
@lilypond[quote,ragged-right,verbatim]
\new Staff \relative c' {
\voiceOneStyle
- % The following notes are monophonic
+ % The following notes are homophonic
c16^( d e f
% Start simultaneous section of three voices
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Lilypond patchy and other Lilypond problems
Hello, 2012/4/26 Łukasz Czerwiński milimet...@gmail.com: ... On 26 April 2012 09:05, James pkx1...@gmail.com wrote: I've run patchy-test just now for the three patches outstanding this morning. It's no a big deal, I've just never got round to running the patchy-test scripts (well since the scripts were very first created when I had trouble understanding them), so don't worry about patches David now, I'll pick up the slack here. Thanks, James! That's really great! :) No problem, but it doesn't mean that you can just do some code and throw it up for review without ANY basic testing your side, it should apply to current tree and it should also pass a basic 'make'. I am sure you are aware of that courtesy. It is true that Patchy does this also and so catches the basic mistakes, but patchy's main goal is to take away the more intensive 'make test' from developers which can take a long time on less powerful machines. Also patchy testers are not (usually) programmers - like me for instance - so I'm not going to go into much detail; if patchy shows up regressions then that is easy to spot - that is a web page for me to see, but more subtle 'make' problems or 'patch apply' problems Like this this morning - see comment #1 http://code.google.com/p/lilypond/issues/detail?id=2498 are going to get a 'failed - patch doesn't apply' or 'failed to make' messages and not much else. Hence the need for some basic housekeeping on your side. Mike, Graham and David wrote about more or less automatic running of tests and presenting only the results, possibly on an unused computer. I realised that I have a server on Dreamhost that probably could be such a computer - there is unlimited disk space and unlimited bandwidth (to some extend, I guess, but that will be enough for us). Now I'm trying to compile Lilypond on it - there are some libraries missing, I'm in progress of figuring out whether I can install it locally (it's a shared server, not a private one, so I don't have root on it). Did you look at LilyDev? This is specifically aimed at LilyPond developers who don't have the time or inclination to set up their dev build. It's got pretty much all you need right there and yuo can be up and running in a few minutes (once you have it installed). LilyDev is a pre-built Ubuntu dist with all the dependencies. I run it in a VM (I use KVM at home but Virtual Box at work). It might be simpler. See: http://lilypond.org/doc/v2.15/Documentation/contributor/installing-lilydev The instructions have been updates significantly but I am sure you can understand how to install an OS using an ISO file. On 26 April 2012 11:43, James pkx1...@gmail.com wrote: Still requires 'someone' to 'do' something and then say 'LGTM' and I don't know what the feed back has been with regard to the http://lilypond.org/doc/v2.15/Documentation/contributor/grand-regression-test-checking.html is this just not the same thing in essence? Woow, what's that: http://www.philholmes.net/lilypond/regtests/ for? Is it for rating regression tests or for rating that particular result of a particular test run? Phil does a pixel comparison reg test between *releases* i.e. http://lists.gnu.org/archive/html/lilypond-devel/2010-11/msg00078.html and has some programming experience so this is an offshoot of what he does with the project anyway and he offered this as a service, I am sure he will fill you in (I cannot find he original email I think he sent out). James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Lilypond patchy and other Lilypond problems
Hello, On 26 April 2012 21:38, James pkx1...@gmail.com wrote: No problem, but it doesn't mean that you can just do some code and throw it up for review without ANY basic testing your side, it should apply to current tree and it should also pass a basic 'make'. Yes, before uploading a patch I make sure that it will apply and compile. Now I also know that I should be aware that patchy is run on each patch set, so I must check the result of it before uploading the next patch set. Mike, Graham and David wrote about more or less automatic running of tests and presenting only the results, possibly on an unused computer. I realised that I have a server on Dreamhost that probably could be such a computer - there is unlimited disk space and unlimited bandwidth (to some extend, I guess, but that will be enough for us). Now I'm trying to compile Lilypond on it - there are some libraries missing, I'm in progress of figuring out whether I can install it locally (it's a shared server, not a private one, so I don't have root on it). Did you look at LilyDev? This is specifically aimed at LilyPond developers who don't have the time or inclination to set up their dev build. It's got pretty much all you need right there and yuo can be up and running in a few minutes (once you have it installed). LilyDev is a pre-built Ubuntu dist with all the dependencies. I run it in a VM (I use KVM at home but Virtual Box at work). It might be simpler. See: http://lilypond.org/doc/v2.15/Documentation/contributor/installing-lilydev The instructions have been updates significantly but I am sure you can understand how to install an OS using an ISO file. Well, LilyDev won't help me - on the server exists an already installed system (Linux). As for Virtualbox, I believe, that without having admin rights I can't install it - correct me if I'm wrong. On 26 April 2012 11:43, James pkx1...@gmail.com wrote: Still requires 'someone' to 'do' something and then say 'LGTM' and I don't know what the feed back has been with regard to the http://lilypond.org/doc/v2.15/Documentation/contributor/grand-regression-test-checking.html is this just not the same thing in essence? Woow, what's that: http://www.philholmes.net/lilypond/regtests/ for? Is it for rating regression tests or for rating that particular result of a particular test run? Phil does a pixel comparison reg test between *releases* i.e. http://lists.gnu.org/archive/html/lilypond-devel/2010-11/msg00078.html and has some programming experience so this is an offshoot of what he does with the project anyway and he offered this as a service, I am sure he will fill you in (I cannot find he original email I think he sent out). Do you mean Phil Holmes? Łukasz ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Lilypond patchy and other Lilypond problems
Hello, 2012/4/26 Łukasz Czerwiński milimet...@gmail.com: Well, LilyDev won't help me - on the server exists an already installed system (Linux). As for Virtualbox, I believe, that without having admin rights I can't install it - correct me if I'm wrong. Well I'm not a *NIX admin - I do have to use 'sudo' to install the program but not run it and I do need to add a vboxuser to allow USB support (and to stop the annoying warning even if I never use the USB support). There are lots of other virtualization platforms out there, I'd ask at your 'institution', if you don't already know, as from my own day-to-day working experience a lot of these places use Virtual Environments because it is so easy now to set up, XCP, Cirix XENserver, KVM, VMware ESX, Windows Hyper-V etc. In fact in many of these places set up a VM in preference to a /home dir because it is now so easy to manage a VM is just a 'big file' (no different in essence to a /home 'directory') - but I digress. Phil does a pixel comparison reg test between *releases* i.e. http://lists.gnu.org/archive/html/lilypond-devel/2010-11/msg00078.html and has some programming experience so this is an offshoot of what he does with the project anyway and he offered this as a service, I am sure he will fill you in (I cannot find he original email I think he sent out). Do you mean Phil Holmes? Yes. ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
PATCH: Countdown to 20120429
For 20:00 MDT Sunday, April 29 Defect: Issue 2449 http://code.google.com/p/lilypond/issues/detail?id=2449: Redesign stream event class representation - R6121050 http://codereview.appspot.com/6121050/ Enhancement: Issue 2496 http://code.google.com/p/lilypond/issues/detail?id=2496: Patch: 30 day webathon for kickstarter support - R6068045 http://codereview.appspot.com/6068045/ Issue 2491 http://code.google.com/p/lilypond/issues/detail?id=2491: Patch: Macro for(UP_and_DOWN) and 3 similar - R6109046 http://codereview.appspot.com/6109046/ Patch: Issue 2480 http://code.google.com/p/lilypond/issues/detail?id=2480: hideNotes and unHideNotes should include also TabNoteHead - R6105049 http://codereview.appspot.com/6105049/ Thanks to James for running test-patches, too! I'll take a run at getting it going in a VM at the office tomorrow: should be feasible to run it a couple of times a day. Cheers, Colin -- I've learned that you shouldn't go through life with a catcher's mitt on both hands. You need to be able to throw something back. -Maya Angelou, poet (1928- ) ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Website build crashing
Hey all, My website build crashes with: mikesol@mikesol-laptop:~/lilypond-git$ sudo make LILYPOND_WEB_MEDIA_GIT=/home/mikesol/lilypond-extra website make --no-builtin-rules config_make=./config.make \ top-src-dir=/home/mikesol/lilypond-git \ -f /home/mikesol/lilypond-git/make/website.make \ website make[1]: Entering directory `/home/mikesol/lilypond-git' cp /home/mikesol/lilypond-git/Documentation/misc/out out-website/website/misc/out cp: omitting directory `/home/mikesol/lilypond-git/Documentation/misc/out' make[1]: *** [out-website/website/misc/out] Error 1 make[1]: Leaving directory `/home/mikesol/lilypond-git' make: *** [website] Error 2 It seems that the cp command is trying to copy the misc/out directory without adding the -r flag. Can someone confirm this problem before I open a tracker issue? Cheers, MS ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
LoMuS
Hey all, I've received a couple e-mails from colleagues and one nudge from Valentin about: http://concours.afim-asso.org/ I've been reticent about applying because the development community is rather diffuse and there isn't any good way to accept the prize money if we win. However, after having received now two e-mails from people who I respect a lot in the French computer music community, I think it'd be a good idea and that we should let institutional barriers stop us from applying. I'm OK with writing up the application (due the 29th) but before I do, people would need to agree on where the prize money would go if we won. My two thoughts are: 1) Use it internally on projects (i.e. we'd all agree that person X would get paid Z euros to do thing Y) in which case there'd have to be a money shepherd. I'd rather not do this, but I can if no one else wants to. 2) Donate it to GNU. I'd be good to set a precedent for this now so that LilyPond can apply to other software competitions in the future. Cheers, MS P.S. Sorry for the last-minuteness of this e-mail: I had sent it from m...@mikesolomon.org and it didn't go through. I'll have to change e-mail addresses on the list...___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: LoMuS
I've received a couple e-mails from colleagues and one nudge from Valentin about: http://concours.afim-asso.org/ Aah, very nice! Yes, participating in this contest would be a good thing; and thanks for your offer to writing up the application. 1) Use it internally on projects (i.e. we'd all agree that person X would get paid Z euros to do thing Y) in which case there'd have to be a money shepherd. I'd rather not do this, but I can if no one else wants to. I suggest that *you* are the person receiving the money, acting as a representative and contact person for this contest. In due course it is up to you how to distribute the money within the lilypond development. Werner ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
