text:
User talk:ERNesbitt~enwikibooks

Come introduce yourself at the new users page. If you have any questions, you can ask there or contact me personally. Kellen T 10:43, 5 July 2006 (UTC)
 * Please also check out the Cookbook policy page and the Cookbook talk pages.

 * Thank You. --ERNesbitt 19:07, 5 July 2006 (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 ERNesbitt. To make sure that both of you can use all Wikimedia projects in future, we have reserved the name ERNesbitt~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:07, 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:ERNesbitt~enwikibooks


text:
Umbraco/Various useful XSLT methods in Umbraco

The basics of using XSLT in Umbraco
Creating a variable:  Variables a after this referenced using $myVarName (prefix with $)

Outputting a value:

Expressions:

Converting to string: string($myVarName) Converting to number: number($myVarName)

If test:

Choose test:

Loop all nodes from root and down of a certain doc-type (this example includes sorting on a field in this doc-type):

Get a node name from the first parent node of a certain doc-type:

(Since the Umbraco 4.5 Schema, @nodeTypeAlias is no longer used) - for versions 4.5 and above, use: <xsl:variable name="myVarName" select="$currentPage/ancestor-or-self::doc-type-alias-goes-here/@nodeName"></xsl:variable>

Details of the change from using @nodeTypeAlias are here: http://our.umbraco.org/wiki/reference/xslt/45-xml-schema/no-more-@nodetypealias

Get an attribute value from the first parent node that has a certain doc-type: <xsl:variable name="myVarName" select="ancestor-or-self::node [@nodeTypeAlias = 'myDocType']/data [@alias = 'myAttributeAlias']"/>

Limit a for-each loop to run only five times (if position <= 5) (REMEMBER in XSLT the '<' sign must be written as '&lt;'  !) : <xsl:for-each select="$currentPage/descendant::node"> <xsl:if test="position &lt;= 5"> </xsl:if> </xsl:for-each> Loops first five descendents of current node.

Get attribute value from a current node in a loop: <xsl:value-of select="data [@alias = 'myAttributeAlias']"/>

Creating a template with two parameters: <xsl:template name="myTemplate"> <xsl:param name="startnode"/> <xsl:param name="endnode"/> </xsl:template>

Calling a template: <xsl:call-template name="myTemplate"> <xsl:with-param name="startnode" select="23"/> <xsl:with-param name="endnode" select="49"/> </xsl:call-template>

Get a parameter from a macro <xsl:variable name="myParam" select="/macro/parameterAlias"/>

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


text:
Talk:Horticulture

Project goals
Proposal:

 * 1. To create an exhaustive treatment of gardening techniques and methods.
 * 2. To capture "how-to" sections of WP articles related to gardening.

Wikilinking
Best not to overdo them... this is not WP.

Templates
Seems a good idea to have some regular outline that all chapters follow, particularly on chapters about individual plants.

Transwiki:How to distinguish a monocot from a dicot
Would you be interested in adopting this orphan? If the page will be useful, please integrate it into this book. By the way, I recommend you move the above to a "project information" or "to-do" page. --hagindaz 05:04, 14 July 2006 (UTC)

Transwiki:Proper care of a cactus is another page you may find useful. I also suggest merging Potato growing into this book. By the way, there's some content that should be integrated at A Wikimanual of Gardening/Organic Lawn Care/transwiki. --hagindaz 07:51, 14 July 2006 (UTC)

 * What do you mean by "integrated"? I'll check the TW and the potato book. SB_Johnny 17:44, 14 July 2006 (UTC)
 * The monocot/dicot article probably falls under botany rather than hotriculture...so might not belong in this particular book (though an introduction to botany would be a useful book too!) SB_Johnny 17:50, 14 July 2006 (UTC)

The difference between the two is essential to gardening as they will have very different nutritional, light, and other requirements. Also products such as the herbicide 24d are based on these physiological differences and are the reason that 24d will kill dandilions but not grass. 209.115.237.182 (talk) 19:45, 19 April 2009 (UTC)

Orphaned page
Found A Wikimanual of Gardening:Garden bed cleanup when going through orphaned pages, not sure where it should go within the book so I'll leave it up to someone involved with the project. Xerol Oplan 03:26, 17 August 2006 (UTC)
 * I'll grab it up. I'm kind of restructuring the whole thing anyway, so haven't been linking as much. SB_Johnny | talk 03:36, 17 August 2006 (UTC)

Going through orphans again, found a bunch of pages (some stubs, some with content). The fact that there's so many leads me to believe a listing or index was removed/deleted somewhere.

 * A Wikimanual of Gardening/Allium aflatunense
 * A Wikimanual of Gardening/An Invitation to Contribute
 * A Wikimanual of Gardening/Book Development Strategies
 * A Wikimanual of Gardening/Cardamine impatiens
 * A Wikimanual of Gardening/Cold Composting
 * A Wikimanual of Gardening/Corydalis ochroleuca
 * A Wikimanual of Gardening/Erythronium americanum
 * A Wikimanual of Gardening/Helleborus x hybridus
 * A Wikimanual of Gardening/Lonicera x heckrottii
 * A Wikimanual of Gardening/Mazus reptans
 * A Wikimanual of Gardening/Mukdenia rossii
 * A Wikimanual of Gardening/Paeonia obovata
 * A Wikimanual of Gardening/Pests and Diseases of Digitalis
 * A Wikimanual of Gardening/Pests and Diseases of Iris
 * A Wikimanual of Gardening/Rubus occidentalis
 * A Wikimanual of Gardening/Sassafras albidum
 * A Wikimanual of Gardening/Suburban Forestry
 * A Wikimanual of Gardening/Thymus 'Spicy Orange'
 * A Wikimanual of Gardening/Trillium stamineum
 * A Wikimanual of Gardening/Veronica peduncularis
 * A Wikimanual of Gardening/Viburnum x burkwoodii
 * A Wikimanual of Gardening/Waldsteinia fragarioides

Collapsing volumes...
I'm going to collapse all volumes of this project into one book (A Wikimanual of Gardening) for ease of linking from other wiki projects, the cookbook, etc. New entries should use the form A Wikimanual of Gardening/, preferably without subchapters, to make linking here as easy as possible. -- SB_Johnny | talk 13:00, 28 August 2006 (UTC)

Cover images
Currently I'm changing the cover/template image once per month. SB_Johnny | talk 10:00, 3 October 2006 (UTC)

Previous images (click to expand)

 * September, 2006: [[Image:English_Daisy_(Bellis_Perennis).jpg|50px]]

List of templates using this image

 * Horticulture/Stub

"Modifying Wikipedia Articles for Use in a Wikimanual of Gardening"
why isn't /Modifying Wikipedia Articles for Use in a Wikimanual of Gardening/ a part of this discussion page? Hoogli 16:25, 29 May 2007 (UTC)

 * It's part of the meta side of this book. I didn't bring it up for discussion here because there wasn't really anyone to discuss it with :P. Nice to see you! -- SB_Johnny | talk 19:15, 29 May 2007 (UTC)

title: Talk:Horticulture


text:
User:Ecb6pitt

I'm Emily, and I'm from Pittsburgh, PA. I have a 9 month primary contract in the town of St-Paul-Les-Dax, in Landes. I'm looking for any advice! :) My email is ecb6pitt@yahoo.com.

title: User:Ecb6pitt


text:
User:Skasavaraju

How to add an image from the java class?

I have to call matlab excutable for some processing.Once processing is done matlab will generate some images. Since matlab take some substantial amount of time for processing i want to create a thread that waits for the matlab excutions and then creates a hbox and appends these resulted images from the matllab. i created images in theard class as follows.

String[] imgsrc={"/images//results/OutImage_perf_run.png","/images//results/OutImage_over_lowbody.png","/images//results/OutImage_acute_lowbody.png"};

String[] labelValues={"Physical Fitness Test","Overuse Injury","Stress Fracture"};

String[] styles={"color:green;font-size:10pt;background:white"};

// String[] buttonIds={"pftButton", "oiButton", "sfButton"};

String[] pageSrc={"/Analysis/PftResult.zul", "/Analysis/OveruseResult.zul", "/Analysis/SFResult.zul"}; Hbox hbox=new Hbox; for (int i=0; i< imgsrc.length;i++) {

Vbox vbox=new Vbox; Window w=new Window; Label label=new Label(labelValues[i]); label.setStyle(styles[0]); w.appendChild(label); com.potix.zul.html.Image deleteImage=new Image; deleteImage.setSrc(imgsrc[i]); w.appendChild(deleteImage); Button button =new Button("Details"); button.addEventListener("onClick", new ButtonListener(pageSrc[i],page)); w.appendChild(button); vbox.appendChild(w); hbox.appendChild(vbox); }	 }//end of constructor Whatever path i mention it says some null pointer exception.

Please guide me how to do this ?

Thank you

title: User:Skasavaraju


text:
User talk:82.159.137.18

California AB 1493
Hi. Original texts are not appropriate for Wikibooks, of any language. Please use Wikisource and the Spanish version instead. Thanks, hagindaz 15:58, 5 July 2006 (UTC)
 * OK. Thank you. But you could leave the text in a subpage (i.e. California AB 1493) upto the moment I can move it to Wikisource. And use the template:move to Wikisource

 * Done. Sorry about that, I assumed you had the bill available elsewhere. :) --hagindaz 08:08, 6 July 2006 (UTC)

 * By the way, for future reference, we use transwiki to mark pages for transwiki, delete for speedy deletions, and vfd for votes for deletion. --hagindaz 08:11, 6 July 2006 (UTC)

 * Thank you a lot. Now we can say everything is ok. Regards.--82.159.137.18 08:25, 6 July 2006 (UTC)

title: User talk:82.159.137.18


text:
User talk:Alistairbanks

