date:20161130

Re: New LilyPond website

2016-11-30 Thread Henning Hraban Ramm

Am 2016-11-30 um 22:51 schrieb John Roper :

> OK, I removed the JavaScript drop down menu and will do it another
> way. I have also updated the letter spacing on the text so it matches
> what we had previously.

I didn’t look at it (yet), but thanks for your efforts!

I was always trying to have CSS-only menus, but they behave badly on touch 
screens (since there’s no mouseover).
So, in my experience as a professional (web) designer, I’d go for something 
that works without JS, but also/better with. (Bootstrap is one candidate.)

At the moment I see no dropdown menus at all – do you think we can manage 
without?

Regarding the font: While I find it acceptable for most of the text, I’d prefer 
something different for titles, esp. the main title.


Greetlings, Hraban
---
fiëé visuëlle
Henning Hraban Ramm
http://www.fiee.net




___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: request for help: huge score

2016-11-30 Thread Urs Liska



Am 01.12.2016 um 04:21 schrieb Kieren MacMillan:
> Hi Karl,
>
>> there is a good point in avoiding tweeks, because you can just 
>> wait a few years and then magically you don't need it any longer ---
>> because lilypond has become so much better and does it for you 
>> automatically.
> A little OT, but… If you use the edition-engraver, all tweaks are external to 
> the main Lily code, so when improvements are made, you can fine-tune them in 
> the edition file (or, in the best case scenario, eliminate them altogether).

OTOH, as long as the edition-engraver is not part of LilyPond itself
this adds an admittedly non-trivial dependency to the score (non-trivial
in the sense of sustainable).

Urs

>
> Cheers,
> 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


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: New LilyPond website

2016-11-30 Thread Federico Bruni

Il giorno mer 30 nov 2016 alle 20:13, Noeck  ha 
scritto:

 I wanted to do that, but I got so much dislike from the community
 members about the design, I redid it in a way that would be more
 pleasing to them.


That's a pity. My summary of the opinions here is different: Some like
the proposed changes and some do not. It is sad that the one who cries
the loudest will win.

To me the green color and the color gradient is the most off-putting
part. But beauty is in the eye of the beholder.


+1




___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: request for help: huge score

2016-11-30 Thread Kieren MacMillan

Hi Karl,

> there is a good point in avoiding tweeks, because you can just 
> wait a few years and then magically you don't need it any longer ---
> because lilypond has become so much better and does it for you 
> automatically.

A little OT, but… If you use the edition-engraver, all tweaks are external to 
the main Lily code, so when improvements are made, you can fine-tune them in 
the edition file (or, in the best case scenario, eliminate them altogether).

Cheers,
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: New LilyPond website

2016-11-30 Thread John Roper

And another fix for links.

On Wed, Nov 30, 2016 at 9:35 PM, John Roper  wrote:
> Ok, I tested, and I made some more fixes.
>
> On Wed, Nov 30, 2016 at 9:18 PM, John Roper  wrote:
>> Ok, here are my updates on the lilypond-website.css.
>>
>> On Wed, Nov 30, 2016 at 8:53 PM, Paul  wrote:
>>> On 11/30/2016 08:01 PM, John Roper wrote:
>>>
 Why is the website auto generated? What content is auto generated or
 is it just setup that way so that it is always built to the latest
 version for releases?
