Difference between revisions of "Talk:Nyquist Audio Programming"

From Audacity Wiki
Jump to: navigation, search
(answers to some answers - thanks to Gale Andrews for extensive explanations)
(minor clean-up)
Line 23: Line 23:
 
<code>Code tags give near-invisible grey background....</code>
 
<code>Code tags give near-invisible grey background....</code>
  
 +
<font color="green">Using code tags is strongly discouraged because long lines flow off the screen and if you use carriage returns you lose the background. This is one advantage of code template because you can either use <nowiki><br></nowiki> in the template to get a clean line break, otherwise the text simply wraps round.</font>
 +
 
'''Edgar:''' yes, I have read on the 'Wiki Edit Help' (or similar) page.
 
'''Edgar:''' yes, I have read on the 'Wiki Edit Help' (or similar) page.
  
<font color="green">Using code tags is strongly discouraged because long lines flow off the screen and if you use carriage returns you lose the background. This is one advantage of code template because you can either use <nowiki><br></nowiki> in the template to get a clean line break, otherwise the text simply wraps round.
+
<font color="green">You can also put code inside <nowiki><pre> </pre> </nowiki> tags which produces a dotted box:</font>
 
You can also put code inside <nowiki><pre> </pre> </nowiki> tags which produces a dotted box:</font>
 
  
 
<pre><pre>dotted box</pre>
 
<pre><pre>dotted box</pre>
 +
 +
<font color="green"><nowiki><pre></nowiki> tags give you what you write, so there is still the problem that long text overflows, though you can use a carriage return and keep the background.</font>
  
 
'''Edgar:''' yes, I'm an idiot, I haven't tried the most obvious solution.
 
'''Edgar:''' yes, I'm an idiot, I haven't tried the most obvious solution.
  
<font color="green"><nowiki><pre></nowiki> tags give you what you write, so there is still the problem that long text overflows, though you can use a carriage return and keep the background.
+
<font color="green">You can also start your code by indenting it one space, so typing this:
 
 
You can also start your code by indenting it one space, so typing this:
 
  
 
&nbsp;<nowiki>code starts here </nowiki>
 
&nbsp;<nowiki>code starts here </nowiki>
Line 49: Line 49:
 
*text size in relation to main text (currently it is set to be slightly larger)  
 
*text size in relation to main text (currently it is set to be slightly larger)  
 
*type of border
 
*type of border
 
  
 
I don't want to specify the font family as many people choose their own fonts anyway these days. If you like we could just have black text against a faint pink background, something like code tags used to produce.  
 
I don't want to specify the font family as many people choose their own fonts anyway these days. If you like we could just have black text against a faint pink background, something like code tags used to produce.  

Revision as of 07:47, 11 February 2008

Edgar wrote: Hi all, I have uploaded some drafts for these pages to:

http://www.audacity-forum.de/download/edgar/nyquist/nyquist-doc/examples/audacity-wiki/index.htm

Q: The 'Audacity Nyquist Prompt' page has a lot of screenshots (png files). Would it be more clever to upload the picture files to somewhere here in the Wiki or leave them in the german Audacity forum and create external links, what also would be no problem because I wanted to keep 'backup copies' of these pages in the german forum anyway.

I'm afraid the Wiki has no way to link to external images, so all the images must be uploaded locally via Special:Upload. Also the images at present will have to be uploaded one at a time. We're aiming soon to install an extension that will allow multiple uploads at one go.

Edgar: Doesn't matter, I can live that way.

Q: Problem: The 'code' template produces pink text with pink background on my wacky LCD monitor and make my 42 year old eyes produce bad headache instantly. I'm sorry but I can't work that way. Is there any other way to mark source code? Or could this be changed to a readable colour?

Sure the code template can be changed. I have been wondering about the pink colour too, but the background is currently grey, not pink.

Edgar: This probably depends on the color adjustment of the monitor (I do not doubt that it is grey, but on my monitor it appears in pink letters on light pink background).

Incidentally another user really likes that pink colour.....

Edgar: It's not a matter of taste (I fortunately do not have such problems), it's a matter of health (the contrast is too low).

The pink text colour came about because until recently enclosing text inside <code> </code> tags produced a pink background. But now, code tags only produce a near-invisible grey background:

Code tags give near-invisible grey background....

Using code tags is strongly discouraged because long lines flow off the screen and if you use carriage returns you lose the background. This is one advantage of code template because you can either use <br> in the template to get a clean line break, otherwise the text simply wraps round.

Edgar: yes, I have read on the 'Wiki Edit Help' (or similar) page.

You can also put code inside <pre> </pre> tags which produces a dotted box:

<pre>dotted box

<pre> tags give you what you write, so there is still the problem that long text overflows, though you can use a carriage return and keep the background.

Edgar: yes, I'm an idiot, I haven't tried the most obvious solution.

You can also start your code by indenting it one space, so typing this:

 code starts here

gives you the same dotted box:

code starts here

However this has both the problems of <code> tags (overflowing lines, and using a carriage return loses the background). So let's agree something about Code template and I can change it. The choices are:

  • background colour
  • text colour
  • text size in relation to main text (currently it is set to be slightly larger)
  • type of border

I don't want to specify the font family as many people choose their own fonts anyway these days. If you like we could just have black text against a faint pink background, something like code tags used to produce.

Gale

Edgar: 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.

And thanks for your explanations.