Alistair Banks
I have deleted the page Alistair Banks because it does not appear to be a textbook. If you do wish to write a textbook on the subject, then please recreate the page after reading WB:NEW. Thanks. Wikipedia is more appropriate for biographical encyclopedia articles. Please read w:WP:VANITY and w:WP:N before creating your article, however. --hagindaz 16:12, 5 July 2006 (UTC)

 * Welcome to Wikibooks. Having reviewed Hagindaz's deletion, it looks like you were just trying to write up a brief summary of yourself. These are perfectly acceptable, they just need to be in your userspace (ie in pages beginning with User:Alistairbanks) rather than in the main namespace. I ahve therefore restored the page and moved it to User:Alistairbanks.

 * I hope this does not deter you from making a positive contribution towards Wikibooks' aim of producing high quality textbooks and annotated texts. All the best, Jguk 16:56, 5 July 2006 (UTC)

Welcome
Come introduce yourself at the new users page. If you have any questions, you can ask there or contact me personally. Urbane  (Talk)   (Contributions)  22:15, 11 February 2008 (UTC)

title: User talk:Alistairbanks


text:
User talk:208.197.234.251

Academical village people
I have deleted the page Academical village people because it does not appear to be a textbook. If you do wish to write a textbook on the subject, then please recreate the page after reading WB:NEW. Thanks. Try Wikipedia instead. --hagindaz 16:15, 5 July 2006 (UTC)

title: User talk:208.197.234.251


text:
User:Alistairbanks

Alistair Banks is now a technology consulant and investor, living in The New Forest, England.

Alistair has most recently been involved with WebBrick Systems], a home & building automation "Smart Homes" company, as an investor and Director, while still managing New Forest Community Broadband Ltd and Mid Fowey Community Broadband]. Since returning to the UK in 1999, he has also been a director of UK ISP izR Solutions Ltd until its sale, had been a director of the Marais Group Ltd and built out the technology in its conferencing site, Gresham Court Hotel in Bournemouth.

In a voluntary capacity, Alistair is on the board of the New Forest Business Partnership with special remit for rural broadband & the New Forest Show marketing committee, helping them with web and social networking issues.

From 1988 for 10 years, Alistair was an evangelist and program manager for Microsoft Corp at its headquarters in Redmond, WA, and at Microsoft's UK Development Labs in Eastleigh, England. During his first 5 years, as the first software evangelist, he mangaged Microsoft's relationship with a number of large ISVs (e.g. Lotus, Novell), and was involved in many projects including the definition of the Win32 APIs, WinSock, OLE2, the promotion of a standard Windows user interface, and also in projects of some notority including OS/2 & Cairo. His second 5 years were as a program manager, when he worked on the development of multimedia in Windows NT 3.5, then on the creation of ActiveMovie (later to be DirectShow) and laterly WDM Streaming.

Prior to Microsoft, Alistair worked for Midland Bank's dealing rooms (Midland Montagu) in the City of London, in the Personal Computer group there. He created dealing systems from 1983 for 5 years, even starting writing of Windows 1.0 applications in 1985, also involved in the development of NetDDE which was sold to Microsoft in 1989.

Alistair has a degree in Computer Science from Imperial College, London University, and when to school at Epsom College. He has 3 daughters.

title: User:Alistairbanks


text: Category:Book:Haiku

title: Category:Book:Haiku


text: Category:Book:Harmonica

title: Category:Book:Harmonica


text: Category:Book:Hebrew

title: Category:Book:Hebrew


text:
Category:Book:Hungarian

la:Categoria:Lingua Hungarica

title: Category:Book:Hungarian


text:
A-level Physics/Nuclear and Particle Physics

Contents

 * The Nucleus
 * Neutrons And Fission
 * Fusion
 * Matter and Antimatter
 * Fundamental Particles


text: Category:Book:Høgnorsk

title: Category:Book:Høgnorsk


text: Category:Book:Hindi

title: Category:Book:Hindi


text: Category:Book:Home Remedies

title: Category:Book:Home Remedies


text:
A-level Physics/Nuclear and Particle Physics/The Nucleus

Nucleons
Protons and neutrons are the constituents of atomic nuclei. A proton is a positively charged particle which has the same charge as an electron, but positive. A neutron, on the other hand, is a neutral particle with zero charge. Protons have a mass of 1.6552e-27 kg and a charge of +1.66e-19 Coulombs, while neutrons have a mass of 1.6725e-27 kg. Protons and neutrons collectively are called NUCLEONS. The number of protons in the nucleus give the atomic number, while the sum of the total mass of protons and neutrons gives 99.9% of the mass of the atom, the rest is due to electrons. On the periodic table, you can see the number of nucleon written as the mass number.

What force holds the atomic nuclei together?
For many years people had wondered what held an atom in place and why it doesn't just split apart due to repulsive electric forces. At first they thought that it was gravity which held the atoms, protons and neutrons in place. This was disproved after they found out gravity was very very weak at nuclear levels. In fact it's a million million million million million million times too small. (10^36) We now know the interaction responsible for binding quarks, anti-quarks, and gluons to make hadrons is called strong nuclear force (SNF) or The Strong Interaction. Residual strong force interactions provide the nuclear binding force. Simply put, strong force is the force that holds atomic nuclei together against the Coulomb (electrostatic repulsion) force of repulsion between protons. The strong force acts on any pair of hadrons. It has an extremely short range of only a few femtometers. Even so, at a very short range indeed, the SNF becomes repulsive, otherwise the neutrons and protons would be attracted together to the point where they would become a singularity.

The radii of atomic nuclei
The following gives the formula to work out the radii of atomic nuclei. $$r=r_0A^\frac{1}{3}$$ Where:
 * r is the radii
 * A is the number of nucleons
 * r0 is a constant having value 1.2 fermi to 1.5fermi.

Density of nuclear matter
$$density = \frac{mass}{volume}$$

$$\rho= \frac{m}{\frac{4}{3}(\pi r ^3)}$$ (since $$\frac{4}{3}(\pi r ^3)$$ is the volume of nucleus which is considered as sphere of radius r).NUCLEAR DENSITY is constant throughout the nuclear dimensions.

Calculating electrostatic force
$$F = \frac{1}{4\pi\epsilon_0} \frac{Q_1Q_2} {r^2} $$ Where: above expression is known as a coulomb law of electrostatics.
 * F is the force
 * $$\epsilon_0$$ is the permittivity of free space with the value 8.8541878176e-12 F/m c(farad per metre per coulomb)

Calculating gravitional force
$$ F = G \frac{m_1 m_2}{r^2} $$

Where:
 * F is the force
 * m1 and m2 are product of the two masses;
 * and r being the distance between them.
 * G is the value of the gravitational constant, which is

 * $$ G = 6.67 \times 10^{-11} \ \mbox{N} \ \mbox{m}^2 \ \mbox{kg}^{-2} \,$$


text: Category:Book:Homeopathy

title: Category:Book:Homeopathy


text: Category:Book:Horn

title: Category:Book:Horn


text: Category:Book:How To Become A Good Student


text: Category:Book:How To Assemble A Desktop PC


text:
User:ERNesbitt~enwikibooks

My Recipes

 * Cookbook:Strong Noodles

Misc

 * Talk:Cookbook
 * /Scratch

title: User:ERNesbitt~enwikibooks


text: Category:Book:How to use a Motorola DVR

title: Category:Book:How to use a Motorola DVR


text: Category:Book:IB Biology

title: Category:Book:IB Biology


text: Category:Book:IB Chemistry

title: Category:Book:IB Chemistry


text: Category:Book:IB Economics

title: Category:Book:IB Economics


text: Category:Book:IB English

title: Category:Book:IB English


text: Category:Book:IB Cultural Anthropology

title: Category:Book:IB Cultural Anthropology


text: Category:Book:ILife

title: Category:Book:ILife


text: Category:Book:IB Music

title: Category:Book:IB Music


text:
Category:Book:Icelandic

pt:Categoria:Islandês

title: Category:Book:Icelandic


text: Category:Book:Immigrating to Canada

title: Category:Book:Immigrating to Canada


text: Category:Book:Immunology

title: Category:Book:Immunology


text:
Category:Book:Indonesian

id:Kategori:Bahasa Indonesia

title: Category:Book:Indonesian


text: Category:Book:Instructional Technology

title: Category:Book:Instructional Technology


text:
Muggles' Guide to Harry Potter/Magic/Floo Powder

Overview
Floo powder is a greyish or silvery powder which allows access to the Floo Network transportation system.

Extended Description
The Floo Network is a magical linking of most fireplaces in the Wizarding world; it is used as a means of rapid transportation from one Wizarding building to another. Floo Powder provides entry to that network; place a pinch of Floo powder in the fire, and it becomes green and harmless. You may then enter the fire, and speak your destination, and you will be carried to the fireplace you have named. It is a very dizzying ride; you spin very rapidly while in transit, and you would be well-advised to keep your elbows tucked in.

It is also possible to place only a body part, such as a head, in the fire, whereupon that part will be the only thing that is carried to your named destination. Placing your head in someone else's fireplace is one way to communicate over long distances, but as Harry finds out, it can be rather disconcerting to have your head spun around rapidly while your body stands still. Colloquially, this is sometimes referred to as a Fire-call.

Apparently in certain circumstances, Floo powder or something similar to it can be used to summon someone. Professor Snape uses this in Harry Potter and the Prisoner of Azkaban to summon Professor Lupin to his office.

Analysis
Most commonly, after you toss a pinch of the powder in the fire, you step into the fire and pronounce the name of the place you want to go to (e.g. "Diagon Alley"). If you only want your head transported you sit in front of the fire and only stick your head in. Unclear pronunciation has its consequences; you might end up somewhere other than your intended destination.

However, if you only want to call someone, it seems that it is unnecessary to say the name of that person's actual residency, the name of that person will do. It is unclear whether you need to know their current whereabouts, though.

Questions

 * 1) When someone is talking to another person with Floo powder, their head is in that other person's fireplace. If someone was in the same room as you, talking to someone else with Floo powder, what would you see?


