text:
SuperCard Programming/Basics/Handlers & Functions

Handlers
Handlers in SuperCard are subroutines.

They begin with the "on" keyword, followed by the handler name. They end with the "end" keyword, also followed by the handler name.

Example: on calculateInterest -- other lines of code would be here end calculateInterest

Arguments
Handlers can take one or more arguments or parameters passed to them. These arguments should be included in the handler definition following the handler name and should be separated by commas.

Single Argument
Here's an example where a handler called "calculateInterest" takes a single argument "baseAmt" and multiplies it by an already defined global variable "gInterestRate" and stores it in an already defined global variable "gInterestAmt".

Example: on calculateInterest baseAmt global gInterestRate global gInterestAmt

put (baseAmt * gInterestRate) into gInterestAmt end calculateInterest

To call this handler in your code, you would do something like this:

Using a fixed, literal number: calculateInterest 5599

Or, like this, using a variable: calculateInterest preInterestAmt

Multiple Arguments
Here's an example where a handler called "calculateInterest" that takes two arguments, "baseAmt" & "interestRate", multiplies them and then stores the result in an already defined global variable "gInterestAmt".

Example: on calculateInterest baseAmt, interestRate global gInterestAmt

put (baseAmt * interestRate) into gInterestAmt end calculateInterest

To call this handler in your code, you would do something like this:

Using fixed, literal numbers: calculateInterest 5599,0.07

Or, like this, using variables: calculateInterest preInterestAmt,anInterestRate

Functions
Functions are also subroutines like handlers, however functions should return a value using the "return" keyword just before the "end [function_name]" line that terminates the function. SuperTalk doesn't enforce this. It will let you declare functions that do not return values, just as it will let you return values in handlers. However, it is good form to not return values from handlers and to use a function rather than a handler when you need to return a value. Following this convention will help you write code that is easier to follow, debug, and maintain.

Calling functions is slightly different than calling handlers. Calling a function generally requires that the function name be followed by a set of opening and closing parentheses, even if no arguments are being passed.

Here's an example of a function that takes no arguments: function piTimesTwo put pi * 2 into theResult

return theResult end piTimesTwo

To call this function you would do something like this: put piTimesTwo into doublePi

Or, you could use it without storing its results like this: if someOtherVariable > piTimesTwo then -- lines of code for a true result would go here else -- actions for the false result would go here end if

Notice that even though the "piTimesTwo" function takes no arguments, when it is called, its name is followed by a set of empty parentheses.

Arguments
Just like a handler, a function can take one or more arguments.

Single Argument
Building on the example above, here's a function to calculate interest that takes only one argument, multiplies it by an already defined global variable, but instead of storing the result in another global variable, it returns it:

function calculateInterest baseAmt global gInterestRate

put (baseAmt * gInterestRate) into theResult

return theResult end calculateInterest

You could call this function with a literal number like this: set tInterestAmt to calculateInterest(5995)

But, more realistically, you would probably pass it an amount stored in a variable: set tInterestAmt to calculateInterest(somePreInterestAmt)

Multiple Arguments
And, finally, here's a more realistic (although probably overly simplistic) example of a function that takes two arguments, multiplies them, and then returns the result. The advantage being, that you don't need a globally defined variable for the interest rate. The reason this is overly simplistic is that you would not need to define a function just to multiply two numbers and store the result, however, I'm sure you can envision creating functions that do much more than just multiply two numbers before they return a result.

Example: function calculateInterest baseAmt,interestRate put baseAmt * interestRate into theResult

return theResult end calculateInterest

Note: It is not actually necessary to place (baseAmt * interestRate) into a new variable called "theResult". The preceding function could have looked like this: function calculateInterest baseAmt,interestRate return (baseAmt * interestRate) end calculateInterest

To call the function using two values already stored in variables, you would do something like this: put calculateInterest(someAmt,someInterestRate) into someInterestAmt

Summary
Both handlers and functions allow you to define subroutines within your SuperTalk scripts.

Both handlers and functions can take:
 * no arguments
 * one argument
 * multiple arguments

Handlers begin with the "on" keyword followed by the handler name.

Functions begin with the "function" keyword followed by the function name.

Both handlers and functions are terminated with the "end" keyword followed by the handler/function name.

When calling a handler that takes one or more arguments, the argument(s) are placed after the handler name without any enclosing parentheses.

When calling a function with no arguments, it is best to follow the function name with an empty set of parentheses. And when calling a function with one or more arguments, the argument(s) must be enclosed in parentheses.

You should use functions to create subroutines that return a value using the "return" keyword followed by a variable name or a calculation.

You should use handlers to create subroutines that do no return a value.


text:
User talk:193.231.30.200

Regarding edits made during December 20 2006 (UTC)
Thanks for experimenting with Wikibooks. Your test worked, and has now been removed. Please use Sandbox for any other tests you want to do, since testing material in modules will normally be removed quickly. Please see the welcome page if you would like to learn more about contributing to our project. Thanks. If this is an IP address, and it is shared by multiple users, ignore this warning if you did not make any unconstructive edits. Az1568 07:38, 20 December 2006 (UTC)

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

title: User talk:193.231.30.200


text:
Talk:Muggles' Guide to Harry Potter/Major Events

I think another set of major events that could be tracked would be relationships, such as Harry - Cho, Harry - Ginny, Ron - Hermione. Thoughts?
 * If you proposed a way of doing this, I would be interested. As long as it's planned well, I think that would fit in nicely. We can create a section of the page for them and list each with a subpage for each relationship. One thing I will absolutely remove is fan-like poppy relationship ideas and other things that are not fully apparent in the books. No Harry-Hermione, Hermione-Draco, Harry-Draco, etc. Proper analysis only, and only if that relationship is truly useful to the Guide. We need to execute such a thing with high standards. -within focus 16:33, 20 December 2006 (UTC)
 * Intriguing idea... though I am going to suggest that perhaps fan-inspired relationships might be mentioned and dismissed, with perhaps documentation on lack of evidence. But it would be difficult, because Ginny's relationships start with Harry, and go on to a couple of others, before they return to Harry. And presumably we'd want to mention Cho / Cedric and Lavender / "WonWon" as well... Hmm. Needs thought. Would the appropriate way to do this be to track the relationships only from the point of view of the principals, e.g. Ron, Harry, Hermione, Ginny, Cho, through the seven books? Chazz 21:49, 4 January 2007 (UTC)
 * I think there are way too many relationships in all the book to cover them all. Only those of importance should be addressed. Mentioning some of the "made up" relationships might not be a bad idea as well since it is helpful to explain why they did not occur, but I personally wouldn't like much more coverage than that. Sticking to the primary characters is probably the best idea. -within focus 22:51, 4 January 2007 (UTC)
 * How about this? Chazz 09:05, 5 January 2007 (UTC)
 * (now edited to point to the updated page) Chazz 05:42, 7 January 2007 (UTC)

Possible Additions
An important event that definitely should have a page is "Voldemort's First Downfall/Harry's Parents' Deaths". Some other ones that can be considered are the "Godric's Hollow Fiasco" and the "Visit to the Lovegood House". Thoughts? RunningBlind (discuss • contribs) 01:45, 22 January 2012 (UTC)


text:
User:Alan.ca~enwikibooks

w:user:Alan.ca

title: User:Alan.ca~enwikibooks


text:
User talk:Ian888

Hello and welcome to Wikibooks!

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

You will find more resources in Community Portal. If you want to ask a question, visit the Study help desk, the Staff lounge, IRC channel or ask me personally on my talk page. For site news, see the Bulletin board. It might be an idea if you add this page to your "watchlist" so that you can see when any new information is posted there.

Good luck! -- Herby talk thyme 10:29, 20 December 2006 (UTC)

title: User talk:Ian888


text:
User talk:Ccny930

Hello and welcome to Wikibooks!

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

You will find more resources in Community Portal. If you want to ask a question, visit the Study help desk, the Staff lounge, IRC channel or ask me personally on my talk page. For site news, see the Bulletin board. It might be an idea if you add this page to your "watchlist" so that you can see when any new information is posted there.

Good luck! -- Herby talk thyme 11:00, 20 December 2006 (UTC)

title: User talk:Ccny930


text:
Wikibooks:Requests for deletion/Neopets

