Andrew Yoon <andrewyo...@gmail.com> writes: > There are certainly many options to explore, many of them quite simple. At > any rate, over the next few days I'll take a crack at something and see > what people think. Should future discussions about this belong in the dev > mailing list? Apologies if this is the wrong place...
Well, yes and no. The developer list is the right place to discuss implementation and extensions of LilyPond and "how to do $x". This may lead to getting feedback from the user list, of course. When we are talking about what amounts to changes in the CSS for mere appearances' sakes, the "how" question is pretty much already answered. We are not really talking about any extension of functionality (yet?). I'm not sure all developers read the user list, however. But I also am not sure how many of those not reading the user list care about the appearance of the web page, either. I haven't seen any proposals for _technical_ changes yet: those may well see a veto from developers for technical reasons. As long as the main topic is the question of style (rather than concrete frame works and stuff), I don't see much potential for wasted work when an actual proposal (which needs to go through the developer resources anyway) is placed on the table only to get "oh, we can't do it in this way because of $SERVER, $FRAMEWORK, $ACCESSIBILITY, $SECURITY, $WEBSTANDARDS". -- David Kastrup _______________________________________________ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