text: Category:Book:Intelligence Intensification


text:
Talk:Organic Chemistry/Aromatic reactions

I just quickly added the reactions for Halogenations, nitrations and sulfonations. Sorry if they're not quite formatted correctly. Oldthrasbarg 21:46, 5 July 2006 (UTC)


text: Category:Book:International Relations

title: Category:Book:International Relations


text: Category:Book:Communication Theory

title: Category:Book:Communication Theory


text:
Managing Groups and Teams/Leader Credibility

Questions Posed
Once a team is formed, how should the team leader handle questions about his/her ability? For example, in the case where the team has had its first significant meeting and the leader did something to cause others to questions his/her ability to lead the project. Along the same line, are there particular steps a team leader can take to mitigate a blow to the team either from external forces or internal forces (say in the form of personal conflict or someone essential to the project leaving the company)?

Introduction
The question above is presented as to ask how you can mitigate questions to your credibility as a team leader. This lack of credibility could be from something you did wrong in a meeting or a mistake you made on a project. The question also asks how you, as a team leader, can soften the blow to the team from an internal or external force affecting the team. This last question is very broad and because of this, the chapter will focus that question and the others with respect only to establishing, maintaining and restoring credibility as a team leader.

You can read all the books and follow all the rules about managing and leading, but inevitably, you will find your credibility in question from one, or a number of team members at some point during your career. It may almost seem easier to deal with if you know you did something wrong or inappropriate. The hard part is when you have somehow lost credibility when you’ve done, pretty much, everything right. During this chapter, we will look into a number of reasons for finding yourself lacking credibility with your team members. We will also offer general advice on how to keep or restore your credibility.

While there are many reasons your team may find your credibility lacking, we will focus on a few very common ones. First, we will look at how your credibility may be threatened simply by a stereotype attached to you. Second, we will look at how your personality traits can affect credibility. Then we will look into how leading your former peers can cause credibility problems and how to alleviate them. Following these sections we will offer advice on how to establish credibility in a newly formed team, and finally, how to establish your credibility in general as well as avoid pitfalls.

Overcoming Stereotypes
Establishing leadership credibility in a group or team setting can be difficult enough without having to battle stereotypes along the way. This section will focus briefly on the different stereotypes that exist within the work organization, specifically, the groups and teams within these organizations. This section will also attempt to advise on how to avoid the pitfalls of stereotypes.

First, we will define exactly what a stereotype is and what it is capable of. Stereotypes occur when we assign and generalize certain attributes, characteristics, qualities or shortcomings to a specific group of people. For example: "The elderly drive poorly," "Women are too emotional," "Teenagers are lazy," or "Men are cold and distant." You may think these examples are harmless, but these are only starting points from which stereotypes can become extreme and irrational. Some categories which can be a target of stereotypes are: race, religion, gender, class, age, etc.

Stereotyping is a way our brain tries to processes the endless amount of information it is presented with daily. With so much stimulation to account for, stereotyping is a way the brain cuts through it all in order to make it presentable. This is often done subconsciously and is not always linked to negative outcomes. The danger presents itself when we are unaware of this process going on in our brain and we begin to accept stereotypes as fact or reality. Stereotypes are far reaching and virtually everyone is a potential victim.

Stereotypes are damaging when we assume something about someone, or judge them prematurely, simply because we assign them to a larger group with a predetermined set of characteristics. Stereotyping is often linked closely with prejudice, which occurs when one makes a conscious decision to dislike, distrust, or work against a specific group because of the negative stereotypes associated with that group.

History is laced with stereotyping and prejudices. Modern time takes no exception. A common place stereotyping takes place is within organizations and teams within these organizations. This behavior can destroy any attempts to create a collaborative environment within work teams and can effectively prevent production or progression. So the question presents itself, how do we keep this behavior out of our teams in order to be more successful?

As a leader of a group/team who may be battling a stereotype while trying to obtain credibility, you must first make it your priority to rid yourself of any thought or behavior that endorses or exhibits stereotyping. You must be careful not to get defensive expecting that you are being stereotyped. Give your team the benefit of the doubt initially. Team attitude often reflects leadership. If they see you are relaxed and open they may adopt your attitude. This is one way to battle stereotypes within groups.

Another way to battle stereotypes is to create an atmosphere conducive to open communication. It is through talking to people and forging relationships with others that stereotypes can be shattered and put to rest. This is easier said than done, but achievable if a team leader is determined to have a successful group.

Also, when creating a group, create groups with diversity. This builds off the previous point of communication. We are often afraid of what we don't know. A diverse group can create an environment where learning and understanding can be achieved and stereotypes dispelled.

It may sound simple, but one final way to counter a stereotype when leading a team is to simply work hard and prove you are a good leader first and foremost. If you leave no doubt in your groups’ mind you are there to facilitate their success, you will begin to create an atmosphere where attitudes can change and minds can be enlightened.

Personality Types
When dealing with team environments, the personality of the group and those of individuals are determinants in whether the group will succeed or fail at its goals and endeavors. Within each group, there is the potential for each of the members to have significantly different strengths and weaknesses which are essential for an effective team. Examples of these characteristics are being introverted and extroverted. Introverts are people whose thoughts and interests are directed inward rather than outward toward others. On the other hand extroverts are interested in others or in the environment. Speaking in broad terms, they are a gregarious and unreserved person. With this in mind, to be an effective leader, you need to not only identify these traits in others, but also identify them in yourself in order to establish leadership credibility. Otherwise, ineffective management of your team of different personalities, working motifs, and styles may lead to unnecessary challenges and conflicts that could possibly lead to the demise and failure of the overall project.

In understanding introversion and extroversion, Carl Jung (one of the earliest leaders into the understanding and exploration of this type of personality trait), was able to understand and develop the core principles of extroversion and introversion. He was able to view the behavior of humans as either habits or as personality patterns. He then explained the differences accordingly to those unique, distinguishable, and variable social patterns. He directed and focused his research on the intuition, thinking, sensing, and feeling components which were later published as major players in his psychological traits theory.

During different events in our daily lives, we tend to utilize both aspects of introversion and extroversion. But, generally speaking, most people rely upon one dominant expression, whether it is introversion or extroversion, during the daily events and dramas that induce stressful situations. The preferences that are expressed by these different types of personalities also affect and impact social understanding and learning of perceptions, judgments, different learning styles, as well as sociological preferences each individual resorts to.

When comparing introverts and extroverts, with our perception of what the team and its organization represents, there are still different view points we hold. First, introverts might view and feel the team meeting and discussions as draining, stressful, and (more or less) a waste of time. While extroverts view the team meetings as productive and energizing toward the end goal of the team.

It is essential for you, as the team leader, to not only understand the different aspects of each team member, but also of yourself and what impact you have in leading the group. Being able to assess your ability and draw upon the abilities and strengths of others will provide an easy path to a successful team. By understanding and acknowledging different personality types, strengths and weaknesses, learning styles, perceptions, and judgments of each group member, you have already taken steps in the right direction to becoming an effective leader. Doing this should dismiss most, if not all, skepticism of your leadership ability. When you have been able to identify these aspects of your group, you can effectively direct and coordinate the team towards your goal or directive in the most efficient manner possible.

As the team leader, understanding group meetings is an integral component of the development, planning of the assigned project, and development of team unity. As previously indicated, extroverts view these meetings as a venue for essential thought provoking discussions and a place to surcease any problems that may arise. So to be an effective leader, you must acknowledge and mitigate these circumstances to the contrary of the introverts. These introverts would rather use the time (that most meetings would use up) to research, prepare, and plan for these meetings on a lesser scale. By understanding this, you can handle any skepticism and quandaries about your leadership ability by providing advanced written information about the team members, agenda(s), reports, or possible discussion questions. This forethought and preplanning allows introverts the necessary time to organize and preplan their feelings and thoughts so their involvement within the group will be more substantial and appreciated by the extroverts who, by their very nature, will applaud and welcome their contributions.

In addressing the possible scenario of conflict from within the team itself or from external forces, you need to address and understand the different areas of conflict that may arise. As previously mentioned, the different personalities may be cause for conflict within the team environment. To quell such proprieties and demurrals from the different team members, using the knowledge and understanding of each team member and their strengths and weaknesses is essential as an effective team leader. When such internal conflicts arise, being able to negotiate and mitigate conflicts is essential. In addition, knowledge of the team members' personality and learning styles is important in order to show foresight and understanding of the conflict that has occurred.

So in conclusion, as an effective and forthright leader will need to have perception and knowledge based upon the different personality types of each group member so any possible conflict and prejudice arising can be eliminated.

Effectively Leading Your Former Peers
You have spent the last few years working hard with your team, you’ve seen great success together and you’ve been able to establish some very positive professional relationships. You are comfortable with your team and are satisfied with the work you have done together. Now things are about to change, you have been rewarded for your hard work and have been selected to lead the team you were once a part of.

After the initial euphoria and excitement of your recent promotion wears off, you may realize the relationships with your team members is not the same. Suddenly they look to you for motivation and guidance. Will they buy into your ideas? Will they respect you? Will they still be your friends? Do you want them to be your friends? How will performance evaluations go? As managers continue to climb the corporate ladder many of them have had to (or will) deal with these types of situations at one time or another. This section is dedicated to helping managers effectively manage their relationships with former peers, while at the same time adapting to their new leadership role.

Generally speaking, two behaviors can emerge as managers begin to lead their former peers. One end of the spectrum is trying to remain “one of the guys” (or gals). This type of manager has difficulty making unpopular decisions, performing disciplinary action, performance evaluations, assigning responsibility, and holding people accountable. At the other end of the spectrum, one morphs into an unrecognizable individual that feels he or she must change everything the team has been doing and make it their own. After all, the leader is ultimately responsible for the success and failure of the team. This behavior oftentimes results in rifts between the leaders and the rest of the team. The following are some effective methods in making the transition from team member to leader.