Neopets
A game guide, not a textbook. I've kept a copy at Neopets. GarrettTalk 07:49, 25 October 2006 (UTC)

 * Speedy Delete - Also remember to protect the page and use our standard "transwikied according to policy" looks. -within focus 00:53, 26 October 2006 (UTC)

 * Now that it's been transferred to the other wiki, Delete the copy here - Video games, being the transient, and unproductive, things they are, rarely have a place in a library outside of books on video game programming or video game history. Much like it would be impractical for wikibooks to try to maintain an instruction manual book for every DVD or MP3 player, it's impractical to think that we can or should document the workings of the gameplay of every game out there. -Monk 19:02, 18 November 2006 (UTC)

 * It is not the job of _us_ to maintain a wikibook or wikiproject. It is the job of the authors. If a specific group wants to create a wikibook on a subject that they like, then why not? It is great practice for people to create a game guide, as well as giving Wikibooks some publicity. For example, I personally would not have come to wikibooks as an active contributor if it weren't for my Maple Story book. I also disagree with your statement and reasoning. We do by policy allow software manuals on this site. We have guides for Linux, Windows, and tons of programming languages. We have manuals for specific software like Matlab, CSound, and even Gmail around here.

 * Additionally, what do we waste? Resources? These files are stored as pure text files and take up very little server space. I do realize that it is compressed, but you can download the entire Wikibooks database, images and complete histories included at 298.2 MB. Guideline does say 20x the size uncompressed, but even by today's standards, several Gigs is not much space indeed. Remember, thats the _entire_ Wikibooks project I'm talking about here. Even if the pages were deleted, they'd remain on the server anyway. So we wouldn't gain any resources either.

 * Leaving video game guides on this site offers little cost with lots of reward. I don't really see the issue with moving them. --Dragontamer 16:29, 21 November 2006 (UTC)

 * My concern is not so much that video games aren't academic subjects, or that they are specific to a given audience of those that use them, or that they are solely electronic in nature, or even that the audience or authorship of any given one of these books may be large or small. My concern is the amount of work it will create for others if dozen after dozen video game guides are created under a relativistic "everything's good" policy, only to have the videogames stop being developed at some point and to have us left with a bunch of meaningless content here. Not everyone finishes what they start and I'm concerned that we'll have dozens of people people who would otherwise spend their time more productively waste time checking on and cleaning up video game pages.

 * Video games are not just trivial. They're often transient. Open Source software with a wide base of developers, or a huge institutional software or web company, whose products have been known to stick around, provide justifiable material for time expenditure. On the same vein I wouldn't be adverse to a guide for the heavily popular video games out there. World of Warcraft or such. Those things are likely to be important in a few years just as they are important today. And if Neopets is shown to be a notable, widely used videogame that is likely to be maintained for the next few years, well, perhaps it's okay to have it here, because it's of some educational relevance. But just like I wouldn't advise the creation of a wikibook about some new software created by some nowhere startup new jersey IT company, I don't think we should clog this site up a hundred other books that will be more or less useless to people.

 * The "we have the space" argument doesn't phase me. The reason we have votes for deletion is because some books need to be deleted. Not necessarily because they contain innapropriate content or violate copyright, but because they contain no content or their content is useless. Books with no text, and books with useless text, should be deleted. They're a waste of time and space, and make wikibooks harder to organize. The problem with video game guides is that, for most of them, in a few years they'll be useless. They don't hold their use for long. Thus, it would be prudent to make sure that video game guides are created, or kept, in another wiki which has a more liberal policy as to what kinds of content it will uphold. -Monk 01:56, 4 December 2006 (UTC)

 * I agree with monk on these points, and I would also like to add that we aren't deleting these guides entirely, but instead they have been moving--of their own accord--to strategy wiki. Once the book is moved to the new location, it is beneficial for the book not to fork the contributing community. In other words, the book will benefit the most if it is in one location (not copied here and there), and if there is one dedicated group of people working on a single version of it. I dont think anybody here wants to blindly cut out all videogame guides, but at the same time, if this isn't the best home for them, they should be moved someplace better, where they will get the attention they deserve. --Whiteknight (talk) (projects) 04:39, 4 December 2006 (UTC)

 * When the book becomes useless, then delete it. Until then, there is no argument against a specific book. There are useless video game guides. There are also plenty of other useless Wikibooks around here. Nonetheless, I do think I should concede on this point; as this Neopets book is somewhat incomplete and can be easily considered a stub. However; if someone was willing to spend the time and effort to create a video game guide on Wikibooks; I don't think we should stop them. Basically, I feel that deleting a book because it is a Video Game is a dangerous path. Delete it because it is useless, delete it because it is a stub. But if there is a well written, well maintained, and overall well done Wikibook on a subject that deals with a specific Video Game, we should keep this rare gem on Wikibooks. --Dragontamer 01:55, 14 December 2006 (UTC)

I think it is safe to say that all videogame guides that have been migrated to another site are going to be deleted. no sense listing them here on VfD if they dont need to be here. Just mark all of them in the future as speedy deletes, and we will take care of them. --Whiteknight (talk) (projects) 02:48, 26 October 2006 (UTC)
 * I disagree, kinda. Mark them as transwiki so that we don't scare off potential users. I still remember that case where books were being deleted too fast. Deletion is a strong word, especially to newbies, so I think it would do us well to refrain from using it. In this case, transwiki would not only describe the situation better, but keep some PR a little better. If you know what I mean. --Dragontamer 18:47, 10 November 2006 (UTC)
 * A little semantic change can make a difference, I agree. However, this page is for the discussion of pages that are going to be deleted, and the pages of the videogame guides are going to be deleted from this project. Now, we can call the process "transwikiing", and we can post a link to the "new home of the book", but fact is it still gets deleted. Perhaps we need a new temple to mark books that are being transwikied in this way?--Whiteknight (talk) (projects) 03:16, 4 December 2006 (UTC)
 * Perhaps a "This page has moved to ..." message? Or "This page is moving to xxx project" ? --Dragontamer 02:00, 14 December 2006 (UTC)

 * Hold I'm surprised this hasn't been deleted yet, but I'm glad that I get to post a comment. Are we sure that deleting the wikibook is what the contributing community wants? Or are we just assuming we are being nice by deleting it? Do any in the interested (note interested not contributing) community know that this or the other exists? Do any in the contributing community know that the other exists? I think those are serious questions that need to be answered before we consider deleting this book with the intent to do good for the apparent community. Cheers, Iamunknown 18:02, 12 December 2006 (UTC)
 * Oppose deletion. Circumstances surrounding are too unclear for me to vote delete. --Iamunknown 01:58, 14 December 2006 (UTC)

 * I've played Neopets before, but I'm no real expert. This book seems to have only one real complete section in it, which is Neopets/Stock market. The guide has been stalled for several months, and on that grounds, I guess you could consider this to be a stub. The Stock Market may be one important part of Neopets, but there is a lot more to Neopets than just the stock market. Enough for me to say that this book is a stub. --Dragontamer 02:00, 14 December 2006 (UTC)

