text:
Amiblitz/PED

Using the Amiblitz Text Editor (or PED)
To enter and compile your programs you need an editor. Blitz2 comes with a text editor that acts both as an interface to the Blitz2 compiler as well as a standalone ascii editor (ascii is the computer standard for normal text). The horizontal and vertical bars are called 'scroll bars'. When the file you are editing is longer or wider than the screen you can position your view of the file by dragging these bars inside their boxes with the left mouse button. At the bottom of the screen is information about the cursor position relative to the start of the file you are editing as well as a memory monitor that lets you know the largest block of memory available in your Amiga system. Using the left mouse button you can drag the Blitz2 screen up and down just like any other Amiga screen as well as place it to the back with the front to back gadgets at the top right of the screen.

Note on Current Directories

If you change the pathname in the file-requester to locate a program to load you will usually need to click on the CD gadget before selecting OK on the file requester. This changes the current directory to that which you loaded the program.

By changing the current directory any files the program attempts to use will be loaded from the same directory as that from which the source code was loaded.

This means that when the program is executed (run) and attempts to load any data or graphics from disk, the default path (directory it looks for files) will be set to, the same directory as where the program itself was loaded. If a program comes up with a runtime error "Couldn't Load Shape" or the like it will be because the current directory has not been to set. Hit Escape to exit the debugger and return to the editor. If a program crashes the machine, it its because the same error occurred but error checking was disabled on the compiler options menu.

Entering Text

The editor can be treated just like a standard typewriter, just go ahead and type, using the return key to start a new line.

The small box that moves across the screen as you type is called the cursor. Where the cursor is positioned on the screen is where the letters will appear when you type. By using the arrow keys you can move the cursor around your document, herein to be known as the file.

If you place the cursor in the middle of text you have already typed you can insert letters just by typing, the editor will move all the characters under and to the right of the cursor along one and insert the key you pressed into the space created.

The DEL key will remove the character directly under the cursor and move the remaining text on the line left one character to cover up the gap. The key to the left of the DEL key will also remove a character but unlike the DEL key it removes the character to the left of the cursor moving the cursor and the rest of the line to the left. The TAB key works similar to a typewriter moving the cursor and any text to the right of the cursor right by so many columns.

The RETURN key as mentioned allows you to start a new line. If you are in the middle of a line of text and want to move all text to the right of the cursor down to a new line use shift RETURN, this is known as inserting a carriage return. To join two lines of text use the Amiga keyboard combination.

Using the shift keys in combination with the arrow keys you can move the cursor to the very start or end of a line and up and down a whole page of the document. By pointing with the mouse to a position on the screen you can move the cursor there by clicking the left mouse button. See keyboard shortcuts at the end of this chapter for other important keys used with the Blitz2 editor.

Highlighting blocks of text

When editing text, especially programs you often need to operate on a block of text. Position the mouse at the start or end of the block, hold down the left mouse button and drag the mouse to highlight the area you wish to copy, delete, save or indent. While holding down the button you can scroll the display by moving the pointer to the very top or bottom of the display.

You can also select a block with the keyboard, position the cursor at the start of the block of text, hit the F1 key then position the cursor at the end of the text and hit F2.

A special feature for structured programmers is the Amiga-A key combination, this automatically highlights the current line and any above or below that are indented the same number of spaces.

The Editor Menus

Using the right mouse button you can access the menu system of the Blitz2 editor. The following is a list of the features accessible from these menus in order from left to right.

The PROJECT Menu

NEW Kills the file you are editing from the Amiga's memory. If the file has been changed since it was last saved to disk a requester will ask you if you really wish to NEW the file.

LOAD Reads a file from disk. A file requester appears when you select LOAD which enables you to easily select the file you wish to edit. See later in this chapter for a full description of using the file requester.

SAVE Writes your file to disk. A file requester appears when you select SAVE which enables you to easily select the file name you wish to save your file as. See later in this chapter for a full description of using the file requester.

DEFAULTS Changes the look of the Blitz2 editor. You can edit the palette, select the size of font and tell the system if you wish icons to be created when your files are saved. The scroll mARG1ns dictate how far from the edge of the screen your cursor needs to be before Blitz scrolls the text.

ABOUT Displays version number and credits concerning Blitz2.

PRINT Sends your file to an output device usually PRT: the printer device.

CLI Launches a command line interface from the editor, use the ENDCLI command to close this CLI and return to the Blitz2 editor.

CLOSEWB Closes WorkBench if it is currently open. This option should only be used if you are running very short on memory as closing WorkBench can free about 40K of valuable ChipMem.

QUIT Close the Blitz2 editor and returns you to workbench or CLI.

The EDIT Menu

COPY Copies a block of text that is highlighted with the mouse or f1-f2 key combination to the current cursor position. The F4 key is another keyboard shortcut for COPY.

KILL Deletes a highlighted block of text (same as shift F3 key).

BLOCK TO DISK Saves a highlighted block of text to disk in ascii format.

INSERT FROM DISK Loads a file from disk and inserts it into the file you are editing at the current cursor position.

FORGET De-selects a block of text that is selected (highlighted).

INSERTLINE Breaks the line into two lines at the current cursor position.

DELETE LINE Deletes the line of text the cursor is currently located on.

DELETE RIGHT Deletes all text on the line to the right of the cursor.

JOIN Places the text on the line below the cursor at the end of the current line.

BLOCK TAB Shifts all highlighted text to the right by one tab mARG1n.

BLOCK UNTAB Shifts all highlighted text to the left by one tab mARG1n.

The SOURCE Menu

TOP Moves the cursor to the top of the file BOTTOM Moves the cursor to the last line of the file.

GOTO LINE Moves the cursor to the line number of your choice.

The SEARCH Menu

FIND Will search the file for a string of characters.

NEXT Positions the cursor at the next occurrence of the Find-String entered using the FIND menu option (as below).

PREVIOUS Will position the cursor at the last occurrence of the Find: String entered using the FIND menu option (as below).

REPLACE Will carry out the same function as discussed in the FIND requester below.

After selecting FIND in the SEARCH menu the following requester will appear: Type the string that you wish to search for into the top string gadget and click on NEXT. This will position the cursor at the next occurrence of the string, if there is no such string the screen will flash.

Use the PREVIOUS icon to search backwards from the current cursor position.

The CASE SENSITIVE option will only find strings that have the same letters capitalized, default is that the search will ignore whether letters are caps or not.

To replace the find string with an alternate string click on the box next to REPLACE: and type the alternate string. REPLACE will search for the next occurrence of the Find: string, delete it, and insert the Replace:  string in its place.

REPLACE ALL will carry on through the file doing replaces on all occurrences of the Find: string.

The Blitz File Requester

When you select load or save, Blitz2 places a file requester on the screen. With the file requester you can quickly and easily find the file on a disk.

Clicking on the top left of the window or on the CANCEL gadget at the bottom right will cancel the file requester returning you to the editor.

The slider at the right enables you to scroll up and down through the files in the currently selected directory (drawer).

Double clicking on a file name (pointing to the name and pressing the left mouse button twice) will select that file name.

Clicking on a  will change to that directory and list the files contained in it.

Clicking on PARENT will return you to the parent directory.

Clicking on drives adds a list of all drives, volumes and assigned devices to the top of the file list so you can move into their directories.

You can also enter path and file names with the keyboard by clicking on the boxes next to PATH: and FILE:  and entering the suitable text. Then Click on the OK gadget.

