text:
C Programming/Serialization

Serialization
It is often necessary to send or receive complex data structures to or from another program that may run on a different architecture or may have been designed for different version of the data structures in question. A typical example is a program that saves its state to a file on exit and then reads it back when started.

The 'send' function will typically start by writing a magic identifier and version to the file or network socket and then proceed to write all the data members one by one (i.e. in serial). If variable length arrays are encountered (e.g. strings), it will either write a length followed by the data or it will write the data followed by a special terminator. The format is often XML or binary; in the latter case the htonl set of macros may come in handy.

The 'receive' function will be nearly identical: it will read all the items one by one. Variable length arrays are either handled by reading the count followed by the data, or by reading the data until the special terminator is reached.

Since these two functions often follow the same pattern as the declaration of the data(structures), it would be nice if they could all be generated from a common definition.

X-Macros
X-Macros uses the preprocessor to force the compiler to compile the same piece of text more than once. Sometimes a special file (with extension .def) is included multiple times. For example variables.def may look like this : INT(value) INT(shift)

In this example the C programming will then look like this : ... ... printf ("version=1\n"); ...
 * 1) define INT(var) int var;
 * 2) include "variables.def"
 * 3) undef INT
 * 1) define INT(var) printf (#var "=%d\n", var);
 * 2) include "variables.def"
 * 3) undef INT

If including a separate file multiple times is undesirable, another macro can be used. For example : INT(shift) The #includes can then be replaced with calls to the macro.
 * 1) define VARIABLES INT(value) \

Using this method, one can also pass in the name(s) of (an)other macro(s) that can operate on the list of values. For example: _(shift) ... VAR_LIST(VAR_INT_DECL) ... printf ("version=1\n"); VAR_LIST(VAR_INT_PRINTF) ...
 * 1) define VAR_LIST(_) _(value) \
 * 1) define VAR_INT_DECL(var) int var;
 * 1) define VAR_INT_PRINTF(var) printf (#var "=%d\n", var);

This does not require the redefinition of macros and can make the code easier to understand and maintain.

X-Macros are also particularly useful for keeping mappings between strings and enumerated types synchronized.

Serialization with versioning
Suppose we want to add additional variables to the above example, but we still want the program to be able to read the old version 1 files. Then we would add a version parameter and a default value parameter to the list processing macros: _(shift,1,0) \ _(mask,2,0xffff) ... int inputVer; VAR_LIST(VAR_INT_DECL) ... scanf ("version=%d", &inputVer); VAR_LIST(VAR_INT_SCN) ... printf ("version=2\n"); /* Always output at highest known version */ VAR_LIST(VAR_INT_PRT) ...
 * 1) define VAR_LIST(_) _(value,1,0) \
 * 1) define VAR_INT_DECL(var,varVer,default) int var;
 * 1) define VAR_INT_SCN(var,varVer,default) if (varVer <= inputVer) scanf (#var "=%d", &var); else var = default;
 * 1) define VAR_INT_PRT(var,varVer,default) printf (#var "=%d\n", var);

title: C Programming/Serialization


text:
C Programming/Coroutines

A little known fact is that most C implementations have built-in primitives that can be used for cooperative multitasking / coroutines. They are setcontext and setjmp.

setjmp
The function  is used in a pair with   to transfer execution to a different point in the code. It relies on an existing  declaration.

stores the current execution point in memory, which remains valid as long as the containing function doesn't return. It initially returns. Control is returned to  once   is called with the original   and the replacement return value.

Note that jmp_buf is passed to setjmp without using the address-of operator.

The easiest way to understand setjmp and longjmp, is that setjmp stores the state of the cpu which includes program counter, stack pointer, all the registers, including the bits of the flags register, at the location pointed to by jmp_buf, which is defined some LEN+1, which is enough bytes to store the registers of whatever CPU is involved. The longjmp(buf), never returns, because it restores the CPU from the contents of struct jmp_buf buf previously set by a previous call the setjmp, so execution begins from after setjmp was called, but the return value of setjmp is not 0, but whatever value was used in the second parameter to longjmp. This is similar to the fork system call, which returns 0 to the child process, and the PID of the child process to the parent.

The internet suggests co-routines are useful for implementing software as state machines cooperating, such as lexer processing input text and emitting tokens, so that a parser can decide to store the token and ask for the next one, or to act on its current set of token. This is not multithreaded programs synchronising on data, with possibly race conditions if a bug forgets to acquire a lock, but with setjmp and longjmp, seems to be cooperative processes that guarantee only one process will run at a time, with no worries about context switches waking up sleeping processes ( using separate jmp_buf static locations, each process can call setjmp for its own jmp_buf, before calling longjmp later on if zero was returned, or continue a loop to process shared data for non-zero returns).

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

title: C Programming/Coroutines


text:
User:Msg~enwikibooks

hello :]

title: User:Msg~enwikibooks


text:
User talk:Kittieskull

Come introduce yourself at the new users page. If you have any questions, you can ask there or contact me personally. --Girdi 21:01, 3 December 2007 (UTC)

title: User talk:Kittieskull


text:
User talk:Ajeeter

Come introduce yourself at the new users page. If you have any questions, you can ask there or contact me personally. --Girdi 21:01, 3 December 2007 (UTC)

title: User talk:Ajeeter


text:
User talk:Mpozzi

Come introduce yourself at the new users page. If you have any questions, you can ask there or contact me personally. --Girdi 21:01, 3 December 2007 (UTC)

title: User talk:Mpozzi


text:
User talk:Mschel

Come introduce yourself at the new users page. If you have any questions, you can ask there or contact me personally. --Girdi 21:01, 3 December 2007 (UTC)
 * Hey! Thank you for the welcome message. I would go introduce myself at the new users page, but it seems that one is supposed to have a question when posting there, and I currently do not have any questions. I decided to try and help out since I have strongly benefited from several of the books here, and felt is only proper to give back a little in return for what I have received. I will probably mainly confine myself to minor edits such as spelling corrections. --Mark (Mschel) 02:25, 10 December 2007 (UTC)

title: User talk:Mschel


text:
User talk:Mlmcadoo

Come introduce yourself at the new users page. If you have any questions, you can ask there or contact me personally. --Girdi 21:01, 3 December 2007 (UTC)

title: User talk:Mlmcadoo


text:
User talk:Anonymouse

Welcome to Wikibooks, Anonymouse!

Welcome!
Welcome to Wikibooks:Chess, glad you joined. Please ask if there is anything that doesn't make sense. I will do my best to make it clear. SunCreator (talk) 12:10, 29 May 2008 (UTC)

English Defence
The English Defence or English Defense(American spelling) is different from the English opening, see  , English Defence. In wikibooks we have the page Chess/English_Defence, it is not often played, not very good and not well known hence some confusion with the English Opening. SunCreator (talk) 12:13, 29 May 2008 (UTC)

Template:Elements of chess strategy/Navigation
Have created a navigator for the Elements of chess strategy book, that you might like to use.

It's basically a copy of the navigator used in the Chess book, see for example it's used at the end of this page Chess/Playing_The_Game. SunCreator (talk) 22:03, 30 May 2008 (UTC)

 * Oh thanks. Never could have thought of that one myself.

Anonymouse--nerd and proud of it (talk) 00:36, 31 May 2008 (UTC)
 * By the way, is there a way to redirect the "previous" and "next" subpage name links? They're both redlinks.

 * The previous and next are the 2nd and third option on the navigator.
 * Example SunCreator (talk) 21:08, 25 June 2008 (UTC)

Chess Opening Theory/ECO index
Thanks for the effort your putting into Chess Opening Theory/ECO index I can only imagine how time consuming and tedious doing that can be. 21:09, 25 June 2008 (UTC)

Najdorf Book
Looking forward to your book on the najdorf. I'm sure that will be quite popular. SunCreator (talk) 21:15, 25 June 2008 (UTC)

Four Knights' Game ECO index
On Chess/ECOC moves don't seem correct for Four Knights' Game, Marshall Variation and Rubinstein Variation. SunCreator (talk) 13:41, 11 March 2009 (UTC)
 * Now fixed thanks to Oleander. SunCreator (talk) 12:49, 12 March 2009 (UTC)

title: User talk:Anonymouse


text:
User talk:Somerset~enwikibooks

Come introduce yourself at the new users page. If you have any questions, you can ask there or contact me personally. --Girdi 21:02, 3 December 2007 (UTC)

Your account will be renamed
Hello,

The developer team at Wikimedia is making some changes to how accounts work, as part of our on-going efforts to provide new and better tools for our users like cross-wiki notifications. These changes will mean you have the same account name everywhere. This will let us give you new features that will help you edit and discuss better, and allow more flexible user permissions for tools. One of the side-effects of this is that user accounts will now have to be unique across all 900 Wikimedia wikis. See the announcement for more information.

Unfortunately, your account clashes with another account also called Somerset. To make sure that both of you can use all Wikimedia projects in future, we have reserved the name Somerset~enwikibooks that only you will have. If you like it, you don't have to do anything. If you do not like it, you can pick out a different name.

Your account will still work as before, and you will be credited for all your edits made so far, but you will have to use the new account name when you log in.

Sorry for the inconvenience.

Yours, Keegan Peterzell Community Liaison, Wikimedia Foundation 23:42, 17 March 2015 (UTC)

Renamed
 This account has been renamed as part of single-user login finalisation. If you own this account you can |log in using your previous username and password for more information. If you do not like this account's new name, you can choose your own using this form after logging in: . -- Keegan (WMF) (talk) 05:31, 19 April 2015 (UTC)

title: User talk:Somerset~enwikibooks


