Re: [frogs] joining the team

["Trevor Daniels" <t.daniels@xxxxxxxxxxx>]

William Bajzek wrote Tuesday, August 10, 2010 5:17 PM
> On Aug 8, 2010, at 12:09 PM, Trevor Daniels wrote:
> > The first step is to work through CG 2.1 and send me a test
> > patch set.  Anything will do, but we may as start with one of
> > the web css's.  When you have the source available navigate to
> > Documentation/css, make a trivial change to lilypond.css
> > (anything will do for a test - "WB woz 'ere" for example)
> > save it, and send me a patch set.  When you've done that
> > successfully we can go on to something more concrete.
>
>
> Here is a test patch:
> http://dl.dropbox.com/u/597433/lilypatch/0001-Test-patch.patch

Great!  It looks perfect, and applies cleanly.

We can get down to business - on to 1105.

I've updated 1105 to "started" and indicated you're
looking into it.  I'll help, but I'm just learning how
the web build works myself, so we'll learn together.

Here's what Patrick McCarty told me:

> The file "lilypond-mccarty.css" is used for the docs 
> (everything except the website), and "lilypond-web.css" 
> is used for the website.
>
> There is quite a bit of overlap between the two CSS files, 
> and as Graham mentioned, combining them into one CSS file 
> would be an ideal solution.

I'm not sure yet whether we can combine the two css files.
The first step is to order them in the same way so we can
compare them.  I suggest you use lilypond-mccarty.css as
the model and recast lilypond-web.css the same way, without
introducing any functional changes.  You can do this in
sections, sending me patches as you go, or all at once,
but I suggest smallish sections to begin with.

You'll need to test your changes before you send me the
patch.  You can do this by editing the lilypond-web.css
file in 
.../lilypond-git/out-www/offline-root/Documentation/
while looking at the html starting at
...lilypond-git/out-www/offline-root/Documentation/web/index.html
Changes to that css file will show up immediately, although
for this first task there shouldn't be any :) (you might try
an obvious change which you later revert to reassure 
yourself everything is working as intended.)

When you're ready to submit a patch you'll need to copy the
changed css file into
.../lilypond-git/Documentation/css/
overwriting the old lilypond-web.css file, and generate a
patch.

That sounds a little mundane, so if you spot anything you
think could be improved as you go please suggest it.

> - William Bajzek

Trevor



---
----
Join the Frogs!