Difference between revisions of "Talk:Nyquist Audio Programming"

From Audacity Wiki
Jump to: navigation, search
(Answer)
(maybe better suggestion for a alternate comment color inside the code template)
Line 16: Line 16:
  
 
Gale </font>
 
Gale </font>
 +
 +
 +
What I meant is: if you look at the code example in my drafts, e.g.:
 +
 +
http://www.audacity-forum.de/download/edgar/nyquist/nyquist-doc/examples/audacity-wiki/basics/change-volume.htm#3-2
 +
 +
you will see that I use the comments to explain the source code. Therefore
 +
it is important that the comments (the explanations) get displayed in a
 +
different color than the rest of the code.
 +
 +
This must not be necessarily
 +
be a "free" choice by the user but could also be a second text color
 +
predefined by the template programmer, which then can be used e.g. via
 +
<nowiki><comment>...</comment></nowiki> tags by the user. This then still
 +
would guarantee a "unified" look of the whole Wiki.
 +
 +
'''Maybe also important to know:'''
 +
 +
In the human eye and the related "visual" brain processing there exist three
 +
contrast values: red/green, blue/yellow, and black/white.
 +
 +
The grayscale of a color image computes as:
 +
 +
<pre>0.33*red + 0.57*green + 0.11*blue</pre>
 +
 +
(I know: equals to 101 percent, what is based on the missing digits).
 +
 +
Wether a color-blind person can read your wiki you can test just simple:
 +
 +
Make a screenshot, load it into the Gimp (or any other graphics tool) and
 +
convert it to a greyscale image. If you still can read the text, you have
 +
won (it's sometimes not-so-easy to judge from a color image, I have fooled
 +
myself often enough).
 +
 +
Thanks anyway,
 +
 +
- edgar

Revision as of 13:41, 11 February 2008

Edgar wrote: I think I just will use <pre>...</pre> tags. My code lines always are as short as possible (otherwise I won't understand myself) and the wacky "unbreakable" Nyquist plugin header lines will be just simply shortened by me myself to an appropriate length.

OK, as long as the lines are short. I'll change the colours of Code Template anyway (I have an LCD too and even if I stand away from it I can still see the text against the background). It's also odd as I have checked my monitor against a calibration image and it was not very far out....


Gale


In the code template it would also be necessary to let the user specify the text foreground color, because comments must be displayable in a different color than ordinary code. I don't know how much this contradicts the meaning of a template, because if the user can change everything afterwards anyway you don't need a template...

Indeed, I said that text color was a decision to make, but it's a unitary color through the whole template. The user should not change the template really because as you say it is then no longer a template. There could be an alternative template with different text and background colour, if there is some definite opinion on a good colour scheme. Yellow on blue would be high contrast but not I think very popular....:) I'll do just a black on light pink I think like the old code tags, for the main template. You can suggest an alternative if you wish where the text colour is other than black. There is not much choice though (red and blue are not recommended as they are dead and active link colours), hence another reason for the pink choice.

If you are talking about displaying a range of colours in the code box like some text editors do for different types of string, that has to be wait to install an appropriate extension that can do that (or before then the user hard codes the whole thing in a table according to the color scheme they want).


Gale


What I meant is: if you look at the code example in my drafts, e.g.:

http://www.audacity-forum.de/download/edgar/nyquist/nyquist-doc/examples/audacity-wiki/basics/change-volume.htm#3-2

you will see that I use the comments to explain the source code. Therefore it is important that the comments (the explanations) get displayed in a different color than the rest of the code.

This must not be necessarily be a "free" choice by the user but could also be a second text color predefined by the template programmer, which then can be used e.g. via <comment>...</comment> tags by the user. This then still would guarantee a "unified" look of the whole Wiki.

Maybe also important to know:

In the human eye and the related "visual" brain processing there exist three contrast values: red/green, blue/yellow, and black/white.

The grayscale of a color image computes as:

0.33*red + 0.57*green + 0.11*blue

(I know: equals to 101 percent, what is based on the missing digits).

Wether a color-blind person can read your wiki you can test just simple:

Make a screenshot, load it into the Gimp (or any other graphics tool) and convert it to a greyscale image. If you still can read the text, you have won (it's sometimes not-so-easy to judge from a color image, I have fooled myself often enough).

Thanks anyway,

- edgar