text:
User talk:BlackHawk 848

Come introduce yourself at the new users page. If you have any questions, you can ask there or contact me personally. --Girdi 21:02, 3 December 2007 (UTC)

title: User talk:BlackHawk 848


text:
User talk:Chdenis

Come introduce yourself at the new users page. If you have any questions, you can ask there or contact me personally. --Girdi 21:02, 3 December 2007 (UTC)

title: User talk:Chdenis


text:
User talk:Terry1~enwikibooks

Come introduce yourself at the new users page. If you have any questions, you can ask there or contact me personally. --Girdi 21:02, 3 December 2007 (UTC)

Your account will be renamed
Hello,

The developer team at Wikimedia is making some changes to how accounts work, as part of our on-going efforts to provide new and better tools for our users like cross-wiki notifications. These changes will mean you have the same account name everywhere. This will let us give you new features that will help you edit and discuss better, and allow more flexible user permissions for tools. One of the side-effects of this is that user accounts will now have to be unique across all 900 Wikimedia wikis. See the announcement for more information.

Unfortunately, your account clashes with another account also called Terry1. To make sure that both of you can use all Wikimedia projects in future, we have reserved the name Terry1~enwikibooks that only you will have. If you like it, you don't have to do anything. If you do not like it, you can pick out a different name.

Your account will still work as before, and you will be credited for all your edits made so far, but you will have to use the new account name when you log in.

Sorry for the inconvenience.

Yours, Keegan Peterzell Community Liaison, Wikimedia Foundation 23:49, 17 March 2015 (UTC)

Renamed
 This account has been renamed as part of single-user login finalisation. If you own this account you can |log in using your previous username and password for more information. If you do not like this account's new name, you can choose your own using this form after logging in: . -- Keegan (WMF) (talk) 05:35, 19 April 2015 (UTC)

title: User talk:Terry1~enwikibooks


text:
User talk:Frogzzzzz

Come introduce yourself at the new users page. If you have any questions, you can ask there or contact me personally. --Girdi 21:03, 3 December 2007 (UTC)

title: User talk:Frogzzzzz


text:
User talk:Jwr1594

Come introduce yourself at the new users page. If you have any questions, you can ask there or contact me personally. --Girdi 21:03, 3 December 2007 (UTC)

title: User talk:Jwr1594


text:
User talk:Treyrich41

Come introduce yourself at the new users page. If you have any questions, you can ask there or contact me personally. --Girdi 21:03, 3 December 2007 (UTC)

title: User talk:Treyrich41


text:
Using Ubuntu Linux/Introduction

Welcome to the guide!

Basic Information
Ubuntu (IPA pronunciation (oo-BOON-too )) is a predominantly desktop-oriented Linux distribution, based on Debian GNU/Linux but with a stronger focus on usability, regular releases, and ease of installation at the expense of platform diversity. Ubuntu is sponsored by Canonical Ltd, owned by South African billionaire entrepreneur Mark Shuttleworth.

The name of the distribution comes from the southern African concept of ubuntu which may be rendered roughly as "humanity toward others", "we are people because of other people", or "I am who I am because of who we all are," though other meanings have been suggested.

Kubuntu and Xubuntu are official sub-projects of the Ubuntu project, aiming to bring the KDE and Xfce desktop environments, respectively, to the Ubuntu core. Edubuntu is an official sub-project designed for school environments, and should be equally suitable for children to use at home. Gobuntu was an official sub-project, which was aimed at adhering strictly to the Free Software Foundation's Four Freedoms. However, Gobuntu is no longer being developed, since the regular Ubuntu release now gives users the option of installing only free software. The newest official subproject is JeOS. Ubuntu JeOS (pronounced "Juice") is an efficient variant of the popular desktop and server operating system, configured specifically for virtual appliances.

Ubuntu releases new versions every six months, and always supports them for at least 18 months with daily security fixes and patches to critical bugs. Some releases are designated as Long Term Support (LTS) versions, which have three years support for the desktop and five years for the server editions. It is intended that new LTS versions will be released at two year intervals.

The most recent (and sixth) LTS version, Ubuntu 16.04 (Xenial Xerus), was released on April 21 2016.

Ubuntu aims to use only free software to provide an up-to-date yet stable operating system for the average user. The initial download and installation is of course free of charge. In addition to free updates, and support from the ubuntu community, and this guide, there are a number of other books about Ubuntu Linux, and paid technical support is available from Canonical Ltd.

Features

Ubuntu focuses on usability, including the widespread use of the sudo tool for administrative tasks. The Ubiquity installer allows installing Ubuntu to the hard disk from within the Live CD environment without the need for restarting the computer prior to installation. Ubuntu furthermore emphasises accessibility and internationalization, to reach as many people as possible. As of version 5.04, UTF-8 is the default character encoding. The default appearance of the user interface until Ubuntu 10.04 was called human and was characterised by shades of brown and orange. On 4 March 2010, it was announced that Ubuntu 10.04 would feature a new theme, including new logos. Beginning with release 11.04, Ubuntu will use the new Ubiquity desktop environment, rather than GNOME, by default.

Besides standard system tools and other small applications, Ubuntu comes installed with the following software: the OpenOffice.org productivity suite, the Internet browser Firefox, the instant messenger Pidgin (formerly known as Gaim), and the raster graphics editor GIMP. Several lightweight card and puzzle games are pre-installed, including Sudoku and Chess. Ubuntu has all ports closed by default adding to security, although some people choose to run a firewall in order to keep tabs of incoming and outgoing connections.

Ubuntu offers a fully featured set of applications that work straight from the standard install, but nonetheless fits on a single CD. The live CD allows users to see whether their hardware is compatible before installation to the hard disk. The live CD is then used to install Ubuntu. CDs are mailed free to anyone who requests them, and CD images are available for download. The Ubuntu live CD requires 256 megabytes of RAM, and once installed on the hard disk, Ubuntu needs four gigabytes of hard-disk space. An alternate install disc using the standard debian-installer in text mode is available for download, and is aimed at people with lower system specifications, computer dealers selling systems already installed with Ubuntu, and for complex partitioning including the use of LVM.

With the release of Ubuntu 7.04 in April 2007, the Ubuntu installation process changed slightly. It now supports migration from Windows. The new migration tool imports Windows users' bookmarks, desktop background (wallpaper), and settings for immediate use in the Ubuntu installation.

For Ubuntu there are tools available to create a specific installation CD/DVD. With Wubi, it is possible to install Ubuntu on a Windows partition. It also makes use of the migration tool which imports Windows users' configurations.

Multilingual
Since Ubuntu uses GNOME, the language of the GUI can set up in different languages.

Response
Ubuntu's popularity has climbed steadily since its 2004 debut. It is currently the second most viewed Linux distribution on Distrowatch.com, and was the most accessed on the site in 2005 and 2006. This popularity is borne out by a rise in Google searches for "Ubuntu" since 2004 as compared to shrinking or plateauing numbers for terms related to other major desktop Linux distributions such as "Fedora", "Debian" or "SUSE" over the same period. In a 2007 survey of 38500 DesktopLinux.com users Ubuntu was the most popular distribution, with 30.3 percent of respondents using it.

Ubuntu was awarded the Reader Award for best Linux distribution at the 2005 LinuxWorld Conference and Expo in London. It has been favourably reviewed in online and print publications. Ubuntu won InfoWorld's 2007 Bossie Award for Best Open Source Client OS.

Mark Shuttleworth has stated that there were at least 8 million Ubuntu users at the end of 2006.

Internal Links
../Introduction/
 * ../Introduction for n00bs/
 * ../Introduction for Windows users/
 * ../Introduction for Mac users/
 * ../Introduction for Ubuntu users/
 * ../Introduction for users of other Linux distributions/
 * ../Introduction for users of Unix and/or Unix-like operating systems/
 * ../Introduction for users of other operating systems/

title: Using Ubuntu Linux/Introduction


text:
Talk:Celestia/Celx Scripting/CELX Lua Methods

This is an initial entry of a slightly edited html page origininally authored by Harald Schmidt of the Celestia community. With his permission, it is being converted for use in the Celestia WikiBook where it will be maintained by others. A lot of reformatting has yet to be done, but this seems to be the best place to do it.

I think the tables (lists?) of methods may be best managed if those tables are all on a separate page instead of being included here, with each method specified as a section on that page.

Selden 23:21, 29 November 2007 (UTC)


text:
User:Nroets

[mailto:nroets@gmail.com nroets@gmail.com]

title: User:Nroets


text:
Chess Strategy

""If one piece is badly placed, your whole game is bad."" Siegbert Tarrasch, chess master at the turn of the twentieth century.

Strategy in chess is the overall art of forming a plan. A quote from the second World Champion, Emmanuel Lasker, goes, "A bad plan is better than no plan at all." This implies that the ability to plan and make decisions about what the position calls for is one of the most important parts of playing great chess. Remember: it is not what you call for, it is what the position calls for.

Modern-day chess strategy was, in a sense, discovered by the scientific thinker Wilhelm Steinitz, who was also the first World Champion. This method of evaluating a position, and then making a plan based on this evaluation, was developed in the 19th century. Steinitz's idea was that chess was divided into positional elements, which are listed here:

 * 1. /Development/
 * 2. /Mobility/
 * 3. /The center/
 * 4. /The positions of the kings/
 * 5. /Weak and strong squares/
 * 6. /Pawn structure/
 * 7. /Queenside pawn majority/
 * 8. /Open lines/
 * 9. /Minor pieces/