Delete - I used to play neopets a fair bit (though it's been a few years). The main "gameplay" was in the minigames, which this guide has very little information about. The main way to make money was Restocking (buy items from official "shops" resell them in personal stores) which has no info at all. The stock market section isn't that "big" in the game, and the guide here seems more like a general stock market thing than neopets specific (neopets might even make a nice addition to a real stock market book). -- Prod-You 06:11, 14 December 2006 (UTC)

 * Comment reviewing this one in the hope of closing before its "long service award" the balance of votes seems to me to be delete. It appears to be a very patchy stub with no current interest.  Unless there is a real indication of value or interest very soon I will close as delete -- Herby  talk thyme 16:53, 15 December 2006 (UTC)

title: Wikibooks:Requests for deletion/Neopets


text:
Horticulture/Phytopathology

Phytopathology is the study of how disease processes develop in plants. These processes are of particular concern in the fields of agriculture and horticulture. There are several major groups of organisms that cause disease on plant, each of these are outlined below.

Fungal Phytopathogens
There are over 10,000 fungal pathogens of plants. The fungal plant pathogens themselves fall into to major groups, the biotrophs which feed from living plant tissue and the necrotrophs which kill plant cells and then live off the nutrients released. However, many plant pathogens adopt a hybrid lifestyle, initially acting as biotrophs before converting to a nectrophic lifestyle. These are called hemibiotrophs.

The majority of phytopathogenic fungi belong to the ascomycetes and the basidiomycetes.

The fungi reproduce both sexually and asexually via the production of spores. These spores may be spread long distances by air or water, or they may be soil bourne. Many soil bourne spores, normally zoospores and capable of living saprophytically, caring out the first part of their lifecycle in the soil.

Fungal diseases can be controlled through the use of fungicides in agriculture, however new races of fungi often evolve that are resistant to various fungicides.

The Oomycete Phytopathogens
The oomycetes are fungal like organisms that until recently used to be mistaken for fungi. They include some of the most destructive plant pathogens including the genus ../Phytopthora/ which includes the casual agents of potato blight and sudden oak death, and members of the genus ../Pythium/, which causes damping off of seedlings.

Despite not being closely related to the fungi, the oomyctes have developed very similar infection strategies and so many plant pathologists group them with fungal pathogens. The oomycetes are particularly difficult to control, and many can live in the soil as saprotrophs for long periods.

Protozoa
There are a few examples of plant diseases caused by protozoa. They are transmitted as zoospores which are very durable, and may be able to survive in a resting state in the soil for many years. They have also been shown to transmit plant viruses.

When the motile zoospores come into contact with a root hair they produce a plasmodium and invade the roots.

Bacterial Phytopathogens
Most bacteria that are associated with plants are actually saprophytic, and do no harm to the plant itself. However, a small number, around 100 species, are able to cause disease. Bacterial diseases are much more prevalent in sub-tropical and tropical regions of the world.

Most plant pathogenic bacteria are rod shaped (bacilli). In order to be able to colonise the plant they have specific pathogenicity factors. There are 4 main bacterial pathogenicity factors:

1. Cell Wall Degrading Enzymes - used to break down the plant cell wall in order to release the nutrients inside. Used by pathogens such as Erwinia to cause soft rot.

2. Toxins. These can be non-host specific, and damage all plants, or host specific and only cause damage on a host plant.

3. Phytohormones - for example Agrobacterium changes the level of Auxin to cause tumours.

4. Exopolysaccharides - these are produced by bacteria and block xylem vessels, often leading to the death of the plant.

Bacteria control the production of pathogenicity factors via Quorum sensing.

../Phytoplasma/ and Spiroplasma are a genras of bacteria that lack cell walls, and are related to the mycoplasmas which are human pathogens. Together they are referred to as the mollicutes. They also tend to have smaller genomes than true bacteria. They are normally transmitted by sap-sucking insects, being transferred into the plants phloem where it reproduces.

Plant Viruses
There are many types of plant virus, and some are even asymptomatic. Most plant viruses have small, single stranded RNA genomes. These genomes may only encode 3 or 4 proteins: a replicase, a coat protein, a movement protein to allow cell to cell movement and sometimes a protein that allows transmission by a vector.

Plant viruses must be transmitted from plant to plant by a vector. This is normally an insect, but some fungi, nematodes and protozoa have been shown to be viral vectors.

Plant Parasitic Nematodes
../Nematodes/ are small, multicellular worm like creatures. Many leave freely in the soil, but there are some species which parasitise plant roots. They are mostly a problem in tropical and subtropical regions of the world, where they may infect crops. Root knot nematodes have quite a large host range, whereas cyst nematodes tend to only be able to infect a few species. Nematodes are able to cause radical changes in root cells in order to facilitate their lifestyle.

Examples of Plant Pathogens
Significant fungal plant pathogens
 * Ascomycetes
 * ../Fusarium/ spp.
 * ../Thielaviopsis/ spp. (Causal agents of: canker rot, black root rot, Thielaviopsis root rot)
 * ../Verticillium/ spp.
 * ../Magnaporthe grisea/ (T.T. Hebert) M.E. Barr; causes blast of rice and gray leaf spot in turfgrasses
 * Basidiomycetes
 * ../Rhizoctonia/ spp.
 * ../Puccinia/ spp.; causal agents of severe rusts of virtually all cereal grains and cultivated grasses

Significant oomycete plant pathogens
 * ../Pythium/ spp.
 * ../Phytophthora/ spp.; including the causal agent of the Irish Potato Famine

Significant bacterial plant pathogens
 * Proteobacteria
 * ../Xanthomonas/ spp.
 * ../Pseudomonas/ spp.

Significant abiotic disorders can be caused by:
 * Natural
 * Drought
 * Frost damage, and breakage by snow and hail
 * Flooding and poor drainage
 * Nutrient deficiency
 * Salt deposition and other soluble mineral excesses (e.g. gypsum)
 * Wind (windburn, and breakage by hurricanes and tornados)
 * Lightning and wildfire (also often man-made)
 * Man-made (arguably not abiotic, but usually regarded as such)
 * Soil compaction
 * Pollution of air and/or soil
 * Salt from winter road salt application
 * Herbicide over-application
 * Poor education and training of people working with plants (e.g. lawnmower damage to trees)
 * Vandalism

title: Horticulture/Phytopathology


text:
User talk:58.178.204.248

Please do not replace Wikibooks pages with blank content. Blank pages are harmful to Wikibooks because they have a tendency to confuse readers. If it is a duplicate article, please redirect it to an appropriate existing page. If the page has been vandalised, please revert it to the last legitimate version. If you feel that the content of a page is inappropriate, please edit the page and replace it with appropriate content. If you believe there is no hope for the page, please see the deletion policy for how to proceed. If page is no longer useful, insert delete to its top. Thanks for contributing to Wikibooks! -- Herby talk thyme 13:59, 20 December 2006 (UTC)

title: User talk:58.178.204.248


text:
User talk:203.135.60.193

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

title: User talk:203.135.60.193


text:
Cookbook:Pepperoni

Pepperoni, or Pepperoni Sausage, is a popular type of salami, and Italian fermented sausage. It usually consists of pork, beef, and spices, and is commonly used as a pizza topping and as a snack. Characteristically, Pepperoni is quite smooth and bright red. Pepperoni is used as a filling in the Pepperoni Roll. Pepperoni is sometimes used as a choice for submarine sandwiches. The Italian word, "peperoni", means sweet bell peppers or capsicums.

title: Cookbook:Pepperoni


text:
Cookbook:Hot Dog

A hot dog (also known as a frankfurter) is a variant on a sandwich, or the sausage inside, usually made of beef. In consists of a bun and a frankfurter sausage, and usually has a variety of toppings, including ketchup, mustard, relish, onions, and pickles. Cheese is also a popular topping for Hot Dogs. Hot Dogs range in size, and can be up to a foot long.

When wrapped in bacon and deep-fried, it is known as a Danger dog when served with mayonnaise and as a Jersey breakfast dog when served on a fried egg and cheese.

title: Cookbook:Hot Dog


text:
Complete Guide to Essential Oils

This is a guide to essential oils that are used in aromatherapy, their properties and other useful information.

Table of contents

 * /A to Z of essential oils/
 * /A to Z of ailments/
 * /Carrier oils/
 * /Safety/
 * How to make perfumes

title: Complete Guide to Essential Oils


text:
C Sharp Programming/Abstract classes

In general terms, an interface is the set of public members of a component. Of course, this is also true for C# interface. A C# class also defines an interface, as it has a set of public members. A non-abstract C# class defines the implementation of each member.

In C#, it is possible to have a type that is intermediate between a pure interface that does not define any implementation, and a type that defines a complete implementation. This is called an abstract class and is defined by including the keyword in the class definition.

An abstract class is somewhere between a C# interface and a non-abstract class. Of the public members defined by an abstract class, any number of those members may include an implementation.

For example, an abstract class might provide an implementation for none of its members.

This class is equivalent to an interface in many respects. (One difference is that a class that derives from this class cannot derive from any other class.)

An abstract class may also define all of its members.

And an abstract class may define some of its members, but leave others undefined.

Although an abstract class is similar to a non-abstract class, some important differences exist. For one thing, you cannot create an instance of an abstract class with the keyword. For example, the following statement will raise a compiler error:

Of course, assuming the concrete class derives from, the following would be correct:

A second difference is that an abstract class may have abstract members. As was shown above, this is not a must. To create a class with at least one abstract member, the keyword must be added before the  keyword.

The third difference is that a class cannot be both and.

Implementing methods
As with virtual methods, you can implement abstract methods or properties with the keyword:

Overriding an abstract method is effectively the same as overriding a virtual method - you cannot change the access specifiers (i.e. you can't convert a protected abstract method into public), and you cannot add a missing get or set to an abstract property. The only difference is that "forgetting" the or  keyword results in an error, if the class this method is belonging to was derived from an abstract class, and it will result in a warning, if the class tries to override a virtual method.

title: C Sharp Programming/Abstract classes


text:
Wikibooks:Decision making/Unstable

Wikibookians may not always agree with each others decisions and sometimes decisions which effect the Wikibooks community come up which need to be discussed beforehand. This proposal tries to address these concerns and provide guidelines on how to resolve them.

Decision making
The best way to resolve a dispute is to avoid one in the first place.

Textbooks are created by making bold changes and through cooperation between users. People naturally feel protective about the work that they create. When someone makes changes you consider biased or inaccurate, do not simply revert the changes, improve it instead. The revision you would prefer will not be established by reverting. Wikibookians are strongly encouraged to follow several basic principles:

 * 1) Following the NPOV policy can help you write "defensively", and limit your own bias in your writing.
 * 2) Provide a good edit summary when making significant changes that other users might object to.
 * 3) Assume good faith and treat changes as reasonable and positive.
 * 4) Be civil and respectful of the opinions and decisions made by other Wikibookians.
 * 5) Discuss changes you disagree with on the talk page. If you encounter rude or inappropriate behavior, resist the temptation to respond unkindly, and remain civil.

When disputes cannot be avoided. The most important tools Wikibookians have for resolving disputes are compromise and consensus. By following a general decision making process disputes can be resolved more easily.

High impact decisions
High impact decisions involve the adoption, adaptation or rejection of policies and guidelines and other decisions that have a long term effect on the culture and structure of Wikibooks. These decisions must always be made through the process of building a community consensus. Such decisions include:

 * 1) Making a Wikibookian an administrator or a bureaucrat
 * 2) Giving a Wikibookian checkuser rights or bot rights
 * 3) Modifying official Wikibooks policies and guidelines
 * 4) Changing the status of policies and guidelines (such as from proposed to official)
 * 5) Establishing the voting rules for low impact decisions
 * 6) Determining whether a page containing substantive content that is not unambiguously outside our inclusion criteria should be deleted

Low impact decisions
Low impact decisions involve proposals that express the community's preferences and feelings about issues that fall well below the level of policies and guidelines, and do not affect the long term culture or structure of Wikibooks. For these sorts of decisions, Wikibookians are welcome to employ multiple means for decision-making, including consensus, majority votes or 3rd party arbitration. Consensus is the manner in which a dispute should be settled if no another method is agreed upon by all Wikibookians involved. The manner in which a dispute is settled may change if the majority of involved Wikibookians agree to the changed.

Examples of low impact decisions are:

 * 1) Determining what books should be listed as featured books.
 * 2) Determining the content, structure or scope of a single textbook or project.
 * 3) Creating a new policy or guideline proposal.

Process
Anyone may start a good faith discussion to discuss any issues and voice their opinion. Decision making relies upon Wikibookians engaging in negotiation and compromise through civil discussions that ultimately leads to a vast majority of involved Wikibookians agreeing on some decision. There is only one allowable voice per person, not one voice per username. Wikibookians with multiple accounts should not post opinions from more then one account. Remember: comments are judged on their quality, not on their quantity. Comments that are suspected of being cast in bad faith may be discarded.

There is no single "right way" to achieve consensus, however discussions should last long enough that all Wikibookians who may be interested are given an opportunity to join in and voice their opinion. One possible step-by-step process for discussions and working towards consensus is:

 * 1) A clearly publicized proposal is made and discussion about the proposal is invited by all interested Wikibookians.
 * 2) The proposal is discussed and initial concerns may be raised.
 * 3) If initial concerns are raised, these are discussed. The proposal may be modified during these discussions.
 * 4) A call for consensus regarding the proposal is made in the form of a discussion and subsequent measurement of the degree of consensus with a straw poll.
 * 5) If there are no objections within a reasonable timeframe, the proposal is accepted and affirmative "community consensus" has been reached on the proposal.
 * 6) If there are still objections, the objections should be discussed and:
 * 7) The proposal may be dropped. Affirmative "community consensus" for the proposal was not reached.
 * 8) The proposal may be modified to address these objections and resubmitted for discussion.
 * 9) A call for determining any consensus regarding the proposal may be made, disregarding objections. A call for this second measurement of the degree of consensus should not be made lightly if there are still objections and should only occur after substantive good faith discussion of both the proposal and objections has taken place. The community can:
 * 10) Accept the proposal in spite of objections, and affirmative "community consensus" has been reached.
 * 11) Not accept the proposal as "community consensus" has not been reached and repeat the process if necessary.

