-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello
On 18/07/15 18:47, David Kastrup wrote:
> Benkő Pál writes:
>
>> 2015-07-18 17:57 GMT+02:00 Federico Bruni :
>>> What do you think about these instructions?
>>> http://lilypond.org/doc/v2.19/Documentation/contributor/pushing-to-staging
>>>
>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 18/07/15 18:05, Federico Bruni wrote:
> Il giorno sab 18 lug 2015 alle 18:33, Benkő Pál
> ha scritto:
>>> 3. I don't like much the `git merge` approach suggested for
>>> those who work with local branches, as the git log is a bit
>>> messed up (a m
> Quoting myself, "tool for the website only" seems pretty clear:
Not at all. The `website' is *everything* addressed by lilypond.org.
You are talking about the top-level page only, I now suppose.
Werner
___
lilypond-devel mailing list
lilypond-
> There will be a pressing need to move to texi2any quite soon,
> otherwise LilyPond may be removed from the distro repository.
Well, having guile 2.0 is *far* more important! And only David is
working on this... Here, I not only have no time, but I also don't
have any knowledge :-(
Werner
Am 19.07.2015 um 07:26 schrieb Werner LEMBERG:
> As a preliminary I want to mention that in general I can imagine that
> we separate the top-level entry page of lilypond.org from the texinfo
> system. Somewhere we could have a `doc' subdirectory, and from there
> on everything is generated with
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 19/07/15 07:25, Federico Bruni wrote:
> Werner, I'm skipping your replies where you were implying that I
> was proposing to change the whole documentation system and not just
> the website.
>
> etc.
OK so after all that, what can we do *today* to
Federico Bruni writes:
> texi2html is deprecated since 2011. It's still present in most
> distributions but I guess that it won't be there forever. For example,
> in Debian:
> https://wiki.debian.org/Texi2htmlTransition
> https://lists.debian.org/debian-devel/2013/05/msg01516.html
>
> There will
Werner LEMBERG writes:
> As a preliminary I want to mention that in general I can imagine that
> we separate the top-level entry page of lilypond.org from the texinfo
> system. Somewhere we could have a `doc' subdirectory, and from there
> on everything is generated with texinfo as usual.
>
>> I
Il giorno dom 19 lug 2015 alle 9:40, James Lowe ha
scritto:
OK so after all that, what can we do *today* to improve what the front
page of the website looks like *now* without (for now) worrying about
CSS and using different web tools and fretting over things that have
not yet happened; but sinp
Hi,
Am 19.07.2015 um 09:21 schrieb David Kastrup:
> That nobody ever bothered to do so in all those
> years is one indicator that there is not much overlap between people
> wanting to use LilyPond and people wanting to use Markdown.
I am one of this (perhaps small) intersection between Markdown a
Il giorno dom 19 lug 2015 alle 10:14, Federico Bruni
ha scritto:
Il giorno dom 19 lug 2015 alle 9:40, James Lowe ha
scritto:
OK so after all that, what can we do *today* to improve what the
front
page of the website looks like *now* without (for now) worrying about
CSS and using different web
James Lowe writes:
> On 19/07/15 07:25, Federico Bruni wrote:
>> Werner, I'm skipping your replies where you were implying that I
>> was proposing to change the whole documentation system and not just
>> the website.
>>
>> etc.
>
> OK so after all that, what can we do *today* to improve what the
Le 19/07/2015 08:25, Federico Bruni a écrit :
[…]
2. We still depend on texi2html and the help request by
Jean-Charles, who tried moving to texi2any, not surprisingly was
ignored:
http://lists.gnu.org/archive/html/lilypond-devel/2015-05/msg00032.html
[Werner]
The `non surprisingly' is p
Joram writes:
> Hi,
>
> Am 19.07.2015 um 09:21 schrieb David Kastrup:
>> That nobody ever bothered to do so in all those
>> years is one indicator that there is not much overlap between people
>> wanting to use LilyPond and people wanting to use Markdown.
>
> I am one of this (perhaps small) inte
Jean-Charles Malahieude writes:
> Le 19/07/2015 08:25, Federico Bruni a écrit :
>>
>> texi2html is deprecated since 2011. It's still present in most
>> distributions but I guess that it won't be there forever. For example,
>> in Debian:
>> https://wiki.debian.org/Texi2htmlTransition
>> https://li
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Federico,
On 19/07/15 09:25, Federico Bruni wrote:
> Il giorno dom 19 lug 2015 alle 10:14, Federico Bruni
> ha scritto:
>> Il giorno dom 19 lug 2015 alle 9:40, James Lowe ha
>> scritto:
>>> OK so after all that, what can we do *today* to improve w
Il giorno dom 19 lug 2015 alle 10:46, James Lowe ha
scritto:
You have just proved my point.
I said:
... OK so after all that, what can we do *today* to improve what the
front page of the website looks like *now* without (for now) worrying
about CSS ...
I.e just content. Moving existing inform
Il giorno dom 19 lug 2015 alle 10:14, Federico Bruni
ha scritto:
a slider of examples, instead of a long list (as the current examples
page), would be nice but it requires more work on CSS
I just made a nice simple slider (few lines of CSS) by following this
tutorial:
http://demosthenes.info
Federico Bruni writes:
> Il giorno dom 19 lug 2015 alle 10:14, Federico Bruni
> ha scritto:
>> a slider of examples, instead of a long list (as the current
>> examples page), would be nice but it requires more work on CSS
>
> I just made a nice simple slider (few lines of CSS) by following this
Il giorno dom 19 lug 2015 alle 11:44, David Kastrup ha
scritto:
If I understand correctly, one point of CSS should be graceful
degradation: if your browser does not support something, the content
will just get displayed like without the CSS.
The graceful degradation would require some externa
Federico Bruni writes:
> Il giorno dom 19 lug 2015 alle 11:44, David Kastrup ha
> scritto:
>> If I understand correctly, one point of CSS should be graceful
>> degradation: if your browser does not support something, the content
>> will just get displayed like without the CSS.
>>
>
> The gracefu
Il giorno dom 19 lug 2015 alle 12:43, David Kastrup ha
scritto:
The graceful degradation would require some external javascript
library like jquery...
Seriously? That would be another unexpected dollar in my "can
standard
committee engineers really be that stupid" account. I really hope
Hi David,
Am 19.07.2015 um 10:37 schrieb David Kastrup:
> Is this something we should try integrating with lilypond-book?
I basically tried to reproduce lilypond-book on markdown for my
purposes. So before the usual md -> html conversion is done, the ly
snippet is compiled by lilypond and replace
Federico Bruni writes:
> Il giorno dom 19 lug 2015 alle 12:43, David Kastrup ha
> scritto:
>>> The graceful degradation would require some external javascript
>>> library like jquery...
>>
>> Seriously? That would be another unexpected dollar in my "can
>> standard
>> committee engineers real
Il giorno dom 19 lug 2015 alle 14:02, David Kastrup ha
scritto:
I was talking about "use CSS3 features as long as the behavior when
those are not supported still makes sense".
it wouldn't make sense
I guess that you would see just the first image of the slider, there
would be no transition to
Joram writes:
> Am 19.07.2015 um 10:37 schrieb David Kastrup:
>
>> I seem to remember that Henning similarly did some LilyPond
>> integration into Context and don't think that this is general
>> knowledge.
>
> This means compared to lilypond-book, one only has to compile it once
> with context an
Federico Bruni writes:
> Il giorno dom 19 lug 2015 alle 14:02, David Kastrup ha
> scritto:
>> I was talking about "use CSS3 features as long as the behavior when
>> those are not supported still makes sense".
>
> it wouldn't make sense
> I guess that you would see just the first image of the sli
> On Jul 19, 2015, at 4:14 AM, Federico Bruni wrote:
>
> a slider of examples, instead of a long list (as the current examples page),
> would be nice but it requires more work on CSS
It’s worth mentioning that there are a lot of web designers who think that
sliders / carousels are not a good i
Federico Bruni writes:
> Il giorno dom 19 lug 2015 alle 14:31, David Kastrup ha
> scritto:
>> Federico Bruni writes:
>>
>>> Il giorno dom 19 lug 2015 alle 14:02, David Kastrup ha
>>> scritto:
I was talking about "use CSS3 features as long as the behavior when
those are not suppor
Il giorno dom 19 lug 2015 alle 16:22, David Kastrup ha
scritto:
Tell you what: I'm probably the Nineties user. That GIF annoys me
because it does not allow me to look at stuff as long as I need. I'd
probably have a similar problem with a "Slider" (which presumably adds
animation to the image f
Federico Bruni writes:
> Il giorno dom 19 lug 2015 alle 16:22, David Kastrup ha
> scritto:
>> Tell you what: I'm probably the Nineties user. That GIF annoys me
>> because it does not allow me to look at stuff as long as I need. I'd
>> probably have a similar problem with a "Slider" (which pres
Il giorno dom 19 lug 2015 alle 16:42, David Kastrup ha
scritto:
We can just display a small gallery. You can click to show the
respective image in a frame, and if JavaScript is available, this can
be
done on hovering over the thumb. That leaves the control with the
user
and will not be usel
Add weight to your opinions by showing that you're not afraid of
getting your hands dirty.
texi2html is a vital part of the documentation. It's currently
used for the website as well, but that is almost incidental to its
use for the rest of the documentation.
https://code.google.com/p/lilypond/is
d...@gnu.org wrote Saturday, July 18, 2015 11:02 PM
> One thing that you have to be aware of is that
> #{ \music #}
> is not equivalent to music but rather to
> (ly:music-deep-copy music (*location*))
> since it creates a copy of the music and puts the point-and-click
> information to the call o
Thanks David
https://codereview.appspot.com/253310043/diff/1/ly/staff-tkit.ly
File ly/staff-tkit.ly (right):
https://codereview.appspot.com/253310043/diff/1/ly/staff-tkit.ly#newcode60
ly/staff-tkit.ly:60: #(if dynUp
On 2015/07/18 22:02:54, dak wrote:
elseif cascades are bad to read in Scheme's
Trevor Daniels writes:
> d...@gnu.org wrote Saturday, July 18, 2015 11:02 PM
>
>
>> One thing that you have to be aware of is that
>> #{ \music #}
>> is not equivalent to music but rather to
>> (ly:music-deep-copy music (*location*))
>> since it creates a copy of the music and puts the point-and-
https://codereview.appspot.com/255280043/diff/1/Documentation/usage/external.itely
File Documentation/usage/external.itely (right):
https://codereview.appspot.com/255280043/diff/1/Documentation/usage/external.itely#newcode726
Documentation/usage/external.itely:726: OpenOffice.org extension that
https://codereview.appspot.com/250530043/diff/1/Documentation/notation/repeats.itely
File Documentation/notation/repeats.itely (right):
https://codereview.appspot.com/250530043/diff/1/Documentation/notation/repeats.itely#newcode764
Documentation/notation/repeats.itely:764: @knownissues
@knowniss
On 2015/07/19 18:43:33, Trevor Daniels wrote:
https://codereview.appspot.com/255280043/diff/1/Documentation/usage/external.itely
File Documentation/usage/external.itely (right):
https://codereview.appspot.com/255280043/diff/1/Documentation/usage/external.itely#newcode726
Documentation/usage/
https://codereview.appspot.com/250530043/diff/1/Documentation/notation/repeats.itely
File Documentation/notation/repeats.itely (right):
https://codereview.appspot.com/250530043/diff/1/Documentation/notation/repeats.itely#newcode769
Documentation/notation/repeats.itely:769: @q{timing track}.
Expe
Reviewers: Trevor Daniels, dak,
Message:
On 2015/07/19 18:56:10, Trevor Daniels wrote:
https://codereview.appspot.com/250530043/diff/1/Documentation/notation/repeats.itely
File Documentation/notation/repeats.itely (right):
https://codereview.appspot.com/250530043/diff/1/Documentation/notatio
hang on, let me try one more time.
:/
https://codereview.appspot.com/250530043/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
https://codereview.appspot.com/250530043/diff/1/Documentation/notation/repeats.itely
File Documentation/notation/repeats.itely (right):
https://codereview.appspot.com/250530043/diff/1/Documentation/notation/repeats.itely#newcode764
Documentation/notation/repeats.itely:764: @knownissues
On 2015/0
On 2015/07/19 19:35:56, J_lowe wrote:
https://codereview.appspot.com/250530043/diff/1/Documentation/notation/repeats.itely
File Documentation/notation/repeats.itely (right):
https://codereview.appspot.com/250530043/diff/1/Documentation/notation/repeats.itely#newcode764
Documentation/notation
Am 2015-07-19 um 17:36 schrieb Joram :
>> I seem to remember that Henning similarly did some LilyPond integration
>> into Context and don't think that this is general knowledge.
>
> This means compared to lilypond-book, one only has to compile it once
> with context and not in two steps? That sou
Am 2015-07-19 um 14:37 schrieb David Kastrup :
> I seem to remember that Henning similarly did some LilyPond integration
> into Context and don't think that this is general knowledge.
Probably not, but ConTeXt at all is not really general knowledge ;)
But users who manage the learning curve of L
46 matches
Mail list logo
