As a way of learning my way around the code, I thought I'd work on some
of the things marked TODO. Here's the first one, a relatively trivial
patch inlining some functions.
By the way, is there a documentation tool in use for the C++ code? I
thought I might document some things as a way of le
Nicolas Sceaux writes:
> OK, of course. Even if the internals will change, the interface, which
> is still simple, can be documented. I'm beginning a draft.
Good.
> a possible explanation for NEWS.texi:
Ok, please install this.
Jan.
--
Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - T
> a possible explanation for NEWS.texi:
>
>* LilyPond expressions can be embedded into Scheme, thanks to the
> `#{ ... #}' syntax. Within such a block, Scheme forms, for
> instance variable names, can be introduced thanks to a `$'
> character (`$$' has to be used to issue a sing
Sun, 25 Apr 2004 21:55:23 +0200, Jan a dit :
> Looks good. When you feel this has fleshed out, there should be some
> documentation (but I'm still `waiting' for the \book stuff to
> stabilize before writing real documentation, eg).
OK, of course. Even if the internals will change, the interf
Hi,
I'm reading again the manual and it has really improved! Congrats!
This is a list of small corrections and suggestions:
introduction.itely cvs 1.97
=
l. 494:
"Score context" has no definition. would be nice to have, since
"Staff Context" and "Voice Context" h
> > Just an idea, you're the meister.
>
> :) Discussion is good. My goal is to minimise my own work while not
> increasing
> your work; please feel free to tell me whenever I don't succeed in
> doing the
> latter.
>
> Erik
A bit of feedback:
Style: Take a look at files in input/regression/*.l
Erik Sandberg writes:
> My thought with the initial naming was to create something minimal
Yes, minimal is good.
> About priority: I like your suggestion, but I would like to add the current
> "important" between normal and regression (& I realise that the currently
> "critical" bugs should be
On Friday 23 April 2004 11.03, Jan Nieuwenhuizen wrote:
> May I suggest to adopt a bit more bugzilla like naming (eg,
> http://bugzilla.gnome.org/bug_status.html), possibly with adaptation,
> it does not need to be as full blown, ie something like:
>
> priority (high to low): crash/critical, regr