Discussions once started must not be forked, but may be moved if the vast majority of Wikibookians agree to it or the dispute has been resolved. Discussions which have been moved should be clearly indicated so that anyone wishing to add to a discussion can find it. Each comment in a discussion should be signed (using four tildes: ~ ), to identify the Wikibookian. Anonymous comments will not be given any weight or consideration, and may be removed altogether. Important discussions should be publicized in the Staff lounge and on the Bulletin board, or other high-traffic areas. For high-impact decisions, discussions and debates should be left open as long as progress towards reaching consensus is being made.

User responses
Wikibookians who strongly disagree with the community consensus may consider the following options:

 * 1) Propose alternatives or alterations to existing decisions.
 * 2) Concede to the community's decision.
 * 3) Take a wikibreak to cool off.

title: Wikibooks:Decision making/Unstable


text:
User:Stepa

Hello.

I'm a 38-year-old tax advisor from Poland.

pl:User:Stepa

title: User:Stepa


text:
Talk:Engineering Tables/Laplace Transform Table 2

s is a complex number, wouldn't it be more correct to write Re{s} ?

 * Where specifically are you talking about? In general, s is treated as a complex number, and both the imaginary and real parts need to be maintained. --Whiteknight (talk) (projects) 16:52, 20 December 2006 (UTC)

when looking at ROC you need to write Re(s) because you can't put a complex number in inequality. (ex: you can't write 3+4i>0)

 * Good point, I hadnt even looked at the ROC when you made your last comment. I'll work on changing it. --Whiteknight (talk) (projects) 14:28, 21 December 2006 (UTC)


text:
Engineering Analysis/Random Vectors

Many of the concepts that we have learned so far have been dealing with random variables. However, these concepts can all be translated to deal with vectors of random numbers. A random vector X contains N elements, Xi, each of which is a distinct random variable. The individual elements in a random vector may or may not be correlated or dependent on one another.

 * $$X = \begin{bmatrix}X_1\\X_2\\\vdots\\X_N\end{bmatrix}$$

Expectation
The expectation of a random vector is a vector of the expectation values of each element of the vector. For instance:

 * $$E[X] = \begin{bmatrix}E[X_1]\\E[X_2]\\\vdots\\E[X_N]\end{bmatrix}$$

Using this definition, the mean vector of random vector X, denoted μX is the vector composed of the means of all the individual elements of X:

 * $$\mu_X = \begin{bmatrix}\mu_{X_1}\\\mu_{X_2}\\\vdots\\\mu_{X_N}\end{bmatrix}$$

Correlation Matrix
The correlation matrix of a random vector X is defined as:

 * $$R_X = E[XX^T]$$

Where each element of the correlation matrix corresponds to the correlation between the row element of X, and the column element of XT. The correlation matrix is a real-symmetric matrix. If the off-diagonal elements of the correlation matrix are all zero, the random vector is said to be uncorrelated. If the R matrix is an identity matrix, the random vector is said to be "white". For instance, "white noise" is uncorrelated, and each element of the vector has an equal correlation value.

Matrix Diagonalization
As discussed earlier, we can diagonalize a matrix by constructing the V matrix from the eigenvectors of that matrix. If X is our non-diagonal matrix, we can create a diagonal matrix D by:

 * $$D = V^{-1}XV$$

If the X matrix is real symmetric (as is always the case with the correlation matrix), we can simplify this to be:

 * $$D = V^TXV$$

Whitening
A matrix can be whitened by constructing a matrix W that contains the inverse squareroots of the eigenvalues of X on the diagonal:

 * $$W = \begin{bmatrix}\frac{1}{\sqrt{\lambda_1}} & \cdots \\ 0 & \frac{1}{\sqrt{\lambda_2}} \cdots \\ \vdots & \vdots & \ddots \end{bmatrix}$$

Using this W matrix, we can convert X into the identity matrix:

 * $$I = W^TV^TXVW$$

Simultaneous Diagonalization
If we have two matrices, X and Y, we can construct a matrix A that will satisfy the following relationships:

 * $$A^TXA = I$$
 * $$A^TYA = D$$

Where I is an identity matrix, and D is a diagonal matrix. This process is known as simultaneous diagonalization. If we have the V and W matrices described above such that

 * $$I = W^TV^TXVW$$,

We can then construct the B matrix by applying this same transformation to the Y matrix:

 * $$W^TV^TYVW = B$$

We can combine the eigenvalues of B into a transformation matrix Z such that:

 * $$Z^TBZ = D$$

We can then define our A matrix as:

 * $$A = VWZ$$
 * $$A^T = Z^TW^TV^T$$

This A matrix will satisfy the simultaneous diagonalization procedure, outlined above.

Covariance Matrix
The Covariance Matrix of two random vectors, X and Y, is defined as:

 * $$Q_X = E[(X-\mu_X)(Y-\mu_Y)^T] = E[(Y-\mu_Y)(X-\mu_X)^T]$$

Where each element of the covariance matrix expresses the variance relationship between the row element of X, and the column element of Y. The covariance matrix is real symmetric.

We can relate the correlation matrix and the covariance matrix through the following formula:

 * $$R = Q + \mu_X\mu_X^T$$

Cumulative Distribution Function
An N-vector X has a cumulative distribution function Fx of N variables that is defined as:

 * $$F_X(X) = P[X \le x] = P[X_1 \le x_1, X_2 \le x_2, \cdots, X_N \le x_N]$$

Probability Density Function
The probability density function of a random vector can be defined in terms of the Nth partial derivative of the cumulative distribution function:

 * $$f_X(X) = \frac{\partial^N F_X(X)}{\partial X_1 \partial X_2 \cdots \partial X_N}$$

If we know the density function, we can find the mean of the ith element of X using N-1 integrations:

 * $$\mu_{X_i} = \int_{-\infty}^\infty \int_{-\infty}^\infty \cdots \int_{-\infty}^\infty x_if_X(x) dx_1 dx_2 \cdots dx_n$$

title: Engineering Analysis/Random Vectors


text:
User talk:168.9.22.102

You're blocked -- Herby talk thyme 17:15, 20 December 2006 (UTC)

title: User talk:168.9.22.102


text:
User talk:Gdearing

Hello and welcome to Wikibooks!

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

You will find more resources in Community Portal. If you want to ask a question, visit the Study help desk, the Staff lounge, IRC channel or ask me personally on my talk page. For site news, see the Bulletin board. It might be an idea if you add this page to your "watchlist" so that you can see when any new information is posted there.

Good luck! -- Herby talk thyme 18:21, 20 December 2006 (UTC)

title: User talk:Gdearing


text:
SQL Dialects Reference/Introduction

Preamble
SQL (Structured Query Language) is one of the oldest programming languages in existence, first versions of which date back to 1969. Unfortunately, despite SQL being standardized since 1986, a lot of different implementations exist. They deviate more or less from each other, making developing applications that would work with a range of different SQL servers particularly difficult.

This wikibook is a compact comparative reference for several SQL language dialects. It lists particular common tasks and problems resolved in terms of several popular SQL server implementations. When possible, it tries to emphasize an universal solution. When it's not possible, it tries to list best practices.

Two main goals for the book are compactness and completeness. Obvious information, e.g. that a particular function or query does the same thing on all implementations, will not be listed. However, when some implementation(s) have important (even minor) deviations that can be a major pitfall for developers, such information definitely should be listed.