>>>
>>>
>>> Others can probably give better answers, as this is kind of second hand
>>> based on past discussions... but the website is basically an appendage to
>>> the (much larger) documentation, and, well let me quote
>>>
>>> https://www.gnu.org/software/texinfo/
>>>
>>> ---
>>> Texinfo is the official documentation format of the GNU project. It was
>>> invented by Richard Stallman and Bob Chassell many years ago, loosely based
>>> on Brian Reid's Scribe and other formatting languages of the time. It is
>>> used by many non-GNU projects as well.
>>>
>>> Texinfo uses a single source file to produce output in a number of formats,
>>> both online and printed (dvi, html, info, pdf, xml, etc.). This means that
>>> instead of writing different documents for online information and another
>>> for a printed manual, you need write only one document. And when the work is
>>> revised, you need revise only that one document. The Texinfo system is
>>> well-integrated with GNU Emacs.
>>> ---
>>>
>>> So using texinfo to produce the documentation in info, pdf, html formats
>>> etc. is then also used for the website.  I think that's the main reason, but
>>> it's also tied up with supporting multiple translations of the docs/website
>>> and how building the docs runs LilyPond to generate all of the images for
>>> the examples, etc.  Also the argument is that having one system for docs and
>>> website is simpler and makes maintenance easier, especially with fewer
>>> contributors, etc.  That's the gist of past discussions.
>>>
>>> I think there's a case for decoupling the website from the documentation to
>>> a greater degree, e.g. as Federico argued earlier in the thread, but based
>>> on past discussions I am not optimistic that this would go as far as not
>>> using texinfo.  (But I've often wondered how important is it for the content
>>> of the website to be available in pdf and info formats.)
>>>
>>> Upgrading to the latest version of texi2any[0] and/or using Haunt would
>>> help, but those are non-trivial endeavors.  The current setup certainly
>>> introduces friction for website work, especially for those who are used to
>>> working directly with HTML.
>>>
>>> [0]
>>> https://www.gnu.org/software/texinfo/manual/texinfo/html_node/Generic-Translator-texi2any.html
>>>
>>> Cheers,
>>> -Paul
>>>
>>
>>
>>
>> --
>> John Roper
>> Freelance Developer and Simulation Artist
>> Boston, MA USA
>> http://jmroper.com/
>
>
>
> --
> John Roper
> Freelance Developer and Simulation Artist
> Boston, MA USA
> http://jmroper.com/



-- 
John Roper
Freelance Developer and Simulation Artist
Boston, MA USA
http://jmroper.com/
/* Generic elements */

html {
  padding: 0;
  margin: 0;
}

body {
  position: absolute;
  top: 0;
  left: 0.5%;
  right: 0.5%;
  width: 99%;
  min-width: 42em;
  max-width: 70em;
  line-height: 1.5;
  text-align: justify;
  padding: 0;
  margin: 0 auto;
  /* fallback for IE8 which doesn't support multiple backgrounds */
  background: url(../pictures/background-top-left.png) no-repeat top left;
  background-color: #f5fcf2;
  background-image: url(../pictures/background-top-right.png),
url(../pictures/background-top-left.png);
  background-position: top right, top left;
  background-repeat: no-repeat, no-repeat;
  @import url('https://fonts.googleapis.com/css?family=Cabin');
  font-family: 'Cabin', sans-serif;
  letter-spacing: 1px;
}

hr {
  display: none;
}

p {
  margin: 0.5em;
}

h1, h2, h3, h4, h5 {
  margin: 1em 10px;
}

li {
  margin-right: 1em;
}

a img {
  border: 0;
}

/* Hyperlinks */

/* no dotted line around clicked tabs */
a:focus {
  outline-style: none;
}

a:link {
  color: #0c51ab;
}

a:visited {
  color: #0c6be8;
}

a:hover {
  color: #0105ad;
}

/* Table of Contents */
/* first level toc (unnumbered) */
div#tocframe {
  position: absolute;
  top: 0;
  left: 0;
  right: 0;
  background: #239b50;
  max-width: 70em;
  font-size: 100%;
  line-height: 1;
  padding: 0;
  margin-top: 15px;
  border-radius: 2px !important;
}

#tocframe a {
  color: #fff;
  text-decoration: none;
}

#tocframe ul.toc {
  list-style-type: none;
  padding: 0;
  margin: 0;
}

#tocframe > ul:first-child > li:first-child a span {
  background: url(../pictures/lily-home-32x32.png) no-repeat scroll 0% 40% transparent;
  padding: 16px 0px 16px 38px;
}

#tocframe li {
  display: inline;
  padding: 0;
  margin: 0;
}

