: output-lib.scm
scripts: abc2ly.py convert-ly.py etf2ly.py
lilypond-book.py midi2ly.py musicxml2ly.py
Something's not quite right in midi2ly. Attached patch seems to fix it,
but I don't know if it is correct.
2006-07-25 Joe Neeman [EMAIL PROTECTED
are attached in a tar archive (I cc to Han-Wen just in
case the list strips it). There are 13 of them, so I thought it would be
easier.
2006-07-25 Joe Neeman [EMAIL PROTECTED]
* scm/page.scm (make-page): make it friendlier to call (esp. from C++)
* scm/layout-page-layout.scm (make
On Fri, 2006-07-21 at 11:44 +, Han-Wen Nienhuys wrote:
CVSROOT: /cvsroot/lilypond
Module name: lilypond
Changes by: Han-Wen Nienhuys hanwen 06/07/21 11:44:59
snip
Log message:
* scm/output-lib.scm (grace-spacing::calc-shortest-duration): new
function.
On Fri, 2006-06-23 at 20:16 -0400, Kieren MacMillan wrote:
Hi, Joe!
I haven't tested it, but it should work to change the context property
Staff.keepAliveInterfaces to include multi-measure-rest-interface.
Thanks for the hint.
However, I can't seem to get it to work -- am I trying the
On Fri, 2006-06-23 at 11:07 -0400, Kieren MacMillan wrote:
Hello, all --
What would I have to do to add MultiMeasureRest to items-worth-
living in a given Staff (but not the whole Score)?
I haven't tested it, but it should work to change the context property
Staff.keepAliveInterfaces to
(c) 2006 Joe Neeman [EMAIL PROTECTED]
*/
#ifndef MATRIX_HH
#define MATRIX_HH
#include std-vector.hh
templateclass T, class A=std::allocatorT
class Matrix
{
public:
MatrixT, A ()
{
rank_ = 0;
}
MatrixT, A (vsize rows, vsize columns, T const t)
: data_(rows * columns, t
On Fri, 2006-06-09 at 12:18 +0200, Han-Wen Nienhuys wrote:
Joe Neeman schreef:
Here are the final differences between my working copy and CVS lilypond.
To use the new page breaker, add Page_turn_engraver to the staff which
is relevant for page turns, then add
#(define page-breaking
On Fri, 2006-06-09 at 13:37 +0200, Mats Bengtsson wrote:
Joe Neeman wrote:
...
(Note: this page-breaker doesn't support break-before. Use \pageBreak or
\noPageBreak at the end of the previous score instead)
Great, since break-before was introduced because you previously couldn't use
On Thu, 2006-06-08 at 17:18 +0200, Han-Wen Nienhuys wrote:
Joe Neeman schreef:
On Thu, 2006-06-08 at 09:05 +1000, Joe Neeman wrote:
Anyway, here's another try. Same ChangeLog as before
After your last email, I've removed the changes to
Item::handle_prebroken_dependencies and changed
On Thu, 2006-06-08 at 17:17 -0700, Paul Scott wrote:
A part produced with:
\book {
\score { }
\score { }
}
Using 2.9.8 seems to force a page break at the end of a movement
(\score) whether there is room for part of the next movement or not.
That is unless there is room for
On Wed, 2006-06-07 at 10:25 +0200, Han-Wen Nienhuys wrote:
Joe Neeman schreef:
Did my previous mail make it to the list? I never saw it... but anyway,
here's an update
sorry, it was on my todo list, but your patch got caught up in other stuff.
That's fine, it's just that for some reason I
+++ ChangeLog 7 Jun 2006 22:54:54 -
@@ -1,3 +1,39 @@
+2006-06-08 Joe Neeman [EMAIL PROTECTED]
+
+ * scm/paper-system.scm (paper-system-annotate): also annotate the
+ estimated pure-Y-extent
+
+ * scm/define-grobs.scm: add pure-Y-extent and pure-Y-offset functions
+
+ * lily/system.cc (break_into_pieces
On Thu, 2006-06-08 at 09:05 +1000, Joe Neeman wrote:
Anyway, here's another try. Same ChangeLog as before
After your last email, I've removed the changes to
Item::handle_prebroken_dependencies and changed axis-group-interface.cc.
I'm only attaching the part of axis-group-interface.cc
On Tue, 2006-06-06 at 09:18 +0200, Han-Wen Nienhuys wrote:
Joe Neeman schreef:
Just to make things a bit weirder, I have a working copy with
modifications that _should_ be completely irrelevant (the
spacing-stick-out patch). In this working copy, I get the second png
file no matter what
On Tue, 2006-06-06 at 10:17 +0200, Han-Wen Nienhuys wrote:
Joe Neeman schreef:
On Tue, 2006-06-06 at 09:18 +0200, Han-Wen Nienhuys wrote:
Joe Neeman schreef:
Just to make things a bit weirder, I have a working copy with
modifications that _should_ be completely irrelevant (the
spacing
Did my previous mail make it to the list? I never saw it... but anyway,
here's an update
On Mon, 2006-05-22 at 20:58 +1000, Joe Neeman wrote:
On Mon, 2006-05-22 at 10:57 +0200, Han-Wen Nienhuys wrote:
Does this patch already work for determining system heights, or is just
the beginning
The attached patch fixes a segfault/heap corruption that I was having,
but I'm not really sure why because I don't fully understand how the
guile garbage collection works.
Valgrind was complaining about reads/writes to unallocated memory from
line 57 of tuplet-number.cc. The memory had been freed
When I make web a clean lilypond CVS version, instrument-name.ly
compiles to the first attached png file. If I do
$ rm input/regression/out-www/lily-409* input/regression/out-www/coll*
$ make web
I get the second attached png file. I also get the second attached png
file if I try to generate it
+++ ChangeLog 5 Jun 2006 01:38:33 -
@@ -1,3 +1,11 @@
+2006-06-05 Joe Neeman [EMAIL PROTECTED]
+
+ * lily/simple-spacer.cc (get_line_configuration): add the
+ keep-inside-line rods.
+
+ * lily/simple-spacer.cc (get_line_forces): check for forced
+ line-breaks here also.
+
2006-06-05 Han-Wen
On Fri, 2006-06-02 at 11:12 -0400, Kieren MacMillan wrote:
Hi, Han-Wen --
I think it should work to define a context TimeSignatureContext that'
contains only Time_signature_engraver and Axis_group_engraver.
If I understand what you're suggesting, this is exactly what the docs
On Mon, 2006-05-22 at 20:58 +1000, Joe Neeman wrote:
On Mon, 2006-05-22 at 10:57 +0200, Han-Wen Nienhuys wrote:
Joe Neeman schreef:
In that case, you could get the approximate height of one broken system
in logarithmic time.
Here's a first attempt at doing this. It isn't complete
On Mon, 2006-05-15 at 12:20 +0200, Han-Wen Nienhuys wrote:
Perhaps you could even compute for each VerticalAxisGroup the range of
column ranks where it would disappear, and use that information add a
method to compute the approximate height of an alignment spanner, where
you explicitly call
On Mon, 2006-05-22 at 10:57 +0200, Han-Wen Nienhuys wrote:
Joe Neeman schreef:
In that case, you could get the approximate height of one broken system
in logarithmic time.
Here's a first attempt at doing this. It isn't complete or well-tested
yet. I add 4 grob properties
Y-extent
On Mon, 2006-05-15 at 12:20 +0200, Han-Wen Nienhuys wrote:
Joe Neeman schreef:
There is actually another possibility that I've only just thought of so
it's
pretty half-baked:
Add an approximate-Y-extent to each grob that
1) leaves the grob constant (in particular no caching)
2
On Sun, 14 May 2006 20:40, Han-Wen Nienhuys wrote:
Joe Neeman schreef:
We discussed this a bit a long time ago but I'm getting close to actually
implementing something so I thought I'd bring it up again.
Getting the Y-extent of a system is potentially destructive, causing all
sorts
On Sun, 14 May 2006 02:07, Han-Wen Nienhuys wrote:
Joe Neeman schreef:
{
Output_def *l = pscore_-layout ();
- Real extent = scm_to_double (l-c_variable (system-height));
+ Real extent = robust_scm2double (l-c_variable (system-height),
12.0); Real padding
We discussed this a bit a long time ago but I'm getting close to actually
implementing something so I thought I'd bring it up again.
Getting the Y-extent of a system is potentially destructive, causing all sorts
of non-undoable caching and possibly suiciding of grobs. So I need to do make
a
Here is a patch for the bug found by Trent Johnston:
2006-05-13 Joe Neeman [EMAIL PROTECTED]
* lily/constrained-breaking.cc (resize): give a default value
for system-height
Index: ChangeLog
===
RCS file: /sources
On Fri, 12 May 2006 05:38, Han-Wen Nienhuys wrote:
2006/5/11, Han-Wen Nienhuys [EMAIL PROTECTED]:
So it seems 2.8.1 is linked statically with libstdc++ and 2.9.4 isn't.
Is this intentional?
No, there was a packaging error with GCC that slipped through in the
installer.
can you try
I'm trying to install the GUB 2.9.4-1 on gentoo linux (amd64, but with a bunch
of x86 compatibility libs). I get
$
LD_LIBRARY_PATH=/home/joe/oldlilypond/usr/lib/
/home/joe/oldlilypond/usr/bin/lilypond
/home/joe/oldlilypond/usr/bin/lilypond:
On Tue, 9 May 2006 18:07, Han-Wen Nienhuys wrote:
Han-Wen Nienhuys schreef:
Joe Neeman wrote:
OK, here's another try
(and I made web successfully).
how is this possible? Did you do make web-clean in between?
I did, but I didn't notice this because it didn't cause the build to fail
On Tue, 9 May 2006 18:52, Han-Wen Nienhuys wrote:
Joe Neeman schreef:
On Tue, 9 May 2006 18:07, Han-Wen Nienhuys wrote:
Han-Wen Nienhuys schreef:
Joe Neeman wrote:
OK, here's another try
(and I made web successfully).
how is this possible? Did you do make web-clean in between
On Wed, 10 May 2006 00:13, Han-Wen Nienhuys wrote:
Joe Neeman schreef:
On Tue, 9 May 2006 18:07, Han-Wen Nienhuys wrote:
Han-Wen Nienhuys schreef:
Joe Neeman wrote:
OK, here's another try
(and I made web successfully).
how is this possible? Did you do make web-clean in between
On Wed, 10 May 2006 09:37, Han-Wen Nienhuys wrote:
Joe Neeman wrote:
On Wed, 10 May 2006 00:13, Han-Wen Nienhuys wrote:
it's customary to add such changes to define-grobs.scm
OK, here's a patch. (I've just modified my previous ChangeLog entry. Is
that OK or should I make a new entry
On Mon, 8 May 2006 04:07, Han-Wen Nienhuys wrote:
there's a bit of confusion with the breakable property, because it both
signals whether or not items are on nonmusical Paper_columns (see eg.
the use of Item::is_breakable in separating-line-group-engraver.cc) and
to signal whether a
OK, here's another try (and I made web successfully).
2006-05-08 Joe Neeman [EMAIL PROTECTED]
* scm/define-context-properties.scm:
* scm/define-grob-properties.scm:
* scm/define-grobs.scm:
* scm/define-music-display-methods.scm:
* scm/define-music
I'm probably just being retarded with CVS, but:
$ cvs ci
# only wants to commit the changelog
$ cvs ci lily/bar-engraver.cc lily/beam-engraver.cc
# wants to commit both files
$ cvs ci lily/bar-engraver.cc lily/beam-engraver.cc ChangeLog
# only wants to commit the ChangeLog
I've also tried all
Please disregard. The problem was that CVS/lily/Root still listed the anoncvs
server.
On Tue, 9 May 2006 08:11, Joe Neeman wrote:
I'm probably just being retarded with CVS, but:
$ cvs ci
# only wants to commit the changelog
$ cvs ci lily/bar-engraver.cc lily/beam-engraver.cc
# wants
On Sun, 7 May 2006 12:49, Han-Wen Nienhuys wrote:
Joe Neeman wrote:
I'm not entirely sure what you mean by this. Are you thinking of having
multiple Events? With a BreakEvent, PageBreakEvent and PageTurnEvent we
could tweak break-permission, page-break-permission and
page-turn-permission
On Sat, 6 May 2006 22:07, Han-Wen Nienhuys wrote:
Joe Neeman wrote:
I don't think I've explained it very well, but suppose you want to do
\break \noPageBreak. Then \noPageBreak needs to respect the changes made
by \break so there must be a symbol that means don't change anything
-- in order to forbid
line breaks, engravers will set forbidBreak = #t in the Score context instead
of doing it with function calls through Score_engraver.
2006-05-05 Joe Neeman [EMAIL PROTECTED]
* scm/define-context-properties.scm:
* scm/define-grob-properties.scm:
* scm
On Fri, 5 May 2006 18:43, Han-Wen Nienhuys wrote:
Joe Neeman wrote:
First of all, instead of penalty, breakable and page-penalty, we now
have: break-penalty, break-permission
page-break-penalty, page-break-permission
page-turn-penalty, page-turn-permission
sounds good.
where XXX
On Fri, 5 May 2006 18:43, Han-Wen Nienhuys wrote:
Joe Neeman wrote:
First of all, instead of penalty, breakable and page-penalty, we now
have: break-penalty, break-permission
page-break-penalty, page-break-permission
page-turn-penalty, page-turn-permission
sounds good.
where XXX
I would like to add a forbid/force/default datatype to lilypond. In C++, it
would be represented by
enum {
FORBID = -1,
DEFAULT = 0,
FORCE = 1
}
and in scheme it would be
(define-public FORBID -1)
(define-public DEFAULT 0)
(define-public FORCE 1)
with the usual
On Thu, 4 May 2006 21:13, Han-Wen Nienhuys wrote:
Joe Neeman schreef:
Why an enum?
Because C++ has damaged my brain and I'm used to thinking of discrete types as
enums/integers.
Isn't an SCM symbol ( 'forbid vs. 'force) more appropriate?
Yes it is, thanks
On Mon, 1 May 2006 11:04, Joe Neeman wrote:
On Mon, 1 May 2006 10:04, Han-Wen Nienhuys wrote:
If you have checked that the regtest document
looks ok, please apply the spacing patch too.
I have a couple regressions that may be caused by my spacing patch (or
maybe by some of my other changes
On Mon, 1 May 2006 09:35, Han-Wen Nienhuys wrote:
Joe Neeman wrote:
I'm also not certain if these are normal.
Given that this is where lilypond exits with an error, I'd hope not ;).
It turns out that this is caused by guile 1.6. The compatibility hack (if
(not (defined? 'inf
On Mon, 1 May 2006 10:04, Han-Wen Nienhuys wrote:
looks good. Please apply.
Done (my first CVS commit! very exciting :))
If you have checked that the regtest document
looks ok, please apply the spacing patch too.
I have a couple regressions that may be caused by my spacing patch (or maybe
On Fri, 28 Apr 2006 19:35, Graham Percival wrote:
On 28-Apr-06, at 2:17 AM, Joe Neeman wrote:
warning: can't find line breaking that satisfies constraints
Drawing systems...
Writing lily-4123261884423383907-systems.tex...
Writing lily-4123261884423383907-systems.texi...
Layout output
My bad, sorry. Patch attached.
2006-04-25 Joe Neeman [EMAIL PROTECTED]
* lily/stem-tremolo.cc (print): fix whole note tremolo placement
* input/regression/stem-tremolo.ly: add 2 more whole note examples
On Tue, 25 Apr 2006 08:34, Panteck wrote:
Windows XP, Lilypond 2.8.1-4
This patch represents my changes to line spacing over several weeks so it's
fairly big. Most of it is intertwined, though, so I can't separate it much
except for some of the small changes in paper-score and system.
2006-04-20 Joe Neeman [EMAIL PROTECTED]
* lily/simple-spacer.cc
On Tue, 11 Apr 2006 22:31, Geoff Horton wrote:
I don't know if that information helps at all, but at least it provides
some sort of motivation for the behaviour. In any case, I would vote for
changing it too.
But what if a person wants to refer to a Scheme variable (as in the
flower/include/std-vector.hh contains the comment:
/* FIXME: the COMPARE functionality is broken? */
and the version of vector_sort that makes use of the STL sort algorithm is
commented out. But based on my reading of the SGI STL manual[1], you are just
using the wrong compare function. You
On Fri, 7 Apr 2006 16:31, Werner LEMBERG wrote:
TeX has exactly the same problem.
Does TeX allow the user to arbitrarily assign penalties for inserting a line
break at the end of any word?
Interestingly, Knuth seems to have
accepted this. Isn't it possible to provide default values for the
On Fri, 7 Apr 2006 20:02, Han-Wen Nienhuys wrote:
Juergen Reuter wrote:
Maybe I am totally wrong, but this discussion reminds me of an issue
that I raised on Nov 18, last year; see the thread starting here:
http://lists.gnu.org/archive/html/lilypond-devel/2005-11/msg00088.html
I am
On Fri, 7 Apr 2006 19:55, Han-Wen Nienhuys wrote:
Joe Neeman wrote:
Suppose we add penalties. Let G(B) be the penalty function for a
partition into lines. G(B) has no nice structure at all. It will probably
be zero most of the time, with a few very large spikes. And we want to
minimize F
On Sat, 8 Apr 2006 00:52, David Feuer wrote:
On 4/7/06, Joe Neeman [EMAIL PROTECTED] wrote:
In constrained-breaking, I use the square of the force rather than its
absolute value -- I made the change for precisely this reason.
The sum of absolute values will generally be more stable than
On Fri, 7 Apr 2006 20:00, Han-Wen Nienhuys wrote:
Joe Neeman wrote:
On Fri, 7 Apr 2006 16:31, Werner LEMBERG wrote:
TeX has exactly the same problem.
Does TeX allow the user to arbitrarily assign penalties for inserting a
line break at the end of any word?
Yes, I'm certain. See ch. 14
On Fri, 7 Apr 2006 00:48, Han-Wen Nienhuys wrote:
Hi Joe,
any news on the new line breaking patches? shouldn't we move to
include them in lp 2.9 ?
I'm flat out until Monday, so I'll try to start sending things then. The
current status is that the big missing feature is the ability to
On Wed, 29 Mar 2006 10:16, Han-Wen Nienhuys wrote:
Joe Neeman wrote:
As far as I can tell, page and line penalties are used _only_ for
forbidding and forcing page breaks.
correct
Is there much chance they will ever be used for
anything else? If not, they could be replaced
instead of
g'4:32. I'm not quite sure how I caused a regression here, but here's a patch
anyway...
2006-03-30 Joe Neeman [EMAIL PROTECTED]
* lily/chord-tremolo-engraver.cc (acknowledge_stem): set the
stem-tremolo object in the stem (or else the stem might not be
long enough
On Thu, 30 Mar 2006 20:58, Han-Wen Nienhuys wrote:
Joe Neeman wrote:
2006-03-30 Joe Neeman [EMAIL PROTECTED]
* lily/chord-tremolo-engraver.cc (acknowledge_stem): set the
stem-tremolo object in the stem (or else the stem might not be
long enough).
just a minor nit, but can
behaviour of
tremolos and I'm also not quite sure what the protocol is for adding things
to interfaces (I added style to stem-tremolo-interface. It can be
'rectangle or 'default) but here is another try anyway. I also enclose a
regression test and an image of the output.
2006-03-28 Joe Neeman
On Thu, 30 Mar 2006 01:46, Han-Wen Nienhuys wrote:
thanks. I've added your changes to 2.9 ; I'll probably backport the diff
of 2.9.0 to 2.8.1 as a whole.
Before you do, I've just realised that I caused a regression for tremolos on
whole notes. I'll fix that today.
Can you look at the regtests
On Thu, 30 Mar 2006 10:55, Han-Wen Nienhuys wrote:
Joe Neeman wrote:
I've just realised that I caused a regression for tremolos
on whole notes. I'll fix that today.
Please do.
Here we are:
2006-03-30 Joe Neeman [EMAIL PROTECTED]
* lily/stem-tremolo.cc (print): for whole notes
On Tue, 28 Mar 2006 14:39, Joshua Parmenter wrote:
This is described in Matt Stone's book Music Notation in the 20th
Century (not just 20th century music notation, but the practices of
notation in the 20th century):
The tremolo bars should be thinner than beams, and as long or a
little
On Tue, 28 Mar 2006 21:26, Joshua Parmenter wrote:
I'll do this tonight (when I'm home with my scanner).
Looking over some older scores, I definitely see examples like the
one sent earlier... but over 10 years of typesetting, most current
style sheets (if memory serves me correctly) specify
On Tue, 28 Mar 2006 23:41, Joshua Parmenter wrote:
Ignoring modern style sheets means not being able to type-set for
those companies. Which also means using Finale or Sibelius.
Or, perhaps this can be configurable. Maybe a stylesheet could be
loaded?
If you're new here, you may not realise
As far as I can tell, page and line penalties are used _only_ for forbidding
and forcing page breaks. Is there much chance they will ever be used for
anything else? If not, they could be replaced by booleans - this would make
the breaking algorithms a bit easier.
Also, there seems to be some
2006 06:44:59 -
@@ -1,3 +1,13 @@
+2006-03-28 Joe Neeman [EMAIL PROTECTED]
+
+ * lily/stem-tremolo.cc (raw_stencil): position
+ the tremolo depending only on the end of the stem
+ and not on the notehead
+ (print) idem
+
+ * lily/stem.cc (calc_stem_info): make sure the stem
+ is long enough to fit
On Tue, 28 Mar 2006 07:01, Joshua Parmenter wrote:
Shouldn't all tremolo lines be at the same angle (usually about 30
degrees)?
Sorry, I am new to the list, and am not sure where this thread
started. But in standard notation, this is not what usual tremolo
markings look like.
I started the
@@
+2006-03-08 Joe Neeman [EMAIL PROTECTED]
+ * lily/constrained-breaking.cc (get_max_systems): used to return a
+ much too big value
+ (combine_demerits): use pointers to reduce copying data
+ (calc_subproblem): idem
+ (get_page_penalty): add page turn penalties
+
2006-03-07 Han-Wen Nienhuys [EMAIL
On Sat, 11 Mar 2006 06:13 am, Han-Wen Nienhuys wrote:
Joe Neeman wrote:
This contains a bug-fix, an optimisation (been doing some profiling :))
and a
+ (combine_demerits): use pointers to reduce copying data
Are you sure about this? AFAIK references are internally handled in the
same
Han-Wen Nienhuys wrote:
Joe Neeman wrote:
OK, how about this one? It basically uses the original method, but
the engravers communicate by setting/reading properties in the Score
context (inspired by the guh. Use properties! comment).
it's probably wonderful, but can I see the patch first
Han-Wen Nienhuys wrote:
Joe Neeman wrote:
Is there a reason why breaks are on by default and the barline
engraver forbids them whenever there is no bar line? It seems simpler
for breaks to be off by default and to have Paper_column_engraver
acknowledge bar lines by setting the current
Han-Wen Nienhuys wrote:
Joe Neeman wrote:
Is there a reason why breaks are on by default and the barline
engraver forbids them whenever there is no bar line? It seems simpler
for breaks to be off by default and to have Paper_column_engraver
acknowledge bar lines by setting the current
Han-Wen Nienhuys wrote:
cool. I've added your patch, and it seems to work now !
Great! Any more issues, just yell. In the meantime, I might start
playing around with getting page-breaks to work automatically.
___
lilypond-devel mailing list
Han-Wen Nienhuys wrote:
Joe Neeman wrote:
There is a bug in do_solve (it calls get_solution with arguments in
the wrong order). It's supposed to print a programming error and
format it with 4 staves. But the use in paper-score is wrong, too.
Can you send a patch for it ?
Sorry, I lied
Hi,
I've put constrained breaking into CVS HEAD. Can you head over and
have a look?
I have the following remarks:
* vsize vs. int: casts should not be necessary. Can you use VPOS iso
-1 as a magic signaling value?
Sure.
* The specification uses A j, k, n and m as variables.
Werner LEMBERG wrote:
It is necessary that both the left and the right page are treated
as a pair, having the same number of bars. A good place for a page
break is a larger rest in either the left or right hand of one of
the two players.
Hopefully, the used algorithm can be prepared to handle
It is necessary that both the left and the right page are treated as a
pair, having the same number of bars. A good place for a page break
is a larger rest in either the left or right hand of one of the two
players.
Hopefully, the used algorithm can be prepared to handle this -- it's
not
Han-Wen Nienhuys wrote:
Joe Neeman wrote:
And maybe I should attach the patch too...
System *system = dynamic_castSystem * (clone (i));
- system-rank_ = i;
+ system-rank_ = broken_intos_.size ();
why this change?
So I can do
system-break_into_pieces (the first 5
Han-Wen Nienhuys wrote:
Joe Neeman wrote:
I've cleaned up most (all?) of the issues that you brought up with my
There's still some variable naming issues. I prefer not to postpone
those until the code is merged, because I tend to fix those asap, and
that makes it harder to sync your
I've cleaned up most (all?) of the issues that you brought up with my
previous code. I've moved some things around to improve readability and
I've addressed a few of the performance problems. Also, it is now
possible to force (or prevent) starting on the right hand page by using
And maybe I should attach the patch too...
Joe Neeman wrote:
I've cleaned up most (all?) of the issues that you brought up with my
previous code. I've moved some things around to improve readability
and I've addressed a few of the performance problems. Also, it is now
possible to force
The problem with this is that having a huge bonus effectively forces
a page break. I set allowPageTurn to have a penalty of -1 because I
don't
Sorry, I misunderstood you; I gathered that allowPageTurn was a
hard-coded obligatory break.
I still support \pageBreak and \noPageBreak for
Joe Neeman wrote:
Han-Wen Nienhuys wrote:
have a look at Paper_book::get_system_specs() in CVS HEAD. Can you
use this?
Sure can, thanks :)
... except that you made it private ;)
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http
Han-Wen Nienhuys wrote:
Joe Neeman wrote:
I'm just worried that the algorithm will have to deal with scores
that have almost no viable breaks. Either we allow breaks at
practically every rest (with huge penalties) or we don't have enough
break points. The first solution will have very poor
I doubt whethre this is convenient. Since this isn't related to the
page size, i think it's easier to use staff-space here, eg. a normal
staff is 4 spaces high,
system-height = #4
Shouldn't this be something like 8 by default? It should approximate the
stencil height of the staff and I
Han-Wen Nienhuys wrote:
[I'm taking the liberty of CC-ing the devel list.]
Joe Neeman wrote:
If I understand corrrectly, your page breaker tries to put
everything on one page by unless you say \allowPageBreak, which does
not seem like a sensible default.
Two pages, actually, but yes. I
Han-Wen Nienhuys wrote:
have a look at Paper_book::get_system_specs() in CVS HEAD. Can you
use this?
Sure can, thanks :)
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Yes, I think that might be possible without too much work. Maybe we
could allow the user to specify a global page-break-system-extent. We
then do the page breaking assuming all music systems have that
Y-extent. For 95% of the music I would use this for, that would be
acceptable since
Han-Wen Nienhuys wrote:
Joe Neeman wrote:
Come to think of it, wouldn't it also be easy to make a
Constrained_page_breaker, ie. a page-breaking routine that is
constrained to put the final result in X pages? That still wouldn't
be an optimal solution to the complete problem, but it would
Jose-Luc Hopital wrote:
I'm used to work this way: once a score is completely
keyed , i estimate the ideal number of pages for legibility,
turns , occupation of pages. Next i try different values
with set-global-staff-size until I obtain this number.
First of all, i recommend playing with
Han-Wen Nienhuys wrote:
I don't understand; how do you use line breaking in the page-breaker?
Within the current architecture, the vertical formatting step is non
reversible, so you can't really figure out the height of one
line-break configuration (which requires vertical formatting), and
Stephen wrote:
I believe revert- works like every other revert and only reverts a
previous override, restoring the default, not reverting the default
itself. After all, revert means to go back to a previous state, not to
establish a state.
I think the confusing thing here (for me at least)
501 - 596 of 596 matches
Mail list logo