Who should use this book
Target audience is:

 * Developers who know a single dialect of SQL and want to develop for other SQL implementation right away (it's a simple way to).
 * Developers who port a ready project from one SQL implementation to another or a bunch of SQL implementations.
 * Developers who want their applications to be portable on a set of SQL servers (it's particularly useful for developers of open source projects that want to ensure that their application can be used on a variety of platforms).
 * System administrators who have to support a wide range of SQL servers and don't want to memorize all possible queries and nuances for every server.
 * Project managers or lead developers that want to estimate what SQL server is best for their project, given a list of requirements.

Who shouldn't use this book
This book is not a general learning course, not a comprehensive manual - it's a quick and compact reference that assumes that the reader knows basic concepts of SQL and precisely what is needed. The book discusses fairly advanced topics and minor, but important differences in SQL implementations that beginners / learners generally don't have to worry about.

Technical notes
Always where it is possible, a book tries to reference a web-published documentation, so a reader can always check particular detail, so a page is usually full of external documentation links.

As the full names of implementations are pretty long and inconvenient to spell out thoroughly every time, we'll use common abbreviations (shown in bold) to distinguish SQL dialects. Also, we only provide links to corresponding Wikipedia articles here, not on every occasion.

Many pages in this book include comparison tables that can be pretty long. It is recommended to install a comparison table extension to view these tables comfortably.

SQL implementations covered in this book
Several SQL dialects are covered in this book. Note that in all cases of particular implementations, only the latest stable version is described.

 * Standard. There are several versions of SQL standard (SQL-86, SQL-89, SQL-92, SQL:1999, SQL:2003, SQL:2011). The book would list all popular practices to do a job in all implementations, particularly emphasizing SQL versions that a particular solution works for (i.e. if some feature became standard since version X, it would be stated that such solution works since version X).
 * DB2 (IBM DB2).
 * Firebird (Firebird 2.5). An open-source RDBMS forked from sources of InterBase that were released by Borland on July 25, 2000. Firebird differs from Interbase and tries to be close to SQL standard as much as possible
 * MonetDB An open-source column-store. (MonetDB. V11)
 * MySQL (MySQL 5.0)
 * MSSQL (Microsoft SQL Server 2008). A proprietary RDBMS produced by Microsoft, targeting enterprise market. Original codebase was derived from Sybase SQL Server, but was mostly rewritten. Documentation is available in MSDN in a well-structured form, quite easy to reference.
 * Oracle (Oracle Database 11g2)
 * PostgreSQL (PostgreSQL 13)
 * SQLite.
 * Virtuoso (OpenLink Virtuoso running on Virtuoso Universal Server).
 * Linter

title: SQL Dialects Reference/Introduction


text:
SQL Dialects Reference/SQL XML

The ISO publication (ISO/IEC 9075-14) is part of the SQL standard. Formerly it was named SQLX or SQL/XML. It defines the data type  and functions acting on this data type as well as functions creating and handling XML objects (elements, attributes, ...) within this data type. Oracle denotes the data type XMLType.

title: SQL Dialects Reference/SQL XML


text:
SQL Dialects Reference/References

Standards

 * SQL-86
 * SQL-89
 * SQL-92 — full text is available
 * SQL:1999 — can be purchased from ISO
 * SQL:2003 — can be purchased from ISO
 * working draft of SQL:2008, downloadable from Whitemarsh Information Systems Corporation.
 * SQL:2008 — can be purchased from ISO
 * SQL:2011 — can be purchased from ISO

Official product documentations

 * DB2 Version 9 Information Center
 * MonetDB documentation
 * SQLite documentation
 * Firebird / Interbase 6 language reference (ZIP archive, 8.9MB)
 * OpenLink Virtuoso Universal Server Documentation
 * Oracle Database 12g1 SQL Reference
 * Microsoft SQL Server Documentation
 * Linter SQL Server Documentation (English, old version);Linter SQL Server Documentation (Russian)
 * Oracle Database 12g1 SQL Reference
 * Microsoft SQL Server Documentation
 * Linter SQL Server Documentation (English, old version);Linter SQL Server Documentation (Russian)

Single implementation references and cheat sheets

 * Oracle PL/SQL Cheatsheet
 * Oracle XML Cheatsheet

Comparisons

 * Comparison of different SQL implementations
 * Comparison of Oracle, MySQL and PostgreSQL DBMS by Computing Division of Fermi National Accelerator Laboratory
 * SQL Function Reference: Oracle vs. SQL Server
 * SQL Functions — MySQL vs Oracle comparison by Eric Brian
 * Standard SQL - an article by Peter Gulutzan that compares SQL standards support in DB2, MSSQL and Oracle
 * Standard SQL - an article by Peter Gulutzan that compares SQL standards support in DB2, MSSQL and Oracle

Migration

 * Converting MySQL to PostgreSQL

title: SQL Dialects Reference/References


text: User:RyGuy~enwikibooks

title: User:RyGuy~enwikibooks


text:
User talk:RyGuy~enwikibooks

Welcome
As a wikipedian take a look at the relevant pointer - the places are not the same!

Hello and welcome to Wikibooks!

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

You will find more resources in Community Portal. If you want to ask a question, visit the Study help desk, the Staff lounge, IRC channel or ask me personally on my talk page. For site news, see the Bulletin board. It might be an idea if you add this page to your "watchlist" so that you can see when any new information is posted there.

Good luck! -- Herby talk thyme 18:37, 20 December 2006 (UTC)

Thank you Herby, and by the way, I do know the basics of talk pages (such as the ~ ). I am a student in school and plan on primarally using Wikibooks for reference (as I do with Wikipedia). Again, Thanks for the welcome. If I have anything to contribute with, I will. Bye! RyGuy 18:42, 20 December 2006 (UTC)

 * No problem but it was Wikibooks for Wikipedians that I was meaning, plenty the same - quite a bit different -- Herby talk thyme 18:46, 20 December 2006 (UTC)

Wikimedia Pennsylvania
Hello there!

I'm writing to inform you that we are now forming the first local Wikimedia Chapter in the United States: Wikimedia Pennsylvania. Our goals are to perform outreach and fundraising activities on behalf of the various Wikimedia projects. If you're interested in being a part of the chapter, or just want to know more, you can: Thanks and I hope you sign up!  Cbrown1023  talk  16:29, 12 July 2007 (UTC)
 * Contact us on IRC at #wikimedia-pa
 * Join our mailing list
 * Visit our blog at http://wmfpa.blogspot.com
 * Sign our list of interested participants

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 RyGuy. To make sure that both of you can use all Wikimedia projects in future, we have reserved the name RyGuy~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:39, 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:26, 19 April 2015 (UTC)

title: User talk:RyGuy~enwikibooks


text:
User talk:Rtcearly

This is now your new username. You should be able to use your old password to login. All your existing preferences should be the same. If you have any questions, please don't hesitate to ask. --Whiteknight (talk) (projects) 18:42, 20 December 2006 (UTC)

title: User talk:Rtcearly


text:
User:KostaToronto

Who I Am and What I'm Writing
My name is Kosta, and I live in Toronto (no big surprise there!). I am currently working on the following Wikibook:

 * Student's Guide to Michel Foucault

Interests
My personal interests include:

 * Literature (I'm currently into thrillers, but I keep coming back to works by Joyce and Atwood)
 * English (I love etymology and theories of language acquisition)
 * Education (especially technology-enhanced learning and critical pedagogy)
 * History (mainly post-confederation Canadian history, but also general Western history)
 * Philosophy (I've recently re-discovered my interest in Foucault, hence the Wikibook)

My applied interests include:
 * Teaching English to college-level ESL learners
 * Using Web 2.0 tools such as discussion boards, wikis, blogs, and podcasts, both in my own teaching and in my training of colleagues
 * Developing resources (handouts, "user guides," online demos, etc.)

Wiki Workbench

 * /Foucault Wikibook/ | /Work in Progress 1/ | /Scraps/

title: User:KostaToronto


text: User:Indolences~enwikibooks

title: User:Indolences~enwikibooks


text:
Wikibooks talk:Decision making/Unstable

Move to Enforce
I would like to start a motion to enforce this proposal as a policy instead of the current guideline text at Decision making. The current guideline is already followed with few (if any) exceptions, and this should be a case of policy conforming to the community. --Whiteknight (talk) (projects) 19:24, 20 December 2006 (UTC)

 * Have to say I'm not sure I agree with "For high-impact decisions, discussions and debates should be left open as long as progress towards reaching consensus is being made." to me that is death by attrition - those not bored to death will win? -- Herby talk thyme 19:40, 20 December 2006 (UTC)

 * That's actually one part of the proposal that hasn't changed from the current enforced version! But yes, it is death by attrition, because the community must reach concensus before a change can be made. Basically, there are three ways a discussion can end:
 * Everybody agrees to accept (proposal accepted)
 * Everybody agrees to reject (proposal rejected)
 * People can't agree, nothing happens (implicit rejection).
 * As such, it is much harder to change the status quo then it is to keep things the same. --Whiteknight (talk) (projects) 20:31, 20 December 2006 (UTC)

I see Whiteknight as making two distinct proposals:

 * That the decision making guideline should be reclassified as a policy
 * That Decision making/Unstable should replace the current verson of WB:Decision making

On the first point, I agree that we should have a decision making policy. That policy may, in time, get supplemented by guidelines, but for now I think it is sufficient just to have a policy.

In terms of the unstable branch, I'm afraid that I'm not really sure what it is trying to achieve. I note from the history that it appears to be a joint effort of Darklama and Whiteknight. I'd be grateful if one or both of them could let me know what their objective is and how they see the unstable branch version as achieving that objective.

One aspect I do not like is the early introduction of a substantial section on "Ownership and Authorship". Ownership and authorship has no bearing on decision making, so I don't see why a section on this is needed in this policy. If there is a point to be made there, it is either for another policy on a related topic or in an explanatory guideline to the policy proper. Jguk 21:54, 20 December 2006 (UTC)

 * The objective was to make it clearer that the reason for the decision making process is due to the nature of Wikibooks not having a single author or owner and that the decision making process is used for more then making policy decisions. I disagree with you. Ownership/Authorship does have bearing on decision making. If there was but one owner/author there would simply be no need to deal with disagreements since there would be nobody else to disagree with. The point is to make the decising making process more understandable and explain why it is needed. --dark [[Image:Yin yang.svg|12px]] lama 22:10, 20 December 2006 (UTC)

 * Very astute, I am making two separate proposals (or, I am proposing that one thing happens in a particular way). Due to some recent events, it was brought to our attention that wikibooks doesnt have a policy equivalent to w:WP:OWN, something that has already caused a few problems. I drafted a local version at WB:OWN, but (out of fear of sprawl or instruction creep) User:Darklama proposed instead that we merge the text of the draft at WB:OWN into another policy.
 * History aside, I think that the section on ownership is an important one to have, and I also think that this is a mostly appropriate place for it. If decisions are made by concensus, then it's implicit that one user can't treat a particular discussion like a dictatorship. However, nowhere in all of wikibooks policy is it mentioned that this is the case (except implicitly from the definition of "concensus"). For that reason, I think that this policy needs to have at least some mention of ownership. However, you and I are of the same mind in that we both seem to prefer succinct policy documents with supporting guidelines. We could minimize the section here on ownership and redirect inquiries on the subject to WB:OWN, but I'm afraid that (again, due to instruction creep), that people will fight the establishment of two separate documents much more then they would fight the establishment of a single monolithic policy.
 * Given the two options: (A) create a single monolithic policy document, or (B) create a succinct policy with supporting guidelines, I would prefer the latter, but not to the extent that I would try to prevent these policies from being implemented.--Whiteknight (talk) (projects) 22:11, 20 December 2006 (UTC)

First, may I thank Darklama and Whiteknight for their explanations? I'm afraid, however, that I find myself disagreeing with them: I don't see ownership and authorship as being related to our decision making process.

Let me illustrate by way of an example. Suppose, for sake of argument, that I protected all the book modules that I created so no-one else could edit them, so that I "own" those pages. (I agree this is contrary to policy, I just make this supposition to show that our decision making rules are a separate issue to ownership and authorship).

Under that supposition, there is only one sentence of the whole of the policy that follows that would be out of place ("Decisions that affects the content, structure or scope of a single textbook or project, must follow the rules for high impact decisions except where all parties agree to use another basis.") The rest of the policy, eg how we decide admins, bureaucrats, BOTM, COTM, etc. is unchanged.

My conclusion is that we should not have something on ownership and authorship in this policy/guideline. I don't comment here on whether it may be appropriate to have it as a separate policy/guideline, or merged in with another policy/guideline. Jguk 15:18, 21 December 2006 (UTC)

 * The one sentence you speak of is a clarification of one that already exists in the current policy "Should a decision need to be made that affects a single module, a single book or a single project it will usually use the rules for high impact decisions except where all parties agree to use another basis." So how we are suppose to decide book contents is unchanged as well, These changes are relatively minor and are ment to aid in clarifying whats already present in the policy and current practise. The current policy only mentions it as a possible after thought and seems to focus almost entirely on decision making as it applies to policy making. With these changes I think the policy becomes more balanced rather then focusing on one or the other and provides clarity as a result that decision making is about both working together to make decisions about books when disagreements arise and when working together on making policies that effect everyone. --dark [[Image:Yin yang.svg|12px]] lama 16:20, 21 December 2006 (UTC)

 * ownership and authorship as being related to our decision making process

 * There is a need on Wikibooks to reduce debates and clear the path for active collaboration, there is a need to specify local or if you wish book policies (policies that go beyond general Wikibooks policies or guidelines), book communities etc...

 * There are now several books that do provide not only a set of internal guidelines but also some external rules to how content contribution should proceed inside the books namespace, it is my view that such guidelines or rules are good and increase the consistency and enable a more structured and productive collaboration (a central location to express and establish the wishes of contributors for the evolution of the book) but this rises another problem...

 * Who should have a say on the evolution of a particular book, Wikibookians in general are and should continue to be able to set general rules (or non book specific policies and guidelines), be able to participate in any book community (we must define that), etc... the normal rules doesn't need any change on that regard as we fallow a decision by consensus this would not involve any change in the voting it would only reduce the scope of the debate to a specific interest group...

 * Who should be defined as a book community, well anyone that actively participates in adding content to a book this should set aside spammer and people with no good intentions or even people that place form above content, form is ephemeral, content will always prevail by shifting the rules to define this new concepts a increased level of stability is archived for the development and general evolution of the books.

 * So I do agree with User:Darklama "Ownership/Authorship does have bearing on decision making.", as in the sense that authors is the one that sign and are responsible for their work (even legally) and are the first person interested in the work itself and its evolution, and we cannot forget that contributors do own their contributions, lets say for example a user has a book under a non GFDL compatible license and wants to port it/or part to Wikibooks, he may need to keep a consistent relation within the works structure...

 * As for Jguk example it doesn't work, any similar action (even if not prevented by a policy) could be objected to by any Wikibookian and an dispute and the need of consensus would arise that would restore the status quo, if not then it would have been sanctioned by the community and a future reversal would need the same consensus. --Panic 18:50, 29 December 2006 (UTC)

Consensus
Until a consensus can agree that a good majority vote is necessary for decision taking there will always be problems. The recent bust up over a programming text was small beer compared with what happens on Wikipedia. That said, any policy on the decision taking issue is better than none! RobinH 15:21, 14 January 2007 (UTC)

Establishing policys
From my own experience, many of the policies and even the "rules" that govern things like the "Wikijunior New Book of the Quarter" section are usually done in such a way that somebody merely is bold and takes the initive to simply make something happen.

Certainly there is reason to say that policies that are established in this manner are merely "proposed" rather than "enforced", which is precisely why for some time Wikibooks was mostly dominated by proposed policies rather than enforced ones. Of course the distinction between proposed and enforced polcies was only done because a previously active admin decided to be bold and make the distinction, establishing a preceedent.

I will say that it has been very interesting to see how some of these policies have emerged. My worry that I've expressed in the past is that I hate to see policies established for the sake of establishing policies. Or more to the point, I also try to follow the policy (for my own behavior) of "he who governs best governs least."

As another way to put it: Rules are established to fix the mistakes of those who screwed it up for the rest of us.

There are times that policies and rules simply need to be established because of abusive behavior in the past. Clearly some of the actions of vandals and the establishment of the various heirarchies of Wikimedia projects are a direct result of trying to deal with blatant vandalism and keep it down to a dull roar. I have seen wikis where the vandals were successful in taking over and overthrowing the "legitimate" content developers (it is ugly BTW, especially when the website owner doesn't care in the least). For the most part I think we have been successful in winning this particular battle, in spite of some bizzare things that happen from time to time.

On the other hand, there are some people who like to be rule lawyers and make rules and policies just for the sake of pure political power. When done to an extreme, you end up with legalese text that is volumnous and discouraging to those who simply want to "get the job done". Often this is done explicitly to achieve some political objective or to promote some "faction" over another group. This kind of policy making should be discourgaed when possible, and to be honest seems to be something of why I'm against (weakly) this whole decision making policy from becoming an enforced policy at all.

I don't think there are too many policies that really fit strongly into either extreme group, although I do believe there are some that are more strongly one or the other (the rules about granting check user rights are more to the rules made simply to write rules, for example). In order to even get into the business of wrting policies, you have to have a bit of an ego on you anyway and being a bit of a politician and a lawyer to boot.

All this said, most of what is written here with this policy is mainly common sense written down, with the only "policy" really being the section on the community concensus process. I would consider that a strong guideline, only to be circumvented when a genuine crisis situation develops.

It should be noted that the process never really is completed. It is reasonable for somebody to challenge a decision that was made in the past and question why it was done that way. I have seen some policies get overturned in the past, even when set down by a prominent individual.

The worst situations I've dealt with while being an admin were those individuals who for some reason or another decided to appeal to "higher authority" and cause the wrath of members of the WMF board of trustees to be directly involved in settling a dispute. While I like Jimbo personally, and I think his contributions have been very useful, he has been an incredibly disruptive force here on Wikibooks in the past. Most of this is because his decisions have largly thrown out the whole concept of concensus, and even when you want to gain concensus his actions taint the whole process. "Jimbo says" is usually sufficient to kill a discussion or change it to debate what exactly Jimbo said. Luckily I don't think any admin except Jimbo has that sort of power.

BTW, as a side note, I do think Jimbo edits here on Wikibooks on addition account names and has even gone into the Staff Lounge under such names. I strongly suspect a couple of them for personal reasons, but if he wants to be anonymous in doing so I will leave him in peace. --Rob Horning 18:50, 21 December 2006 (UTC)

 * I agree with a majority of what you have said, Rob. I do believe that we should keep our policy documents to a minimum, and I say this for a number of reasons: We want people to have a good amount of freedom, we want people to be able to excercise a certain amount of judgement and common sense when making decisions, and we don't want to fall into the over-legislative problems that wikipedia has experianced. However, I am not of the belief that we should have no policy documents, or that we should only have guidelines, or anything so extreme as that. I think that it should be the official policy of wikibooks that decisions are made by concensus, and not by any other method. We do need some rules here, and I think this is one of the few that we absolutely do need. --Whiteknight (talk) (projects) 01:59, 29 December 2006 (UTC)

My edits (Proposal Text)
I edited a bit. If you look at the diff, you be'll horrified. It looks worse than it is. I don't know how to explain my edits; just take a look. Thank you very much. --Iamunknown 01:52, 24 December 2006 (UTC)

 * I like your changes for the most part, I thought the definition of concensus should go before the impact of decisions section though in order for readers to know what concensus means before they get to that part. I merged most of it into the Terminology section. I tried to clearify what I believed you ment by "deciding to enforce official Wikibooks" by splitting it into its own example and changing it to say "Changing the state of policies and guidelines (such as from proposed to official)". I changed the begining of the Process section to read:

 * 'Wikibooks is not a demoncracy, Wikibookians discuss points, compromise and try to reach community consensus. Wikibookians generally do not "vote" on anything and a simple voter majority is not the default, nor recommonded method of deciding any discussion. Decision making relies upon Wikibookians acting in good faith to come to a commonly acceptable decision through negotiation and compromise.'
 * 'There is no single "right way" to achieve community consensus. However, one possible step-by-step process for discussions and working towards a community consensus is:'

 * And a few other minor things. --dark [[Image:Yin yang.svg|12px]] lama 03:56, 24 December 2006 (UTC)

 * I liked your changes, and you got my meaning right on. I made minor edits. I think that I didn't change the meaning of any of the clauses; it was all prosaic. Check 'em out here. --Iamunknown 07:48, 24 December 2006 (UTC)

 * I liked some of your changes. I undid the introduction bit, because I think what it previously said was friendlier, but I kept "than" over "then" and I turned Textbook into a link to WB:WIW. I also cut down a little bit on the process through some I hope clarification. --dark [[Image:Yin yang.svg|12px]] lama 09:28, 24 December 2006 (UTC)

There should a time restriction on re-evaluation of the same problem, and a limit to the number of votes to be equal or greater than the previous, something on those lines this will prevent needless debaites and policies to be passed or changed without the community noticing it.--Panic 19:15, 29 December 2006 (UTC)
 * How to run a discussion/User responses

This should be asked to User_talk:Darklama but I ask it here because it explains a change on the text.
 * "Decisions that affects the content, structure or scope of a single textbook or project, must follow the rules for high impact decisions except where all parties agree to use another basis."

Darklama, why did you convert that to a low impact decision, what was rational of the change ? txs. --Panic 21:16, 30 December 2006 (UTC)

 * I believe the only way it is concidered a high impact decision is in the method it imploys which is using concensus as the method to resolve disputes when they arise if no other method is agreed to by the Wikibookians involved in the dispute. For example at one point you and I agreed to moderation which changed the method imployed to resolve an issue that arose. I believe calling it a high impact decision is misleading and is considerably inconsist with the rest of the text. --dark [[Image:Yin yang.svg|12px]] lama 21:24, 30 December 2006 (UTC)

 * Not so, I proposed mediation to provide more view points (comments) but we were already working toward a consensus, well not a consensus but a compromise, since some of the dispute did arise form interpretation of our actual license and its use and that couldn't be compromised. Remember also that most of the moderators( they were also administrators ) avoided to make direct interpretations and none provided any acceptable solution . --Panic 21:41, 30 December 2006 (UTC)

title: Wikibooks talk:Decision making/Unstable


text:
Cookbook:Pork and Lima Skillet

| Meat Recipes

Ingredients

 * 2 packages (10 ounces) frozen baby lima beans
 * 5–6 pork loin chops
 * 1 teaspoon pork-flavored gravy base (granules)
 * 1 tablespoon all-purpose flour
 * ⅛ teaspoon dried basil, crushed
 * ¾ cup water

Procedure

 * 1) Cook lima beans according to package directions, omitting salt in cooking water; drain.
 * 2) In skillet, brown chops over medium heat. Remove chops from skillet. Pour off all but 1 tablespoon drippings.
 * 3) Add gravy base to skillet. Blend in flour and basil.
 * 4) Add ¾ cup water; cook and stir over medium heat until thickened and bubbly.
 * 5) Add limas to skillet, stirring to coat with sauce.
 * 6) Arrange chops over limas. Cover and cook over low heat about 5 minutes, or until heated through.