These elements were further developed by later thinkers like Nimzowitsch, Capablanca and Alekhine, who all made their own contribution to the strategy of the game. Capablanca said himself, in his instructive, timeless, and quintessential primer, Chess Fundamentals, that "in chess the tactics may change but the strategic fundamental principles are always the same, so that Chess Fundamentals is as good now as it was thirteen years ago.... It will be as good a hundred years from now; as long in fact as the laws and rules of the game remain what they are at present." This means that, while openings go in and out of style, and tactics may be refuted, basic chess strategy will always remain the same. It doesn't matter which opening you play, or what style you play in; the rules of chess strategy will always be helpful.

Steinitz's Four Rules of Strategy

 * 1. The right to attack belongs to the side that has a positional advantage, which not only has the right to attack, but the obligation to do so, else the advantage will evaporate. The attack should be concentrated on the weakest square in the opponent's position.
 * 2. If in an inferior position, the defender should be ready to defend and make compromises, or take other measures, such as a desperate counterattack.
 * 3. In an equal position, the opponents should maneuver, trying to achieve a position in which they have an advantage. If both sides play correctly, an equal position will remain equal.
 * 4. The advantage may be a big, indivisible one, or it may be a whole series of small advantages. The goal of the stronger side is to store up the advantages, and then to convert temporary advantages into permanent ones.

Using this Wikibook
This Wikibook assumes that the reader understands the rules of chess and algebraic notation. While it is up to the reader whether he/she should continue further from here, this book lays the foundation for all great chessplayers, as described above.

title: Chess Strategy


text:
Template:Celx:type

Celestia/Celx_Scripting/CELX_Lua_Methods/Celx_ /Templates

title: Template:Celx:type


text:
User talk:Trevsie

Come introduce yourself at the new users page. If you have any questions, you can ask there or contact me personally.--Whiteknight (Page) (Talk) 23:14, 3 December 2007 (UTC)

title: User talk:Trevsie


text:
Template:Celx:v132

1.3.2 /Templates

title: Template:Celx:v132


text:
Template:Celx:v150

1.5.0 /Templates

title: Template:Celx:v150


text:
Template:Celx:arg

 /Templates

title: Template:Celx:arg


text:
User talk:Greeves

As I am not very active here, please see my talk page on Meta-Wiki or the English Wikipedia. Thanks!

title: User talk:Greeves


text:
Template:Celx:func

 /Templates

title: Template:Celx:func


text:
Template:Celx:argdesc

Arguments:

/Templates

title: Template:Celx:argdesc


text:
Chess Strategy/Development

Development
At the beginning of a chess game, both players compete in a process called development. The process of development comprises three equally important main tasks:

 * Moving all pieces to their most advantageous squares.
 * Occupying and attacking (controlling) centre squares. These are: e4, e5, d4, and d5.
 * Hindering the opponent's development without wasting moves (tempo).

Being ahead in development is the aim of the opening. An advanced player can easily convert a lead in development into a larger advantage by way of attack or combination. Hence, the process of development is about being efficient. For a campaign of development to be successful, it must adhere to several laws which can be discerned from the works of Wilhelm Steinitz, Siegbert Tarrasch, and Aron Nimzowitsch:

 * 1) Each piece must be moved only once during the opening.
 * 2) Pawn moves are made only to control center squares, open lines for pieces, or attack more valuable enemy pieces.
 * 3) Pieces should not be placed where they can be attacked by less valuable pieces.
 * 4) First develop the pieces which have fewer options or a certain home.
 * 5) Consider the King's safety at all times.

An advantage in development
An advantage in development is quite easy to spot - you will have more pieces out in the field than your opponent. When possible, try to combine attack and development; try to develop to gain time, to gain tempo(s). For example, after the moves 1.e4 e5 2.Nf3, White has attacked the e5-pawn, forcing Black to defend it. Of course, Black could easily defend the pawn with 2....d6, but this doesn't develop a piece. Black's best moves here are either 2....Nc6, developing and defending, or 2....Nf6, developing and attacking the e4-pawn. An advantage in development is an advantage against your opponent, as you have more pieces out in the field that can easily attack an uncastled king. An important thing to remember about development is that it is a dynamic advantage, that is, if you do not use it immediately it will disappear. This fits in nicely with Steinitz's first law of strategy.

Gambits
Most of the time, gambits are sacrifices to gain a lead in development or position. One example of a gambit to gain time to develop pieces is the Danish Gambit, where White quickly develops their bishops, which can expertly use and control the open diagonals of the board. 1.e4 e5 2.d4 exd4 3.c3 dxc3 4.Bc4 cxb2 5.Bxb2. White has received an enormous lead in development for their comparatively measly two-pawn investment. In this position, Black will try to exploit their material advantage while developing their pieces, while White will aim for a quick attack that will prove the validity of their lead in development. Black can play a countergambit, a sacrifice of one of their pawns to equalize in development. Black normally plays in this position the counter gambit 5....d5!, giving up one of their extra pawns to gain time (to gain a tempo) on the White bishop. 6.Bxd5 Nf6 and White has nothing better than 7.Bxf7+ Kxf7! 8.Qxd8 Bb4+ =/=

Sound or not?
The great master, Steinitz, once said: "The only way to refute a gambit is to accept it." Some gambits don't aim for a lead in development. For example, the Smith-Morra Gambit in the Sicilian Defense goes 1.e4 c5 2.d4 cxd4 3.c3 dxc3 4.Nxc3. This gambit is considered unsound at master level. Although White gets a lead in development, in this case Black expects to eventually catch up. The main reason for this pawn sacrifice was to gain the open c- and d-files for White. Gambits of this nature are considered unsound because of the abstract nature of the advantage; it is disputed whether the open lines are enough for the sacrifice.

What to do if your opponent has a lead in development
If your opponent has a lead in development, the most important thing to do is to get your king safely castled. Remember that if the opponent has a lead in development, they can open lines—right up to your king. That's not good, because open lines to your king mean that pieces can easily get to him, and easy access to the king means mate sooner or later. After the king is safely tucked away in a corner, your next objective is to get out the rest of your pieces. This will refute the pawn sacrifice. The final step is to keep your material advantage until the endgame, or use the extra material to attack the opponent's king.

What to do with a lead in development
Now you have the advantage! Here are the priorities for you, in no particular order:
 * 1) Open lines to the enemy king. If you do this, the enemy king becomes a sitting duck in the center of the board.
 * 2) Keep the opponent's king in the center. The center is normally where all the action takes place, and it is not particularly safe to keep the king where the action is. Also, a centralized king blocks communication from the pieces, which suffer from a lack of coordination.
 * 3) After both of the above are accomplished, try to either mate the king or regain your lost material.

