I would like to make the following proposal for the binary
distribution of the Windows NT version of lilypond.

PROPOSAL
-------

1. I propose to distribute the enclosed version rooted directory
   structure.  This structure enables for efficient distribution, easy
   installation, and the additional capability of installing and
   running multiple versions.  With a minor addition, a platform
   specific hierarchy to bin like cygwin32 or whatever, would enable
   multiple platforms per version.

2. I propose a python version of ly2dvi called ly2dvi32.py.  This will
   allow Window's folks to generate music with titles and the like.
   This assumes the presence of Python.  I do not believe that this is
   much of a problem due to the plug-and-play nature of Python's
   download and installation on Windows.

3. Initially this distribution would be a zip file.  The installation
   should require an unzip with little to no post installation steps
   other than setting the path variable.

4. Eventually I would like to see an InstallShield like installation
   interface.  I have searched for a freeware version of such a thing
   and have not been successful.  

ISSUES
------

1. Hard coded lilypond search path does not suit relocation of
   the binary.  

   o ly2dvi32.py will handle this thru the use of argv[0].
   o We could make lilypond's internal search path use argv[0] as a
     seed to the internal search path.
   o The LILYINCLUDE environment variable can be leveraged.
 
2. Internationalization.  Being a bone headed American, I don't know
   if this is an issue or not.  I assume the internationalization code
   in gettext keys off of environment variables.

3. Search path separation in Windows is ';' not ':'.  

   o I believe I remember seeing a cpp macro in the flower lib for the
     search path separation character.

4. Environment variables.  Not being an experienced NT user I don't
   know if this is an issue or not.  Many programs seem to set values
   in the registry during the post installation process.  I'm not so
   crazy about this however.

5. I presently can not generate the web documentation due to my
   inability to find command line graphic translators for the Windows
   NT platform.  
  
   o Any suggestions for pstogif etc. on windows?
   o Download the html tree from the lilypond distrubution site.
   o Build doco on UNIX box

CONCLUSION
----------

I have a rough draft of python32.py that I have been using.  And with
the blessing of the major contributors, I would be willing to
distribute the proposed binary to anyone who is interested.

Please feel free to comment.

DIRECTORY STRUCTURE
-------------------

lilypond-1.0.1
|
+---bin
|    convert-mudela
|    cygwinb19.dll
|    lilypond.exe
|    ly2dvi32.py
|    mi2mu.exe
|    mudela-book
|       
+---doc
|    web-doco
|           
+---share
|   +---lilypond
|   |    a4.ly
|   |    bar-numbering.ly
|   |    book-fragment.ly
|   |    book-init.ly
|   |    center-fragment.ly
|   |    center.ly
|   |    declarations.ly
|   |         .
|   |         .
|   |         .
|   |       
|   +---locale
|       +---it
|       |   +---LC_MESSAGES
|       |        lilypond.mo
|       |           
|       +---nl
|           +---LC_MESSAGES
|                lilypond.mo
|                   
+---texmf
    +---mf
    |   +---public
    |       +---lilypond
    |            feta-autometric.mf
    |            feta-banier.mf
    |            feta-beugel.mf
    |            feta-beum.mf
    |            feta-black16.mf
    |            feta-bolletjes.mf
    |            feta-braces16.mf
    |            feta-braces20.mf
    |            feta-brackets16.mf
    |                   .
    |                   .
    |                   .
    |               
    +---tex
        +---lilypond
             dyndefs.tex
             feta11.tex
             feta13.tex
             feta16.tex
             feta19.tex
             feta20.tex
             feta23.tex
                 .
                 .
                 .

Optimistically,

Jeffrey B. Reed

-- 
Jeffrey B. Reed
[EMAIL PROTECTED]

Reply via email to