title: Cookbook:Pork and Lima Skillet


text:
User talk:66.215.160.215

Ditto - you are blocked -- Herby talk thyme 19:41, 20 December 2006 (UTC)

title: User talk:66.215.160.215


text:
User:Colin Kiegel~enwikibooks

I'm going to contribute something about gauge theory. But I'll keep it here, until it's finished.

Dirac Theory
Dirac in 1928 successfully established a theory to describe relativistic free electrons (or any spin-1/2 particle). Within the framework of Lagrangeformalism he derived

$$\mathcal{L}_D = \bar{\psi}(x)(i\gamma^\mu \partial_\mu - m) \psi(x)$$

where

$$\bar{\psi} := \psi^\dagger \gamma^0$$

$$\gamma^0:=\left( \begin{array}{cc} \mathbb{E}_2 & \\ & -\mathbb{E}_2\\ \end{array}\right)$$

$$\gamma^i:=\left( \begin{array}{cc} & \sigma^i \\ \sigma^i & \\ \end{array}\right)$$

We will now start with Diracs Theory of a free

title: User:Colin Kiegel~enwikibooks


text:
Talk:ACE+TAO Opensource Programming Notes/Find a service on a naming server

Deletion
Forgive me, I have much less experience on wikibooks than wikipedia, but this page contains no content, and has remained that way for months. Should it not be deleted? Pgrodt 21:17, 20 December 2006 (UTC)