/* search

Re: New LilyPond website

2016-11-30 Thread John Roper

Ok, I tested, and I made some more fixes.

On Wed, Nov 30, 2016 at 9:18 PM, John Roper  wrote:
> Ok, here are my updates on the lilypond-website.css.
>
> On Wed, Nov 30, 2016 at 8:53 PM, Paul  wrote:
>> On 11/30/2016 08:01 PM, John Roper wrote:
>>
>>> Why is the website auto generated? What content is auto generated or
>>> is it just setup that way so that it is always built to the latest
>>> version for releases?
>>
>>
>> Others can probably give better answers, as this is kind of second hand
>> based on past discussions... but the website is basically an appendage to
>> the (much larger) documentation, and, well let me quote
>>
>> https://www.gnu.org/software/texinfo/
>>
>> ---
>> Texinfo is the official documentation format of the GNU project. It was
>> invented by Richard Stallman and Bob Chassell many years ago, loosely based
>> on Brian Reid's Scribe and other formatting languages of the time. It is
>> used by many non-GNU projects as well.
>>
>> Texinfo uses a single source file to produce output in a number of formats,
>> both online and printed (dvi, html, info, pdf, xml, etc.). This means that
>> instead of writing different documents for online information and another
>> for a printed manual, you need write only one document. And when the work is
>> revised, you need revise only that one document. The Texinfo system is
>> well-integrated with GNU Emacs.
>> ---
>>
>> So using texinfo to produce the documentation in info, pdf, html formats
>> etc. is then also used for the website.  I think that's the main reason, but
>> it's also tied up with supporting multiple translations of the docs/website
>> and how building the docs runs LilyPond to generate all of the images for
>> the examples, etc.  Also the argument is that having one system for docs and
>> website is simpler and makes maintenance easier, especially with fewer
>> contributors, etc.  That's the gist of past discussions.
>>
>> I think there's a case for decoupling the website from the documentation to
>> a greater degree, e.g. as Federico argued earlier in the thread, but based
>> on past discussions I am not optimistic that this would go as far as not
>> using texinfo.  (But I've often wondered how important is it for the content
>> of the website to be available in pdf and info formats.)
>>
>> Upgrading to the latest version of texi2any[0] and/or using Haunt would
>> help, but those are non-trivial endeavors.  The current setup certainly
>> introduces friction for website work, especially for those who are used to
>> working directly with HTML.
>>
>> [0]
>> https://www.gnu.org/software/texinfo/manual/texinfo/html_node/Generic-Translator-texi2any.html
>>
>> Cheers,
>> -Paul
>>
>
>
>
> --
> John Roper
> Freelance Developer and Simulation Artist
> Boston, MA USA
> http://jmroper.com/



-- 
John Roper
Freelance Developer and Simulation Artist
Boston, MA USA
http://jmroper.com/
/* Generic elements */

html {
  padding: 0;
  margin: 0;
}

body {
  position: absolute;
  top: 0;
  left: 0.5%;
  right: 0.5%;
  width: 99%;
  min-width: 42em;
  max-width: 70em;
  line-height: 1.5;
  text-align: justify;
  padding: 0;
  margin: 0 auto;
  /* fallback for IE8 which doesn't support multiple backgrounds */
  background: url(../pictures/background-top-left.png) no-repeat top left;
  background-color: #f5fcf2;
  background-image: url(../pictures/background-top-right.png),
url(../pictures/background-top-left.png);
  background-position: top right, top left;
  background-repeat: no-repeat, no-repeat;
  @import url('https://fonts.googleapis.com/css?family=Cabin');
  font-family: 'Cabin', sans-serif;
  letter-spacing: 1px;
}

hr {
  display: none;
}

p {
  margin: 0.5em;
}

h1, h2, h3, h4, h5 {
  margin: 1em 10px;
}

li {
  margin-right: 1em;
}

a img {
  border: 0;
}

/* Hyperlinks */

/* no dotted line around clicked tabs */
a:focus {
  outline-style: none;
}

a:link {
  color: #0c51ab;
}

a:visited {
  color: #804f01;
}

a:hover {
  color: #0105ad;
}

