Re: Re: Lilypond Architectural Overview Request

[jim . showalter]

Mike,

Thanks for the info.  I am about to go on vacation so I will have more time to look into this stuff in depth.

Regarding Graham's comment, my question was certainly not a complaint but an observation (and one which may have been that I was looking in the wrong places).  As to asking questions on the mailing list, after many years of participating in mailing list exchanges II have been conditioned to do at least attempt a thorough search before posting.  That can take a lot of time so I figure my time would best be spent understanding how the system functions by reading the appropriate documentation (before asking too many questions).  And that is what lead to my question about the overall system architecture.

Thanks!
Jim



Aug 4, 2010 04:09:25 AM, address@hidden wrote:
> >Hey Jim,
> >    I've recently started to ask (and am still asking) similar questions
> >about how Lilypond is put together.
> >    I think that the graphviz functionality in the link Graham provided is
> >excellent and quite helpful.
> >    Otherwise, git grep is your best friend.  Usually, I use it to:
> >
> >1)  Find a music function that creates some sort of event in ly.
> >2)  Find the engraver that handles this event in lily.
> >3)  Find the grob(s) that this engraver makes in scm.
> >4)  Look at all of said grobs' properties and callbacks, which may be in 
> >scm
> >or lily.
> >
> >The most pedagogically useful thing I've done so far is to recreate the
> >TextSpanner verbatim as FoobarSpanner (not rewriting from the ground up, but
> >rather copying and pasting, which means looking in the right places).  Once
> >you get all of the information correct, you'll have understood a great deal
> >about the internal functionality.
> >
> >~Mike
> >
> >On 8/4/10 9:50 AM, "Graham Percival" <address@hidden> wrote:
> >
> >> On Tue, Aug 03, 2010 at 10:22:05PM -0400, jim.showalter wrote:
> >>> I have been reviewing the online manuals and am having trouble finding
> >>> documentation that describes the overall architecture of the Lilypond
> >>> system.
> >> 
> >> If you're looking at the 2.13 docs,
> >> http://lilypond.org/website/development.html
> >> then what info we have written down is in Extending and the
> >> programming section of the Contributor's Guide.  Both are on that
> >> page.
> >> 
> >> If you have a specific question, somebody might have a specific
> >> answer.  If you want to volunteer to write such a document, then
> >> let's talk.  If you want to complain that Extending doesn't
> >> explain a lot, then don't bother.
> >> 
> >> Cheers,
> >> - Graham
> >> 
> >> _______________________________________________
> >> lilypond-user mailing list
> >> address@hidden
> >> 
> >target="_blank">http://lists.gnu.org/mailman/listinfo/lilypond-user
> >> 
> >
> >
> >