text:
User talk:69.180.25.238

Xania talk 21:26, 20 December 2006 (UTC)

title: User talk:69.180.25.238


text:
Talk:How to frame a picture/Fixing common problems

i'm trying to frame a record for my boyfriend for christmas, but im not sure how to attach the sleeve and record to the matte board. i'm afraid to just glue them to it since it's a valuable record, but how do i make them stay upright?


text:
User:Celestianpower/Spanish

Continue to the Main Contents Page

title: User:Celestianpower/Spanish


text:
User:Celestianpower/Spanish/Contents

 *   Start learning Spanish with ¡Aprovéchalo!
 * }

Punto de partida
A starting point; the basics of conversation and grammar.
 * ¿Cómo te llamas? — Greetings, Names, the Alphabet.
 * ¿Cuándo es tu cumpleaños? — Numbers, Ages, Dates.
 * Introducir a gramática — Articles, Regular Verbs, Questions and Exclamations.

Barcelona, Spain
Barcelona, Spain; the world of places, food and activities.
 * ¿Dónde vives? — Countries, Houses, Cities and Countryside.
 * ¿Qué te gusta hacer? — Sports and Activities, Telling the Time, Preferences.
 * ¿Qué comes? — Food, Likes and Dislikes, Adjectives.

title: User:Celestianpower/Spanish/Contents


text:
Bartending/Cocktails/Eucazini

The Eukazini is a cocktail invented on the December 17, 2006. It was invented by bartender Kaz Santiago and customer Euan Morse in Edinburgh's Ryan's Bar.

Ingredients

 * 1 oz or jigger of Vodka
 * 1 oz or jigger of Cointreau
 * 1 oz or jigger of Midori
 * 1 oz or jigger of Pimms

Garnish
A small triangle of orange to complete the drink.

The Glass
A chilled martini glass rimmed with granulated sugar. Use a lemon or lime wedge to 'juice' the glass.

Method

 * Fill a shaker with ice, then add all ingredients.
 * Shake ingredients till shaker is frosted, (shake very vigorously).
 * Then strain into a chilled martini glass.
 * Garnish with orange and serve.

title: Bartending/Cocktails/Eucazini


text:
User:Elaragirl~enwikibooks

 Monday 29 July  UTC

 Welcome to Elar a girl 's  User Page ''Mmm. Cookies!''

This user has had a lot of recent personal problems, and may be slow to answer.

title: User:Elaragirl~enwikibooks


text:
Talk:IB Geography

This page is/was a mess. I've started in on a reorganization to have it reflect the IB Syllabus. Graymc (talk) 02:50, 19 February 2008 (UTC)

This page could use some work to make it nice like the other IB subject books.

New Syllabus
This page is outdated. There is a new syllabus for First Examination 2010121.73.240.145 (discuss) 04:34, 26 April 2011 (UTC)

title: Talk:IB Geography


text:
User talk:Elaragirl~enwikibooks

{| align="center" cellpadding="10" cellspacing="10" style="background: none;"
 * style="color: white; -moz-border-radius-topright: 20px; -moz-border-radius-topleft: 20px;" width="700px" align="left" bgcolor="lightsteelblue" | Welcome to Heaven, where there's no need for deletionists.
 * align="left" style="background: #FFFFF3; border:2px solid lightsteelblue; font-size: 90%; -moz-border-radius-bottomright: 20px; -moz-border-radius-bottomleft: 20px;"|
 * align="left" style="background: #FFFFF3; border:2px solid lightsteelblue; font-size: 90%; -moz-border-radius-bottomright: 20px; -moz-border-radius-bottomleft: 20px;"|

"Any sufficiently advanced incompetence is indistinguishable from malice" - Think before you type, please.

Greetings
Greetings, Elaragirl, Dark Queen of the Deletionist Cabal against Kittens, Stubs, Hope, and Inclusionists. I am familiar with your goings-on at Wikipedia, and have come to say "Hi!" and "Welcome to Wikibooks!" --Iamunknown 22:44, 20 December 2006 (UTC)

Hi Elaragirl!
Yes, I remember you... was pleased to see the new account on the RC feed :). Sorry if you're having a hard time on wp: the politics can get overwhelming there, for me it's just a matter of knowing when to ignore the politics (and to hit the ignore button before I'm fried with them).

That's a totally appropriate subject... actually there's a book on abnormal psych being written, I'll try to track it down. But if you have notes to start posting up, just go ahead and start... page and book merges are common on wikibooks. If you add the book title to Template:New, it will be noticed, and if a merge is needed someone will get in touch.

Let me or someone else know if you want wikipedia articles imported to include in the book... it's often nice not to have to start "from scratch. -- SB_Johnny | talk 23:17, 20 December 2006 (UTC)

 * I couldn't help but read your message to User:SBJohnny, and I wanted to donate my two cents to the conversation (for what little they are worth). If your book is on abnormal sexual psych, I would say that's sufficiently different from the current abnormal psych to avoid being merged. We are always looking for more knowledgible, intellegent, educated people to help write books here, and I can guarantee that the atmosphere is much more laid-back then it is at WP. Welcome to wikibooks (i love your talk page!) and if you have any other questions, there are plenty of people here to ask. --Whiteknight (talk) (projects) 15:09, 21 December 2006 (UTC)

Obligatory welcome template
Come introduce yourself at the new users page. If you have any questions, you can ask there or contact me personally. -- SB_Johnny | talk 23:17, 20 December 2006 (UTC)

Wikibooks Newsletter, Volume 1
(Wikibooks gazette home | Discuss | Bulletin board | Subscription list)

This is a short newsletter that is being distributed to all active wikibookians. You are getting this message because you are recognized as an established contributor to the project. This newsletter will be distributed on a regular basis to help share news, information, and tips. It comes from a bot account, User:The Staff. User:The Staff is currently operated by a team of wikibooks admins, the complete list of which is available on the user page of the bot. If you would like to not receive this newletter anymore, please remove your name from the list at Active wikibookians.

The work you do at Wikibooks is greatly appreciated. However there are plenty of other opportunities for you to get involved and help us to create a thriving Wikibooks community. We are sure that there are things we can do to help you and your understanding of Wikibooks and similarly there are certainly things you could do to help Wikibooks become a better place.

We would like to ask all wikibookians to add the Bulletin Board to your watchlists. The Bulletin Board is a fast and easy way for wikibookians to communicate important news and events to the entire community. If you have important news to share with the community, you can feel free to add your own entry to that page.

If you have general questions or comments about Wikibooks, you are welcome to post a message on The Staff Lounge, a free discussion area. Your input would also be welcomed in the Votes for Deletion and Requests for Adminship discussion pages. These pages are all active discussion areas that help to shape the Wikibooks community as a whole.

Sometimes it is easy to forget that the Wikibooks community is much larger and more diverse than the people who work in a single book, or on a single bookshelf. Hopefully, together we can all make Wikibooks a better place, and a more valuable educational resource.

The staff at Wikibooks 13:11, 21 December 2006 (UTC)

User page new header!
I have to say I like that (& long may it stay that way) - regards -- Herby talk thyme 18:30, 21 December 2006 (UTC)

I like it too. I was a deletionist at Wikipedia, but I've quickly come to realise that I am not here, and that there is little need for deletionism. I like it that way. :) --Iamunknown 21:05, 21 December 2006 (UTC)

 * Long may the grin last. I guess I arrived as a peeved deletionist but I'm getting better.  I still a bit prejudiced about crap pages tho.  In the end I guess WP just didn't suit me (twice! - the current one and a previous one so your name was familiar) WB does.  It is mildly frustrating at times but there's a good bunch here which helps a lot and its waay more laid back.  Would it bother you if I steal some of your user page style?  Mine was deliberately minimalist but it's bugging me a bit now (no idea when I'll get to it tho).  Looking forward to the book BTW. -- Herby  talk thyme 08:00, 22 December 2006 (UTC)

 * Thanks - I like to learn from others. Hope things get better for you, be happy to help if I can.  The book should be a good outlet -- Herby  talk thyme 16:51, 22 December 2006 (UTC)

Fixed...
I'm not sure why that was protected against editing... it was done by a sysop who was desysopped on wikipedia a few months ago, go figure :).

It's unprotected now, feel free to list it. -- SB_Johnny | talk 00:49, 22 December 2006 (UTC)

Howdy
Nice CSS. :) --Remi0o 06:34, 22 December 2006 (UTC)

wp mess
I saw the title of the page, and didn't read a single word. Wikipedia will be OK, it just needs to implode for a while... it's a tempest in a teapot, and regardless of the tempest, the tea's still yummy. Ignore it, there's nothing to see there :).