First, don’t try and change everything at once. You will have plenty of time to implement your ideas and plans for success. Now the important part is getting your team on board with you as their leader. Second, get the message out that you will be even handed in dealing with subordinates. There will certainly be some subordinates you were closer with then others. The ones you were close with may expect some preferential treatment while others may expect to see you come down harder on them. Ensuring your team members you will be even handed will help them develop trust and respect for you as their leader. Next, steer clear of situations where favoritism might be perceived. In addition, repair rifts with former colleagues. There will certainly be some hurt feelings and disappointment among your peers. After all, you beat them out for the job. Some peers may also harbor ill feelings from previous conflicts that you may have been engaged in. Take action to repair these rifts and work towards establishing positive relationships. Finally, clearly define your role and what your expectations are. You are the leader act like it. Let your peers know what you expect of them and hold them accountable for their performance.

Stepping into a leadership role involving peers can be a very challenging situation. Difficult situations will certainly arise and tough decisions will have to be made but that’s why you’re the leader. By clearly establishing goals and expectations of every team member and ensuring the entire team that you will not play favorites and everyone will be treated equally you will be able to establish your credibility as an effective leader an ultimately lead a more successful team.

Leading a New Team
You’ve spent the money, done your homework, and earned your degree now you have the job. You are now leading your own team. Now, how do you do it? How do you establish your credibility to team members you have never met? What are their expectations of you? How do you instill confidence in your team about your leadership abilities? How do you handle questions and concerns about your leadership abilities? The following section is dedicated to assisting new leaders in managing their teams and promoting success within their new role.

As the new leader you need to take charge. You may be replacing a great leader who had great success and admiration from his or her team and the shoes you are expected to fill may be great. Or you may be replacing a leader who was despised by his or her team and the team was a disappointment. Either way, there are several challenges leaders face as they step into new environments as team leaders. They may be dealing with high expectations and questions from their team such as, “That’s not how so and so would do it” or “How will this new leader be different from the last”. Despite how the team may have performed in the past it’s your ship now, the success or failure of the team is your responsibility. Your team needs to know that you are committed to being their leader and leading them to success. Communicate your goals and expectations clearly to every team member. Let them know the importance of their role in the team. Be sure to give your team the time and resources to achieve their goals and give them the training to achieve their goals.

Your team needs to trust you and one of the best ways to gain their confidence in your abilities is through your example. You were hired for a reason, obviously your boss has confidence in your abilities. Now is the time to showcase them for the rest of your team. Your attitude and the manner in which you perform your tasks will be infectious. The way you act and interact with your team will ultimately reflect the way you and your team will perform together.

Next, be accountable. Problems will arise and mistakes will be made and at times human nature prompts us to deflect blame or try and spin things in a better way, after all no one wants to be blamed for a major screw up. Effective leaders know how to stand up and be held accountable.

Finally, never underestimate the power of effective listening Take the time to get to know your people. Effective leaders must be willing to see the team from the team’s perspective. As a leader you may have your own vision of what success is, if your team has a different vision than you, the team will never arrive at the same point of success. Talk to each individual team member, find out what is important to them. It is the only way you will know how to effectively motivate them.

Individual interviews with each team member can be very effective in helping to establish positive relationships within your team. Furthermore, you can gain valuable insight into the nature of the team and how you can effectively use the team’s resources to achieve the team’s goals. Be sure to act upon the information you gain from your team through your individual interviews. Involving your team’s insights will help create a culture of trust and unity within your team and their insights may oftentimes be more profound than your own. Build up your people, give them responsibility and hold them accountable. Praise and recognize them when they deserve it. When they perform poorly let them know you expect more from them. They will respect you more as a leader and most often will be inclined to perform at a higher level for the success of the team.

Certainly leading a new team is a challenging role filled with many obstacles. Creating a positive environment is essential in achieving success as a team. After all, the team's performance is indicative of the leadership abilities of its leader. By taking charge, leading by example, listening, and taking action you will be able to instill confidence within your team. You will also establish your credibility and, ultimately, have more success as a team.

Establishing Credibility and Avoiding Pitfalls
Having or establishing credibility from the outset can make leading a team easier and give more leeway in decision making while leading a team (when it is done right). This section is easy when things go right. What about when they don't?

The first thing you should never do, is try and save face by pushing the blame onto someone else. This rarely works in the long run. You would hope the people in your team are smart and, as a consequence, see through this. Members of the team may play dumb at the moment to avoid conflict, but they will not appreciate you for it. This will always be in their mind when dealing with you. "Will they try and pin the next thing that goes bad on me?"

Think about those you respect most in your organization. Not who has the most influence or power, but who you respect. This is the type of person who is honest with themselves and their coworkers (this includes subordinates and higher-ups). When was the last time you were upset with someone for fessing up to an issue they caused before someone else mentioned it? Or graciously accepted criticism for a perceived or a real issue they may have caused? You may have been upset with what happened or the consequences, but think about your respect level for the person. This is most likely a person you would go to bat for in a tight situation, because you know they would have done their best and improved where they could. Taking this type of stance yourself, can go a long way in negating any issues that may happen early on in a group that question your ability to lead a project.

Most problems boil down to communication. Members of the group may have different interactive styles based on backgrounds or individual disciplines. Failure to accommodate different communication styles can lead to misunderstandings and possibly questioning abilities. One way to help members understand you is to give them an instruction manual. Even a cheap $25 tape recorder has instructions, why not you? Let your manual say, amongst other things: "Here's what gets me going," "Here's what annoys me," "Warning! Here's what will get you in trouble." These types of suggestions are probably better suited for a manager, but they could also work for subordinates or peers. Other sections of the manual could include: "Ask me to 'get to the point,' “If a description is not clear, please ask to be more concrete," "Warn me if I am heading down the wrong path," and "I tend to refer to statistics when I am uncomfortable with a topic." This type of instruction manual of yourself can be useful as a daily reminder to yourself on what you need to work on. Others, even timid ones, can call you on one of your issues without fear of offending or overstepping bounds. It will show you are truly looking to do your best and eliminate perceived inabilities caused by communication breakdown. As result, they will know where you are coming from.

Conclusion
During this chapter we have touched on a few items which can affect your credibility as a team leader. The issues we have discussed are common, but there are many more reasons why you may have lost credibility with members of your team. Knowing how to deal with common reasons for losing credibility will help you when other issues arise.

Hopefully the latter part of this chapter has given you some insight into how to, in general, establish, maintain, and restore your credibility as a team leader. You will never be able to please everyone, but you can certainly do your best to be an effective leader and use the information in this chapter to help you credibility as a leader and an example to the rest of you team.


text:
Talk:JavaScript

About

 * Started: 18 September 2005
 * Size: 8,200 words (Sep 2008)

DOM Manipulation features
It would be nice to have a list of DOM Features, with exsamples. I'd like to see what can and what can not be modified in a page on the browser side. Ervinn 22:33, 5 July 2006 (UTC)

 * Sitepoint are working on that and now have a JavaScript reference section which covers the DOM Pmw57 (talk) 03:56, 21 February 2009 (UTC)

 * The JavaScript Wiki, which I administrate, has the beginnings of such a reference for both DOM and ordinary JavaScript types, along with useful templates for such content. The top-level category is here. --Jesdisciple (talk) 08:27, 11 May 2010 (UTC)

files
I use  in a form to load a file. Normally, the user clicks it to load a file, and when the form is submitted, the file gets sent directly to the server.

Is there any way for JavaScript to read some of that file? (Perhaps something similar to the way JavaScript can read a file on the server using Programming Ajax?) So JavaScript code can check to see if it's the right sort of file (validate)? That way JavaScript could immediately tell the user to pick some other file (or cancel), rather than waiting until that file is sent to the server and rejected there.