All of these actually make sense, because if your opponent's king is stuck in the center, open lines are like highways leading to the king! The game at right, Grünfeld—Spielmann, went from here '''12....e5! 13.fxe5 Nxe5!! 14.dxe5 d4! 15.Nd1 Bxe5'''. At the cost of a knight, Black has opened up lines in the center. He now has a clear advantage because, despite his piece deficit, the king is wide open and White's pieces are uncoordinated. '''16.e4!? Bxe4 17.Nf2 Bd5 18.Qh3 Qe7 19.Be2 d3!''' The center has been destroyed and White's king loses the game for him. White resigns on move 34 (...Bxe1).

title: Chess Strategy/Development


text:
User talk:Msg~enwikibooks

Welcome message
Hello, and welcome to Wikibooks!

Here are some tips to help you get started:
 * To learn the wiki-markup-language syntax, see Help:Editing.
 * You should sign your name on Talk and vote pages using four tildes, like this: ~~~~
 * There is a box at the top of the edit window that will insert this, too; it looks like part of a signature.
 * Remember to conduct any editing experiments in the sandbox.
 * You can tell the community something about yourself in your userpage.
 * You can get to this page by clicking the tab at the top of the page labeled with your registered username.
 * Wikibooks is a collection of open-source textbooks. (What is Wikibooks).
 * If you are 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 (requests for importation) 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 Reading Room with any questions or ideas.
 * Eventually, you might want to read the Manual of Style and Policies and Guidelines.
 * Help us by participating in policy and guideline creation.
 * 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 Reading Room, IRC channel or ask me personally on my talk page. For site news, see the Bulletin board. It might be a good idea to add that page to your "watchlist" so that you can see when any new information is posted there. You can do that by clicking the tab labeled "watch" at the top of the page.

Good luck! --Panic 23:49, 3 December 2007 (UTC)

Your account will be renamed
Hello,

The developer team at Wikimedia is making some changes to how accounts work, as part of our on-going efforts to provide new and better tools for our users like cross-wiki notifications. These changes will mean you have the same account name everywhere. This will let us give you new features that will help you edit and discuss better, and allow more flexible user permissions for tools. One of the side-effects of this is that user accounts will now have to be unique across all 900 Wikimedia wikis. See the announcement for more information.

Unfortunately, your account clashes with another account also called Msg. To make sure that both of you can use all Wikimedia projects in future, we have reserved the name Msg~enwikibooks that only you will have. If you like it, you don't have to do anything. If you do not like it, you can pick out a different name.

Your account will still work as before, and you will be credited for all your edits made so far, but you will have to use the new account name when you log in.

Sorry for the inconvenience.

Yours, Keegan Peterzell Community Liaison, Wikimedia Foundation 23:29, 17 March 2015 (UTC)

Renamed
 This account has been renamed as part of single-user login finalisation. If you own this account you can |log in using your previous username and password for more information. If you do not like this account's new name, you can choose your own using this form after logging in: . -- Keegan (WMF) (talk) 05:16, 19 April 2015 (UTC)

title: User talk:Msg~enwikibooks


text:
User talk:Scribe1290

Welcome message
Hello, and welcome to Wikibooks!

Here are some tips to help you get started:
 * To learn the wiki-markup-language syntax, see Help:Editing.
 * You should sign your name on Talk and vote pages using four tildes, like this: ~~~~
 * There is a box at the top of the edit window that will insert this, too; it looks like part of a signature.
 * Remember to conduct any editing experiments in the sandbox.
 * You can tell the community something about yourself in your userpage.
 * You can get to this page by clicking the tab at the top of the page labeled with your registered username.
 * Wikibooks is a collection of open-source textbooks. (What is Wikibooks).
 * If you are 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 (requests for importation) 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 Reading Room with any questions or ideas.
 * Eventually, you might want to read the Manual of Style and Policies and Guidelines.
 * Help us by participating in policy and guideline creation.
 * 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 Reading Room, IRC channel or ask me personally on my talk page. For site news, see the Bulletin board. It might be a good idea to add that page to your "watchlist" so that you can see when any new information is posted there. You can do that by clicking the tab labeled "watch" at the top of the page.

Good luck! --Panic 23:49, 3 December 2007 (UTC)

title: User talk:Scribe1290


text:
User talk:Pradeep reddy

Welcome message
Hello, and welcome to Wikibooks!

Here are some tips to help you get started:
 * To learn the wiki-markup-language syntax, see Help:Editing.
 * You should sign your name on Talk and vote pages using four tildes, like this: ~~~~
 * There is a box at the top of the edit window that will insert this, too; it looks like part of a signature.
 * Remember to conduct any editing experiments in the sandbox.
 * You can tell the community something about yourself in your userpage.
 * You can get to this page by clicking the tab at the top of the page labeled with your registered username.
 * Wikibooks is a collection of open-source textbooks. (What is Wikibooks).
 * If you are 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 (requests for importation) 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 Reading Room with any questions or ideas.
 * Eventually, you might want to read the Manual of Style and Policies and Guidelines.
 * Help us by participating in policy and guideline creation.
 * 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 Reading Room, IRC channel or ask me personally on my talk page. For site news, see the Bulletin board. It might be a good idea to add that page to your "watchlist" so that you can see when any new information is posted there. You can do that by clicking the tab labeled "watch" at the top of the page.

Good luck! --Panic 23:49, 3 December 2007 (UTC)

title: User talk:Pradeep reddy


text:
User talk:Nroets

Welcome message
Hello, and welcome to Wikibooks!

Here are some tips to help you get started:
 * To learn the wiki-markup-language syntax, see Help:Editing.
 * You should sign your name on Talk and vote pages using four tildes, like this: ~~~~
 * There is a box at the top of the edit window that will insert this, too; it looks like part of a signature.
 * Remember to conduct any editing experiments in the sandbox.
 * You can tell the community something about yourself in your userpage.
 * You can get to this page by clicking the tab at the top of the page labeled with your registered username.
 * Wikibooks is a collection of open-source textbooks. (What is Wikibooks).
 * If you are 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 (requests for importation) 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 Reading Room with any questions or ideas.
 * Eventually, you might want to read the Manual of Style and Policies and Guidelines.
 * Help us by participating in policy and guideline creation.
 * 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 Reading Room, IRC channel or ask me personally on my talk page. For site news, see the Bulletin board. It might be a good idea to add that page to your "watchlist" so that you can see when any new information is posted there. You can do that by clicking the tab labeled "watch" at the top of the page.

Good luck! --Panic 23:49, 3 December 2007 (UTC)

title: User talk:Nroets


text: Template:User contrib

title: Template:User contrib


text: User talk:61.16.238.115

title: User talk:61.16.238.115


text:
Haskell/Database

Introduction
Haskell's most popular database module is HDBC. HDBC provides an abstraction layer between Haskell programs and SQL relational databases. This lets you write database code once, in Haskell, and have it work with a number of backend SQL databases.

HDBC is modeled loosely on Perl's DBI interface, though it has also been influenced by Python's DB-API v2, JDBC in Java, and HSQL in Haskell. Like how DBI requires DBD in Perl, HDBC requires a driver module beneath it to work.

These HDBC backend drivers exist: PostgreSQL, SQLite, and ODBC (for Windows and Unix/Linux/Mac). MySQL is the most popular open-sourced databases, and there are two drivers for MySQL: HDBC-mysql (native) and HDBC-odbc (ODBC). MySQL users can use the ODBC driver on any MySQL-supported platform, including Linux.

An advantage of using ODBC is that the syntax of the SQL statement is insulated from the different kinds of database engines. This increases the portability of the application should you have to move from one database to another. The same argument for preferring ODBC applies for other commercial databases (such as Oracle and DB2).

PostgreSQL or SQLite
See the HDBC FAQ for more information.

Native MySQL
The native ODBC-mysql library requires the C MySQL client library to be present.

You may need to wrap your database accesses to prevent runtime errors.

ODBC/MySQL
Making HDBC work with MySQL via ODBC is somewhat involved, especially if you do not have root privileges.

 * If your platform doesn't already provide an ODBC library (and most do), install Unix-ODBC. See here for more information.
 * Install MySQL-ODBC Connector. See here for more information.
 * Install Database.HDBC module
 * Install Database.HDBC.ODBC module
 * Add the mysql driver to odbcinst.ini file (under $ODBC_HOME/etc/) and your data source in $HOME/.odbc.ini.
 * Create a test program

Since the ODBC driver is installed using shared library by default, you will need the following env:

export LD_LIBRARY_PATH=$ODBC_HOME/lib

If you do not like adding an additional env variables, you should try to compile ODBC with static library option enabled.

The next task is to write a simple test program that connects to the database and print the names of all your tables, as shown below.

You may need to wrap your database accesses in order to prevent runtime errors.

Connect and Disconnect
The first step of any database operation is to connect to the target database. This is done via the driver-specific connect API, which has the type of:

Given a connect string, the connect API will return  and put you in the IO monad.

Although most programs will garbage-collect your connections when they are out of scope or when the program ends, it is a good practice to disconnect from the database explicitly.

conn->Disconnect

Running Queries
Running a query generally involves the following steps:
 * Prepare a statement
 * Execute a statement with bind variables
 * Fetch the result set (if any)
 * Finish the statement

HDBC provides two ways for bind variables and returning result set:  and. You need to use the functions with s prefix when using, instead of. allows you to use strongly typed data if type safety is very important in your application; otherwise,  is more handy when dealing with lots of database queries. When you use, you assume the database driver will perform automatic data conversion. Be aware there is a performance price for this convenience.

Sometimes, when the query is simple, there are simplified APIs that wrap multiple steps into one. For example, Run and sRun are wrappers of "prepare and execute". quickQuery is a wrapper of "prepare, execute, and fetch all rows".

Transaction
Database transaction is controlled by  and. However, be aware some databases (such as mysql) do not support transaction. Therefore, every query is in its atomic transaction.

HDBC provides  to allow you automate the transaction control over a group of queries.

title: Haskell/Database


text:
Directing Technology/Ethics

Introduction
What are Ethics and how do they relate to Directing Technology?

Ethics can be described as:

1. The discipline dealing with what is good and bad and with moral duty and obligation. 2. A set of moral principles (a theory or system of moral values). 3. The principles of conduct governing an individual or a group. 4 A consciousness of moral importance. 5. A guiding philosophy. Found at:

As Director of Technology, situations may arise at any time and in any degree of frequency which require the existence of a strong code of ethics to be addressed properly. These situations can vary from a personal nature to a professional issue, a legal concern or a sexual matter (among others). Each one may present a dilemma to the Technology Director in regards to how the situation should be handled.

Establishing and enforcing a clear code of ethics within the district should be a primary consideration of the Technology Director while creating guidelines which are to be embraced by the administration, staff and students.

title: Directing Technology/Ethics


text:
User:Paranoidrocker

== Courtney is my name; climbing is my game. ==

title: User:Paranoidrocker


text:
User talk:76.5.108.185

Welcome!
Welcome to Wikibooks, a collection of open-content textbooks! You don't have to log in to read or edit articles on Wikibooks, but creating an account is quick, free and non-intrusive, requires no personal information, and gives you many benefits, including:
 * The use of a username of your choice
 * The ability to view all your contributions via a "My contributions" link
 * Your own user page
 * Your own talk page which, if you choose, also allows users to send you messages without knowing your e-mail address
 * The use of your own personal watchlist to which you can add articles that interest you
 * The ability to rename pages.
 * The ability to upload images
 * The ability to customize the appearance and behavior of the website
 * The eligibility to become an administrator
 * The right to be heard in votes and elections
 * Your IP address will no longer be visible to other users.

We hope that you choose to become a Wikibookian and create an account. Feel free to ask me any questions you may have on my talk page. By the way, make sure to sign your posts and comments with four tildes (~~~~), which will let others know who left it.

– Mike.lifeguard  | talk 02:53, 4 December 2007 (UTC)

title: User talk:76.5.108.185


text:
User talk:Giddonah

Welcome message
Hello, and welcome to Wikibooks!

Here are some tips to help you get started:
 * To learn the wiki-markup-language syntax, see Help:Editing.
 * You should sign your name on Talk and vote pages using four tildes, like this: ~~~~
 * There is a box at the top of the edit window that will insert this, too; it looks like part of a signature.
 * Remember to conduct any editing experiments in the sandbox.
 * You can tell the community something about yourself in your userpage.
 * You can get to this page by clicking the tab at the top of the page labeled with your registered username.
 * Wikibooks is a collection of open-source textbooks. (What is Wikibooks).
 * If you are 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 (requests for importation) 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 Reading Room with any questions or ideas.
 * Eventually, you might want to read the Manual of Style and Policies and Guidelines.
 * Help us by participating in policy and guideline creation.
 * 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 Reading Room, IRC channel or ask me personally on my talk page. For site news, see the Bulletin board. It might be a good idea to add that page to your "watchlist" so that you can see when any new information is posted there. You can do that by clicking the tab labeled "watch" at the top of the page.

Good luck! --Panic 02:57, 4 December 2007 (UTC)

title: User talk:Giddonah


text:
User talk:Evren35

Welcome message
Hello, and welcome to Wikibooks!

Here are some tips to help you get started:
 * To learn the wiki-markup-language syntax, see Help:Editing.
 * You should sign your name on Talk and vote pages using four tildes, like this: ~~~~
 * There is a box at the top of the edit window that will insert this, too; it looks like part of a signature.
 * Remember to conduct any editing experiments in the sandbox.
 * You can tell the community something about yourself in your userpage.
 * You can get to this page by clicking the tab at the top of the page labeled with your registered username.
 * Wikibooks is a collection of open-source textbooks. (What is Wikibooks).
 * If you are 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 (requests for importation) 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 Reading Room with any questions or ideas.
 * Eventually, you might want to read the Manual of Style and Policies and Guidelines.
 * Help us by participating in policy and guideline creation.
 * 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 Reading Room, IRC channel or ask me personally on my talk page. For site news, see the Bulletin board. It might be a good idea to add that page to your "watchlist" so that you can see when any new information is posted there. You can do that by clicking the tab labeled "watch" at the top of the page.

Good luck! --Panic 02:57, 4 December 2007 (UTC)

title: User talk:Evren35


text: Talk:Using Ubuntu Linux/Introduction

title: Talk:Using Ubuntu Linux/Introduction


text:
Talk:Directing Technology/Ethics

Contributors: Bobby Siegfried Jack Tevnan --- Jack Entry - 12/4/07 (4:30pm)

Ethics and Personal Gain Discuss how it is unethical to promote or relegate ideas, etc. for ones own personal gain.

Ethics and Influence Discuss how it is unethical to use a position of power to influence a course of action.

Ethics and Weakness/Ignorance/Complicity Not sure exactly what to discuss here.

The "Talking Shop: School technology coordinator gets lesson in ethics – Explicit Emails" article had so many areas to consider. The Tech director was faced with the ethical decision to report the inapropriate behavior existing in his district even though he was aware of repercussions that had fallen on the last person to "blow the whistle". There was the fact that there were other staff and admin that were aware of the issues and chose to ignore them. Certain menmers of the staff promoting favoritism for other staff. Then there was the harassment the tech director faced once he uncovered the issue and shed light on it.

--- Jack Entry- 12/3/07 (10:30pm)

I figured I would just start it off with an introduction and small explanation of Ethics and how it relates to the Director of Technology.

I know Bobby had some specifics he wanted to cover in regards to policies so I did not want to step on any toes or begin to change too much. Bobby emailed that he was thinking about: policies such as email privacy policies, school technology plans, usage of school servers and client computers.

He also stated that "well written policies often detail how to deal with ethics and set parameters" which I think is very valid and should be included in the section where appropriate. --

title: Talk:Directing Technology/Ethics


text:
Cookbook talk:Cooking for Children

followed wikibookian's suggestion to move book. How can I get rid of wikibookian's message now?

title: Cookbook talk:Cooking for Children


text:
Cookbook talk:Homemade Corned Beef

Corned Beef is meant to be a kind of salted beef, according to the wikipedia article. This recipe seems to describe nothing more than a kind of beef marinade.

The "history" claimed in this article is utter nonsense, and does not belong in an encyclopedia. And the recipe is not much better either, the whole point is that corned beef (American style), is salt cured beef.

title: Cookbook talk:Homemade Corned Beef


text:
Cookbook:Kid-Friendly Pizza

Pizza is a tasty snack that many people all over the world enjoy. It can be fun to eat and even more fun to make! This recipe is specially designed for children to make and eat.

Ingredients:

 * 1 pre-baked whole-grain pizza shell
 * ¼ cup tomato pasta sauce
 * 1 cup shredded pizza cheese
 * ½ cup cubed cooked chicken breast (optional)
 * 1 red bell pepper, diced

Procedure

 * 1) Preheat oven to 350°F.
 * 2) Spread the tomato sauce on the pizza shell.
 * 3) Top it with half of the shredded cheese.
 * 4) Add the chicken and red pepper on top of the pizza crust in whatever design you want. Have fun with it!
 * 5) Sprinkle the rest of the cheese on top.
 * 6) Bake it for 10–12 minutes.

title: Cookbook:Kid-Friendly Pizza


text:
Cookbook:Kid-Friendly Pasta

This easy recipe for pasta is designed for children to make and eat. Make sure to supervise children when cooking.

Ingredients

 * 1 lb whole-wheat spaghetti
 * 2 carrots, cut into thin strips
 * ½ lb green beans
 * ¼ cup tomato pasta sauce

Procedure

 * 1) Bring a pot of water to a boil.
 * 2) Add spaghetti and carrots to the boiling water, and cook for 4 minutes.
 * 3) Add green beans, and cook for another 4 minutes.
 * 4) Meanwhile, heat the tomato sauce.
 * 5) Drain the spaghetti and the vegetables, then mix it with the heated sauce.
 * 6) Add a pinch of salt if needed.
 * 7) Serve.

title: Cookbook:Kid-Friendly Pasta


text:
Cookbook:Peach, Strawberry and Ice Cream Smoothie

The mixture of ice cream and yogurt gives a richer taste to this smoothie. Replacing the peaches with sliced bananas also works well.

Ingredients

 * ½ cup (150 g or 5.3 oz) plain yogurt
 * ½ cup (125 ml or 4.2 oz) vanilla ice cream
 * ½ cup (40 g or 1.4 oz) sliced peaches
 * ½ cup (40 g or 1.4 oz) sliced strawberries

Procedure

 * 1) In a blender, blend the peaches, strawberries, yogurt, and ice cream until smooth.


text:
User:Breakmode/AxiomSetPageLayout

About
Information, in paragraph form.

Topics in 'Axiom Set'

 * Link to page discussioning theorems related to a particular topic
 * Link to page discussioning theorems related to a particular topic
 * Link to page discussioning theorems related to a particular topic

Definitions

 * 1) Statement of Definition 1, links to Definition 1 page
 * 2) Statement of Definition 2, links to Definition 2 page
 * 3) Statement of Definition 3, links to Definition 3 page

Axioms

 * 1) Statement of Axiom 1, links to Axiom 1 page
 * 2) Statement of Axiom 2, links to Axiom 2 page
 * 3) Statement of Axiom 3, links to Axiom 3 page

Theorems

 * 1) Statement of Theorem 1, links to Theorem 1 page
 * 2) Statement of Theorem 2, links to Theorem 2 page
 * 3) Statement of Theorem 3, links to Theorem 3 page

title: User:Breakmode/AxiomSetPageLayout


text:
Talk:Past LSAT Explained/Method of Argument(LR)

Everyone contribute!


text:
Wikijunior:Scottish Gaelic

Fàilte chun na Gàidhlig!
Tha Gàidhlig glè mhath!

I designed this Wikibook for self-learners and have included a few small test yourself sections which are useful for revising.

It may be useful to get your hands on a Gaelic dictionary, and if you receive them, watch and listen to Gaelic programs on the TV and radio, or alternatively there is lots of Gaelic music and even lessons on Youtube.

Gur math a thèid leibh!

Your journey
James Fergusson

Latha math! Is mise Seumus MacFheargais agus tha mi a' fuireach ann am Glaschu. Good day! I am James Fergusson and I live in Glasgow.

Catherine Munro

Hallo. Is mise Catrìona Rothach agus tha mi a' fuireach ann an Inbhir Nis. Hello. I am Catherine Munro and I live in Inverness.

Callum MacAulay

Ciamar a tha thu? Tha mi gu math, tapadh leat. Is mise Calum MacAhmlaigh agus tha mi a' fuireach ann an Nis, air Eilean Leòdhais. How are you? I am good, thank you. I am Calum MacAulay and I live in Ness on the Isle of Lewis.

Jane MacDonald

Is mise Sìne NicDhòmhnaill agus tha mi a' fuireach ann an Slèite, air an Eilean Sgitheanach. Tha i glè shnog. I am Jane MacDonald and I live in Sleat on the Isle of Skye. It is very nice.

Neil MacInnes

Is mise Niall MacAonghais agus tha mi a' fuireach ann an Earra Ghàidheil. I am Neil MacInnes and I live in Argyll.

Mark Douglas

Tha mi a' fuireach ann an Alba Nuadh agus tha mi ag ionnsachadh Gàidhlig aig an sgoil. Tha i math. Ò - is mise Marc Dùghlas! I live in Nova Scotia and I learn Gaelic at school. It is good.

Unit 1
Fàilte gu Glaschu!

Hallò!

It is a busy morning at Sgoil Ghàidhlig Ghlaschu, and James Fergusson is meeting his friends outside his classroom.

Seumus Hallò, a Iain. Ciamar a tha thu? Iain Tha mi math, tapadh leat. Cait a bheil Alasdair? Mairead Madainn math, a Iain. Chan eil Alasdair gu glè mhath. Seumus Oh. Tapadh leat. Nic' Dohmnaill Latha math dhuibh. Seumus agus Iain Latha math.

James Hello, John. How are you? John I am good, thank you. Where is Alastair. Mary Good morning John. Alastair isn't very well. James Oh. Thank you. Mrs. McDonnell Good day to you (all). James and John Good day.

You do not need to learn all of the words in this conversation, but if you can, great!

You will probably regocnise the word Hallò!, from English. It means hello, and is usually used to greet friends. Latha math and Madainn math are more polite and used more formally, like talking to someone you don't know very well or a teacher. Finally Latha math duibh is also used formally.

One of the things you have to get to grips with in Gaelic is that there is a formal and informal set of words. The formal version is also used for plurals when you are speaking to more than two people. To understand this you will need to know the words for 'you' - sibh and thu.

Thu is the informal word for you, and used only when speaking to one person. Sibh is more formal but is also used if you are speaking to more than one person.

For example, Ciamar a tha thu? me

OLD VERSION

Introduction
Scottish Gaelic is closely related to Irish Gaelic. It is in fact believed to have been brought over by Celts emigrating to Scotland. Nowadays though it is confined mainly to the Western Isles of Scotland though there are still smaller communities of speakers in the Highlands, Glasgow, Inverness and Cape Breton Island, Nova Scotia.

I hope that with this book you will be able to learn a little of this fascinating language and be inspired to learn on.

Gur math a thèid leibh! (Good Luck!)

Useful Information
Alphabet

The Gaelic alphabet contains only 18 letters, these being A,B,C,D,E,F,G,H,I,L,M,N,O,P,R,S,T and U. Vowels, however can be accented, making there seem like a lot more letters.

Pronunciation

A Pronunciation Guide can be found here.

However the best way is to listen to native speakers. You can listen to recording clips here and Gaelic Radio here. If you know any Gaelic speakers make use of one of the most useful learning aids around!

Names

Because of the Gaelic alphabet and spelling system many names are changed. For example, the name John becomes Iain and the name Jane becomes Siné. For more Gaelic names please visit this site.

Equipment

Pens, pencils and paper are a basic requirements. A dictionary is very useful. An online one can be found here. Later on in the course it may be of good use to frequently read Gaelic texts, for example a Gaelic section of a newspaper, a book or a website.

Unit 1
Hallo!

Saying hello and goodbye in Gaelic.

Starter

Can you think of 5 Gaelic words. These could be names, places, objects or activities, anything you want!

To say hello to a friend, just a "Hàllo" will do. To say goodbye "Tìoradh" is good in casual situations.

If you are speaking to someone such as a teacher, elder relative, someone you don't know or lots of people, you can use the following. You can also use them with your friends:

Madainn mhath. - Good morning. Feasgar math. - Good afternoon/evening. Oidhche mhath. - Good night. Latha math. - Good day.

To say goodbye, you say "Mar sin leibh". This can also be used in informal situations but you change the leibh to a leat. To say for now, add "an drasda" whether formal or informal.

Exercises

1) Answer these questions:

a. How would you greet your teacher in the morning? b. What would you say to your parents when going to bed? c. You are saying goodbye to a group of friends as you leave school. What do you say? d. How do you say Good Afternoon in Gaelic?

2) Make a table with two columns. Put in one column formal greetings and in another informal.

3) Match up the following:

- Madainn     Afternoon/Evening - Oidhche     Morning - Feasgear    Night

Extension/Homework

Make a cartoon involving you and either:

- A teacher - A friend - A parent

Tha mi gu glè mhath!

Asking how people feel. Answering about yourself.

Starter

L

title: Wikijunior:Scottish Gaelic


text:
Sicilian

Sicilian (Sicilianu) is a Romance language of Italy, mostly spoken in Sicily. Sicilian dialects (or dialects comprising the Italiano meridionale-estremo language group) are spoken on the island of Sicily (and all of its satellite islands), as well as in the southern and central sections of Calabria ("southern Calabro") and Puglia ("Salentino") on the Italian mainland. Ethnologue (see section below) describes Sicilian as being "distinct enough from Standard Italian to be considered a separate language".

Doubled consonants
Sicilian has a lot of words that begin with doubled consonants but the ones that are written are:

S'attròvanu puru ddi paroli chi pirderu la vucali, lassannu cunzunanti duppricati ô principiu di na palora, p'asempiu: mmeci; mmernu; nnuccenti; mmàggini; llustrari; ecc.

Articles
Definite: Indefinite:

Unu (masculine) and una (feminine) are used as cardinal numbers and as articles.

Simple prepositions
Pripusizzioni cumposti

These prepositions may be joined with the definite article:

Adverbs
Of place: Of time:

Of quantity: Of manner:

Other adverbs:

The apostrophe
The apostrophe is a graphic sign that is used when two vowels meet. Nna lu casu di eliminazzioni naturali di na vucali chi si trova a principiu di parola, nun è nicissariu usari l'apòstrufu, picchì, secunnu Giorgiu Piccittu anchi senza l'apòstrufu la parola si capisci lu stissu e livannu l'apòstrufu, quannu si pò, si elìminanu tutti sti signali nni la lingua scritta. Pi la stissa raggiuni, sempri secunnu Piccittu, l'apòstrofu nun s'havi mai a usari mancu nni la cuntrazzioni di l'artìculu nditerminativu picchì lu senzu è chiaru:

na               nu

Words that begin with i, where the i is lost, as said before, the apostrophe isn't used to demonstrate the loss of the vowel:

Mpurtanti; Nnuccenti; Nzignanti; Ntattu; Ntisu; Mparari.

So, we can say that the articles la, lu, li and pronouns la, lu, li, take the apostrophe as demonstrative adjectives ddu, dda, ddi, stu, sta, sti, ssa, ssu, ssi. The personal pronouns ti, nni, vi, and reflexives si and cci may take apostrophe too. If cci meets a, o, u it doesn't take the apostrophe.

Other phrases where the apostrophe may be used:
 * C'avem'a fari = chi avemu a fari
 * C'avem'a diri = chi avemu a diri

Verbs
The verb is the most important part of speech. The verbs are divided in: regulars, irregulars, transitives, intransitives, reflexives, defectives and modals. Sicilian has one verb that is auxiliary.

Auxiliary Verbs

Regular Verbs

Irregular Verbs

Other Special Forms

See also:

 * cumpenniu stilìsticu

 * vocabulary of preferred sicilian words

Other links:
Sites where you can find good examples of sicilian standard:
 * Arba Sicula - a sicilian-american organization for sicilian literature
 * Pruverbi siciliani scritti pi sicilianu e ngrisi
 * Na discrizzioni dâ grammàtica siciliana di Sergio Giorgi
 * Tanti puemi, cunti e saggìstichi, scritti o traduciuti di Ninu Russu
 * Linguasiciliana.org - nn'havi tanti matiriali diversi a rispettu dâ lingua scritta

Common phrases
Sicilianu

title: Sicilian


text:
User:Mike.lifeguard/Integrity

Lifeguarding as an analogy
I'd like to use an analogy which is relevant to me personally to talk about integrity within Wikimedia projects, particularly as it relates to administrators and bureaucrats. As you might be able to tell from my username, I am a lifeguard. To start off with, I'd like to do a quick overview of how certification of lifeguards works in Canada to lay the framework for discussing the common thread of integrity.

In Canada, lifeguards are certified by the Lifesaving Society. After taking a course from a certified instructor, candidates must pass a practical exam - the person who runs this exam is an examiner. Examiners are experienced and talented instructors who are given special training, apprentice with experienced examiners and then apply for certification. If the examiner candidate has shown the ability and integrity to perform the duties required, then they're certified. Simply completing the training course and apprenticeship is not enough. Examiners are expected to apply the standards fairly, and equally to all candidates.

Often, a facility will have an examiner on staff who will run courses, and certify the lifeguards working at that facility. This seemingly raises concerns about impartiality - surely there will be pressure to certify staff; to give them an easy ride? Well, yes and no. The pressure may exist, but the whole point of the training, apprenticeship and approval process is that you'll end up with examiners who value their own integrity more highly than pushing through candidates who shouldn't pass. Likewise in officiating Lifesaving Sport. While an Official or Judge may work with the people on a given team, they're expected to be impartial in spite of that fact.

While there are (occasionally) problems with impartiality, they're few and far-between; the system does a very good job of weeding out those who can't be trusted to set aside whatever biases they might otherwise have. Furthermore, examiners who are found not to have the integrity required are sometimes de-certified.

What do lifeguarding and Wikimedia projects have in common?
I want to suggest that this conception of integrity is common to both - that is, administrators (and particularly bureaucrats!) must be expected to act with just the sort of integrity that I described. Whether it's closing a VFD or giving a user admin tools, sysops and bureaucrats must be careful to apply community consensus - regardless of their own opinions and biases.

My own position
As an examiner in several award streams (including lifeguarding), I have "real-life" experience with this kind of situation. I've had numerous classes where I've had issues of attitude, maturity etc. with candidates... but if they can meet the standards, they pass. No matter how big a dick they are.

I've had classes I've taught where all the candidates were co-workers and friends. But I've failed those same people if they can't meet the standards. It's more important to me to have integrity than it is to not have people pissed off at me. It's more important to me to have integrity than is to hold a grudge.

Applying the lesson within Wikimedia projects
There are a few cases I'd like to examine, to clarify how this lesson should be applied. In short, users must have integrity in four critical areas; namely, VFD; community bans and arbitration; RFA; and content disputes. This is not to say that the lesson can't be applied elsewhere; on the contrary! This should be so constant that any infraction should be like nails on a blackboard. ''N.B.: nothing in this section is intended to refer to me, nor to any other real person. For example, I have yet to find a single post on my talk page which I would call a "petty concern."''

 * Votes for Deletion
 * This is one area where I think we've done well in the past.
 * Imagine there's some module or book up for deletion. People !vote on whether to delete or not. My !vote is "delete", but most !vote "keep." When closing the discussion, there's no room for your own opinion - it's been expressed already, perhaps discussed at great length. Beyond that, it matters not; gauge the consensus or lack thereof, including your own comments, but giving them no special weight.

 * Community bans and blocks
 * This is not an area which Wikibooks has much experience with. In the past, there have been incidents requiring community intervention, but as a close-knit community (much smaller than Wikipedia, for example), we simply don't have this kind of problem. As a hypothetical, however, let's examine a case where an ad hoc binding arbitration has taken place, with one of the administrators as the arbiter.
 * Binding arbitration is stressful for all involved; doubly so in a small community like this. The accused seems to be behaving in a manner that is hostile and belligerent. Because of this, the community call for a permanent ban. Despite feelings that the community is not assuming good faith, it's your job to simply apply the consensus, of one exists. In this case, although you feel the community is being hasty and there are legitimate options yet to be explored, you must simply exercise the community's will - ban the user. It's not your place to tell the community what to think, nor to overrule them.

 * Requests for Adminship
 * WB:RFA might be seen by some outsiders as rather like a cabal; despite the obvious deficiencies in the theory, there is a grain of truth to that assessment. That is, active contributors are likely to !vote on these discussions, and administrators tend to be active. This means our active editors tend to be admins, and our admins tend to be active editors. This is simply the nature of the Wikibooks beast. That's not a cabal. That's not a bug; it's a feature.
 * Imagine a mildly belligerent user has requested adminship. In the past, I've had contact with them - primarily respond to the user's demands for help which is easily found in the Help: pages. Nevertheless, they're a solid contributor of content. Since I have a bad taste in my mouth from the last time they demanded that I create a template for them, I !vote "oppose." After community input, it falls to me as a bureaucrat to close the debate, and give the rights or not. Fortunately(?) for the user requesting adminship, they only bothered me with their petty demands, and several community members supported their request. Here it is important that I set aside my own opinions and gauge consensus (or lack thereof) with impartiality; grant the rights, regardless of my own opinion on the matter (it's already been expressed, and consensus won out).

 * Content disputes
 * As an administrator, it sometimes falls to us to "police" content disputes. At Wikibooks, this is rare, but other wikis have recurring problems, often involving large numbers of editors bickering over part of a single page. While it's sometimes easy to determine when blocking and/or page protection are required, it sometimes isn't. But setting aside that issue (since it doesn't deal with integrity except tangentially), it may also fall to admins to determine whether consensus exists for a certain change. Regardless of your own opinion on the subject, your function in this case is to gauge consensus - nothing more. Although it could be seen as a conflict of interest to express your views, then gauge consensus, under this model of integrity, there's no issue. You voice your opinion, but set it aside when making any decision.

The current state of affairs
This conception of integrity is, of course, an ideal. Nonetheless, it's one I feel all Wikibookians (and indeed, all Wikimedians) should strive for. Particularly when we look at issues of privacy (CUs and Oversight) and cross-wiki rights and right-management (Stewards), integrity becomes an issue which can be difficult to gauge, due to the nature of the rights exercised. With Checkusers, for example, only other CUs can see your actions; the same is true of those with Oversight permissions. Stewards have CU access, and their user rights logs are effectively hidden from many Wikimedians (I wonder how many are aware of Meta's existence, or that all user rights changes by stewards are publicly logged?).

At Wikibooks, we've had relatively smooth sailing during my time here. That has not always been the case, and I'm sure will not always be the case. Specifically for that reason, integrity becomes an issue of function. If the community can't trust those with extra rights to have this conception of integrity, then the community cannot (and will not) function properly. If we ever come to that point, we'll know we've done something horribly, horribly wrong.

It's my hope that this essay will clarify my own position on some issues, and act as an expression of my own integrity for all to see.

title: User:Mike.lifeguard/Integrity


text:
User talk:Jonkopp

Come introduce yourself at the new users page. If you have any questions, you can ask there or contact me personally.

User:Provophys was the professor teaching the class that wrote the Human Physiology book. He has told me that he has taken a semester off from the book, which would explain why he appears to be inactive. The Human Physiology book was written by a class of nursing students (two classes, in fact), and this may be a reason why some of the material may be a little inaccurate. I am, however, no expert on physiology, although I do agree with your logic that a larger bone structure would reasonate at a lower frequency. I'm an engineer, so I do know about resonation, but I don't know specifics about the size and composition of inner-ear components. I would suggest that you check out some pages on Wikipedia about the topic, and see if you can find the information to resolve this issue. If you find a reliable source of information about this (wikipedia can, in general, be considered pretty reliable for our purposes) we can change the material on the page.

Welcome to wikibooks, let me know if you need anything. --Whiteknight (Page) (Talk) 15:46, 4 December 2007 (UTC)
 * I saw the note you left on Whiteknight's talk page. I just finished studying this as I have an exam in 2 days on this subject. You can see my answer there, but I also wanted to point out that the reasoning used both in your question and in WK's response above is incorrect. The bone structure has (almost) nothing to do with hearing. The vibrating component that matters is the basilar membrane. It has several interesting properties relevant here. It is wider and more flexible towards the apex, and comparatively narrow and rigid towards the oval window (which I didn't mention on WK's talk page). This is at least partially responsible for why high frequencies are coded for close to the oval window and low frequencies near the apex. I hope this helps you. (It helps me; we actually learn best by teaching, so this counts as studying... or at least that what I tell myself to justify my inability to maintain the wikibreak I am supposedly on :P) – Mike.lifeguard  | talk 17:02, 4 December 2007 (UTC)
 * Thanks Mike.lifeguard for jumping in. I guarantee you know more about this topic than I do, so please don't hesitate to edit the description. Based on your messages I made some changes, but hope that others will feel free to modify what I have written. Sorry Jonkopp for not answering your question--I kind of left the book on its own for a time. I just finished another semester of physiology, but we did wikinotes on wetpaint.com. Feel free to check those out [here]. Provophys (talk) 00:29, 18 December 2007 (UTC)

title: User talk:Jonkopp


text:
Teaching Elementary School Health Education/Injury Prevention and Safety/Unintentional Injuries/Fires

Most deaths and injuries relating to fires occur within the home environment. Cigarettes, lighters, and matches are the leading causes of these fires. However, some include faulty electical outlets and overloaded circuits.

A smoke detector is an alarm that sounds when it detects smoke. A heat detector is an alarm that sounds when the room temperature resis above a certain level. Every home should have one of these (on each floor) to prevent fire injuries. Batteries for these alarms need to be checked frequently to ensure that they are working properly.

In case of a fire

1. Have a predetermined plan for getting out and meeting your family.

2. Practice the plan.

When a real fire happens you should

1. Alert everyone in the home or building.

2. Place a wet cloth over the face.

3. Crawl out of the building on your hands and knees (stay below the smoke).

4. Feel doors for heat before opening. Do not open hot/warm doors. Open cool doors slowly.

5. Stuff rugs, blankets or clothes around a door to stop smoke from entering (if unable to leave the room). Call out a window for help.

6. Call 911 after you have escaped.

7. Meet family members at the designated meeting place.

8. Never go back into a burning building.

9. Tell fire officials if any people or animals are still in the building.

10. Have ropes or ladders available to help family members escap from two-story houses.


text:
User:Brastonuck

Don't pay attention to our retarded-ass name. Brastonuck is cool.

title: User:Brastonuck


text:
User talk:Brastonuck

If you wished to submit a message to Brastonuck, this is the place in which you would do so.

title: User talk:Brastonuck


text:
User talk:Bjhdht08

Welcome message
Hello, and welcome to Wikibooks!

Here are some tips to help you get started:
 * To learn the wiki-markup-language syntax, see Help:Editing.
 * You should sign your name on Talk and vote pages using four tildes, like this: ~~~~
 * There is a box at the top of the edit window that will insert this, too; it looks like part of a signature.
 * Remember to conduct any editing experiments in the sandbox.
 * You can tell the community something about yourself in your userpage.
 * You can get to this page by clicking the tab at the top of the page labeled with your registered username.
 * Wikibooks is a collection of open-source textbooks. (What is Wikibooks).
 * If you are 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 (requests for importation) 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 Reading Room with any questions or ideas.
 * Eventually, you might want to read the Manual of Style and Policies and Guidelines.
 * Help us by participating in policy and guideline creation.
 * 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 Reading Room, IRC channel or ask me personally on my talk page. For site news, see the Bulletin board. It might be a good idea to add that page to your "watchlist" so that you can see when any new information is posted there. You can do that by clicking the tab labeled "watch" at the top of the page.

Good luck! --Panic 18:11, 4 December 2007 (UTC)

title: User talk:Bjhdht08


text:
User talk:Daniel.Stevens

Oi, como vai? I've just started a totally new wiki for IB study, here:. I think that a wiki specifically made for IB can be more effective than these wikibooks alone. Would you mind if we copied your study guides to our wiki? Please reply to my user page at http://ibstudy.editthis.info/wiki/User:Admin .217.209.203.191 19:28, 4 December 2007 (UTC)

title: User talk:Daniel.Stevens


text:
User:Smck0

Hello, my name is Sandra, and I am a word nerd.

I am also a professional editor at a mid-sized university in Canada. For several years, my particular area of expertise was editing content for online courses. Alas, over the past couple of years, the powers that be at my university have eliminated this function, deeming that professors who possess PhDs are capable of writing both comprehensively and comprehensibly in any medium, Web included. Anyone who has suffered through an online course consisting of some bozo's 40-year-old lecture notes that have been cut and pasted into a PDF will instantly recognize the wisdom of this decision.

So while my primary function has been rendered redundant by Those Who Know Better, I am still gainfully employed, usually editing grant proposals, project descriptions, three-year strategic plans, and the like. At the moment (early Dec., 2007) I am copy-editing a book on online teaching. This book has been very challenging, since it employs 23 authors stretched across four, possibly five, continents, two content editors, a digital licensing specialist, and me. Oh, and the book is being written and edited entirely online, though its published form will be in hard copy. However, I do have a bit of free time (not much) and the freedom to expand my professional horizons. Thus I have decided to put my expertise in online writing directly on the line (so to speak), and will attempt to fill the gaping holes surrounding Writing for the Web in the Rhetoric and Composition Wikibook. In keeping with the spirit of Wikipedia and Wikibooks, my advice is free to anyone who wishes to partake. But caveat emptor: in general, you get what you pay for. This is a universal law of commerce, and I believe it to be a fundamental precept of karma, too.

I sincerely look forward to whatever dialogue ensues!

title: User:Smck0


text:
Introduction to Psychology/Judgment and Decision Making

The psychology of judgment and decision making deals with numerous psychological factors and events, including moral intuitions and performance, intuitive and heuristic modes of evaluating and choosing, conscious reasoning modeled after Western logic, and the factors and biases that affect one's choice of choosing method and the performance of the method itself. As with all mental events, underlying this general topic are the neuroscientific and biological factors that modulate the uses of the various sub-mechanisms.

Fight or Flight Response.


text:
Chess Strategy/Mobility

Mobility
Said the physician and chess master Siegbert Tarrasch, "Cramped positions bear the germs of defeat." Mobility and spatial advantages are key to a positional understanding of chess. A spatial advantage in a game will allow you to move your pieces from one edge of the board to the other faster than the opponent. In general, the side with a weak pawn or weak square to defend has a spatial disadvantage, as they may have to huddle their pieces together to defend that weak point. A spatial advantage allows you more territory to maneuver through. If your opponent has a spatial disadvantage, this is a long-term plus for you. The spatial advantage allows you to build up slowly, letting your opponent stew in his own juices for as long as you want him to. The advantage in space will not go away.

Playing with a spatial advantage
The principal idea of a spatial advantage is to not make too many exchanges. Think of a bottle of water. If you have a spatial disadvantage and your pieces are the water, the air is the remaining maneuvering space you have. But as the water is drunk (pieces get exchanged), there is more space for you, and material is still level!

The principle of two weaknesses
This is the rule that states that when a player has two separated weaknesses in his position, he is strategically lost. In the diagrammed position at right, White (Keres) has his pieces at their optimal posts. Every piece is pressuring a weak point in Black (Capablanca)'s position. The queen is especially well-posted; she is attacking both weak pawns at a6 and c6. Black's chances of surviving this game are pretty bad, but he can still struggle on. Therefore, White creates a third weakness and Black's position collapsed: '''22.Ne6! Qb8 23.Ng5! Rb7 24.Qg4 Bf4 25.Rc4 Rb5 26. Nxf7!!' White sacrifices his knight to create a kingside weakness, for after 26....Kxf7 27.Rd7+'' and White wins due to the weakness of the g7-pawn. Black declined the sacrifice with '''26....Re8! 27.g3 Qc8''', hoping to alleviate the pressure by making the transition into an endgame. However, Black's game is still lost due to the organic weaknesses on a6 and c6. '''28.Rxf4 Qxg4 29.Rxg4 Kxf7 30.Rd7+ Re7 31.Rxe7+ Kxe7 32. Bxg7.''' White is up two pawns and won on move 38.

In that position Black's pawns were already sufficiently protected, so White created a third weakness in the position and concentrated all of his efforts on it. This is another thing a spatial advantage provides: the ability to switch your troops between weaknesses quickly and effectively. Black's forces were tied up defending his weak pawns, and subsequently could not deal with White's kingside assault. Note also that due to the weaknesses on a6 and c6, Black is cramped due to the fact that these pawns will have trouble advancing to gain space. Also, Black could not move for losing the pawn.

Overextension
To be overextended means that you have more space than you can control. This can result in one of three things for your opponent:
 * 1. Receiving weak pawns as targets.
 * 2. Penetration into your camp.
 * 3. Outposts for his pieces.

Of course, none of these things are good. After exchanges, his pawns will be safe in his camp, while your pawns will be deep into his territory. This will allow him to easily line up pieces against them for target practice. Dr. Lasker said, "Distrust a pawn move; check carefully its balance sheet." What this means is that every pawn move weakens squares. So, after your pawns have advanced into enemy territory, many squares in your camp become weak. The opponent's rooks and queens can penetrate through open files into your position, and knights can take up "holes" that would be safely guarded by pawns, but are now weak because these guards have advanced.

One example of overextension in the opening is the Alekhine Defence, 1.e4 Nf6 2.e5 Nd5 3.d4 d6 4.c4 Nb6 5.f4, White hopes to prove that his pawn center gives him a spatial plus. Black hopes to refute this, saying that White's pawns are overextended and will become weak later in the game. The actual result depends on how both players play.

In this example at right, in the first diagram, White (Antoshin) has a huge space advantage. He can seek active play on either the kingside or the queenside. He will obviously be able to switch his pieces from wing to wing faster than Black, whose pieces are gridlocked on the back rank. However, Black (Ivkov)'s position has no defining weakness in it, yet there is a chance that White's pawns will become overextended. Antoshin here, rather recklessly, proceeds to expand in every direction possible. However, just like the Ottoman Empire of Turkey, he got overextended and his position collapsed only eight moves later! The game continued from here: 10.g4 g6 11.Bh6 Ng7 12.b4?! White's last move was questionable. Black can make some liberating moves here that will seriously expose White's weaknesses. 12....b6 13.Qd2 Nf6 14.Ke2? White's king will become a target for Black's pieces, which will penetrate through the soon-to-be-opened b-file. '''14....Kh8 15.Rag1 Bd7 16.Rg3 Qc7 17. Rhg1 b5!''' The second diagram has been reached. White has been slowly preparing for a kingside attack, since he correctly believes that his spatial advantage would not go away. However, he has left his queenside bare. Now his queenside caves in. 18.h4 bxc4 19.Bc2 cxb4 20.axb4 Rab8 21.h5 Rxb4 22.hxg6 fxg6 23.Rh1 Rb2 24.Kd1 Qa5 25.Ng5 Nxg4 26.Bxg7+ Kxg7 27.Rxh7+ Kg8 28.Qc1 Bxg5 29.Qxg5 Qa1+ 0-1. A drastic example of the risks of overextension. White ignored the fact that extra space could leave his position riddled with holes.

title: Chess Strategy/Mobility


text: Directing Technology/Evaluate/Graph

title: Directing Technology/Evaluate/Graph


text:
Directing Technology/Evaluate/Table

Physical Arrangement of Observed Classrooms
Data adopted from Fayette County Public Schools (KY)- District Technology Assessment, May 2001

title: Directing Technology/Evaluate/Table


text:
Directing Technology/Evaluate/Chart

Rubric scores

Categories based on Teacher Self-Efficacy Rubric.

title: Directing Technology/Evaluate/Chart


text:
User talk:Mshar014

Welcome message
Hello, and welcome to Wikibooks!

Here are some tips to help you get started:
 * To learn the wiki-markup-language syntax, see Help:Editing.
 * You should sign your name on Talk and vote pages using four tildes, like this: ~~~~
 * There is a box at the top of the edit window that will insert this, too; it looks like part of a signature.
 * Remember to conduct any editing experiments in the sandbox.
 * You can tell the community something about yourself in your userpage.
 * You can get to this page by clicking the tab at the top of the page labeled with your registered username.
 * Wikibooks is a collection of open-source textbooks. (What is Wikibooks).
 * If you are 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 (requests for importation) 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 Reading Room with any questions or ideas.
 * Eventually, you might want to read the Manual of Style and Policies and Guidelines.
 * Help us by participating in policy and guideline creation.
 * 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 Reading Room, IRC channel or ask me personally on my talk page. For site news, see the Bulletin board. It might be a good idea to add that page to your "watchlist" so that you can see when any new information is posted there. You can do that by clicking the tab labeled "watch" at the top of the page.

Good luck! --Panic 23:15, 4 December 2007 (UTC)

title: User talk:Mshar014


text:
User talk:Gphat

Welcome message
Hello, and welcome to Wikibooks!

Here are some tips to help you get started:
 * To learn the wiki-markup-language syntax, see Help:Editing.
 * You should sign your name on Talk and vote pages using four tildes, like this: ~~~~
 * There is a box at the top of the edit window that will insert this, too; it looks like part of a signature.
 * Remember to conduct any editing experiments in the sandbox.
 * You can tell the community something about yourself in your userpage.
 * You can get to this page by clicking the tab at the top of the page labeled with your registered username.
 * Wikibooks is a collection of open-source textbooks. (What is Wikibooks).
 * If you are 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 (requests for importation) 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 Reading Room with any questions or ideas.
 * Eventually, you might want to read the Manual of Style and Policies and Guidelines.
 * Help us by participating in policy and guideline creation.
 * 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 Reading Room, IRC channel or ask me personally on my talk page. For site news, see the Bulletin board. It might be a good idea to add that page to your "watchlist" so that you can see when any new information is posted there. You can do that by clicking the tab labeled "watch" at the top of the page.

Good luck! --Panic 23:15, 4 December 2007 (UTC)

title: User talk:Gphat


text:
User talk:71.191.107.209

Az1568(Talk) 23:42, 4 December 2007 (UTC)

title: User talk:71.191.107.209