CD is a special command used when programming in Blitz2 to change the editors current directory to that specified in the path name. This means that when you select CLI or launch a task from the editor its root directory will be that selected by the CD gadget.

The last feature of the Blitz2 FileRequester is the ability to size its window, by dragging the bottom right of the window with the left mouse button you can see more files at one time.

The Compiler Menu

The following is a discussion of the extra options and commands available with Ted when used in Blitz2 programming mode. The Compiler menu includes all the commands needed to control the Blitz2 compiler.

COMPILE/RUN Compiles your Blitz2 program to memory and if there are no errors run the program.

RUN Runs the program if it has already been successfully compiled to memory.

CREATE FILE Compile your Blitz2 program to disk as an executable program.

OPTIONS See next page for details about Blitz2 compiler options.

CREATE RESIDENT Will create a 'resident file' from the current file. A resident is a file including all constants and macro definitions as well as newtype definitions. By removing large chunks of these definitions from your code and creating a resident (pre-compiled) file a dramatic increase in compile speed can be attained.

VIEW TYPE Allows you to view all currently resident types. Click on the type name and its definition will be shown. Subtypes can be viewed from this expansion also.

CLI ARGUMENT Enables you to pass parameters to your program when executing it from the Blitz2 editor environment just as if you had run the program from the CLI.

CALCULATOR Allows you do to calculations in base 2, 10 and 16. Precede hex values with $ and binary with %. It also supports multi levels of parenthesis.

RELOAD ALL LIBS Will read all files from BLITZLIBS: back into the Blitz2 compiler environment. This is useful when writing your own Blitz2 libraries and wish to test them without having to re-run Blitz2.

AmiBlitz Extensions

SAVE AND COMPILE/RUN Save your code and then Compile & Run your program.

SAVE AND CREATE EXECUTABLE Save your source code and then create an executable program.

Compiler Options

The following is a discussion of the Options requester found in the Compiler menu.

Create Icons for Executable Files If on, the compiler creates an icon to accompany the file created with the CREATE FILE option. This means the program will be accessible from the WorkBench. Note: for the program to execute correctly when run from workbench the WBStartUp command should be included at the top of the source code.

Enable Runtime Errors When on will trap runtime errors and invoke the Blitz2 debugger. See Chapter 5 for a thorough discussion of runtime errors in Blitz2.

Make Smallest Code Selects two pass compile mode, which always calculates the minimum amount of memory required for the object code. Make Smallest is automatically selected when creating executable files. Unselected, programs will compile quicker.

Debug Info: Creates a symbols table during CREATE FILE so executable can be debugged more easily.

Buffer Sizes Allows different buffers to be altered when using Blitz2 as a one pass compiler. These buffers are automatically optimized when using MakeSmallest (two pass compile). The one exception is the string buffer setting, if using large strings (such as reading entire files into one string) the string workspace buffer should be increased in size to handle the largest string used.

Object Maximums Allows setting of maximum number of Blitz2 objects such as screens, shapes etc. See Chapter 6 for a thorough explanation of Blitz2 objects and their maximum settings.

Resident: Adds precompiled resident files to the Blitz2 environment. Click in the box and type in the resident file name.

Amiblitz extensions

Label list window This will appear as a window on the right side of the screen, exactly where the old label list used to appear, but is now a window with some useful gadgets. The title of the window shows the filename of the current "deflibs" file (see the tooltypes).

The list which fills most of the window is the label list. This will show labels which start with the "." character. AmiBlitz2 also displays functions and statements here, and can also show comments and case statements. The list is limited to displaying 1,000 items, for speed reasons. You can click with the left mouse button on an item in the list and the editor window will jump to the line with that item. You can hold down the left mouse button and drag the pointer over the list to scroll it, or use the prop-gadget on the right side of the window.

The string gadget at the top of the window allows you to shorten the display to specific items (only the items which start with the text in the string gadget will be displayed). The C gadget will clear the string gadget.

The Case gadget makes the list show only the Case statements.

The ; gadget displays all comments.

The All gadget displays all labels, functions/statements, comments and Case statements - the string gadget is usable when "All" is enabled.

Dialog parameter window If you press Ctrl+Help over an instruction a window will open which shows you all the parameters for the instruction and allows you to enter values for each one.

If the dialog parameter window is already open you can simply click on another instruction to have its parameters shown.

The "Add Code" button will add the command and parameters, or modify the existing command and parameters, to the current source position.

AmiBlitz tooltypes

There are also some tooltypes which you can add to the AmiBlitz2 icon.

OLDSEARCH - When the search window is used, the cursor does not jump to the start of the line. This tooltype should be enabled or disabled, and has no parameters.

BACKDROP - This tooltype when enabled will make the editor window into a backdrop window. This is useful if it overlaps other windows on the AmiBlitz screen and you have no "Window-to-back" hotkey (since there is no window depth gadget on the editor window). This tooltype is enabled by default, and has no parameters.

DONTSORT - When enabled, this tooltype tells the label window to not sort the labels in the list into alphabetical order. This tooltype is a switch and so has no parameters.

LIBFILE - You can use this tooltype to tell AmiBlitz2 what file to use as a "deflibs" file. The format is LIBFILE=. The default, or if the tooltype is not specified, is "deflibs".

STANDARDEDITMODE - Makes the editor work like any normal text editor. Pressing return will split a line instead of starting a new one, backspace will join lines and pressing "Del" with a marked block will delete the block. This tooltype is a switch and has no parameters.

STARTDIR - Tells AmiBlitz what directory to use as the current directory after starting. This tooltype is a string and has the format STARTDIR=

NO_AUTO_TOKENIZE - Forces AmiBlitz to not try to automatically decide whether to tokenise a file or not, and will always work in the regular AmiBlitz manner (files are always tokenised). This tooltype is a switch and has no parameters.

NEWCOLORMODE - Allows the editor to work in 8 or 16 colour screenmodes. Without this tooltype set, you can only use palette number 0 to 3 for the following tooltypes (anything higher and it will wrap back to 0). When this tooltype is set, it also makes the block highlight colour the last entry in the palette. This tooltype is a switch and has no parameters.

RemarkForg - The colour number to use for the foreground colour of comments. The format of this tooltype is RemarkForg=.

RemarkBackg - The colour number for the background colour of comments. The format of this tooltype is RemarkForg=.

FunctionColor - The colour number to use for function/statement names. The format of this tooltype is FunctionColor=. This colour will be used in your code when you type a function/statement name followed by a bracket, e.g. "foo" will have the "foo" shown in the specified colour.

MacroColor - The colour number to use for macro names. The format of this tooltype is MacroColor=. This colour will be used in your code when you call a macro, e.g. "!iamamacro" will be shown in the specified colour.

ConstantColor - The colour number to use for constants. The format of this tooltype is ConstantColor=. This colour will be used in your code when you type any constant, e.g. "#MYWINDOW" will be shown in the specified colour.