(Is there a better place to post this kind of question? Perhaps http://developer.mozilla.org/en/docs/Core_JavaScript_1.5_Reference/reorg ?) --DavidCary 04:01, 30 January 2007 (UTC)
 * That would be a security issue. And this wikibook doesn't get much exposure and is largely inactive, so, yes, I'd advise searching for better communities to consult. --68.94.206.90 21:14, 25 November 2007 (UTC)

 * How is this a security issue? The section of the book that discusses this -- JavaScript/Working With Files -- currently doesn't mention any security issues; should it? --DavidCary (discuss • contribs) 12:35, 8 September 2011 (UTC)

Table of Contents
I'm new at this, so I apologize if I did this wrong. The table of contents looked pretty incomplete, had some headings that I found confusing, and had a couple of things that looked like they needed to be restructured. So I just went ahead and changed what I thought needed to be changed.

I added a ton of blank new sections. I'm planning on starting to fill some of these in, but I would love to see other JavaScript programmers tackle some of them if anyone gets the inclination.

--Wanorris 9 March 2007

 * Thank you Wanorris for helping to structure things here - I'm going through some sections now performing many much needed tidyups. Pmw57 (talk) 09:11, 21 February 2009 (UTC)

Contributers page
Made the page to sign if going to contribute Extreme circuitz 00:41, 1 October 2007 (UTC)

Is anyone going to do any work on this book?
I would like to propose some changes.

I think JavaScript should be regarded as a language in its own right, not just an appendage to a web browser. This means that the emphasis in the JavaScript book should be on JavaScript and how to write it well rather than on the application of JavaScript to web pages. Detailed discussions of web page document object models belong elsewhere and anyway the DOM is a sufficiently complex subject to need a book of its own. I don't mean that the DOM must not be mentioned but that it is not dependent on JavaScript nor is JavaScript dependent on it. For instance my interest in JavaScript just now is in programming inside Open Office, hence discussion of a web page DOM is irrelevant to me just now. Of course example code would frequently use the DOM but the details of the DOM should be given in a separate book linked to this one. Anyway I might contribute a chapter or two regardless of the organization. --kwhitefoot 17:38, 27 November 2007 (UTC)

 * Ooh... I didn't know this was here.  In case anyone's still around, we have a load of relevant content at the JavaScript Tutorial.  That wiki also has several general articles, and it's all licensed under the GFDL. --Jesdisciple (talk) 04:47, 2 November 2008 (UTC)

names of pages in this book
You can set up any hierarchy you want on the JavaScript/Contents page. But to make that easy to shuffle around and improve, the actual pages in this book should be named with the standard "flat" Naming policy: "JavaScript/" at the beginning, followed by a chapter name -- a self-descriptive chapter name like "Bookmarklets", not a uninformative "Chapter 17". (Older names such as "Programming:JavaScript:Standards and Best Practices" will eventually be converted to new-style names like "JavaScript/Best Practices"). (If they all were old-style, then I would leave it alone -- but most of them are already new-style today). Also, all pages of this book should have the " " label stuck on somewhere, so they will be automatically listed at Category:Javascript. --DavidCary 07:02, 5 December 2007 (UTC)

Cover image

 * See also JavaScript/Cover.

I have removed the image shown here in the thumb from the main page. IMHO the text "great book" is pretentious. Also, the image overcrowded the top of the page, forcing the readers to scroll down to the table of contents. A book about JavaScript would hardly have a landscape format--another downside.

--Dan Polansky (talk) 09:28, 7 September 2008 (UTC)

Program flow
What was supposed to be the content in the "program flow" section? The two options I know of either describe how JavaScript executed (e.g. executed in order from top of HTML file) or having to do with control loops (for, while, etc.) - and I think that both of these are already covered. --Sigma 7 (talk) 23:07, 6 February 2009 (UTC)

 * Since there wasn't any objection or comments, I removed that section from the draft version. --Sigma 7 (talk) 19:57, 22 February 2009 (UTC)

Purpose of this book
Is this book intended as a tutorial, or as a reference? At the moment it is neither. If the first, we will need to add a couple of exercises to each chapter, and much more explanation. If the latter, we will need to describe all reserved words in detail, as well as all functions.

For the moment i have assumed both. I have started creating small exercises. One additobnal problem we will have to solve is how to supply the answers as downloads: zips are not among the allowed filetypes here.

TeunSpaans (talk) 17:14, 12 May 2009 (UTC)

 * As the limitations here prevent delivery of top quality exercises and answers, i will stop working on this book. Sorry TeunSpaans (talk) 20:13, 15 May 2009 (UTC).

Request for Community Review
I'm revising the contents of some pages and removing others from the primary tutorial altogether. As this is a fairly sweeping change, I want to get community review before making it. If I don't hear anything within a week I'll just go ahead. Here's my revision as it stands: User:Jesdisciple/JavaScript --Jesdisciple (talk) 02:13, 14 May 2010 (UTC)

Thank You
I just want to say that as a person who knows some programming, but not JavaScript, and who now needs to know a little JavaScript, I am finding this book very helpful. Better than other things I've found so far. Communpedia Tribal (discuss • contribs) 23:04, 28 February 2017 (UTC)

Out-of-date
This book seems to be pretty out-of-date, with several obsolete topics still being featured (such as XMLHttpRequests). It would be a good idea to modernize the book somewhat, add pages about TypeScript and new functionality like the fetch api. Maybe a page can also be dedicated to the new operators, like the null-coalescing operator. And finally, we could include a page on popular frameworks like React/Vue. 2603:7000:E43F:9867:7D65:CD90:F560:AA4C (discuss) 03:07, 8 July 2022 (UTC)

+1. I will work on this in the next three months. With a focus on exercises for beginners. --Kelti (discuss • contribs) 14:34, 28 September 2022 (UTC)

After diving a little deeper into the subject, I have doubts whether it is possible to improve the book. I have read the old request for deletion (2013), but this is not my point. My main concerns are: So, my questions are: --Kelti (discuss • contribs) 06:58, 10 October 2022 (UTC)
 * There is a vast number of good Online tutorials and reference books for JS. What entitlement do we have for the additional publication of a JS wikibook? At least, we need one or more distinguishing features compared to the other publications: a different audience, a different level of detail, different usage rights, ....
 * The current book treats many issues closely related to JS: XMLHttpRequest, Ajax, DOM. To establish a higher degree of clarity we shall divide the pure JS issues (purpose of the language, syntax, concepts) from such aspects, which are not JS-specific (events, DOM manipulating, ...).
 * What is the purpose of the book? Tutorial, reference, examples and snippets, front-end focused, back-end focused?
 * What is our audience? Beginners or experienced programmers?
 * How to differentiate the book from similar publications?
 * How to split the pure language aspects from the other topics? Separate books with links to each other? Delete some pages?
 * How to organize books about the JS family: JS, ECMAScript, TypeScript, other derivates?
 * How to integrate popular frameworks?

No comments from anybody? --Kelti (discuss • contribs) 12:54, 13 October 2022 (UTC)
 * About the frameworks, as far as I can see in the other languages, it should be limited to one page max, and refer to a dedicated book if any. JackPotte (discuss • contribs) 14:57, 20 May 2023 (UTC)
 * About the audience, as the other book (Common JavaScript Manual) cannot really be the level one, what about beginners at the beginning of the book, and experts at the end? JackPotte (discuss • contribs) 15:00, 20 May 2023 (UTC)

 * To my mind, the purpose of the book is to provide a structure of topics that come under the larger topic of "JavaScript", provide compact description/treatment of each topic with plenty of examples, and provide the best links to online sources we can as a complement. For instance, I repeatedly return to JavaScript/Regular expressions to remind myself of the particular flavor used by JavaScript. --Dan Polansky (discuss • contribs) 12:16, 27 May 2023 (UTC)

Navigation
I register my opposition to the navigation bar that was recently added to the top right. It adds visual noise while adding almost no value. The table of contents is one click away, and for navigating to a next chapter, there are much less obtrusive aids. --Dan Polansky (discuss • contribs) 09:04, 20 May 2023 (UTC)
 * Hello, I think this might interest who's designed it. About the less obtrusive aids, do you please propose something like into:

There are three elements to decide: the header, the footer and the TOC. JackPotte (discuss • contribs) 14:48, 20 May 2023 (UTC)
 * Python Programming/Internet, or
 * PHP Programming/PHP Include Files or
 * A Quick Introduction to Unix/Directory Structure?
 * The means used by Python is fine: it is fine for navigation to take one line from the header and one line from the footer. It is my position that the TOC should not and need not be on the chapter page itself, to make the page as calm as possible; the TOC is available one click away from the header and the footer. The means used by PHP is basically fine but needlessly gaudy: no need to use strong green color. --Dan Polansky (discuss • contribs) 05:12, 21 May 2023 (UTC)
 * OK, I agree to use the Python book style here, but not its templates because on the contrary of nav or JavaScript, the previous and next pages are not dynamic. Moreover, JavaScript shows that there is no need for two inclusions when we can do one with both templates. JackPotte (discuss • contribs) 12:48, 21 May 2023 (UTC)
 * I do not insist on any particular template; my point is to avoid the sidebar as visually intrusive and low-added-value. I think some generic template could and perhaps should be used, not one specific to JavaScript. I think I was some very unobtrusive looking template that I liked a lot, one that used almost no color; I'll look if I can find it. --Dan Polansky (discuss • contribs) 07:19, 22 May 2023 (UTC)
 * The template used by GIMP/Text Tool looks excellent, very unobtrusive and elegant, except that the top does not link to the index, which it could, although the link to index is at the top above anyway. --Dan Polansky (discuss • contribs) 07:20, 22 May 2023 (UTC)

We shall distinguish between the two topics head/food navigation to next/previous page and fast navigation to important pages (the additional box at the top right).

A) next/previous: Writing a Wikibook is a little different from writing a physical book or an E-Book in that the Wikibook is divided into multiple, independent HTML pages. Obviously, such HTML pages must be arranged in a certain sequence. In the case of physical books or E-Books, the sequence is implicitly given.

Some of our templates use explicit linking by giving the name of the next and previous page. This is very cumbersome and I avoid all of them. (Is the author of page 46 willing to define "the next page is 47 and the previous one is 45"?) Other templates use the TOC mechanism and create the links dynamically. This is ok for me. The styling of the links (color, size, ...) is out of scope for me. Due to a physical issue, I don't see colors like other people. Therefore I avoid comments about this topic.