/* Table of Contents */
/* first level toc (unnumbered) */
div#tocframe {
  position: absolute;
  top: 0;
  left: 0;
  right: 0;
  background: #239b50;
  max-width: 70em;
  font-size: 100%;
  line-height: 1;
  padding: 0;
  margin-top: 15px;
  border-radius: 2px !important;
}

#tocframe a {
  color: #fff;
  text-decoration: none;
}

#tocframe ul.toc {
  list-style-type: none;
  padding: 0;
  margin: 0;
}

#tocframe > ul:first-child > li:first-child a span {
  background: url(../pictures/lily-home-32x32.png) no-repeat scroll 0% 40% transparent;
  padding: 16px 0px 16px 38px;
}

#tocframe li {
  display: inline;
  padding: 0;
  margin: 0;
}

/* search box */
#tocframe li form {
  float: left;
  width: 16%;
  font-size: 100%;
  padding: 0.5em 0.8%;
  margin: 0 0 0 1%;
}

#tocframe li form input {
  display: block;
  float: left;
  width: 92%;
  height: 20px;
  font-size: 90%;
  color: #55;
  background: #ebf2e8;
  padding:

Re: New LilyPond website

2016-11-30 Thread John Roper

Ok, here are my updates on the lilypond-website.css.

On Wed, Nov 30, 2016 at 8:53 PM, Paul  wrote:
> On 11/30/2016 08:01 PM, John Roper wrote:
>
>> Why is the website auto generated? What content is auto generated or
>> is it just setup that way so that it is always built to the latest
>> version for releases?
>
>
> Others can probably give better answers, as this is kind of second hand
> based on past discussions... but the website is basically an appendage to
> the (much larger) documentation, and, well let me quote
>
> https://www.gnu.org/software/texinfo/
>
> ---
> Texinfo is the official documentation format of the GNU project. It was
> invented by Richard Stallman and Bob Chassell many years ago, loosely based
> on Brian Reid's Scribe and other formatting languages of the time. It is
> used by many non-GNU projects as well.
>
> Texinfo uses a single source file to produce output in a number of formats,
> both online and printed (dvi, html, info, pdf, xml, etc.). This means that
> instead of writing different documents for online information and another
> for a printed manual, you need write only one document. And when the work is
> revised, you need revise only that one document. The Texinfo system is
> well-integrated with GNU Emacs.
> ---
>
> So using texinfo to produce the documentation in info, pdf, html formats
> etc. is then also used for the website.  I think that's the main reason, but
> it's also tied up with supporting multiple translations of the docs/website
> and how building the docs runs LilyPond to generate all of the images for
> the examples, etc.  Also the argument is that having one system for docs and
> website is simpler and makes maintenance easier, especially with fewer
> contributors, etc.  That's the gist of past discussions.
>
> I think there's a case for decoupling the website from the documentation to
> a greater degree, e.g. as Federico argued earlier in the thread, but based
> on past discussions I am not optimistic that this would go as far as not
> using texinfo.  (But I've often wondered how important is it for the content
> of the website to be available in pdf and info formats.)
>
> Upgrading to the latest version of texi2any[0] and/or using Haunt would
> help, but those are non-trivial endeavors.  The current setup certainly
> introduces friction for website work, especially for those who are used to
> working directly with HTML.
>
> [0]
> https://www.gnu.org/software/texinfo/manual/texinfo/html_node/Generic-Translator-texi2any.html
>
> Cheers,
> -Paul
>



-- 
John Roper
Freelance Developer and Simulation Artist
Boston, MA USA
http://jmroper.com/
/* Generic elements */

html {
  padding: 0;
  margin: 0;
}

body {
  position: absolute;
  top: 0;
  left: 0.5%;
  right: 0.5%;
  width: 99%;
  min-width: 42em;
  max-width: 70em;
  line-height: 1.5;
  text-align: justify;
  padding: 0;
  margin: 0 auto;
  /* fallback for IE8 which doesn't support multiple backgrounds */
  background: url(../pictures/background-top-left.png) no-repeat top left;
  background-color: #f5fcf2;
  background-image: url(../pictures/background-top-right.png),
url(../pictures/background-top-left.png);
  background-position: top right, top left;
  background-repeat: no-repeat, no-repeat;
  @import url('https://fonts.googleapis.com/css?family=Cabin');
  font-family: 'Cabin', sans-serif;
  letter-spacing: 1px;
}

