On Thu, Jul 29, 2010 at 08:17:38PM +0200, Mike Solomon wrote:
> True that.
Please do not top-post.
> My three.5 concerns are:
> 1) said code cannot use non-public scheme functions (am I right in thinking
> that?).
I'm not certain about this.
> 2) changes to init.ly are not copied from one versi
True that.
My three.5 concerns are:
1) said code cannot use non-public scheme functions (am I right in thinking
that?).
2) changes to init.ly are not copied from one version of lilypond to the
next, nor are one person's "modules". I do my compiling from the git
repository, so I could likely rig s
On Wed, Jul 28, 2010 at 04:25:08PM +0200, Mike Solomon wrote:
> 1) A folder would be created in (ie PATH/lilypond/2.X.X/module) in which
> all modules hung out so that Lilypond knew to look there. Each module would
> have its own folder and could be internally organized however one fancies.
Kind
Mike Solomon writes:
> Understood. Does this modularity thing seem eventually includable in
> lilypond? I'm finishing a piece for October 1 and would like to be
> consistent about the way that I do the coding for my graphical
> notation: either it'll be done in my git repository or as a module.
Understood.
Does this modularity thing seem eventually includable in lilypond? I'm
finishing a piece for October 1 and would like to be consistent about the
way that I do the coding for my graphical notation: either it'll be done in
my git repository or as a module. Obviously I'd like not to have
On Wed, Jul 28, 2010 at 04:25:08PM +0200, Mike Solomon wrote:
> In doing this, I've realized that almost everything in Lilypond can be
> made modular, which is a testament to how well it is put together. David
> had suggested modularity as an option before (perhaps others as well), and
> there
Hey all,
I've almost finished moving my vector-graphic package into a module that
is usable by invoking one \include statement (it is in scheme code and .so
files importable by guile). I decided to do this because the generation of
vector graphics readable by my code uses too much kludgery to