B) fast navigation: The fast navigation box was introduced to give the reader the chance to reach important pages and topics very quickly. It isn't a repetition of the TOC. Of course, it needs some space. This may be a problem, especially for smartphones. Possibly the community argues against such a fast navigation box. --Kelti (discuss • contribs) 15:15, 23 May 2023 (UTC)
 * We are talking a difference between 1 click and 2 clicks to reach the target page. There are too basic use cases: 1) read the book from the beginning to the end, for which the navigation box is unnecessary. 2) have a specific question and land on a particular chapter to have that question answered. None of the use cases require navigation box. Also of note is that navigation box is yet another page/place to maintain/update, in addition to the TOC and the chapters themselves. --Dan Polansky (discuss • contribs) 11:02, 27 May 2023 (UTC)
 * From looking at the revision histories, I find e.g. this: . I do not see why this had to be abandoned. The last thing Wikibooks need are arbitrary changes in the veneer or style with no substantive value; ideally, keep these things constant and focus on incremental changes and expansions of what the book already covers. --Dan Polansky (discuss • contribs) 12:18, 27 May 2023 (UTC)
 * [//en.wikibooks.org/w/index.php?title=JavaScript/Introduction&diff=next&oldid=4029234 It was obviously abandoned for the lack of dynamicity of the previous and next pages in the "prognav" template].
 * Now if I would sum up this debate, I would say that we all agree about the fact that these templates are better when dynamic and that the short embed TOC is too large for mobiles. So we need to vote:
 * For the previous and next page style (color and position).
 * For the presence of the TOC in the desktop view. JackPotte (discuss • contribs) 12:22, 28 May 2023 (UTC)
 * I have not said the navigation template is better when "dynamic". I guess that by "dynamic" you mean something like that the previous and next pages are not coded in the template invocation in the chapter itself but rather somewhere else. Where is the technique described and how is the mere mortal who wants to add a new chapter going to find the place to modify? That is what I gathered from Special:Diff/4193587. This diff introduced Template:Nav; why was the template abandoned later in favor of a book-specific template?
 * The book-specific template 'JavaScript' covers templates and categories that shall occur on every page: AutoHeader, Footer, BookCat, and Category:Sidebars. It summarises the common aspects of the subpages. --Kelti (discuss • contribs) 17:23, 29 May 2023 (UTC)
 * As for mobile, I did not say anything about mobile vs. desktop; I am on a desktop. I am in principle opposed to visually distracting elements with low added value that add maintenance overhead for anyone trying to work on the book.
 * In my view, everything was fine as for navigation templates before the change. The result looks unseemly (subjective taste) and is harder to maintain for mere mortals. As far as votes go, I vote for abandoning the navigation bar on both mobile and desktop, and leaving it to the users to click at the TOC at the top of the page, and using the TOC to navigate to chapters that are not directly linked from a chapter. --Dan Polansky (discuss • contribs) 07:40, 29 May 2023 (UTC)
 * As for colors and icons, I accept the current output produced by Template:Nav, with green background; I accept with the current output produced by Template:prognav, which has light yellow background; I prefer the output produced by Template:chapter navigation; what I oppose are the unseemly large arrows currently produced by Template:JavaScript. Thus, of the 4 options listed, I oppose only 1 of them, accept 2 of them, and prefer 1 of them. --Dan Polansky (discuss • contribs) 07:48, 29 May 2023 (UTC)

What constitutes a Wikibook?
A Wikibook consists of many pages. What criterion makes a page part of a particular Wikibook? Is it: Or is there no clear definition and every template (toc, nav, ...) can do what it wants? --Kelti (discuss • contribs) 15:17, 23 May 2023 (UTC)
 * The page is a subpage (recursively?) of the intended Wikibook?
 * There is a link to the page (recursively?) and the link points to the Wikibook domain?
 * Usage of a certain template?
 * I do not understand what these questions are aiming at. At any given point, all subpages of "JavaScript" are part of a single book, JavaScript. Whether they all belong to the book is another question. One could envision multiple books on JavaScript, if one wanted to, but that does not seem necessary or helpful at this point, does it? --Dan Polansky (discuss • contribs) 12:13, 27 May 2023 (UTC)
 * Sorry, I'm not a native English speaker. For me the two statements "all subpages of [/]JavaScript are part of ... JavaScript" and "whether they all belong to the book is another question" is not clear. Therefore I prefer an example: JavaScript/Glossary is a subpage of JavaScript, but it is not in the TOC of the book. Hence my question: Is it part of the DocBook JavaScript?
 * Of course, someone can create a second Docbook e.g.: JavaScript for Beginners and refer from its TOC to JavaScript/Glossary. Is JavaScript/Glossary part of the DocBook JavaScript for Beginners?
 * Your astonishment about my question leads me to guess that there is no clear definition.
 * The background of my question is: About what pages shall templates (navigation, PDF generation, printable version, ...) iterate over? Kelti (discuss • contribs) 15:56, 27 May 2023 (UTC)
 * I had created JavaScript/TOC OLD (which you renamed) for that, because it can order all the book subpages.
 * Concerning the pages belonging to several books, to avoid duplication, I propose to use inclusions. In the example above, that would imply to create a JavaScript for Beginners/Glossary containing:

JackPotte (discuss • contribs) 12:38, 28 May 2023 (UTC)

 * I don't plan to create a second Wikibook about JavaScript. It is only a theoretical example to clearify the question "What constitutes a Wikibook?". Also, the question doesn't have any relationship to a 'fast navigation box'. Kelti (discuss • contribs) 07:02, 29 May 2023 (UTC)
 * I am pretty confused from the above. One thing is clear: when you create a subpage like JavaScript/Glossary, you should add it to the TOC, as is the usual practice. As an aside, JavaScript/Glossary does not look like a glossary: it has a table with items that are too long for a glossary, which normally only provides a quick definition or a characterization; that should be clear from looking at various things called a "glossary". As for "DocBook", it does not seem to do anything with Wikibooks, does it? So how does "DocBook" relate to this discussion, if at all? --Dan Polansky (discuss • contribs) 07:58, 29 May 2023 (UTC)
 * Sorry for using the term "DocBook". That was a mistake. In all cases it should read "WikiBook". Kelti (discuss • contribs) 16:28, 29 May 2023 (UTC)

Chapter Primitive data types
I do not understand why it was necessary or useful to join(?) the separate chapters for Strings etc. to create single chapter JavaScript/Primitive data types. The last thing a Wikibook needs is an arbitrary restructuring; different people have different ideas about the ideal structure, and such changes in structure usually lead to to-and-fros with no genuine value.

Furthermore, from looking at the revision history of JavaScript/Primitive data types, I do not see any credit given to previous content; was the content a new writeup? Thus, was the original content of chapters Strings, etc. discarded and replaced with a new content? Why? What was wrong with the original text?

I would be happy to undo these changes, and maintain a stable long-term structure unless there are grave defects in that structure, which I do not see to be the case.

People should focus on incremental changes and expansions, not on arbitrary restructuring. --Dan Polansky (discuss • contribs) 11:54, 27 May 2023 (UTC)

 * From October 2022 until Januar 2023 I have done a reworking of nearly all pages, see the discussion Talk:JavaScript#Out-of-date. Concerning the original page variables and types, I splitted it into two pages because there is enough content for each page JavaScript/Variables and JavaScript/Data types. Unfortunatelly the second is no longer part of the TOC.
 * Furthermore, I believe that there should be one page for a description of all seven primitive data types (one page per primitive data type is also ok) plus additional pages for data types that are derived from Object (Array, Date, Error, Function, RegExp, ...). Hence a structure like this would be ok for me:
 * Variables (key words, initializaton, scope)
 * Data types
 * Primitive data types
 * Number
 * String
 * Objects
 * Array
 * Date
 * Maybe, some confusion arrised because I didn't do proper 'renaming' of old pages - instead I sometimes reused their name with divergent content. This may result in some cases in a mismatch beween page name and page content. Kelti (discuss • contribs) 15:16, 27 May 2023 (UTC)
 * Concerning the quality of the description of data type related 'functions', I tried to differentiate between properties, methods and constants of static Objects like, and methods of the data type. Perhaps we shall add a paragraph where this aspect is introduced. But in general, I consider that an improvement. Kelti (discuss • contribs) 15:27, 27 May 2023 (UTC)
 * Did you use any of the preexisting material in your merged content that you placed to JavaScript/Primitive data types? If so, which material did you use in the merged content? --Dan Polansky (discuss • contribs) 07:51, 29 May 2023 (UTC)
 * Concerning the quality of the description of data type related 'functions', I tried to differentiate between properties, methods and constants of static Objects like, and methods of the data type. Perhaps we shall add a paragraph where this aspect is introduced. But in general, I consider that an improvement. Kelti (discuss • contribs) 15:27, 27 May 2023 (UTC)
 * Did you use any of the preexisting material in your merged content that you placed to JavaScript/Primitive data types? If so, which material did you use in the merged content? --Dan Polansky (discuss • contribs) 07:51, 29 May 2023 (UTC)

Arbitrary restructurings are the bane of Wikibooks
I would like to make the general point that I believe arbitrary restructurings are the bane of Wikibooks. They undermine stability of books and chapters and all too often produce nothing of genuine value. It is much better to work in an incremental manner: expand existing chapters, and add new chapters. Restructurings are nearly invariably subjective, and should the will of original authors of a Wikibook prevail, they would lead to costly to and fros with no value. I would make a general appeal to editors to think twice before turning things upside down, apply colorful veneer, make unnecessary splits to chapters of a book that is under 200 KB, etc. --Dan Polansky (discuss • contribs) 08:02, 29 May 2023 (UTC)

 * +1. So, let us create a general, long term structure for this WikiBook. Kelti (discuss • contribs) 16:51, 29 May 2023 (UTC)

A) Here is my suggestion for a long term TOC:

Welcome
 * Hello World!
 * Introduction + Relation to other Languages (merged to a SINGLE page)
 * JavaScript within HTML
 * Helpful hints
 * Development tools (merged with 'Useful software tools')

Core Language Aspects
 * Variables (key words, scope)
 * Data types (explanation of the type system: 'primitive', 'Object', and wrappers for 'primitive' (boxing))
 * Primitive data type: String
 * Primitive data type: Number
 * Other primitive data types: Bigint, Boolean, Undefined, Null, Symbol
 * Objects (summary and distinction to primitive data types)
 * Arrays
 * Dates
 * Regular Expressions
 * JSON (delimitation to data type 'Object')
 * Operators
 * Program flow I: if, switch, try
 * Program flow II: loops
 * Functions
 * Object-oriented programming (OOP)
 * Objects (constructor, inheritance, access control)
 * Prototype-based syntax
 * Class syntax

Extended Language Aspects
 * Closures
 * Asynchronous behavior
 * Sequence generators
 * Automatic semicolon insertion (ASI)
 * Reserved words

Document Object Model and Dynamic Websites
 * Basics
 * Finding elements
 * Adding elements
 * Changing element's content
 * Changing element's styles
 * Removing elements
 * Restructure the DOM tree
 * Handling DOM events
 * Forms
 * Bookmarklets

Client/Server Programming (summary about AJAX, XMLHttpRequest, jQuery, Axios, Fetch API) Server Side Programming (summary about existing Webservers, frameworks, libraries) Miscellaneous
 * Debugging
 * Optimization
 * Shell

