Re: Extend Whiteout property
2018-09-07 16:39 GMT+02:00 Lukas-Fabian Moser : > I took this as an intencive to take a stab at delving into the source code > (which I always did read-only up to now). I think I managed to create a > working branch from current master (I also never got the hang of git...) that > allows for [...] > > Is there a way that one of the more experienced developers might take a look > at what I produced at help me in getting it up to scratch? A look at what you did would be helpful. ;) Could you post a git formated patch? Or a diff? Cheers, Harm ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Extend Whiteout property
Hi Kieren, Well done. Does it also work with other whiteout styles (e.g., outline)? Not yet. Of course, "rounded-box" would be nice to have (and probably not too hard to implement). I expect "outline" would be more involved; tbh, I'm not quite certain what the precise meaning would be for that style, anyway. In any case, I haven't yet taken a look at how "outline" actually works. Best Lukas ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Extend Whiteout property
Am 07.09.2018 um 16:39 schrieb Lukas-Fabian Moser:
Dear Kieren,
Am 07.09.2018 um 15:24 schrieb Kieren MacMillan:
Hi Fox & folks,
I wonder if it is possible to extend in the X-direction the whiteout property
on a grob?
This is something I’ve been musing about for about six months now. There are
definitely situations where I want to have independent control of the
[thickness/extent of the] X- and Y- directions of the whiteout.
Looking forward to hearing any solutions offered (beyond the obvious markup
solution you posted).
I took this as an intencive to take a stab at delving into the source
code (which I always did read-only up to now). I think I managed to
create a working branch from current master (I also never got the hang
of git...) that allows for
\version "2.21"
\new Staff {
\override NoteHead.whiteout = #'(5 . 40) % Pair of X-thickness and
Y-thickness
g'4
r2
\override NoteHead.whiteout = #'(40 . 5)
g'4
}
producing
But, to be honest, I
a) am a bit ashamed because I certainly produced quite a mess in terms
of code quality (being a once-a-year programmer),
b) don't quite now how to proceed with it from now.
Is there a way that one of the more experienced developers might take
a look at what I produced at help me in getting it up to scratch?
I assume you won't get push access to the official Git repository on
Savannah too soon.
A significantly lower threshold is on the Github mirror
(https://github.com/lilypond/lilypond). This is only partially
up-to-date, but I have right now pushed the latest state of the master
and the staging branches, so they are in sync with the Savannah repository.
What you can do now is
* fork this repository
* register the fork and the main Github repository as "remotes" in
your local repository (I suggest to name them "github" and
"" if you have the Savannah repository
as "origin")
* create a branch for your path
* commit
* push to your fork
* create a Pull Request on Github
* tell us here about it because we won't be automatically notified
about it.
That way anyone can look at your code, and you should be able to refine
the code together with others.
At some point you may then do the required registrations and upload your
patch for review (as per LilyPond's Contributrs' Guide), or you may ask
someone else to "sheperd" your patch through the review process.
HTH
Urs
Best
Lukas
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Extend Whiteout property
Hi Lukas,
> I took this as an intencive to take a stab at delving into the source code
> (which I always did read-only up to now).
Nice!
> I think I managed to create a working branch from current master (I also
> never got the hang of git...)
Ugh… I have to do that someday, too.
> that allows for
>
> \version "2.21"
>
> \new Staff {
> \override NoteHead.whiteout = #'(5 . 40) % Pair of X-thickness and
> Y-thickness
> g'4
> r2
> \override NoteHead.whiteout = #'(40 . 5)
> g'4
> }
Well done. Does it also work with other whiteout styles (e.g., outline)?
> Is there a way that one of the more experienced developers might take a look
> at what I produced at help me in getting it up to scratch?
I hope so! I’ve copied this to -devel, just in case that helps get the word out.
Thanks,
Kieren.
Kieren MacMillan, composer
‣ website: www.kierenmacmillan.info
‣ email: i...@kierenmacmillan.info
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Extend Whiteout property
Dear Kieren,
Am 07.09.2018 um 15:24 schrieb Kieren MacMillan:
Hi Fox & folks,
I wonder if it is possible to extend in the X-direction the whiteout property
on a grob?
This is something I’ve been musing about for about six months now. There are
definitely situations where I want to have independent control of the
[thickness/extent of the] X- and Y- directions of the whiteout.
Looking forward to hearing any solutions offered (beyond the obvious markup
solution you posted).
I took this as an intencive to take a stab at delving into the source
code (which I always did read-only up to now). I think I managed to
create a working branch from current master (I also never got the hang
of git...) that allows for
\version "2.21"
\new Staff {
\override NoteHead.whiteout = #'(5 . 40) % Pair of X-thickness and
Y-thickness
g'4
r2
\override NoteHead.whiteout = #'(40 . 5)
g'4
}
producing
But, to be honest, I
a) am a bit ashamed because I certainly produced quite a mess in terms
of code quality (being a once-a-year programmer),
b) don't quite now how to proceed with it from now.
Is there a way that one of the more experienced developers might take a
look at what I produced at help me in getting it up to scratch?
Best
Lukas
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Extend Whiteout property
Hi Fox & folks, > I wonder if it is possible to extend in the X-direction the whiteout property > on a grob? This is something I’ve been musing about for about six months now. There are definitely situations where I want to have independent control of the [thickness/extent of the] X- and Y- directions of the whiteout. Looking forward to hearing any solutions offered (beyond the obvious markup solution you posted). Best, Kieren. Kieren MacMillan, composer ‣ website: www.kierenmacmillan.info ‣ email: i...@kierenmacmillan.info ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lilypond website down?
Han-Wen Nienhuys writes: > On Wed, Sep 5, 2018 at 2:24 PM Simon Albrecht wrote: >> >> On 16.08.2018 23:37, Han-Wen Nienhuys wrote: >> > Well, currently, it's coming out of the $300 new user credit that >> > Google offers to new cloud users. $300 is enough to keep it running >> > for a year or two. >> >> This sounds slightly dangerous and like we should search for a new >> solution rather sooner than later, doesn’t it? > > When the free credit runs out, costs will be paid from my credit card. What's the bus factor on the current solution? Not regarding the money but the actions to be taken? -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lilypond website down?
On Wed, Sep 5, 2018 at 2:24 PM Simon Albrecht wrote: > > On 16.08.2018 23:37, Han-Wen Nienhuys wrote: > > Well, currently, it's coming out of the $300 new user credit that > > Google offers to new cloud users. $300 is enough to keep it running > > for a year or two. > > This sounds slightly dangerous and like we should search for a new > solution rather sooner than later, doesn’t it? When the free credit runs out, costs will be paid from my credit card. -- Han-Wen Nienhuys - hanw...@gmail.com - http://www.xs4all.nl/~hanwen ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Frescobaldi testing requested
Am 06.09.2018 um 21:10 schrieb Partitura Organum: This is not what happens for me. Could you specify the OS/distribution you're running? And maybe provide a screenshot of the dialog. I could imagine that some combination of options would be able to produce unwanted behaviour. I'm running it on Windows. Here's a screenshot of the dialog. ... I doesn't matter which option I choose, PDF, PNG, SVG or some of the other options. Starting Lilypond results in nothing. The dialog disappears and that's it. When I run it on Linux, it works as expected. So it's somehow Windows-related. Please pull and checkout the branch dev/urs/refactor-job-test-windows. This includes two test prints on the command line to check what code is actually reached and the value(s) of some variables. Is anything printed with that when you use Engrave (custom)? Urs ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Frescobaldi testing requested
Am 06.09.2018 um 21:10 schrieb Partitura Organum: This is not what happens for me. Could you specify the OS/distribution you're running? And maybe provide a screenshot of the dialog. I could imagine that some combination of options would be able to produce unwanted behaviour. I'm running it on Windows. Here's a screenshot of the dialog. ... I doesn't matter which option I choose, PDF, PNG, SVG or some of the other options. Starting Lilypond results in nothing. The dialog disappears and that's it. When I run it on Linux, it works as expected. So it's somehow Windows-related. What would be the path to LilyPond on your Linux system? My first suspicion would be that it chokes on the spaces in the file name (which of course should be fixed in Frescobaldi). Urs ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