StringColor - The colour number to use for strings, including quotation marks. The format of this tooltype is StringColor=. This colour will be used in your code when you type, e.g. `"hello, world"' will be shown in the specified colour (including quote marks).

NewtypeColor - The colour number to use for fields inside newtypes. The format of this tooltype is NewtypeColor=. This colour will be used in your code when you use a field from inside a newtype, e.g. "hi.there\dr_nick" will have the "\dr_nick" part shown in the specified colour.

ClassicColor - The colour number to use for instructions from libraries which use the classic Amiga chipset directly. The format of this tooltype is ClassicColor=. A value of 99 will also disable the classic commands in the instruction helper.

The actual colours used by the new tooltypes can be changed in the Prefs item in the Project menu. Note the USA style of spelling "Color" in the tooltype names!

Other Amiblitz extensions to the editor

Joining lines of code A new feature is you can now join lines together, which is useful if you reach the limit of the line length (which is 250 since AB2.26, 128 characters before this and in the original Blitz2). To do this, simply put @@ in your code and AmiBlitz will continue from the next line as if they were the same line. This feature requires you use optimise with at least a value of 4.

Source position saved When you save your source in AmiBlitz2, the current position of the editor is also saved. When you re-load your source, the editor will start with the previous cursor position displayed.

Executable format AmiBlitz can now create different styles of executable. The first, most obvious change is that it can create PPC executables, when you use PPC assembly language in your programs. The executable format is a WarpOS fat binary, which will run under WarpOS and also MorphOS using the WarpOS emulation. Note that a lot of the current libraries are still 68k, and so is the code generated by AmiBlitz! If you want to create PPC executables, you need to write the PPC assembly language code yourself.

The second addition is that AmiBlitz can create chip or BSS sections in your executable (only one!). This can be useful if you need to put specific parts of your executable into e.g. chipmem for a picture which you can then display without decoding from fastram->chipmem.

AmiBlitz2 defaults to the CODE section. You can type either "chip" or "bss" in your code to change to another section, which will remain the current section until the other type of section is typed in your code (either "bss" or "chip") or the end of the code. Do NOT use the same section type twice (i.e. do not use "chip" twice)!

AB2 source file format If you save your sourcecode with the extension ".ab2" then the source code will be saved as an ASCII file, but the ".xtra" file will also be saved.

This is useful since you do not need to load your source into the AmiBlitz editor just to read it (as you would have to do with the ".bb2" source format) and you also have the use of the .xtra file (which you would not get if you saved your source as ASCII).

Keyboard Shortcuts

The right Amiga key is just to the right of the space bar.

Amiga A SELECTs all text that is indented the same amount as the current line (strictly for structured programming housekeeping)

Amiga B BOTTOM will position cursor on last line of file

Amiga D DELETE LINE removes the line of text on which the cursor is currently positioned

Amiga F FIND/REPLACE executes the FIND command in the SEARCH menu

Amiga G GOTO LINE moves cursor to specific line of file

Amiga I INSERT LINE moves all text at and below the cursor down one line

Amiga J JOIN LINE adjoins next line with current line

Amiga L LOAD reads a file from disk

Amiga N NEXT searches for the next occurrence of the 'find string'

Amiga P PREVIOUS searched for previous occurrence of the 'find string'

Amiga Q QUIT will exit the Blitz2 editor

Amiga R REPLACE will replace text at cursor (if same as find string) with the alternate string specified with the Find command.

Amiga S SAVE writes a file to disk

Amiga T TOP moves the cursor to the top of the file

Amiga W FORGET will unhighlight a selected block of text

Amiga Y DELETE TO RIGHT of cursor

Amiga Z CLI

Amiga ? DEFAULTS allows the user to change the look and feel of the Blitz2 editor

Amiga ] BLOCK TAB moves whole block right one tab

Amiga [ BLOCK UNTAB moves whole block left one tab

Amiblitz Extensions

CTRL U				Undo current line

CTRL CursorUp 			Jump to top of source

CTRL CursorDown 		Jump to end of source

ALT Left Mouse (cursor right) 	Jump to function/label etc.

ALT Mid Mouse (cursor up) 	Back to old pos

ALT (cursor down) 		Back to previous pos

LAmiga A 	Jump to position in source code where text was last added

LAmiga Shift 1/2/3 		Store a bookmark at this line

LAmiga 1/2/3 			Jump to previously stored bookmark

F4/F5/F6 				Fast switching between three different window configurations*

LAmiga F4/F5/F6 			Store settings for window configuration*

F7/F8 				Previous / Next entry in label listview

You must save the preferences to store the window configuration to a file and when AmiBlitz starts, it always defaults to the F4 configuration.

HELP

"Help" with nothing under the cursor (and nothing in the position to the left of the cursor) will bring up an instruction search window. You can type some text in the string gadget and all the instructions and 'library' macros which contain that text will be shown in the listview. This is known as the "instruction helper".

"Help" when there is a character under, or to the left of, the cursor will display the usual help string in the title-bar of the screen if the character is part of a recognised instruction. When it is not part of an instruction, AmiBlitz will show you how many times you have used this word in your source code. This is useful to check the correct spelling of a variable (Count>1) or to make sure you have not used that variable before (Count=1).

"Help" while over a slash character ("\") as used in types will show you all the fields of that NEWTYPE. This will work for variables, USEPATH code (e.g. "\name") and arrays. If you have local and global variables with the same name but different types then the local variable type will be shown.

Shift+Help over an instruction or object name will show you the full text of the online help for that instruction (if it is available). Pressing Alt+Help over an instruction will show you the commands in the library that the instruction is in. These are changeable in the PED menu editor (in the Custom menu).

RAmiga+Help will bring up the default help program, which is useful for internal AmiBlitz commands. This help can be in English or German, depending on which help.dat file you use (help_en.dat or help_de.dat). By default, the English help file is used.

Ctrl+Help gives you the dialog parameter window

title: Amiblitz/PED


text:
User talk:Peterb323

Hello and welcome to Wikibooks!

Here are some tips to help you get started:
 * You can sign your name on Talk and vote pages using four tildes, like this: ~~~~.
 * Remember to conduct any editing experiments in the sandbox.
 * If you're a Wikipedian, see Wikibooks for Wikipedians for a primer on how things work here (it's a little different).
 * If you want to base your work here on materials from Wikipedia, please use WB:RFI to bring the material over in compliance with the GFDL.
 * If you're an instructor and plan on using wikibooks for a class project, see Guidelines for class projects
 * Please say hello at the Staff Lounge with any questions or ideas.
 * Eventually, you might want to read the Manual of Style and Policies and Guidelines.
 * Please take a look at Naming policy before starting a new book.
 * Remember to maintain a Neutral point of view.
 * Explore, be bold in editing pages, and have fun!

You will find more resources in Community Portal. If you want to ask a question, visit the Study help desk, the Staff lounge, IRC channel or ask me personally on my talk page.

Good luck!

Contra Dance
Hi Peter. Sorry for the confusion with the bookshelves... I'm not sure why those templates are protected, I'll have a look.

There is another book this: Ten_Stupid_Things_Beginners_Do_to_Mess_Up_Their_Contradance_Experience. Several chapters to it as well, but it looks like it hasn't been worked on in over a year, and it uses old naming conventions too. I'll request some assistance for you on the Staff Lounge. If you don't mind, I'm going to suggest just using Contra Dance as the title, since it's always nice to have some information about a subject to go with the tips, techniques, etc.

If there are more wikipedia articles about contra dance, we can import them to be incorporated into the book. Just list the articles on WB:RFI and we'll bring them over. -- SB_Johnny | talk 12:58, 22 November 2006 (UTC)

 * Hi again...yes, your stub is better... that book is a bit odd, if you ask me :). The merge proposal was to take the best from the older book and merge it into yours, rather than the other way around. -- SB_Johnny | talk 10:37, 29 November 2006 (UTC)

license: Creative Commons - Attribution Share-Alike - https://creativecommons.org/licenses/by-sa/4.0/

title: User talk:Peterb323


text:
Template:Treeprof

This page template is deprecated. Use instead and be sure to place a "y" in the "large tree" or "small tree" line of the  template that is placed in the resulting page.

/Templates/Profiles

title: Template:Treeprof


text:
Wikijunior:Languages/Icelandic

What writing system(s) does Icelandic use?

Icelandic uses what is today called the Latin Alphabet. This alphabet is thought by many historians to have been a modified version of the ancient Greek alphabet, which in turn is also a variation of ancient Phoenician writing. Icelandic also uses some letters that are not very common in other languages, like ð (eth) and æ (ash).

Icelandic is descended from Old Norse.

How many people speak Icelandic?
All inhabitants of Iceland (about 300,000) speak Icelandic.

Where is this language spoken?
In Iceland, some parts of Canada and also some people from Denmark, Sweden, Norway speak the language.

What is the history of this language?
It descends from Old Norse.

Some famous people who spoke this language

 * Björk Guðmundsdóttir- Björk is a famous singer from Iceland.
 * Eiríkur Rauði- Eiríkir Rauði or "Erik the Red" was an Icelandic Viking.
 * Gunnar á Hlíðarenda- Gunnar á Hlíðarenda or "Gunnar from Hlíðarendi" is a character from book Njála.
 * The band Sigur Rós from Iceland
 * The band Of Monsters and Men from Iceland

What are some basic words in this language that I can learn?

 * Halló, hæ- Hello, hi
 * Bless, bæ- Goodbye, bye
 * Fögur er hlíðin- The hill is beautiful, an excerpt from Njála.
 * Og - And
 * Ég - I
 * Hvað heitir þú? - What is your name?
 * Ég heiti Páll. - My name is Paul.
 * Hvaðan kemurðu? - Where do you come from?
 * Ég kem frá Bretlandi. - I come from Britain.
 * Takk (fyrir).- Thank you

title: Wikijunior:Languages/Icelandic


text:
User talk:BiT

Hello and welcome to Wikibooks!

Here are some tips to help you get started:
 * You can sign your name on Talk and vote pages using four tildes, like this: ~~~~.
 * Remember to conduct any editing experiments in the sandbox.
 * If you're a Wikipedian, see Wikibooks for Wikipedians for a primer on how things work here (it's a little different).
 * If you want to base your work here on materials from Wikipedia, please use WB:RFI to bring the material over in compliance with the GFDL.
 * If you're an instructor and plan on using wikibooks for a class project, see Guidelines for class projects
 * Please say hello at the Staff Lounge with any questions or ideas.
 * Eventually, you might want to read the Manual of Style and Policies and Guidelines.
 * Please take a look at Naming policy before starting a new book.
 * Remember to maintain a Neutral point of view.
 * Explore, be bold in editing pages, and have fun!

You will find more resources in Community Portal. If you want to ask a question, visit the Study help desk, the Staff lounge, IRC channel or ask me personally on my talk page.

Good luck! -- Herby talk thyme 14:12, 22 November 2006 (UTC)

And
Nice work on the Icelandic page -- Herby talk thyme 14:12, 22 November 2006 (UTC)

title: User talk:BiT


text:
User talk:Scott1329m

Hello and welcome to Wikibooks!

Here are some tips to help you get started:
 * You can sign your name on Talk and vote pages using four tildes, like this: ~~~~.
 * Remember to conduct any editing experiments in the sandbox.
 * If you're a Wikipedian, see Wikibooks for Wikipedians for a primer on how things work here (it's a little different).
 * If you want to base your work here on materials from Wikipedia, please use WB:RFI to bring the material over in compliance with the GFDL.
 * If you're an instructor and plan on using wikibooks for a class project, see Guidelines for class projects
 * Please say hello at the Staff Lounge with any questions or ideas.
 * Eventually, you might want to read the Manual of Style and Policies and Guidelines.
 * Please take a look at Naming policy before starting a new book.
 * Remember to maintain a Neutral point of view.
 * Explore, be bold in editing pages, and have fun!

You will find more resources in Community Portal. If you want to ask a question, visit the Study help desk, the Staff lounge, IRC channel or ask me personally on my talk page.

Good luck! -- Herby talk thyme 14:14, 22 November 2006 (UTC)

title: User talk:Scott1329m


text:
User talk:Saub09

Hello and welcome to Wikibooks!

Here are some tips to help you get started:
 * You can sign your name on Talk and vote pages using four tildes, like this: ~~~~.
 * Remember to conduct any editing experiments in the sandbox.
 * If you're a Wikipedian, see Wikibooks for Wikipedians for a primer on how things work here (it's a little different).
 * If you want to base your work here on materials from Wikipedia, please use WB:RFI to bring the material over in compliance with the GFDL.
 * If you're an instructor and plan on using wikibooks for a class project, see Guidelines for class projects
 * Please say hello at the Staff Lounge with any questions or ideas.
 * Eventually, you might want to read the Manual of Style and Policies and Guidelines.
 * Please take a look at Naming policy before starting a new book.
 * Remember to maintain a Neutral point of view.
 * Explore, be bold in editing pages, and have fun!

You will find more resources in Community Portal. If you want to ask a question, visit the Study help desk, the Staff lounge, IRC channel or ask me personally on my talk page.

Good luck! -- Herby talk thyme 14:18, 22 November 2006 (UTC)

title: User talk:Saub09


text:
User talk:Satishgavali

Hello and welcome to Wikibooks!

Here are some tips to help you get started:
 * You can sign your name on Talk and vote pages using four tildes, like this: ~~~~.
 * Remember to conduct any editing experiments in the sandbox.
 * If you're a Wikipedian, see Wikibooks for Wikipedians for a primer on how things work here (it's a little different).
 * If you want to base your work here on materials from Wikipedia, please use WB:RFI to bring the material over in compliance with the GFDL.
 * If you're an instructor and plan on using wikibooks for a class project, see Guidelines for class projects
 * Please say hello at the Staff Lounge with any questions or ideas.
 * Eventually, you might want to read the Manual of Style and Policies and Guidelines.
 * Please take a look at Naming policy before starting a new book.
 * Remember to maintain a Neutral point of view.
 * Explore, be bold in editing pages, and have fun!

You will find more resources in Community Portal. If you want to ask a question, visit the Study help desk, the Staff lounge, IRC channel or ask me personally on my talk page.

Good luck! -- Herby talk thyme 14:20, 22 November 2006 (UTC)

title: User talk:Satishgavali


text:
User talk:Monkeyboo

Hello and welcome to Wikibooks!

Here are some tips to help you get started:
 * You can sign your name on Talk and vote pages using four tildes, like this: ~~~~.
 * Remember to conduct any editing experiments in the sandbox.
 * If you're a Wikipedian, see Wikibooks for Wikipedians for a primer on how things work here (it's a little different).
 * If you want to base your work here on materials from Wikipedia, please use WB:RFI to bring the material over in compliance with the GFDL.
 * If you're an instructor and plan on using wikibooks for a class project, see Guidelines for class projects
 * Please say hello at the Staff Lounge with any questions or ideas.
 * Eventually, you might want to read the Manual of Style and Policies and Guidelines.
 * Please take a look at Naming policy before starting a new book.
 * Remember to maintain a Neutral point of view.
 * Explore, be bold in editing pages, and have fun!

You will find more resources in Community Portal. If you want to ask a question, visit the Study help desk, the Staff lounge, IRC channel or ask me personally on my talk page.

Good luck! -- Herby talk thyme 14:20, 22 November 2006 (UTC)

title: User talk:Monkeyboo


text:
User talk:Alejo2083

Hello and welcome to Wikibooks!

Here are some tips to help you get started:
 * You can sign your name on Talk and vote pages using four tildes, like this: ~~~~.
 * Remember to conduct any editing experiments in the sandbox.
 * If you're a Wikipedian, see Wikibooks for Wikipedians for a primer on how things work here (it's a little different).
 * If you want to base your work here on materials from Wikipedia, please use WB:RFI to bring the material over in compliance with the GFDL.
 * If you're an instructor and plan on using wikibooks for a class project, see Guidelines for class projects
 * Please say hello at the Staff Lounge with any questions or ideas.
 * Eventually, you might want to read the Manual of Style and Policies and Guidelines.
 * Please take a look at Naming policy before starting a new book.
 * Remember to maintain a Neutral point of view.
 * Explore, be bold in editing pages, and have fun!

You will find more resources in Community Portal. If you want to ask a question, visit the Study help desk, the Staff lounge, IRC channel or ask me personally on my talk page.

Good luck! -- Herby talk thyme 14:21, 22 November 2006 (UTC)

LaTeX
Can you take a look at Talk:LaTeX/Floats, Figures and Captions? Thanks. --Derbeth talk 20:35, 2 January 2007 (UTC)
 * I think that it would be good to mention how to create SVG or PNG from LaTeX. I mean writing about dvipng (it's available eg. as a Debian package, it's easy to install and use) and pdf2ps, optipng (I hadn't heared of them before I saw your graphics). --Derbeth talk 12:07, 13 January 2007 (UTC)

 * I don't think so, but if you really want to... the point is that with LaTeX you can basically create only DVI (using latex) and PDF (using pdflatex), that's it. Any other format is obtained from "tricks". You can obtain a PS with both dvi2ps or pdf2ps, but it would work with any DVI or PDF source, there isn't any relationship with LaTeX anymore. About the PNG versions of LaTeX sources I have used: there are several ways to obtained them, but it's all about converting a PDF file in PNG, there isn't anything related to LaTeX in it. You could do:
 * opening the file with Acrobat Reader and taking a screenshot
 * let ImageMagic do the work, simply using the command convert my_file.pdf my_file.png
 * opening the PDF file with GIMP and save in PNG

 * the way that gives you the best quality is the last one, I never used it just because you have to choose several settings to perform the conversion, while all the others are meant to use the best settings automatically (but I don't think they actually do). We could add a section with some suggestions about how to get any file from a LaTeX source but, as I have explained, it's not really something about LaTeX... you can start this section if you want, put what you know or just write the titles, I will help you with that as soon as I have some time, ok? Alessio Damato 17:41, 14 January 2007 (UTC)

I wonder where such information should be put: in LaTeX/Introduction? As for me, although converting DVI to PNG or SVG isn't strictly part of LaTeX, it's a common problem connected with LaTeX and this guide should also inform people how to obtain popular graphic formats from LaTeX. --Derbeth talk 22:28, 18 January 2007 (UTC)

 * I have created LaTeX/Export To Other Formats, it's just a beginning, but I guess this is what you were talking about. Alessio Damato 18:15, 19 January 2007 (UTC)

Licensing
I'm not sure if you are aware that Wikibooks content is not under GPL. We are using GNU Free Documentation License so there is no reason for asking Peter Flynn for permission to re-license his work under GPL.

The problem occurs with text by Tobi Oetiker, which is true GPL'd and cannot be used here. You would have to get agreement from all three authors of "Not So Short Introduction to LaTex2e" to license their work under GFDL.

BTW, from what I see ("GNU Free Documentation License (...) allows to use the text freely as long as the original text is quoted and the original author is referenced"), you don't understand GNU Free Documentation license. Please read the entry about it on Wikipedia. --Derbeth talk 09:36, 17 February 2007 (UTC)

 * now I read it all carefully... sorry but I don't like those bureaucratic issues. To sum up, I can include Peter Flynn work without any problem because it has the same license, but I have to contact Tobias Oetiker again because the GPL is not compatible with GFDL. I'll contact them by email and I'll fix everything. Thanks for your notice. Alessio Damato 15:49, 17 February 2007 (UTC)

title: User talk:Alejo2083


text:
User talk:Hardik thakkar

Hello and welcome to Wikibooks!

Here are some tips to help you get started:
 * You can sign your name on Talk and vote pages using four tildes, like this: ~~~~.
 * Remember to conduct any editing experiments in the sandbox.
 * If you're a Wikipedian, see Wikibooks for Wikipedians for a primer on how things work here (it's a little different).
 * If you want to base your work here on materials from Wikipedia, please use WB:RFI to bring the material over in compliance with the GFDL.
 * If you're an instructor and plan on using wikibooks for a class project, see Guidelines for class projects
 * Please say hello at the Staff Lounge with any questions or ideas.
 * Eventually, you might want to read the Manual of Style and Policies and Guidelines.
 * Please take a look at Naming policy before starting a new book.
 * Remember to maintain a Neutral point of view.
 * Explore, be bold in editing pages, and have fun!

You will find more resources in Community Portal. If you want to ask a question, visit the Study help desk, the Staff lounge, IRC channel or ask me personally on my talk page.

Good luck! -- Herby talk thyme 14:22, 22 November 2006 (UTC)

title: User talk:Hardik thakkar


text:
User talk:Sjsu hardik

Hello and welcome to Wikibooks!

Here are some tips to help you get started:
 * You can sign your name on Talk and vote pages using four tildes, like this: ~~~~.
 * Remember to conduct any editing experiments in the sandbox.
 * If you're a Wikipedian, see Wikibooks for Wikipedians for a primer on how things work here (it's a little different).
 * If you want to base your work here on materials from Wikipedia, please use WB:RFI to bring the material over in compliance with the GFDL.
 * If you're an instructor and plan on using wikibooks for a class project, see Guidelines for class projects
 * Please say hello at the Staff Lounge with any questions or ideas.
 * Eventually, you might want to read the Manual of Style and Policies and Guidelines.
 * Please take a look at Naming policy before starting a new book.
 * Remember to maintain a Neutral point of view.
 * Explore, be bold in editing pages, and have fun!

You will find more resources in Community Portal. If you want to ask a question, visit the Study help desk, the Staff lounge, IRC channel or ask me personally on my talk page.

Good luck! -- Herby talk thyme 14:37, 22 November 2006 (UTC)

title: User talk:Sjsu hardik


text:
Switches, Routers, Bridges and LANs

Contents

 * Introduction
 * Bridges
 * Routers
 * Network Architecture
 * Switching Technology
 * Advanced Topics

title: Switches, Routers, Bridges and LANs


text:
User talk:Xcentaur

Hi XC!

Thanks for having a look at the Organic Chem book. Pete and I are the main contributors at the moment, but things change over time. Do have a go at adding sections you think are needed for your content. If we think the section goes somewhere else we can always discuss it and move it if necessary. We'd rather have a section in the 'wrong' place than no section at all!

Hwyl!

Ewen 15:09, 22 November 2006 (UTC)

PS I'll put this page on my watchlist so if you reply here I'll pick it up. Of course, discussing a particular page should be done on that page's talk page.

Reorganisation?
Talk:Organic_Chemistry

A bit of constructive criticism to consider! Ewen 20:21, 30 January 2007 (UTC)

title: User talk:Xcentaur


text:
User talk:Pv2022

Hello and welcome to Wikibooks!

Here are some tips to help you get started:
 * You can sign your name on Talk and vote pages using four tildes, like this: ~~~~.
 * Remember to conduct any editing experiments in the sandbox.
 * If you're a Wikipedian, see Wikibooks for Wikipedians for a primer on how things work here (it's a little different).
 * If you want to base your work here on materials from Wikipedia, please use WB:RFI to bring the material over in compliance with the GFDL.
 * If you're an instructor and plan on using wikibooks for a class project, see Guidelines for class projects
 * Please say hello at the Staff Lounge with any questions or ideas.
 * Eventually, you might want to read the Manual of Style and Policies and Guidelines.
 * Please take a look at Naming policy before starting a new book.
 * Remember to maintain a Neutral point of view.
 * Explore, be bold in editing pages, and have fun!

You will find more resources in Community Portal. If you want to ask a question, visit the Study help desk, the Staff lounge, IRC channel or ask me personally on my talk page.

Good luck! -- Herby talk thyme 15:57, 22 November 2006 (UTC)

title: User talk:Pv2022


text:
User talk:Kjnawal

Hello and welcome to Wikibooks!

Here are some tips to help you get started:
 * You can sign your name on Talk and vote pages using four tildes, like this: ~~~~.
 * Remember to conduct any editing experiments in the sandbox.
 * If you're a Wikipedian, see Wikibooks for Wikipedians for a primer on how things work here (it's a little different).
 * If you want to base your work here on materials from Wikipedia, please use WB:RFI to bring the material over in compliance with the GFDL.
 * If you're an instructor and plan on using wikibooks for a class project, see Guidelines for class projects
 * Please say hello at the Staff Lounge with any questions or ideas.
 * Eventually, you might want to read the Manual of Style and Policies and Guidelines.
 * Please take a look at Naming policy before starting a new book.
 * Remember to maintain a Neutral point of view.
 * Explore, be bold in editing pages, and have fun!

You will find more resources in Community Portal. If you want to ask a question, visit the Study help desk, the Staff lounge, IRC channel or ask me personally on my talk page.

Good luck! -- Herby talk thyme 16:33, 22 November 2006 (UTC)

title: User talk:Kjnawal


text:
User talk:81.177.14.26

Thanks for experimenting with Wikibooks. Your test worked, and has now been removed. Please use Sandbox for any other tests you want to do, since testing material in modules will normally be removed quickly. Please see the welcome page if you would like to learn more about contributing to our project. Thanks. -- Herby talk thyme 17:03, 22 November 2006 (UTC)

Welcome to Wikibooks. We invite everyone to contribute constructively to our collection. Take a look at the welcome page if you would like to learn more about contributing. However, unconstructive edits are considered vandalism, and if you continue in this manner you may be blocked from editing without further warning. Please stop, and consider improving rather than damaging the hard work of others. Thanks. -- Herby talk thyme 17:08, 22 November 2006 (UTC)

Editing from this IP has been temporarily suspended due to consistent vandalism and failure to heed warnings. --Swift 18:46, 22 November 2006 (UTC)

title: User talk:81.177.14.26


text:
GIMP/Remove Coherent Noise

Interference or other regular patterns overlaid on an image can be introduced by a variety of sources, including:
 * Electromagnetic interference in the environment of the device collecting the image;
 * Noise in a transmitted image such as a television still due to analogue transmission interference or degradation of media;
 * The texture of the paper that the image was printed on, particularly if it was printed in a cheap magazine or newspaper.

Attempting to remove these by ordinary image space techniques such as replicating the pattern and subtracting it would be extremely difficult and unlikely to be completely successful. Sometimes interference can be hidden by downscaling or blurring, but this is rarely a satisfactory solution. Sometimes convolutions can be used, but this is an advanced technique.

Since regular patterns have a very small bandwidth in the image's spectrum, a simple and effective technique for dealing with these problems is to identify the interfering features in the power spectrum image produced by Fourier analysis, eliminate them, and convert back to image space.

In order to fully understand what you are doing here, you should know the basic principles of Fourier analysis; anyway, following this step-by-step how-to will let you removing any unwanted regular pattern over the picture you want.

Installing all the necessary software
''This guide is Linux-oriented, mainly on Ubuntu Linux. Since Gimp is multi-platform, this section could be generalized to any OS. Please do it if you know how to do it''

First we have to install all the necessary software. All you need is available for free on Internet.

On Linux, you have to download and install:
 * Gimp (obviously!) www.gimp.org
 * The gimptool utility: it should be within Gimp. Several Linux distributions put it in a different package. On Debian and Ubuntu it is called libgimp2.0-dev
 * fftw, a library to calculate the Fast Fourier Transform of any signal. You can get it from www.fftw.org. It is available on Ubuntu and Debian repositories as fftw3 and fftw3-dev
 * the Fourier Gimp plug-in, you can get it from . There is no package for Debian/Ubuntu, you have to install it from the source.

On Windows, to install the Fourier Gimp plug-in download the "Binaries for Windows" from http://people.via.ecp.fr/~remi/soft/gimp/gimp_plugin_en.php3#fourier and extract its contents into the Gimp plug-ins directory (.gimp-2.x\plug-ins in your user directory or C:\Program Files\GIMP-2.x\lib\gimp\2.0\plug-ins).

An example of coherent noise
On the right, you see the picture of a flower with a coherent noise pattern on it. One might get a picture like this using a scanner. It is evident that the disturbance we want to remove is all over the picture, so it would be very difficult to remove with traditional means, such as blurring, sharpening or cloning. It is regular pattern, so it should be easy to remove in the frequency domain. Unfortunately, removing the coherent noise will cause the removal of some information that is contained in the same frequencies as the pattern. It is very difficult to preserve that information, and it will not be considered in this tutorial.

Edit the image

First open the image with Gimp. If it's coloured, it will be in RGB format and you'll have to manipulate the RGB layers separately. In order to do so, right-click on the image and choose "Image > Mode > Decompose" (see screen-shot on left). Gimp will create another gray-scale image having the RGB as different layers

(With GIMP 2.6.4 "Decompose" can be found at: "Colors > Components > Decompose...".)

Choose RGB and press OK (see screenshot on right). This way you will get the decomposed picture.

Select the window with the new picture, go to the layers window (if you can't see it, go to "File > Dialogs > Layers" and it will appear) and hide all but one layer, by clicking on the eyes. Then select the remaining layer. In the screen-shot on the left, I have isolated the blue layer. Now you can work on one layer without influencing the others. Let us convert it to its spectrum using the FFT plug-in: right-click on the picture and go to "Filters > Generic > FFT Forward" (see again the screen-shot on left). Now you can manipulate the spectrum of the blue layer of the picture. Note: strictly speaking, the Fourier transform of a signal is made of amplitude and phase; Gimp will show you only the amplitude, and that is the only thing you can edit, but it is enough for our purpose.

Looking at the spectrum you should be able to see bright small spots. Those represent the spectrum of the noise you want to remove. Since it was very regular, its power will be very concentrated in the frequency domain. In the picture on the right, you can see the spectrum of the red layer, with two blinking arrows pointing where those spots are. The red layer was chosen just because the spots were more evident (that also means that most of the noise was contained in the red layer). All you have to do now is to delete them. If you were thinking about using the Erase tool, that's not such a good idea, because deleting the information completely will cause a sharp change in the spectrum, thus introducing even more coherent noise. You have to delete them smoothly. One way is to use the Blur tool - since it has an "averaging" effect; if you use it on the bright spots, you will actually decrease its magnitude without deleting them completely. Another possibility is to use the paintbrush tool with a mid-grey colour (808080 in hexadecimal notation). You can not know exactly where the noise ends and where the information you want to keep starts. You might have to experiment a bit to get a good result.

After you have finished deleting the spots, you have to convert it back to the image space domain by performing the inverse FFT. Right-click on the picture and choose "Filters > Generic > FFT Inverse" as shown in the picture on the left. Do the same for all the three layers.

After editing all the layers (remember to perform the inverse FFT on all of them!), you must mix them to get your RGB picture back. Right-click on the picture and choose "Image > Mode > Compose" (see screen-shot on right). Here is your picture!

The result is on the left. There is still some noise, but the picture is much better than the original!

title: GIMP/Remove Coherent Noise


text:
Adventist Youth Honors Answer Book/First aid/Hypothermia

Hypothermia is caused by continued exposure to low or rapidly falling temperatures, cold moisture, snow, or ice. Those exposed to low temperatures for extended periods may suffer ill effects, even if they are well protected by clothing, because cold affects the body systems slowly, almost without notice. As the body cools, there are several stages of progressive discomfort and disability. The first symptom is shivering, which is an attempt to generate  heat by repeated contractions of surface muscles. This is followed by a feeling of listlessness, indifference, and drowsiness. Unconsciousness can follow quickly. Shock becomes evident as the victim’s eyes assume a glassy stare, respiration becomes slow and shallow, and the pulse is weak or absent. As the body temperature drops even lower,  peripheral circulation decreases and the extremities become susceptible  to  freezing. Finally, death results as the core temperature of the body approaches 80 °F (27 °C). The steps  for treatment of hypothermia are as follows:
 * 1) Carefully  observe  respiratory  effort  and  heart beat; CPR may be required while the warming process is underway.
 * 2) Rewarm the victim as soon as possible.  It may be  necessary to treat other injuries  before the victim can be moved to a warmer place.  Severe bleeding must be controlled and   fractures splinted over clothing before the victim is moved.
 * 3) Replace wet or frozen clothing and remove anything that constricts the victim’s arms, legs, or fingers, interfering with circulation.
 * 4) If the victim is inside a warm  place and is conscious, the most effective method of warming is immersion in a tub of warm (100° to 105 °F or 38° to 41 °C) water.  The water should be warm to the elbow - never hot.  Observe closely for signs of respiratory failure and cardiac arrest (rewarming shock).   Rewarming shock can be minimized by warming the body trunk before the limbs to prevent vasodilation in the  extremities  with  subsequent  shock  due to blood volume shifts.
 * 5) If a tub is not available, apply external heat to both sides of the victim. Natural body heat (skin to skin) from two rescuers is the best method. This is called “buddy warming.”   If this is not practical, use hot water bottles or an electric rewarming blanket.  Do not place the blanket or bottles next to bare skin, however, and be careful to monitor the temperature of the artificial heat source, since the victim is very susceptible to burn injury. Because the victim is unable to generate adequate body heat, placement under a blanket or in a sleeping bag is not sufficient treatment.
 * 6) If the victim is conscious, give warm liquids to drink.  Never give alcoholic beverages or allow the victim to smoke.
 * 7) Dry the victim thoroughly if water is used for rewarming.
 * 8) As  soon  as  possible,  transfer  the  victim  to  a definitive care facility.  Be alert for the signs of respiratory  and  cardiac  arrest  during  transfer, and keep the victim warm.

|


text:
User talk:Urhixidur

Hello and welcome to Wikibooks!

Here are some tips to help you get started:
 * You can sign your name on Talk and vote pages using four tildes, like this: ~~~~.
 * Remember to conduct any editing experiments in the sandbox.
 * If you're a Wikipedian, see Wikibooks for Wikipedians for a primer on how things work here (it's a little different).
 * If you want to base your work here on materials from Wikipedia, please use WB:RFI to bring the material over in compliance with the GFDL.
 * If you're an instructor and plan on using wikibooks for a class project, see Guidelines for class projects
 * Please say hello at the Staff Lounge with any questions or ideas.
 * Eventually, you might want to read the Manual of Style and Policies and Guidelines.
 * Please take a look at Naming policy before starting a new book.
 * Remember to maintain a Neutral point of view.
 * Explore, be bold in editing pages, and have fun!

You will find more resources in Community Portal. If you want to ask a question, visit the Study help desk, the Staff lounge, IRC channel or ask me personally on my talk page.

Good luck! -- Herby talk thyme 19:07, 22 November 2006 (UTC)

title: User talk:Urhixidur


text:
User talk:Moka989

Hello and welcome to Wikibooks!

Here are some tips to help you get started:
 * You can sign your name on Talk and vote pages using four tildes, like this: ~~~~.
 * Remember to conduct any editing experiments in the sandbox.
 * If you're a Wikipedian, see Wikibooks for Wikipedians for a primer on how things work here (it's a little different).
 * If you want to base your work here on materials from Wikipedia, please use WB:RFI to bring the material over in compliance with the GFDL.
 * If you're an instructor and plan on using wikibooks for a class project, see Guidelines for class projects
 * Please say hello at the Staff Lounge with any questions or ideas.
 * Eventually, you might want to read the Manual of Style and Policies and Guidelines.
 * Please take a look at Naming policy before starting a new book.
 * Remember to maintain a Neutral point of view.
 * Explore, be bold in editing pages, and have fun!

You will find more resources in Community Portal. If you want to ask a question, visit the Study help desk, the Staff lounge, IRC channel or ask me personally on my talk page.

Good luck! -- Herby talk thyme 19:16, 22 November 2006 (UTC)

Subaru: Rallying for the Impreza
1. The Subaru Subaru USA

1.1 Impreza The impreza is a.

1.2 Impreza WRX: The impreza is a.

1.3 Impreza WRX STI: The impreza is a.

1.4 Impreza WRX STI Limited The impreza is a.

Sandbox
Please use the sandbox and check out the links above before you try another new page - thanks -- Herby talk thyme 17:18, 24 November 2006 (UTC)

title: User talk:Moka989


text:
Horticulture/Hedges

Hedges are groups of plants planted in rows to provide structure to a garden, or as screens. They are generally kept pruned in geometric forms as well.

The most important characteristic making a plant suitable for hedging is that it should tolerate hard pruning. Plants that branch frequently are also preferable.

Hedges are maintained through regular shearing, or in some cases through pollarding.

Common problems for hedges include invasion by weed plants, dying out at the bottom, and improper plant selection, and inconsistent maintenance.

/Design

title: Horticulture/Hedges


text:
Horticulture/Powdery Mildew

Powdery mildew is a fungal disease that affects a wide range of garden plants. It is easily identified, as its symptoms are quite distinctive. Infected plants will display white powder-like spots on the upper surfaces of the leaves and stems. The lower leaves are the most affected, but the mildew can appear on any part of the plant that shows above the ground. As the disease progresses, the spots get larger and thicker, in many cases forming a solid mat over the entire infected surface. Severe infections can cause stunting, distorted foliage, leaf drop, and may eventually be fatal on some plants if left uncontrolled.

Typically powdery mildew only occurs on the upper surfaces, a similar but unrelated group of fungi that grow on the lower sides of leaves are downy mildews.

Life Cycle
The fungi that cause powdery mildews generally feed only on the epidermal cells of the plant, which they penetrate using organs called haustoria.

In early spring, the overwintering bodies release spores which are spread by wind or water splashing onto the leaves and other plant parts. The fungi then spread over the plants' surfaces, while also penetrating the epidermal cells with haustoria, which are short, specialized hyphae. The fungi that cause powdery mildews generally feed only on the epidermal cells of the plant.

During the growing season the fungus continually produces conidiospores, which reinfect the plant or are spread to other hosts.

Late in the season, specialized fruiting bodies called cleistothecia are produced, which either overwinter on the soil surface or release aeciospores, which infect the next years' buds. Cleistothecia are visible to the eye as small yellow to black dots.

Host Range
The various species of powdery mildew affect a wide variety of plants in hundreds of genera.

title: Horticulture/Powdery Mildew


text:
Talk:Horticulture/Powdery Mildew

Powdery mildew in grape
Erysiphe necator (or Uncinula necator) causes powdery mildew in grapes. It produces common odors such as 1-octen-3-one and (Z)-1,5-octadien-3-one.

Powdery mildew in onions
The fungus causing powdery mildew in onions is Leveillula taurica (known as Oidiopsis tauricaby its anamorph) - also attacking the artichoke.

title: Talk:Horticulture/Powdery Mildew


text:
Radiation Oncology/Radiobiology/Linear-Quadratic

Linear-Quadratic Formalism

Linear-quadratic model

 * A model which describes cell killing, both for tumor control and for normal tissue complications
 * Most common underlying biological rationale is that radiation produces a double strand DNA break (DSB) using a single radiation track
 * Individual DSB can be repaired, with first order kinetics and half-life T1/2
 * If more than one unrepaired DSB is present in the cell at the same time (arising from two separate radiation tracks), a misjoining can produce a lethal lesion (e.g. dicentrics)
 * The two separate DSB can happen at different times during treatment, allowing for repair of first DSB prior to misjoining with the second DSB
 * A single radiation track can also give rise to a lethal lesion by itself (e.g. point mutation in vital gene, deletion eliminating vital gene, induced apoptosis, etc)
 * In the LQ formalism, the yield of lethal lesions is the sum of lethal lesions produced from a single radiation track (which are linearly related to dose, αD) and lethal lesions produced from two radiation tracks (which are quadratically related to dose, βD2)
 * Y = αD + βD2
 * Because the two separate DSB can be repaired prior to resulting in a lethal event, the second component is modified by the Lea-Catcheside time factor (G) to show dependence on dose protraction. For single fractions, G=1
 * Y = αD + GβD2
 * Lethal lesions are thought to follow Poisson distribution from cell to cell. Therefore, the surviving fraction (SF) is
 * SF = exp -(Y)
 * This leads to the standardized LQ equation
 * SF = exp -(αD + GβD2)

Protracted Radiation
$$SF = \exp -(\alpha D + \beta D^2)$$
 * SF = surviving fraction

 * First proposed by Douglas and Fowler in 1972 (PMID 1265229 - Douglas BG and Fowler JF. The effect of multiple small doses of X-rays on skin reactions in the mouse and a basic interpretation. Radiat Res 66, 401-26, 1976.)

E = -ln SF
 * E = biological radiation effect

$$ETD = E/\alpha = D[1 + D(\beta/\alpha)] = D \times RE$$
 * ETD = extrapolated tolerance dose
 * D = total dose (Gy)
 * RE = relative effectiveness per unit dose

For fractionated treatments: $$RE = 1 + dn(\beta/\alpha)$$
 * d = dose per fraction (Gy)
 * n = the number of total fraction

For protracted irradiation (constant dose rate): $$RE = 1 + (2R/\mu)(\beta/\alpha)\left\{1 - (1/\mu)T\left[ 1 - \exp(-\mu T)\right]\right\}$$
 * R = dose rate, LDR (Gy/hr)
 * $$\mu$$ = sublethal damage repair exponential time constant (1/hr).
 * $$\mbox{also, } \mu = \frac{\ln 2}{T_{\tfrac{1}{2}}} \mbox{, where } T_{\tfrac{1}{2}} \mbox{ is the half life of sublethal damage repair}$$
 * T = treatment time (hr)

is approximately the same as,
 * $$RE = 1 + (2R/\mu)(\beta/\alpha)\left\{1 - (1/\mu)T\right\}$$,
 * for values of T: 10 hr > T > 100 hr.

 * Glasgow; 1998 PMID 9572622 -- "The linear-quadratic transformation of dose-volume histograms in fractionated radiotherapy." (Wheldon TE, Radiother Oncol. 1998 Mar;46(3):285-95.)
 * Radiobiological transformation of physical DVH to incorporate fraction size effects
 * Outcome: "hot spots" and "cold spots" are further from mean than physical distributions indicate; particularly important in plans with significant dose heterogeneity
 * Conclusion: LQ-DVH should be computed in parallel with conventional DVHs

LQ and High Fractional Dose

 * Duke; 2008 PMID 18725110 -- "The linear-quadratic model is inappropriate to model high dose per fraction effects in radiosurgery." (Kirkpatrick JP, Semin Radiat Oncol. 2008 Oct;18(4):240-3.)
 * Counterpoint argument to PMID 18725109.
 * LQ model does not reflect vascular and stromal damage produced at high doses per fraction, it also ignores impact of radioresistant subpopulations of cells such as cancer stem cells

 * Columbia; 2008 PMID 18725109 -- "The linear-quadratic model is an appropriate methodology for determining isoeffective doses at large doses per fraction." (Brenner DJ, Semin Radiat Oncol. 2008 Oct;18(4):234-9.)
 * Point argument to PMID 18725110
 * Linear quadratic model is reasonably well validated for doses up to 10 Gy/fraction, and could be reasonably used to about 18 Gy/fraction

Extended LQ Models

 * Ohio State; 2010 PMID 20610850 -- "A generalized linear-quadratic model for radiosurgery, stereotactic body radiation therapy, and high-dose rate brachytherapy." (Wang JZ, Sci Transl Med. 2010 Jul 7;2(39):39ra48.)
 * Generalized LQ model (gLQ) developed. Compared to in vitro data. Able to extrapolate up to 11-13 Gy from low dose data
 * UT Southwestern; 2008 PMID 18262098 -- "Universal survival curve and single fraction equivalent dose: useful tools in understanding potency of ablative radiotherapy." (Park C, Int J Radiat Oncol Biol Phys. 2008 Mar 1;70(3):847-52.)
 * Hybridization of two classic radiobiologic models: LQ model and multi-target model. LQ model good for conventionally fractionated therapy; multi-target model good for high (ablative) fractional doses seen in SBRT
 * Allows for easier conversion of doses


text:
Talk:Collaborative Problem-Solving in Educational Settings

This is my second request to have the page deleted. I am the origional author and there have been no contributors. Please delete.

 * There have been contributions to this book by multiple people. Forgive us for being skeptical of your claim to be the original author, but we have seen no evidence of that other than your claim.  Further, this book has survived a vote for deletion, and there have been other contributors. --Jomegat (talk) 12:42, 30 April 2008 (UTC)

I believe what the person above is saying is that he or she wrote the article, not the actual book. I have to say, this explanation does not jibe with my understanding of Collaborative Problem Solving, nor with my experiences using it. It does bring up some very good questions for me to think about and may help explain why the people I have been trying to convince to use it will not.