Appendices
 * Glossary (clear definition of similar terms. e.g.:function/method, argument/parameter, ...). This helps readers as well as authors.
 * Index
 * Links

Related Wikibooks
 * HyperText Markup Language (HTML)
 * Cascading Style Sheets (CSS)
 * Web development
 * WEB pages programming
 * Ajax programming
 * ActionScript programming
 * Coding Cookbook: JavaScript

Resources at Wikipedia and Wikiversity
 * JS at Wikipedia (Main page)
 * JS at Wikipedia (Category)
 * JS at Wikiversity - Introduction
 * JS at Wikiversity - Programming
 * JS at Wikiversity (Category)

External links
 * Website of ECMA-262
 * Latest specification (TC39)
 * JavaScript at MDN Web Docs in different languages
 * JavaScript tutorial at codecademy.com

B) My suggestions for general rules are: --Kelti (discuss • contribs) 11:07, 31 May 2023 (UTC)
 * All examples and descriptions are in ECMAScript 6 (2015) or higher
 * No mention of very old products or concepts (JScript, Internet Explorer, Netscape 7.x, ...)
 * As a counterproposal:
 * 1) Stop playing around with the structure; keep it as is, or perform minor, as if surgical, well justified incremental changes, and make use of edit summaries to document these incremental changes.
 * 2) Avoid nested chapters; keep the simple structure JavaScript/Chapter. It is sufficient for the subject.
 * 3) If you decide to merge chapters, always (i) create a chapter that results from an unmodified merger of the chapters being merged, and save it so it appears in the revision history of the new page, and (ii) indicate in the edit summary that you are doing a merge. Doing something else is rather disruptive and makes it harder to track the editing history of the Wikibook.
 * --Dan Polansky (discuss • contribs) 10:40, 2 June 2023 (UTC)

General rules
The following was proposed: I am not sure what problems these rules are trying to solve. If there are ocassional mentions of these things, not too numerous, I do not think it harms the utility of the material.
 * 1) All examples and descriptions are in ECMAScript 6 (2015) or higher
 * 2) No mention of very old products or concepts (JScript, Internet Explorer, Netscape 7.x, ...)

Instead of inventing rules and big projects turning things upside down, better work through incremental changes to produce objective value. --Dan Polansky (discuss • contribs) 10:43, 2 June 2023 (UTC)

title: Talk:JavaScript


text:
User talk:Wikisquared~enwikibooks

Walkthroughs
I'm sorry to say that walkthroughs are not appropriate for Wikibooks. The ones we already have are in the process of being transwikied. I recommend that you start your walkthroughs on StrategyWiki. --hagindaz 22:41, 5 July 2006 (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 Wikisquared. To make sure that both of you can use all Wikimedia projects in future, we have reserved the name Wikisquared~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:54, 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:38, 19 April 2015 (UTC)

title: User talk:Wikisquared~enwikibooks


text:
Wikijunior:Dinosaurs/Herrerasaurus

Herrerasaurus (pronounced huh-Rare-uh-Sore-us) was one the earliest dinosaurs to have walked on the face of the Earth. It lived in what is now Argentina and was a meat-eater, also known as a carnivore.

What did they look like?
Herrerasaurus was likely up to 10 to 20 feet (3 to 6 meters) in length, walked on its hind legs with short thighs and rather long feet. It was very quick on its feet and had strong claws for grabbing prey. Herrerasaurus weighed at least 400 pounds and at most 750 pounds.

What did they eat?
Herrerasaurus was a meat-eater. It probably fed on small and medium-sized animals. However, it most likely did not hunt for itself, instead it probably ate meat off dead animals. It has been suggested it fed on rhynchosaurs, small prehistoric lizards, and aetosaurs, a kind of mix between an armadillo and a pig.

When did they live?
Herrerasaurus lived in the Late Triassic period, about 230 million years ago. Their favourite habitat was in woodlands, amongst the ferns, conifers and mosses.

Where did they live?
Herrerasaurus once lived in Argentina on the South American continent. Found in the Ischigualasto Formation of Argentina, along with the bones of several other early dinosaurs.

How were they discovered?
The first Herrerasaurus fossil was discovered in 1958 by a local man named Don Victorino Herrera. But, it wasn't until 1988 that the first skull was discovered.

What do we need to learn?

 * The colour of skin
 * Was Herrerasaurus just a hunter, scavenger, or a mix of both?

Wikijunior Dinosauri/Herrerasaurus

title: Wikijunior:Dinosaurs/Herrerasaurus


text:
Java Programming/Keywords/char

is a keyword. It defines a character primitive type. can be created from character literals and numeric representation. Character literals consist of a single quote character (ASCII 39, hex 0x27), a single character, and a close quote, such as. Instead of a character, you can also use unicode escape sequences, but there must be exactly one.

Syntax:

65 is the numeric representation of character 'A', or its ASCII code.

The nominal wrapper class is the  class when you need to store a  value but an object reference is required.

See also:
 * Java Programming/Primitive Types

title: Java Programming/Keywords/char


text:
Java Programming/Keywords/short

is a keyword. It defines a 16 bit signed integer primitive type.

Syntax:  = ;

For example:

See also:
 * Java Programming/Primitive Types

title: Java Programming/Keywords/short


text:
Java Programming/Keywords/long

is a keyword which designates the 64 bit signed integer primitive type.

The  class is the nominal wrapper class when you need to store a  value but an object reference is required.

Syntax:  = ;

For example:

See also:
 * Java Programming/Primitive Types

title: Java Programming/Keywords/long


text:
Java Programming/Keywords/byte

is a keyword which designates the 8 bit signed integer primitive type.

The  class is the nominal wrapper class when you need to store a value but an object reference is required.

Syntax:  = ;

For example:

or

The number 65 is the code for 'A' in ASCII.

See also:
 * Java Programming/Primitive Types

title: Java Programming/Keywords/byte


text:
ACT Study Guide/Math

The ACT Mathematics section is the second test on the ACT. It consists of 60 questions, which must be completed within 60 minutes. Unlike other sections of the ACT, calculators are allowed in this section. In addition, there are 5 multiple choices in the Math section, whereas there are 4 multiple choices in the other sections. It is not known why this is. Like the rest of the ACT, there is NO penalty for incorrectly answering a question. So, it is in your favor to do so. The ACT Mathematics exam tests the following six areas:
 * Pre-Algebra (approx. 14 questions)
 * Elementary Algebra (approx. 10 questions)
 * Intermediate Algebra (approx. 9 questions)
 * Coordinate Geometry (approx. 9 questions)
 * Plane Geometry (approx. 14 questions)
 * Trigonometry (approx. 4 questions)

Pre-Algebra
Pre-Algebra is one of the essential topics to know for the math section.

Trigonometry
With only 4 questions, trigonometry is not one of the most important math topics on the ACT. However, if math is one of your better subjects or if you're shooting for a high score, read on:

SOHCAHTOA is the acronym for the trigonometric ratios. These are extremely important! If you don't remember this, SOHCAHTOA is: Sine=Opposite/Hypotenuse Cosine=Adjacent/Hypotenuse Tangent=Opposite/Adjacent

Graphs of trigonometric functions often make up one or two of the ACT Math Questions. Remember that the normal period for a sine/cosine function is 2π/360°, whereas the tangent graph has a normal period of π/180˚.

title: ACT Study Guide/Math


text:
User talk:Nantosh~enwikibooks

The Seventh Denotaion
Hello, Nantosh, and welcome to Wikibooks! I'm sorry to say that fictional works are not appropriate for Wikibooks. However, we do accept text annotations, but these must be done for notable, published works only. Fortunately, the Fiction Wikia was designed specifically for users to write their own novels. I suggest you move your book there, where it will get the attention it deserves. Once you have done so (or decided not to make available your book), please note so on this page and I will delete the Wikibooks pages. Also feel free to ask any other questions here. Thanks and good luck on your book, hagindaz 04:23, 6 July 2006 (UTC)

Alright

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

title: User talk:Nantosh~enwikibooks


text: Category:Book:Introduction to Medical Statistics


text: Category:Book:Introduction to Moral Reasoning


text: Category:Book:Introduction to Philosophical Logic


text:
Cookbook:Beef Stew I

| Meat Recipes

Beef stew has chunks of softened beef and vegetables in a thick sauce. It is often served with cornbread or biscuits.

Ingredients

 * 2 lb (900 g) beef
 * ½ cup flour
 * ¼ cup oil
 * 1 bay leaf
 * 1 tsp (5 ml) marjoram
 * 1 tsp (5 ml) oregano
 * 46 fl oz (5 ¾ cup, 1.36 L, or 1 large can) tomato juice
 * 10 ½ oz (298 g, about 1 ¼ cup, or 300 mL) double-strength beef broth
 * 2–4 russet potatoes, or other large non-sweet white baking potatoes
 * 4 large carrots
 * 4 stalks of celery

Procedure

 * 1) Cut the beef into chunks about 1 inch (2.5 cm) across.
 * 2) Put the beef and flour in a container, such as a plastic bag, and shake or squish until the beef is well-coated. Use more flour for a thicker stew, or less for a thinner stew.
 * 3) Put oil into a wide pot and heat it.
 * 4) In several batches, brown the beef in the pot with the oil.
 * 5) Return the browned beef to the pot, along with all the spices, tomato juice, and the double-strength beef broth.
 * 6) Cover the pot, then simmer for at least an hour to soften the beef. Stir the stew every few minutes to prevent the beef from burning on the bottom of the pot.
 * 7) Peel the carrots, and cut them into pieces about the same size as the beef. Add them to the stew, and simmer a bit more, stirring every few minutes.
 * 8) Cut the other vegetables likewise, add to stew, and simmer a bit more, stirring.
 * 9) When all the vegetables are soft but not yet falling apart, remove the bay leaf and serve the stew.

Notes, tips, and variations

 * Try adding other vegetables such as turnips, parsnips, and frozen corn. Note that turnips mush quickly.