I'm on IRC, as usual (quite the party!). -- SB_Johnny | talk 23:53, 24 December 2006 (UTC)

Positive Psychology
Sure, I could use help. I don't really know much about it beyond reading a couple of magazine articles and The Art of Happiness by the Dalai Lama (if that counts). But anyway, I started it because it's a new, interesting field in psych and something people should know about. I guess I'll try watching the Positive Psychology lectures taught by Tal Ben-Shahar to educate myself.

You stated in your user page an interest in China. In that case, 看一看 at the progress on the Chinese (Mandarin) Wikibook. It has (IMO) a pioneering design and unparalleled quality for a language Wikibook, but is very short on content for the moment. I'm eager for more contributions or suggestions.

--Everlong 14:32, 27 December 2006 (UTC)

Template:ASPCite
Hey Elara, is Template:ASPCite redundant to Template:DSMCite? And if so, may I (or you) nominate it for speedy deletion? Thanks, Iamunknown 20:19, 21 January 2007 (UTC)

Sexual Health/Rape
Hello Elaragirl, how are things going with your book? It all looks very good to my untrained eye.

This page is part of the Sexual Health book, a pet project of mine. I would like to write something about the topic of rape, to try and dispel the rumors, and talk about some of the issues involved. considering your work on the abnormal sexual psychology book, I was wondering if you had any notes/research/expertise in the area of rape that we could use to help expand this page? Even a short sidenote about the mindset of rapists, or the psychological effects on rape victims would be valuable, if you have such information to share.

If not, that's fine too, I can probably look up most of the information I need on google or wikipedia. Thanks in advance! --Whiteknight (talk) (projects) 03:43, 6 February 2007 (UTC)

 * Thanks very much for your input. I'm sincerely sorry if I have reminded you of any negative memories. --Whiteknight (talk) (projects) 13:50, 8 February 2007 (UTC)

Template:Abnormal Sexual Psychology
Hello Elaragirl, long time no see! I created this template for your book, and I've put it at the top of every page. "Page header templates" help to standardize the look-and-feel of the book, they give a standard way of navigating from page to page, and they serve as a vehicle for properly categorizing all the book's pages. I stole this template from your own work at Template:Abnormal Sexual Psychology/navtemplate, to try and preserve your artistic vision for the book. You are free to change it, of course, if you want something different to suit your needs. Let me know if you have any questions. --Whiteknight (Page) (Talk) 15:12, 17 August 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 Elaragirl. To make sure that both of you can use all Wikimedia projects in future, we have reserved the name Elaragirl~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:11, 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) 04:55, 19 April 2015 (UTC)

title: User talk:Elaragirl~enwikibooks


text:
Automobile Repair/Saturn

Models

 * Saturn S-series (1991-2002)
 * Saturn L-series (1999-2005)
 * Saturn ION (2003-2007)
 * Saturn VUE (2002-present)
 * Saturn AURA (2007-present)
 * Saturn OUTLOOK (2008-present)
 * Saturn RELAY (2005-present)
 * Saturn SKY (2007-present)
 * Saturn Astra (2008-)

title: Automobile Repair/Saturn


text:
User:Celestianpower/Spanish/Lesson 1

Lesson 1 — ¿Cómo te llamas?

Dialogue

 * Raúl: ¡Hola! Me llamo Raúl. ¿Cómo te llamas?
 * ''Sofía: Hola, Raúl. Me llamo Sofía. ¿Cómo se escribe Raúl?
 * ''Raúl: Se escribe R-A-Ú-L. ¿Qué tal?
 * ''Sofía: Regular. ¿Y tú?
 * ''Raúl: Muy bien, gracias.
 * ''Sofía: ¡Qué fantástico! Adiós, Raúl.
 * ''Raúl: ¡Hasta luego!

Translation (wait until the end of the lesson).

Hello!

 * Examples
 * ¡Buenas mañanas, clase!
 * Good morning, class!
 * Hola, ¿Qué tal hoy?
 * Hello, how are you today?
 * Adiós, ¡hasta luego!
 * Bye, see you soon!

Go to the exercise.

What's your name?
To ask someone else's name in Spanish, use Cómo, then one of the phrases in the table below (¿Cómo te llamas? is "What's your name?").

In Spanish, to say your name, you use the reflexive verb llamarse, which means literally to call oneself (Me llamo Robert is "My name is Robert").

 * Examples
 * Me llamo Chris
 * My name is Chris
 * Se llaman Peter y Robert
 * They're called Peter and Robert.
 * ¿Cómo te llamas?
 * What's your name?
 * ¿Cómo se llama?
 * What's his name?

Go to the exercise.

Spanish Vocabulary • Lesson 1 ¿Qué tal? How are you? Inglés 	Español How are you?Qué tal? ¿Cómo estás? Great!Fantástico Fantástica Very well muy bien Well 	Bien Fine 	Regular Bad 	Malo Mala Really bad 	Fatal And you? ¿Y tú? Thank you 	Gracias

How are you?
On some of the words above, there are two options. The one ending in "o" is for males, and the one ending in "a" is for females. It's all to do with agreement, which is covered in the next lesson.
 * Note

 * Examples
 * Roberto: Hola, Rosa. ¿Qué tal?
 * Hello, Rose. How are you?
 * Rosa: Muy bien, gracias. ¿Y tú, Roberto?
 * Very well, thanks. And you, Robert?
 * Roberto: Regular. ¡Hasta luego!
 * I'm OK. See you later!

Go to the exercise. Spanish Vocabulary • Lesson 1 ¿Qué tal? How are you? Inglés 	Español How are you? ¿Qué tal? ¿Cómo estás? Great! Fantástico Fantástica Very well 	Muy bien Well 	Bien Fine 	Regular Bad 	Malo Mala Really bad 	Fatal And you? ¿Y tú? Thank you 	Gracias

The Spanish alphabet
Here is the normal Spanish alphabet. However words aren't alphabetized by it. Please read the notes and sections below. (Blue letters are a part of the normal English alphabet.)

Audio: [[media:Spanish_alphabet.ogg|OGG]] (646KB)

Although the above will help you understand, proper pronunciation of Spanish consonants is a bit more complicated:

Most of the consonants are pronounced as they are in American English with these exceptions:
 * b like the English b at the start of a word and after m or n; otherwise closer to v (in Latin America there's no distinction)
 * c before a, o, u and other consonants, like English k
 * c before i and e like English th in “think” (in Latin America is like English s)
 * ch like ch in “cheese”
 * d between vowels (even if it starts a word following a word ending in a vowel) or at the end of a word, like English d in dental
 * g before e or i like the Scottish pronunciation of ch in “loch”, except that it is voiced
 * g before a or o like g in “get”
 * h is always silent (except in the digraph ch)
 * j like the h in hotel
 * ll is pronounced like English y in “yes”
 * ñ like nio in “onion” (or gn in French cognac)
 * q like the English k
 * r slighty trilled; like a soft d except at the beginning of a word or after l, n or s where it is trilled
 * rr should be trilled longer than a single r
 * v is pronounced like a cross between a v and a b
 * z like the English th (in Latin America, like English s)

How do you spell that?

 * Examples
 * Roberto: Buenas días. Me llamo Roberto. ¿Cómo te llamas?
 * Good day. My name is Robert. What's your name?
 * Rosa: Hola. Me llamo Benjamín. ¿Cómo se escribe Roberto?
 * Hello. I'm Benjamin. How do you spell Robert?
 * Roberto: Se escribe R (de Rioja); O (de Orangutan); B (de Barcelona); E (de España); R (de Rioja); T (de Tigre); O (de Orangutan).
 * It's spelt R (as in Rioja); O (as in Orangutan); B (as in Barcelona); E (as in Spain); R (as in Rioja); T (as in Tiger); O (as in Orangutan).
 * ''Rosa: Muchas gracias. ¡Adiós, Roberto!
 * Many thanks. Goodbye, Robert.

Go to the exercise.

Summary
In this lesson, you have learnt You should now do the exercise related to each section (found here), and translate the dialogue at the top before moving on to lesson 2...
 * How to greet people.
 * How to introduce yourself.
 * How to introduce others.
 * How to say how you are.
 * How to spell your name.
 * How to ask others about any of the above.

title: User:Celestianpower/Spanish/Lesson 1


text:
User:Elaragirl~enwikibooks/articles

 * 1) Automobile Repair

title: User:Elaragirl~enwikibooks/articles