hr {
  display: none;
}

p {
  margin: 0.5em;
}

h1, h2, h3, h4, h5 {
  margin: 1em 10px;
}

li {
  margin-right: 1em;
}

a img {
  border: 0;
}

/* Hyperlinks */

/* no dotted line around clicked tabs */
a:focus {
  outline-style: none;
}

a:link {
  color: #0c51ab;
}

a:visited {
  color: #804f01;
}

a:hover {
  color: #0105ad;
}

/* Table of Contents */
/* first level toc (unnumbered) */
div#tocframe {
  position: absolute;
  top: 0;
  left: 0;
  right: 0;
  background: #239b50;
  max-width: 70em;
  font-size: 100%;
  line-height: 1;
  padding: 0;
  margin-top: 15px;
  border-radius: 2px !important;
}

#tocframe a {
  color: #fff;
  text-decoration: none;
}

#tocframe ul.toc {
  list-style-type: none;
  padding: 0;
  margin: 0;
}

#tocframe > ul:first-child > li:first-child a span {
  background: url(../pictures/lily-home-32x32.png) no-repeat scroll 0% 40% transparent;
  padding: 16px 0px 16px 38px;
}

#tocframe li {
  display: inline;
  padding: 0;
  margin: 0;
}

/* search box */
#tocframe li form {
  float: left;
  width: 16%;
  font-size: 100%;
  padding: 0.5em 0.8%;
  margin: 0 0 0 1%;
}

#tocframe li form input {
  display: block;
  float: left;
  width: 92%;
  height: 20px;
  font-size: 90%;
  color: #55;
  background: #ebf2e8;
  padding: 0.1em 0.1em 0.1em 0.6em;
  border: 0;
  margin: 0;
  border-radius: 3px;
}

#tocframe li form input[type="hidden"] {
  position: relative;
  height: 0;
  overflow: hidden;
  padding: 0;
  margin: 0;
}

#tocframe li a {
  float: left;
  width: 16%;
  text-align: center;

Re: New LilyPond website

2016-11-30 Thread Paul

On 11/30/2016 08:01 PM, John Roper wrote:

Why is the website auto generated? What content is auto generated or
is it just setup that way so that it is always built to the latest
version for releases?

Others can probably give better answers, as this is kind of second hand
based on past discussions... but the website is basically an appendage
to the (much larger) documentation, and, well let me quote

https://www.gnu.org/software/texinfo/

---
Texinfo is the official documentation format of the GNU project. It was
invented by Richard Stallman and Bob Chassell many years ago, loosely
based on Brian Reid's Scribe and other formatting languages of the time.
It is used by many non-GNU projects as well.

Texinfo uses a single source file to produce output in a number of
formats, both online and printed (dvi, html, info, pdf, xml, etc.). This
means that instead of writing different documents for online information
and another for a printed manual, you need write only one document. And
when the work is revised, you need revise only that one document. The
Texinfo system is well-integrated with GNU Emacs.

---

So using texinfo to produce the documentation in info, pdf, html formats
etc. is then also used for the website. I think that's the main reason,
but it's also tied up with supporting multiple translations of the
docs/website and how building the docs runs LilyPond to generate all of
the images for the examples, etc. Also the argument is that having one
system for docs and website is simpler and makes maintenance easier,
especially with fewer contributors, etc. That's the gist of past
discussions.

I think there's a case for decoupling the website from the documentation
to a greater degree, e.g. as Federico argued earlier in the thread, but
based on past discussions I am not optimistic that this would go as far
as not using texinfo. (But I've often wondered how important is it for
the content of the website to be available in pdf and info formats.)

Upgrading to the latest version of texi2any[0] and/or using Haunt would
help, but those are non-trivial endeavors. The current setup certainly
introduces friction for website work, especially for those who are used
to working directly with HTML.

1 2 >

100 matches

Mail list logo