title: Cookbook:Beef Stew I


text:
User talk:68.4.220.113

For prepared foods, the cookbook needs instructions more than it needs definitions.

If you don't know how to write instructions, it is better to leave a dead (red) page link so that somebody else might notice that we are missing the needed instructions.

title: User talk:68.4.220.113


text: Category:Book:Introspector

title: Category:Book:Introspector


text: Category:Book:Inuktitut

title: Category:Book:Inuktitut


text: Category:Book:Investing

title: Category:Book:Investing


text: Category:Book:Irish

title: Category:Book:Irish


text:
Category:Book:Italian

ca:Categoria:Italià es:Categoría:Italiano ko:분류:이탈리아어

title: Category:Book:Italian


text:
User talk:Nicholasbrady

Hello and welcome to Wikibooks!

Here are some tips to help you get started:
 * You can sign your name on Talk and vote pages using four tildes, like this: ~~~~.
 * Remember to conduct any editing experiments in the sandbox.
 * Check out our help page if you need additional help.
 * Eventually, you might want to read the Manual of Style and Policies and Guidelines.
 * Take a look at Naming policy
 * See list of templates which can save your time
 * Remember to maintain a Neutral point of view.
 * Explore, be bold in editing pages, and have fun!

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

Good luck! --Derbeth talk 08:08, 6 July 2006 (UTC)

PCMI
Hello, can you explain what is the purpose of the book and link to it from one of bookshelves? --Derbeth talk 08:08, 6 July 2006 (UTC)

title: User talk:Nicholasbrady


text:
Template:Transwikimoved

This page has been transwikied out of the English Wikibooks into another Wikimedia project.

It has been moved to: ""

title: Template:Transwikimoved


text:
User:Gilbertf

Hello

title: User:Gilbertf


text:
Umbraco/Samples and Articles/Templates/ASPNetFormTag

The ASPNET_FORM tag
Often Umbraco macros will require an ASPNET_FORM tag to be wrapped around them in order to function correctly.

It is good practice to place this tag in a master template as in the following example.

<?ASPNET_FORM> <?UMBRACO_TEMPLATE_LOAD_CHILD/>


text:
Talk:LaTeX/Document Structure

Regarding the two files tutorial2/sample.tex and tutorial2/sample.pdf, it was mentioned that links to both files exist at the end of the LaTeX/Document Structure page. The problem is that I can't find any of these links. May anybody help me, please? Thanks in advance.
 * The page was copied from http://www.andy-roberts.net/misc/latex/latextutorial2.html (with permission). The people who added the stuff didn't fix the links or the reference to the link at the end of the page.  I just fixed it.ConditionalZenith 08:45, 18 September 2006 (UTC)

commas
Commas are incorrectly used if used when you 'breath'. I think discussion of commas is outside the subject of this wiki. A good reference in place perhaps.

Possible bug with fancyhdr?
If I use the:

To create an unnumbered chapter, then the header of the page created with fancyhdr package doesn't display the actual chapter name ("Introduction" in this case), but displays the previous chapter's name. Does it happen to you too?

Answer: yes, this also happen to me. I am looking for a solution.

Separate Table of Contents for Chapters
I have seen some theses in which each chapter has its own table of contents. This is especially useful in long theses and books. I haven't found any documentation yet on how to achieve this. Any ideas? Ben

I just found the solution: the minitoc package.

\author is not self-explanatory
The text claims that \author is self-explanatory. It might be if your document has only one author, but I find it confusing how to use \author when there are multiple authors and you want to get institutions to line up under author names. Now imagine you have a few authors from the same institution and you don't want to repeat the institution name. Not self-explanatory. It would be great to have a tutorial on \author.

poor description of LaTeX's document structure
This article fails to present the options available through this environment, along with the document classes it support. As a consequence, it fails to provide any practical value as a reference. Therefore, it would be great if it was rewritten to not only offer a clear list of the available options but also an explanation of the features of each document class. Mecanismo (talk) 10:56, 24 October 2010 (UTC)

would be good to have additional notes to help identify what document classes are available, options etc.
As a beginner I typically explore the options first. In this case therefore I would be interested in knowing a. what are the available document classes on my system. b. from where can I get extensions(additional classes) c. how do I determine the options available to the class.

Some of these could be considered as advanced based on how the author percieves in which case I would like to suggest to provide these details in the appendix and ask the reader to refer to the appendix for such details.

title: Talk:LaTeX/Document Structure


text:
Modern Greek/Lesson 1x

About the Greek language

The Greek language is one of the oldest written languages in the world, and Greek literary culture extends back in time even past the invention of writing, to the time of Homer. Greek is a language distinguished by an extraordinarily rich vocabulary. The vast majority of Modern Greek vocabulary is directly inherited from ancient Greek, like άνθρωπος (anthropos - man) or θάλασσα (thalassa - sea). Words of foreign origin have entered the language mainly from Latin, Italian and Ottoman Turkish. During older periods of the Greek language, loan words into Greek acquired Greek inflections, leaving thus only a foreign root word. Modern borrowings (from the 20th century on), especially from French and English, are typically not inflected.

Up until the twentieth century, the archaic (καθαρεύουσα, "katharevousa," "purist") form of the language was the only one with cultural prestige, and was the formal language of government. Over the course of the twentieth century, however, the written language was changed to resemble the modern spoken language, becoming the modern demotic language (δημοτική, "of the people"), which is now the official language of the Greek and Cypriot state. The last change became effective as late as 1981, with the abolition of the polytonic system. This book is about the modern language, not classical or biblical Greek.

Introduction to the writing system
Fortunately, Greek is spelled mostly phonetically and the Greek alphabet is very easy to learn. You have probably already seen quite a few of the letters before, since they're used in maths, physics and chemistry. Others, particularly the uppercase letters, are often identical or very similar to Latin letters (the letters most of the western European languages, including English, use). Here are some letters that you can immediately recognise, in their upper and lowercase forms:

The capital letters are all exactly the same as in the Latin alphabet. The small letters show some subtle differences:
 * The lowercase alpha looks similar to the 'single-story' lowercase 'ɑ' in English (not the double-story a).
 * Lowercase kappa and iota looks exactly like a miniature version of the uppercase letter.
 * The lowercase tau is also a miniature version of the capital one, whereas the Latin lowercase "t" is written as a cross stroke.

Knowing these few letters, you can already understand when a cartoon shows people shouting "α!" or "ο!". ο also happens to be the masculine article. το is the one for neuter.

Here's how to pronounce the letters you just learned:
 * Α α is pronounced as the a in father, the IPA symbol is [a]
 * Ι ι is pronounced as the ee in meet, the IPA symbol is [i]
 * Κ κ is pronounced as in keep.
 * Ο ο is pronounced as in obey, the IPA symbol is [o]
 * Τ τ is pronounced as in time (without the extra air at the end that native English speakers like to add), [t]

Let's practice reading some more. For example, do you know the American band whose greatest hit was "Africa"? It's Τότο. (All solutions can be found at the bottom of this page)

''Wait!!! Why is there an accent on the omicron?'' This accent indicates that the word stress should be on the ο. It's pronounced TOto, not toTO. Every Greek word of at least two syllables gets one accent indicating which syllable is stressed. This is a great feature for learners, since - unlike in English or German for example - you don't have to memorize the stress.

Here's another word for practice: κακάο. This is what the Greeks call cocoa. And κότα means "hen" in Greek.

I would like to introduce you to one more letter in this lesson:

Ρ ρ

This is the letter Rho. It looks like P, but it's actually the Greek equivalent of R. Be careful not to confuse it. Its pronunciation is closer to a Spanish R than an English one.

Knowing this letter and the ones introduced above, you can read quite a few new words. For example, do you recognise the following country names: Ιράκ, Κροατία, Κατάρ? The city Κάιρο? And κάρτα, which means "card" in Greek?

If so, you have already begun to read Greek. Please continue with the next lesson, where you will learn a few more letters and many more words.

Solutions

title: Modern Greek/Lesson 1x


text:
Neapolitan/501 Neapolitan verbs/fernì

fernì

 * to stop, finish

1. Innecativo
 * a. presente
 * {| class="wikitable"

 * align="left"|io
 * align="left", bgcolor="#c9c8e9"|fernesco
 * align="left"|tu
 * align="left", bgcolor="#c9c8e9"|fernisce
 * align="left"|isso/essa
 * align="left", bgcolor="#c9c8e9"|fernesce
 * align="left"|nuje
 * align="left", bgcolor="#c9c8e9"|fernimmo
 * align="left"|vuje
 * align="left", bgcolor="#c9c8e9"|fernite
 * align="left"|isse/lloro
 * align="left", bgcolor="#c9c8e9"|fernesceno
 * }
 * align="left", bgcolor="#c9c8e9"|fernite
 * align="left"|isse/lloro
 * align="left", bgcolor="#c9c8e9"|fernesceno
 * }
 * }

Participio passato
 * fernuto

title: Neapolitan/501 Neapolitan verbs/fernì


text:
Java Programming/Keywords/float

is a keyword which designates the 32 bit float primitive type.

The  class is the nominal wrapper class when you need to store a  value but an object reference is required.

Syntax:  = ;

For example:

See also:
 * Java Programming/Primitive Types

title: Java Programming/Keywords/float


text:
Java Programming/Keywords/double

is a keyword which designates the 64 bit float primitive type.

The  class is the nominal wrapper class when you need to store a  value but an object reference is required.

Syntax:  = ;

For example:

See also:
 * Java Programming/Primitive Types

title: Java Programming/Keywords/double


text:
Talk:Arabic/Pronouns/Charts

Untitled
The different forms of the subject pronouns are described, but not their meanings. For example, how does the reader know that "ana" means "I"? Since the page deals specifically with pronouns, their definitions should explicitly be said here.

title: Talk:Arabic/Pronouns/Charts