NAME

Meta::Tool::Lilypond - take care of running Lilypond for you.

COPYRIGHT

Copyright (C) 2001, 2002 Mark Veltzer; All rights reserved.

LICENSE

This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version.

This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.

You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111, USA.

DETAILS

        MANIFEST: Lilypond.pm
        PROJECT: meta
        VERSION: 0.15

SYNOPSIS

        package foo;
        use Meta::Tool::Lilypond qw();
        my($object)=Meta::Tool::Lilypond->new();
        my($result)=$object->method();

DESCRIPTION

This tool handles all Lilypond stuff in the baseline. It does the following: 1. checks lilypond sources. 2. converts lilypond sources to various formats: midi,tex,ps,dvi. 3. extracts dependency information from lilypond sources. This assumes usage of lilypond 1.4.3 or higher and compatible (as far as command line interaction) versions. Mind you, that 1.2/3 versions will not work as the command line interface was changed and the actual source format for lilypond has changed.

We are using two lilypond supplied command line tools to do what we do here: lilypond and ly2dvi.

There are a couple of problems with running lilypond: 1. the --output switch doesnt work. it still creates the output in the current directory and not in the specified file. 2. it leaves junk behind. because of these reasons we surround lilypond with a protective shield (temp dir, moving of target etc...). 3. Its postscript backend produces postscript files which dont contain the fonts (i.e. bad postscript). On the other hand, the dvi output is good so if you convert lilypond to dvi and then use dvips to convert to postscript the results are good.

There are two problems with just running ly2dvi: 1. it leaves the midi file behind. 2. it adds the suffix .dvi to your specification of the output file. because of these reasons we surround ly2dvi with a protective shield (temp dir, moving of target etc...).

Please also read the instructions I have about installing lilypond (there are some font issues there...).

Also note that the order of arguments to lilypond is crutial (the source should be the last one).

Another funny thing is that ly2dvi adds a ".dvi" suffix to whatever file you want it to create.

FUNCTIONS

        c2chec($)
        c2midi($)
        c2texx($)
        c2psxx($)
        c2dvix($)
        c2deps($)
        myfile($$)
        get_att($$)
        TEST($)

FUNCTION DOCUMENTATION

c2chec($)

This routine verifies the lilypond source. Currently it does nothing. This method returns an error code.

c2midi($)

This routine will convert lilypond files to midi files. This method returns an error code.

c2texx($)

This routine will convert lilypond files to tex. This method returns an error code. This methdd remove the extra midi file which gets created in the process.

c2psxx($)

This routine will convert lilypond files to Postscript. This method returns an error code. This methdd remove the extra midi file which gets created in the process.

c2dvix($)

This routine will convert lilypond files to Dvi format. This method returns an error code. In this method, unlike the previous ones, we use the ly2dvi executable rather than the lilypond executable which seems to crash when asked to create a dvi output. The original lilypond version is remarked. The reason that we use the long version here is because ly2dvi adds a ".dvi" suffix to its output.

c2deps($)

This method will convert lilypond source files to dependency listings. This method currently does nothing. This method returns an error code.

my_file($$)

This method will return true if the file received should be handled by this module.

get_att($$)

This method will return the attribute sepecifed from the header of the lilypond file provided in the first argument.

TEST($)

Test suite for this module.

SUPER CLASSES

None.

BUGS

None.

AUTHOR

        Name: Mark Veltzer
        Email: mailto:veltzer@cpan.org
        WWW: http://www.veltzer.org
        CPAN id: VELTZER

HISTORY

        0.00 MV pics with db support
        0.01 MV spelling and papers
        0.02 MV perl packaging
        0.03 MV BuildInfo object change
        0.04 MV data sets
        0.05 MV md5 project
        0.06 MV database
        0.07 MV perl module versions in files
        0.08 MV movies and small fixes
        0.09 MV thumbnail user interface
        0.10 MV more thumbnail issues
        0.11 MV website construction
        0.12 MV web site development
        0.13 MV web site automation
        0.14 MV SEE ALSO section fix
        0.15 MV md5 issues

SEE ALSO

Meta::Baseline::Utils(3), Meta::Utils::Chdir(3), Meta::Utils::Env(3), Meta::Utils::File::Move(3), Meta::Utils::File::Patho(3), Meta::Utils::File::Remove(3), Meta::Utils::File::Symlink(3), Meta::Utils::Output(3), Meta::Utils::Utils(3), strict(3)

TODO

-do actual dependency calculations for lilypond source files (either with my own parser or use the lilypond parser - or both...)

-do actual checking of lilypond sources (my own parser since lilypond doesnt provide things like that...).

-stop doing all those setenvs to LD_LIBRARY_PATH - now it's NECCESSARY but I haven't figured out why...

cpanm Meta::Init

perl -MCPAN -e shell
install Meta::Init