> that the output filenames would be, lilypond.pdf, > I was hoping to just call it "lilypond". Reports), just like I did for LM and AU -) I'll create a stub for the essay (after having handled Patrcik's > - bibliography/ will be moving to essay/ once it exists. Will be enough pictures for moving them to a Documentation/pictures/,Ĭopying/converting them into Documentation/out-www/, so they end up inĭocumentation/ in the docball and thus will work without extra hacking As we're going to add some more pictures from web-gop, there This won't make the build any simpler, and I see no benefit for theĮditors. > and learning/ - although the latter will be essay/ as soon as > - could the png/eps files be moved to the relevant dirs (notation/ Unless we have more than 8 CSS files, I think it's not necessary. They are necessary mixed and interleaved, just like syntax and semanticsĪre often mixed in a language - could the css be moved to a separate dir? > mixture of mundane doc maintance stuff with the website Or at least make it a separate email, so we don't have a > but let's finish the purely doc-related stuff If you want to propose something else that what Iĭo, please specify with enough details, not saying "I thought that." > I think we misunderstood each other somewhere (with regards to Going to add generated PNGs of all examples in input/ and input/mutopia Run lily binary anyway, so let's benefit from this. Most of the future web site will be generated on a machine that has to There is no LilyPond binary that runs on, so that's fair > Again, just like the 10-20 pieces of lilypond output in the , and the rest of the web site will come from an upload ofĬompiled docs, or have you another plan in mind? Current web branch willīe trimmed to keep the minimal stuff that still needs to be built on Whatever, as this is completely unclear to me. What is this web repo you keep talking about? Please draw a picture or To build lilypond.tely, so it won't contain generated images, right? > all, and would only be present in the distinct web repo.Īs I understand it, the web repo won't contain stuff that is necessary In this case, they won't clutter up the main history at > need to be saved in the main repo we only need them in the web > Which I'm expecting to be once a year? These images also don't > This will make 704 Kb evey time the examples are updated. Page, but I think it should be reachable from the page by a link e.g. OK, the source shouldn't be shown by cliking on the PNG image on web The newbie-scaring goes in Text input, not Examples.Īnd what about curious people that want to easily look at the sources? > - we DO NOT want to show the input code. Han-Wen was sceptical about merging the web site into the main > but you and Han-Wen convinced me otherwise. > Yes, it's the opposite of what I originally suggested, This point I expect clearly defined proposals which aim at a complete Mostly point to stable branch docs, let's build the web site from stableīranch this quite clear, isn't it? I'm open to other proposals, but at To take too much risk by building the main web site examples from masterīranch, and as links from the main web site to the documentation will The uploaded website is the generated website as it's generated, itĭoesn't need nor deserve to be stored in a version control system, it > I thought we were keeping the uploaded-website on a separate Le lundi 27 juillet 2009 à 01:17 -0700, Graham Percival a écrit : Re: Directory structure for docs and web site Re: Directory structure for docs and web site lilypond-devel
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |