I would not hard-code the numbers in the names. If you have a file for the
whole suite, which includes all the movements in the right order, you have
already defined the order. Cleaner and more flexible, in my opinion.
On 14 maggio 2014 04:46:22 CEST, Knute Snortum ksnor...@gmail.com wrote:
I
This is how I propose to have the movements and the suite:
https://drive.google.com/folderview?id=0B_aEseOV9KTXamtCeUhXenF2eWcusp=sharing
Knute Snortum
(via Gmail)
On Wed, May 14, 2014 at 4:44 AM, Knute Snortum ksnor...@gmail.com wrote:
I agree. My original idea was to do this: put the
Il 14.05.2014 14:43 Knute Snortum ha scritto:
This is how I propose to have the movements and the suite:
https://drive.google.com/folderview?id=0B_aEseOV9KTXamtCeUhXenF2eWcusp=sharing
[21]
A couple of comments:
- your -all.ly file, which includes all the movements, doesn't print
the
I love it. A while ago I asked how to create a single all-movements suite
file and this is exactly what I needed to see.
Now I need to know how to submit this. One branch and pull request for
each movement separately and one for the suite?
Knute Snortum
(via Gmail)
On Wed, May 14, 2014 at
I would put all the changes into one pull request (I wouldn't even use a
branch) but Glen has said (and this document [1] implies) that there should
be one file per branch per pull request. I admit that this seems strange
but I'm trying to do things the Mutopia way.
[1]
Il 14.05.2014 17:02 Knute Snortum ha scritto:
I would put all the changes into one pull request (I wouldn't even use
a branch) but Glen has said (and this document [1] implies) that there
should be one file per branch per pull request. I admit that this
seems strange but I'm trying to do
Hi Knute,
The issue of collections, availability of a consolidated PDF including all
pieces as well as individual pieces, maintainability, and support within the
current structure and automation is a great topic to discuss.
I've created a discussion topic in github to collect proposals and
I brought up the problem here of how to present a set of movements that can
be individually downloaded and yet allow the user to play the suite as a
whole in the correct order. The easiest solution was deemed the best, that
is, rename the movements with numbers as the beginning of their name so
