lilypond-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Lilypond developing: getting started


From: Han-Wen Nienhuys
Subject: Re: Lilypond developing: getting started
Date: Sat, 27 May 2006 01:28:25 +0200
User-agent: Thunderbird 1.5.0.2 (X11/20060501)

Kieren Richard MacMillan schreef:
Right now, I'm finishing up a big commission (a chamber opera), and have two more coming down the pipe. However, I would like to start in to helping the Lilypond codebase in any way I can, immediately upon completing the current score (should be in about two weeks).

In order to prepare for that, I have a few preliminary questions...  =)

1. How much of the code is in C++, and how much in Scheme? Does the roadmap see this balance changing in any way, and if so in what direction? [n.b. I have very little experience with either C++ or Scheme specifically.]

Most of the code still is C++, but it uses Scheme heavily for infrastructure. In terms of line count, it's 80% C++ and 20% Scheme, but Scheme is much more compact than C++. C++ will probably be more familiar for someone with Java experience.

2. Consequently, can I get away with learning one or the other, and if so which one would you prefer I learn? In other words, where would my


learning curve best be applied, given the needs of Lilypond development over the next few months (and possibly years)?.

I don't know what will happen with Lily development, we don't have a plan :)

3. I would probably also be willing to take on the Newsletter Editor position (but I do want to roll up my sleeves and actually do some bit-pushing as well) -- is there an opportunity for me to start to learn some of the internal workings of Lilypond as a result of "editing the newsletter"?

I think it's not really the best task to get acquainted with the internals.

However, if you want to learn, it's easier to start with a goal, and start to work from there. For example, there is currently a nasty backlog of bugreports. You could try your hand at fixing a simple bug. That's often a good way to learn your way around the code as well.

Also, there is still a lot of work to be done on the website (which is python based ATM), and probably a lot less intimidating than LilyPond. Pedro Kroeger recently studied the source code, he might also be able to give you pointers.

--

Han-Wen Nienhuys - address@hidden - http://www.xs4all.nl/~hanwen

LilyPond Software Design
 -- Code for Music Notation
http://www.lilypond-design.com





reply via email to

[Prev in Thread] Current Thread [Next in Thread]