Hi Keith,
sorry for not responding earlier.
Many thanks for this comparison - i think it is very useful! Doing
such comparisons is very important for LilyPond in my opinion.
Maybe you'd like to turn this into a short blog post? I think that it
would fit well with the focus of
https://codereview.appspot.com/9863047/diff/1/scm/define-context-properties.scm
File scm/define-context-properties.scm (right):
https://codereview.appspot.com/9863047/diff/1/scm/define-context-properties.scm#newcode325
scm/define-context-properties.scm:325: (glissandoMap ,list? A map in
the
https://codereview.appspot.com/9863047/diff/1/scm/define-context-properties.scm
File scm/define-context-properties.scm (right):
https://codereview.appspot.com/9863047/diff/1/scm/define-context-properties.scm#newcode325
scm/define-context-properties.scm:325: (glissandoMap ,list? A map in
the
https://codereview.appspot.com/9863047/diff/1/scm/define-context-properties.scm
File scm/define-context-properties.scm (right):
https://codereview.appspot.com/9863047/diff/1/scm/define-context-properties.scm#newcode325
scm/define-context-properties.scm:325: (glissandoMap ,list? A map in
the
- Original Message -
From: Janek Warchoł janek.lilyp...@gmail.com
To: Jan Nieuwenhuizen jann...@gnu.org; Graham Percival
gra...@percival-music.ca; LilyPond Developmet Team
lilypond-devel@gnu.org; Urs Liska u...@openlilylib.org
Sent: Wednesday, June 05, 2013 11:09 PM
Subject: maybe we
Am 06.06.2013 16:21, schrieb Phil Holmes:
- Original Message - From: Janek Warchoł
janek.lilyp...@gmail.com
To: Jan Nieuwenhuizen jann...@gnu.org; Graham Percival
gra...@percival-music.ca; LilyPond Developmet Team
lilypond-devel@gnu.org; Urs Liska u...@openlilylib.org
Sent: Wednesday,
Am 06.06.2013 18:46, schrieb Jan Nieuwenhuizen:
Can't we just use lilypond.org/blog and/or use iframes to include it into our
home page?
Greetings, Jan
Would that mean that www.lilypond.org/blog.html would be a static HTML
page containing nothing than a full-page frame that points to
Am 06.06.2013 19:00, schrieb Urs Liska:
Am 06.06.2013 18:46, schrieb Jan Nieuwenhuizen:
Can't we just use lilypond.org/blog and/or use iframes to include it
into our home page?
Greetings, Jan
Would that mean that www.lilypond.org/blog.html would be a static HTML
page containing nothing than
Urs Liska writes:
Would that mean that www.lilypond.org/blog.html would be a static HTML
page containing nothing than a full-page frame that points to wherever the
blog is hosted?
Something like that. Possibly we want a lilypond.org-site navigation
menu somewhere at the top,
Urs Liska writes:
(- a minor issue is that I don't know how to define the iframe yet. I had to
manually set a height in pixels, which obviously isn't good.)
Oh, I have been using something like this. Problem is possibly
CORS, no problem if you are hosting I guess?
div
!--[if IE]
- Whoever is the admin of lilypond.org would have to:
- register/set up the subdomain blog.lilypond.org
- edit the nameserver (A-Record) for that subdomain to point to my
provider's IP
- Then my server would transparently serve the blog as blog.lilypond.org
Two aspects have to be
LGTM
https://codereview.appspot.com/10008043/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
I think the original version was more general, but if it produces ugly
output due to a bug then I guess I can't complain about this change.
https://codereview.appspot.com/9705045/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
LGTM
https://codereview.appspot.com/9973043/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
LGTM
https://codereview.appspot.com/9634047/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
I find ... easier to read in texinfo source rather than @dots{}, but oh
well. I won't object to the patch.
https://codereview.appspot.com/9964043/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
Am 06.06.2013 22:44, schrieb Jan Nieuwenhuizen:
Urs Liska writes:
Would that mean thatwww.lilypond.org/blog.html would be a static HTML
page containing nothing than a full-page frame that points to wherever the
blog is hosted?
Something like that. Possibly we want a
Am 06.06.2013 22:57, schrieb Jan Nieuwenhuizen:
Urs Liska writes:
(- a minor issue is that I don't know how to define the iframe yet. I had to
manually set a height in pixels, which obviously isn't good.)
Oh, I have been using something like this. Problem is possibly
CORS, no problem if you
Am 06.06.2013 23:01, schrieb Michel Villeneuve:
- Whoever is the admin of lilypond.org would have to:
- register/set up the subdomain blog.lilypond.org
- edit the nameserver (A-Record) for that subdomain to point to my
provider's IP
- Then my server would transparently serve the blog as
Urs Liska wrote
There's another thing I can throw into the discussion:
blog.openlilylib.org.
www.openlilylib.org is a domain that I recently registered for a
'community' kind side-project to LilyPond. The current content of the
web site is still a stub, but you can get a good impression
Am 06.06.2013 18:46, schrieb Jan Nieuwenhuizen:
Can't we just use lilypond.org/blog and/or use iframes to include it into
our home page?
Hmmm... I think it would help to have a clearer decision on the
relationship of the blog with the main LilyPond site. Once there's an
answer to what is
Urs Liska wrote
Something like that. Possibly we want a lilypond.org-site navigation
menu somewhere at the top, served from either site.
As we'd want such a thing also when the blog is viewed 'standalone' it
would probably better to include this in the blog theme and have the
iframe use
On Thu, Jun 06, 2013 at 11:40:47AM -0700, Paul Morris wrote:
B. a more independent LilyPond community blog? (i.e.
blog.openlilylib.org)
This.
Get it going, wait for it to become something, and if it takes off
then maybe in a year there could be a redirect (or whatever) from
blog.lilypond.org
Reviewers: Graham Percival,
Message:
On 2013/06/06 21:26:28, Graham Percival wrote:
I think the original version was more general,
No, it wasn't. Not having a clue about the alignment of the staff
within the score containing the tuning, it centered the whole score, in
this case between the
On 2013/06/06 21:31:40, Graham Percival wrote:
I find ... easier to read in texinfo source rather than @dots{}, but
oh well. I
won't object to the patch.
Well, you'll see that I did not change any ... inside of a comment or
@ignore section. Which is where ... is only in the Texinfo source.
On Wed, 05 Jun 2013 22:38:17 -0700, Mike Solomon m...@mikesolomon.org wrote:
Could someone please send me minimal examples of things going wrong?
The issues on the tracker that are not marked Fixed have minimal examples of
things still going wrong.
On 6 juin 2013, at 06:52, Keith OHara
26 matches
Mail list logo
