text:
Civ/Sid Meier's Alpha Centauri/Diplomacy

Negotiating with factions
Negotiation with other factions is allowed once you have their commlink frequency, which means you must encounter them physically on the map (you units need to be in adjected squares), receive it from a faction you already have contact with, discover it in a Unity pod, or receive it through the Empath Guild Secret Project. Negotiating with other factions is very important, as it allows you to exchange technologies, maps and commlink frequencies, enter into formal treaties and pacts, declare war on one another, and synchronise your attacks on a third faction.

Formal Relationships
Your relationship with other factions consists of one formal value and an informal one. Your formal status with other factions is one of the following: Vendetta, Truce, Treaty and Pact. Additionally, you may have an "informal truce" with another faction.

"Vendetta" is rather self-explanatory: this faction leader has made a promise to destroy your faction, or at least bust it up pretty good. Unless you are the aggressor, of course. "Truce" (or "Blood Truce") means that your two factions have agreed not to attack each other, at least for the time being. "Treaty" ("Treaty of Friendship") is just that, a treaty which represents your two factions' friendship. More importantly, a Treaty means the citizens and organizations of two faction will now trade with each other, meaning you get extra energy credits, straight into the state coffers. The final kind of formal relationship is the Pact ("Pact of Brotherhood"). This means your two factions are committed to helping each other out, which has several manifestations. First, commerce rates double between your two factions, and secondly, your units may stack theirs. This means closer military cooperation is possible, you may defend each other's bases, and your pact mate might even give you units "to defend your territory against aggression".

When you first meet a faction, you have no formal relationship, or an informal truce. This means that you are not at war with this faction, but no actual agreements have been made. From this point, you may engage in war with the other faction, remain at an unease peace, or commit to a formal relationship. Whether the other faction agrees to a treaty or a pact depends on how they feel towards you, which is the next thing we're going to talk about.

Informal Relationships & Reputation
The informal relationship with another faction is simply how much the other faction leader likes you. This value ranges from "Magnanimous" (or "Submissive" if threatened) to "Seething", and it hinges on three things: how strong your faction is (the stronger the faction, the more respect other factions have for you, and the more they like you), your actions towards this faction, and your Social Engineering choices. If you have attacked this faction (or worse; are at war with it) the faction leader will like you less, whereas if you have traded or presented gifts to this faction, they will like you more.

As you might have guessed by now, a faction leader's opinion of you decides how likely it is that he or she will attack you. Another factor also plays into this, the faction leader's personality. Some, such as Yang or Santiago, are more likely to attack you than others, such as Deidre and Aki-Zeta. This is important to keep in mind, especially in the beginning of the game, so that you can plan the training and construction of military forces accordingly. If you start next to, say, the Usurpers, you can be sure that unless you are far stronger than them, they will declare war soon, especially on higher difficulty levels, and even moreso if you have turned on the "Aggressive Factions" option. Faction leader personalities can be randomized under "Game Rules".

Your Social Engineering choices also play a part in how other faction leaders behave. Each faction has one SE choice on their agenda, and one SE choice aversion (see Understanding the Factions). If you are currently running the SE choice on the agenda of a given faction, this faction will think more highly of you, and if you are employing their aversion, they will criticise you for it, and it may even be a contributing cause for open conflict. Faction leader agendas can also be randomized.

In the course of the game, you will very likely make deals and trades with other factions, as mentioned. Whether or not the other faction leaders will accept the deal you propose depends on their opinion towards you (or "mood"), and your reputation. Reputation starts at "Noble" and can diminish as a result of dishonourable actions; your reputation is affected by whether or not you honour formal agreements. If, for example, you have signed a Treaty of Friendship with another faction, and attack them without waiting for the treaty to expire, your reputation will incur a hit. The same applies to Blood Truce.

Note that while you may not attack a pact mate (your unit will only stack with his or hers), you may still incur a reputation hit if your probe teams are caught trying to operate on one of your pact mate's bases or units. If one of your probe teams are indeed compromised, the target faction has sufficient reason, with regards to reputation, to move against you. This means that if you attempt to steal technology from a pact mate and are caught, your pact mate may declare vendetta against you without going through the normal channels. The same, of course, is the case for a human player.

The Planetary Council
The Planetary Council is a rare feature among Civ games; just like the United Nations of Civilization IV. The Planetary Council consists of every human faction in the game (not counting those who have been eliminated or committed major atrocities). When a player has the commlink factions of all the other human factions, that player may convene the Planetary Council. (When this happens, all the human factions will have each others' comm links.)

The first proposal the Council must consider is electing the Planetary Governor. Only the two factions with the most votes can be eligible. It is advantageous to be the Governor, therefore in some cases it may be best to wait before convening the Council if you haven't enough votes now but have a shot at eligibility within the next few turns.

Proposals
The primary purpose of the Council is to consider various issues which may arise, such as electing a Planetary Governor.

Elect Planetary Governor

 * Prerequisite: N/A

The Planetary Governor can introduce new proposals more often and enjoys automatic infiltration of all factions. That means if the Governor isn't you, it should be somebody you trust.

Global Trade Pact

 * Prerequisite: Planetary Economics

Commerce rates are doubled for all factions. Since choice of faction, social engineering and technologies alter your commerce rating, this proposal can be good or bad accordingly. If your opponents will gain an advantage from increased trading, don't agree to a pact.

Repeal Global Trade Pact

 * Prerequisite: Planetary Economics

Commerce rates are halved for all factions.

Launch Solar Shade

 * Prerequisite: Advanced Spaceflight

Causes global cooling and the sea levels to drop. If a solar shade has already been launched, this proposal will be called "Increase Solar Shade".

Increase Solar Shade
See Launch Solar Shade

Melt Polar Caps
Melts the polar ice caps of Chiron, raising sea levels all around.

Repeal U.N. Charter
Repeals the U.N. Charter, meaning atrocities are counted as normal acts of warfare. The U.N. Charter is in effect when the game starts.

Reinstate U.N. Charter
Self-explanatory: reinstates the U.N. Charter, once again making atrocities subject to harsh penalties.

Salvage Unity Fusion Core
Salvage of the Unity core affords every faction 500 energy credits. Logically, you will not want to do this if you have lots of ECs and your rivals are strapped for cash.

Unite Behind Me As Supreme Leader
All factions unify behind one faction leader, this faction wins and the game is over. When playing with Progenitor in Alien Crossfire, this option is only available after both alien factions are eliminated.


text:
Cortinarius psittacinus

Cortinarius aureofulvus is a fungus in the genus Cortinarius native to Belgium. It was described by Austrian mycologist Meinhard Michael Moser in 1970.

source: wikimedia

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

title: Cortinarius psittacinus


text:
User:SutharsanJIsles

Teaching Experience

Mathematics Teacher, Bedok South Secondary School (2001) English, Mathematics and Science Teacher, Geylang Methodist Primary School (2002) English, Mathematics and Science Teacher, CHIJ (Katong) Primary School (2003) English, Mathematics and Science Teacher, Fengshan Primary School (2004) Private Home Tutor, (2005) ESOL Lecturer, Hannsfield Management Academy (2006) IT Lecturer, Hannsfield Management Academy (2007)

I am currently lecturing in topics for the International Diploma in Information Technology at a private school (Hannsfield Management Academy) in Singapore. I am particularly interested in developing learning resources for Computer programming, Cryptography and Computer Networking. My other interests include Mathematics, Physics and Chemistry.

title: User:SutharsanJIsles


text:
torat

Etymology
From, from , equivalent to. Related to 🇨🇬.

Verb

 * 1)  To tear apart, tear asunder.
 * 2)  To scatter, disperse.

Synonyms

 * See also Thesaurus:disperse
 * See also Thesaurus:disperse

title: torat


text:
Talk:Dwayne Russell

Untitled
It's a Damned shame Wikipedia goes on Verifiability and Not Truth... 08:53, 28 June 2011 <IP_ADDRESS> - Best edit to a Wikipedia Article EVAR. :D <IP_ADDRESS> (talk) 09:06, 1 July 2011 (UTC)

title: Talk:Dwayne Russell


text:
Navasota leuconeurella

Navasota leuconeurella is a species of snout moth in the genus Navasota. It was described by George Hampson in 1918 and is known from South Africa and Uganda.

title: Navasota leuconeurella


text:
Talk:Leighton Buzzard Light Railway

There are a few inconsistencies in the spelling of names both within the text and between the text and the map. I don't know these names well enough to correct them myself. Can someone help? Roly (talk) 13:12, 16 July 2012 (UTC)

External links modified
Hello fellow Wikipedians,

I have just modified one external link on Leighton Buzzard Light Railway. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
 * Added archive https://web.archive.org/web/20050107110712/http://appeva.club.fr/bref.htm to http://appeva.club.fr/bref.htm

Cheers.— InternetArchiveBot  (Report bug) 09:38, 20 December 2017 (UTC)

title: Talk:Leighton Buzzard Light Railway


text:
Business English/Getting More Practice

If you live in the United States, the UK, Canada, Australia or another English-speaking country it is easy for you to practice all of the time watching TV, going to the store, making new friends. If you do not live in an English-speaking area, it may be harder to get practice.

Several magazines are published internationally and will help you practice your reading and listening skills.

 * English2Go, published by Reader's Digest
 * Speak Up, published in Brazil and in Italy.
 * Hot English, this one is OK too

You can also try listening to podcasts - free MP3 lessons you can download to you computer or MP3 player:

Business English Pod - Business English lessons by podcast for intermediate and advanced learners featuring useful phrases and vocabulary. Listening quizzes, transcripts and online exercises available for extra practice.

title: Business English/Getting More Practice


text:
Talk:Visual Basic

How to use this talk page
Just a couple of suggestions: kwhitefoot 06:50:07, 2005-08-26 (UTC)
 * please sign everything with four tilde characters like this ~ so that it is easier to tell who says what to whom.
 * Please be as specific as possible when complaining that the book is inadequate so that effort can be better focussed,
 * consider putting placeholder chapter headings in the actual book. I watch the contents page and all the pages I edit so I'll see the placeholders and try to expand them,
 * If you just change the spelling of a few words or correct some grammar here and there please mark it as a minor edit.

Guidelines for contributors
--kwhitefoot 18:14, 22 October 2005 (UTC)
 * Please capitalize VB code as in the VB IDE.
 * Remember that the book is about programming in VB Classic not VB.Net.
 * Prefix the names of all images with Visual Basic Classic. Please fix any instances that fail to follow this 'rule'.
 * The book is laid out like a printed b ook, everything is at the same level except for main page.  If you follow the Next link in the navigation template you should visit all the pages in the same order as they are found in the table of contents.

To Do

 * Rework the contents page in Python style perhaps. kwhitefoot 13:34:41, 2005-09-04 (UTC)
 * Add previous, next and Up navigation to each page using the prognav template? kwhitefoot 13:34:41, 2005-09-04 (UTC)

Too much like an encyclopaedia articla
This seems more like a Wikipedia explaination than a wikibooks lesson. I came looking to learn something, but went away with a description. HELP! -Jeshii 03:34, 8 Jul 2004 (UTC)

Probably too late for you, but it is getting better. kwhitefoot 06:50:07, 2005-08-26 (UTC)

Reply Yeah.. It does look like a encyclopedic article rather than a book. But I'll try to add more examples to make it more tutorial-ish.EugeneH 20:42, 3 Jan 2005 (UTC) Okay. I'll probably add a new section in the future if I have time...

Added some
I added the getting started section, this is my first Wiki work, so I hope I didn't mess anything up.

Moving
I think the Data types should have their own chapter. Beginner programmers shouldn't need to know it right away, and in depth like that should be saved for later in the book. Maybe after Data I/O?

Beginner's book?
I think this book is way too hard for a beginner... They will soon lose interest. Maybe this book should have more on GUI(Graphical user interface), since that's what VB is mostly used for. If we really want to make this book an easy tutorial, a lot must be rewritten. At least the structure of the tutorial should look like something to this effect:

Introduction - what's the advantages and disadvantages of vb? (in layman's terms) VB is made to be very convenient and user-friendly. Tell them you can make a program in 5 minutes. What is event-driven programming? Give the reader some ideas about it. Take some screenshots. List some cool things VB is good at. i.e. games, applications with heavy GUI, APIs(you can use APIs to make beeping noise etc.)

Exercise 1: Hello world How to create,save and compile your first program in VB Using Print statement to print "hello world" extension: using message boxes, using input boxes to make hello world

Exercise 2: Make a calculator Tell them what they should know: Buttons, Click events, Variables (simple data types), Some built-in functions they need. After they're done, tell them what else they could add to make it better.

Exercise 3: Simple text editor Tell readers what they need to know: Components - learn about rich text boxes More about functions, subroutines How to improve

Exercise 4: First game Introduce: Keyboard events, pictureboxes, shapes, imageboxes, timer movement, game loop, random numbers(rnd and randomize),Types extension: music,winsock(for multiplayer games),classes(OOP)

Exercise 5: how to make an extremely annoying program more on APIs, GUI, ... ...

 * sigh* but you almost have to change everything...

its not impossibble
Thats where I was going with the getting started, learning how to print. This does need to cater more to beginners, however, the advanced content should stay. Just as learning anything goes, it should be progressively harder. If you want to extend the "getting started" area with some examples, go ahead. After giving the user an idea of the VB layout and uses, then they can get into the advanced of loops and such. Once I do some more I hope to make alot more reference programs, like the blast effect and such. I appreciate your contribution though, but maybe we should have some direction? Are you OK with you making the Beginners area more extensive, and I go on with Loops and Data and all the good stuff? Also, we should add programs to the end of each section, showing a common application of the learned technique.

okay I'll extend the beginner's sections. The "visual" part. I think we should have more of those since VB is made for rapid application development... But the fundamentals certainly can't be ignored.

Just some standards
I got rid of any mention of file numbers in I/O, just thought it was confusing, also never heard the use of file number before :P Replaced it with channel number instead. Just keep this in mind when adding more for the sake of the reader. Any ideas on other things to make standard, so we're not using a bunch of different terms to confuse the reader?

yes Yeah that's fine with me. I'll let you know in the future before changing any terms. I never heard of channels before either. But that makes it easier for the readers.

Another note we need to make a standard for picture box names. I feel "pic" works fine, so if its ok with you, ALWAYS use pic.print and what not.

hmmm pic is fine for a picture box, but when "Printing", it's easier to type "print" than "pic.print". :/ It just "prints" on the current Form instead of a picture box. So why don't we all use print?

nah I always thought that was sloppy and hard to read, pic.print is only 4 letters more :P

Random Numbers
Shouldn't the random numbers section mention "ranzomize"? -Joshtek (from other Wikipedia)

This may be rather basic, but shouldn't you tell them how to find/get a Visual Basic editor?

Credits and permissions
Not sure how material lifted from other works should be acknowledged but it seems a good idea to actually record any documentation regarding permissions.
 * This is now collected on Credits and Permissions. --kwhitefoot 17:44, 27 November 2005 (UTC)

GUI Computing Pty Ltd/Mark Trescowthick
Copy of email giving permission for use of coding standards and forum content.

Kevin,

In answer to both emails.

1. Copyright. All we would require is a general statement on the contents page, we certainly wouldn't wish the effort on you of somehow trying to keep track of AVDF content page by page... that would render it pretty much unusable I should have thought! A link to avdf.com would be nice if that doesn't cause any stress.

2. Licensing. Having reviewed your licensing arrangements, I can confirm that GUI Computing Pty Ltd, owner of all copyrights in the material contained both on avdf.com and in the GUI Coding standards, agrees for you to use our above referenced work under terms of the GNU Free Documentation License.

3. Contribution. Keep me in the loop as the project moves forward. I shall mention it to my developers at our next meeting... these days, of course, most of them are .NET hotshots who consider VB "legacy", but there are a couple who might be interested.

Finally, if you need anything in addition to the above, please yell.

All the best,

Mark

> -Original Message- > From: Kevin Whitefoot<EMAIL_ADDRESS>> Sent: Wednesday, 28 September 2005 4:31 AM > To: Mark Trescowthick > Cc<EMAIL_ADDRESS>> Subject: RE: Visual Basic Classic WikiBook > >  > I've just skimmed the coding standards document. I think > that it would be > perfect addition. It is similar in many ways to the corporate coding > standards in force (though not enforced) at the company where > I work. I > can't use ours without rephrasing it completely because in such a big > company there is no one with the authority to allow it, > anyway, your's is > much better written. > > The Wikimedia project is a bit paranoid about copyrights and > so on so at > risk of sounding ridiculously finicky I think I should ask > for an explicit > statement from you that you are willing for the work to be > relicensed under > the GFDL. Here is an excerpt from the Wikibooks boilerplate > request for > permission > (http://en.wikibooks.org/wiki/Wikibooks:Boilerplate_request_fo > r_permission): > > =====quote > However, we can only use your materials if you are willing to grant > permission for us to use your above referenced work under > terms of the GNU > Free Documentation License. This means anybody will have the > right to share > your materials and update them: for example, to keep up with new > information. You can read this license in full at: > http://wikibooks.org/wiki/GNU_Free_Documentation_License > (note: To keep things simple, we don't use Invariant > Sections, Front-Cover  > Texts, or Back-Cover Texts) > > The license also expressly protects authors "from being considered  > responsible for modifications made by others" while ensuring > that authors > get credit for their work. There is more information on our > copyright policy > at: > http://wikibooks.org/wiki/Wikibooks:Copyrights > =====end quote > >  > Kevin Whitefoot > > ---

Elliot Spencer
From : 	Elliot Spencer  Sent : 	11 September 2005 13:48:26 To : 	"'Kevin Whitefoot'"  Subject : 	RE: VB tutorials You're welcome to use those bits from my site Kevin, I swapped over to DotNet as soon as it came out so I don't use vb6 anymore, haven't for quite some time. Sorry. Regards Elliot Spencer -Original Message- From: Kevin Whitefoot<EMAIL_ADDRESS>Sent: Saturday, September 10, 2005 7:51 PM To<EMAIL_ADDRESS>Subject: VB tutorials I'm editing the Visual Basic book on WikiBooks (http://en.wikibooks.org/wiki/Programming:Visual_Basic_Classic) and I wonder if I might include some of your articles in it. Of course if you felt like contributing to the book yourself that would be even better. When I started adding to it I thought I would be one among many but it seems that VB6 programmers are a shy and retiring lot. Kevin Whitefoot. (http://en.wikibooks.org/wiki/User:Kwhitefoot)

Name is not descriptive of the contents
This wikibook would be better named Visual Basic 6 since that is the only version it talks about. There were five other versions of VB Classic for Windows and one for MS-DOS, so the contents of the book don't really live up to the title. The contents describe features which won't work in VBWin3 or earlier and both the 16-bit VB IDEs and the VBDOS IDE are completely different from the one described here. In order to make the book match the title you either need to add a lot more material on the different versions, or to change the title. A title change would be a lot less work.

Must admit that I like the content though. You've done a good job of describing VB6.

 * You sound like a level headed and knowledgeable person; how about lending a hand? Please at least create an account and sign your contributions with four tildes so that we can tell who says what :-)  I agree that the emphasis is on VB6 but most will work on VB5 and a lot on VB4.  As for VB3 and VB.DOS, I've never used them for more than the most trivial of tasks so i'm not really qualified.  If you could track down a tutorial on VB.DOS, VB3, etc. that is in the public domain ro get an author to relicense one then we could create several books.  --kwhitefoot 22:30, 3 October 2005 (UTC)

 * Are we going to rename this book? I think you would get more interest if the focus was narrowed to just VB6, especially if the title mentioned VB6. - Bevo 22:38, 23 October 2005 (UTC)

 * I renamed it Visual Basic Classic because it was originally just Visual Basic and I wanted to distinguish it from VB.NET. The name VB Classic seems to be quite common now but I think you have a good point because it is mostly used by those who are already expert users.  For now I'll add a redirect page that uses VB6 in the title.  You said we in your first sentence, I hope that means you intend to take part :-) --kwhitefoot 10:26, 24 October 2005 (UTC)

How do you search inside a Wikibook?
With all the substructure to this Wikibook, I'm having trouble figuring out how to do a search within it (all of it, not just the current page). - <IP_ADDRESS> 19:37, 14 November 2005 (UTC)
 * If you can think of a better structure I'm open to suggestions. And if you ever find a way of confining a search to a specific book I'm sure a lot of people would love to know.  Probably best to discuss searching on this page: Wikibooks_talk:Searching  --kwhitefoot 20:13, 14 November 2005 (UTC)

 * Search normally would but include the book title. So to search for the history of Visual Basic Classic withing this book, search for "Programming:Visual Basic Classic/History".SteveSims 23:03, 23 June 2007 (UTC)

Visual Basic Classic suggested merge
User:Hagindaz has suggested that Programming:Visual Basic Classic should be merged with VB6 Command Reference? I think that a better course would be for the contributor to VB6 Command Reference to add to Programming:Visual Basic Classic but I might be biased. --kwhitefoot 13:54, 13 April 2006 (UTC)

 * I meant that VB6 Command Reference should either be added as an appendix to Programming:Visual Basic Classic, or have any useful content added to Programming:Visual Basic Classic, then redirected. I found VB6 Command Reference as an orphaned module. Since both books are on the same subject, so I don't think there is any reason to have them both exist as separate books. I'm sorry I wasn't clear, you can't add notes to merge. --Hagindaz 17:27, 13 April 2006 (UTC)

 * Thanks for the clarification. I wonder if we can change the merge template to allow for a short explanation?  Anyway I added a note to the talk page of the contributor, perhaps he or she will get in touch.  --kwhitefoot 20:44, 14 April 2006 (UTC)

 * I've just taken a look at the merge templates. In fact they do allow for optional reason to be added.  There are also mergeto and mergefrom templates that indicate which direction the content should move.  That was something I didn't know.  I'll try the exercise of changing the modules to add a reason for the merge.  --kwhitefoot 20:59, 14 April 2006 (UTC)

 * Merge completed. (There was an uncommented program that I deemed not usable and of no real importance) --Panic (talk) 07:06, 27 March 2010 (UTC)

Splitting into subpages
The book has originally been written as one page. It was split into subpages during August and September 2005 by. For one of the last revisions of the book in one page, see revision 211226. --Dan Polansky (discuss • contribs) 19:24, 7 September 2012 (UTC)

title: Talk:Visual Basic


text:
User:CG janitor/Watch2

January

 * Category:Alumni of the University of Vienna
 * Category:Judicial Districts of Peru
 * Category:Members of WikiProject Tenacious D
 * Category:Motorcycle enthusiast Wikipedians
 * Category:Participants in WikiProject Protected areas of India
 * Category:State Tech Prep
 * Category:Tibetan Americans
 * Category:U.S. Route 150
 * Category:UAAP football team templates
 * Category:UK Raving
 * Category:Uhuru Movement
 * Category:User dsrt interest
 * Category:WikiProject Christian Metal articles
 * Category:WikiProject Shreveport articles
 * Category:Wikipedia Editing Aids
 * Category:Wikipedians interested in wild food
 * Category:Wikipedians who like Initial D
 * Category:Wikipedians who like Lupin III
 * Category:Wikipedians who use Ligatures

 * Category:Durham cricket captains
 * Category:Eguor admins
 * Category:Geobox
 * Category:Torbanists
 * Category:Whitney Independent Study Program alumni

 * Category:Wikipedians in the WikiProject Current Local City Time

 * Category:9/11 Commission
 * Category:Completed Translation/fi
 * Category:Completed Translation/no
 * Category:Featured picture nominations/January 2007
 * Category:Linux CD/DVD writing software
 * Category:Programs produced by Thirteen/WNET New York
 * Category:Proofreaders Needed/no
 * Category:Translation In Progress/no
 * Category:Translation Request/ar
 * Category:Translation Request/he
 * Category:Translation Request/no
 * Category:Translation sub-pages/he
 * Category:Translation sub-pages/no
 * Category:WikiProject Scouting GG/GS task force members

 * Category:Best Original Song Golden Globe winners old cfd - closed
 * Category:People who attended Troy High School (Michigan)

 * Category:Alien (film series) characters
 * Category:Battles of the Ancient era
 * Category:Battles of the Early Modern era
 * Category:Battles of the Industrial era
 * Category:Battles of the Medieval era
 * Category:Battles of the Modern era
 * Category:Buildings and structures in Perth, Western Australia
 * Category:Ethnic German groups in Romania
 * Category:Former departments of France in Belgium
 * Category:Former departments of France in Germany
 * Category:Former departments of France in Italy
 * Category:Former departments of France in the Netherlands
 * Category:Images of Perth, Western Australia

 * Category:Australian military personnel killed in World War One
 * Category:Australian military personnel killed in World War Two
 * Category:Chinese in Japan
 * Category:French military personnel killed in World War One
 * Category:French military personnel killed in World War Two
 * Category:German military personnel killed in World War One
 * Category:Nigerien activists
 * Category:World War II killed in action
 * Category:World War I killed in action

title: User:CG janitor/Watch2


text:
luchten

Etymology 1
From.

Verb

 * 1) to air, bring something into contact with the air; to give a walk in open air
 * 2) to stand, suffer, tolerate

Etymology 2
From, from , from , from , from (modern ).

Verb

 * 1)  to illuminate, to give off light

title: luchten


text:
Talk:List of subcamps of Neuengamme

Untitled
Over half of the articles are redlinks, so I added the tag. They should be removed or the redlinked articles written.--Merfster 22:00, 11 August 2006 (UTC)

work in progress
im changing the list, correcting some mistakes ... plz be patient Sebastian scha. (talk) 03:14, 1 May 2008 (UTC)
 * most changes done. next task neuengamme subcamps? or better working locations Sebastian scha. (talk) 04:15, 5 May 2008 (UTC)

Bot report : Found duplicate references !
In the last revision I edited, I found duplicate named references, i.e. references sharing the same name, but not having the same content. Please check them, as I am not able to fix them automatically :) DumZiBoT (talk) 07:55, 9 August 2008 (UTC)
 * "number" :
 * Refers to the official German list Verzeichnis der Konzentrationslager und ihrer Außenkommandos gemäß § 42 Abs. 2 BEG
 * Refers to the Official German list
 * Done Sebastian scha. (talk) 12:47, 9 August 2008 (UTC)

External links modified
Hello fellow Wikipedians,

I have just modified one external link on List of subcamps of Neuengamme. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
 * Added archive https://web.archive.org/web/20090423004151/http://bundesrecht.juris.de/begdv_6/anlage_6.html to http://bundesrecht.juris.de/begdv_6/anlage_6.html

Cheers.— InternetArchiveBot  (Report bug) 15:37, 23 May 2017 (UTC)

External links modified
Hello fellow Wikipedians,

I have just modified one external link on List of subcamps of Neuengamme. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
 * Added archive https://web.archive.org/web/20070928223659/http://staging3.hauptsache.net/?id=550 to http://staging3.hauptsache.net/?id=550

Cheers.— InternetArchiveBot  (Report bug) 19:28, 29 November 2017 (UTC)

External links modified
Hello fellow Wikipedians,

I have just modified one external link on List of subcamps of Neuengamme. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
 * Added archive https://web.archive.org/web/20140221235630/http://www.holocaustrevealed.org/_domain/holocaustrevealed.org/Camps/camps2.htm to http://www.holocaustrevealed.org/_domain/holocaustrevealed.org/Camps/camps2.htm

Cheers.— InternetArchiveBot  (Report bug) 18:47, 2 January 2018 (UTC)

title: Talk:List of subcamps of Neuengamme


text:
ATP Esercizio

ATP Esercizio Srl was an Italian public transport company operating in 67 small cities near Genoa, Italy. The major shareholder of the company is the Province of Genova (66,16%). The company operates under its owner ATP Azienda Trasporti Provinciali Spa.

History
ATP Esercizio Srl was founded in the beginning of 2012 by the merging of two transport companies: Tigullio Pubblici Trasporti Spa, founded in 1976 and operating in Chiavari, and ALI Autolinee Liguri Provincia di Genova Spa, founded on 2 June 2000.

On the 1st January 2021, ATP Esercizio effectively merged into AMT Genova in its entirety; with its services and staff now being part of the latter operator.

title: ATP Esercizio


text:
User:Fgjhud8y7ghrg

HELLO MY NAME IS UR ANUS. I HAVE A DOG IN AFGHANASTAN. IT IS CHOKING. PLEASE HELP ME. I THINK IT IS DEAD. BEST OF LUCK. MY DEAD DOG. R.I.P. BUT ITS ALL RIGHT I BURRWIEQD IT IN MY SWAMP. IT IS BLEEDING WITH ALL THE OTHER DEAD FISH. ATLEAST IT WILL HAVE SOME FRIENDS

title: User:Fgjhud8y7ghrg


text:
Talk:Kadapa

External links modified
Hello fellow Wikipedians,

I have just modified 2 external links on Kadapa. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
 * Added archive https://web.archive.org/web/20121116192051/http://cdma.gov.in/KADAPA/ to http://cdma.gov.in/KADAPA/
 * Added archive https://web.archive.org/web/20110520054852/http://www.censusindia.gov.in/Census_Data_2001/Census_Data_Online/Social_and_cultural/Religion.aspx to http://censusindia.gov.in/Census_Data_2001/Census_Data_Online/Social_and_cultural/Religion.aspx

Cheers.— InternetArchiveBot  (Report bug) 23:58, 4 December 2017 (UTC)

title: Talk:Kadapa


text:
Dog Care/Debarking

Introduction
"Debarking" a dog requires a veterinarian to enter the dog's trachea and modify its vocal cords. The procedure requires the use of a general anesthesia and involves punching or notching the dog's vocal chords to soften or significantly reduce his ability to bark. No procedure is without risk and debarking risks scarring and narrowing of the tracheal opening following the surgery, causing the dog difficulty in breathing. After the surgery, the dog sounds hoarse whenever it tries to bark, and it can not generate loud barks. Sometimes the bark will return to some extent due to a build up of scar on the vocal chord but the bark will never be as loud as before.

Controversy
Debarking is a contentious issue within the dog community, even among experts and veterinarians. Some advocate debarking as a helpful last-resort for incessant barkers while others maintain the process is cruel and unnecessary. This surgery is considered unethical by some veterinarians who believe that the risk does not justify the benefit while others perform this surgery routinely for certain breeds.

As such, some jurisdictions have outlawed debarking. For instance, Section 6 of the German Animal Welfare Act forbids all deliberately damaging operations. Very few exceptions, such as livestock branding of horses, are granted, but mere cosmetic surgery is not allowed.

Implications
It would be best for a potential dog owner to consider whether a loud animal is acceptable before adopting the dog, as some breeds are less likely to bark than others are. Most dogs can be trained to bark less in situations where it is inappropriate. Should debarking be considered after training has failed, locating a veterinarian that has extensive experience with the procedure is desirable to minimize the risks.

Dogs will be dogs and all dogs bark to some extent. On the other hand, neutered cats rarely make noises loud enough to disturb neighbors, and may be a better choice of pet if noise is unacceptable.

title: Dog Care/Debarking


text:
Birch Hill Nightclub

Birch Hill Nightclub was a music venue and nightclub in Old Bridge Township, New Jersey. The venue ran into trouble in 2000 after an accidental drowning and drug raids, along with a loss of their liquor license. Birch Hill was sold in 2003 and is now a housing development. Many big-name bands played the venue, including Gov't Mule, Dio, Scorpions, Hoobastank, Blue Öyster Cult, Cheap Trick, UFO, Iron Maiden, Rainbow, Eve 6, Toadies, Sudzert and Slayer.

title: Birch Hill Nightclub


text:
1919 Standard Oil Company fire

On September 13, 1919, a fire and explosion occurred at the Standard Oil Company in Greenpoint, Brooklyn, New York City.

Fire
The Standard Oil Company Campus and former Astral Oil Works was spread out over 20 acre. A fire broke in Tank No. 36 on the Standard Oil Company Campus around 2:00 p.m., but before the New York City Fire Department was called, the tank ignited, sparking off multiple fires throughout the campus. The yard held large quantities of naphtha, gasoline, oil and alcohol and more 1000 barrels of other explosive and flammable liquids. The fire burned furiously for three days, destroying millions of gallons of oil and caused damage estimated at $5,000,000 ($0 in 2024). Over 1,000 firemen fought the spectacular blaze, 300 of which were treated for burns and minor injuries.

Standard Oil’s Brooklyn refinery may have been an intentional attempt to clear the land and draw insurance. The fire site is now the location of the Bayside Fuel Oil depot at Bushwick Inlet.

title: 1919 Standard Oil Company fire


text:
Wings 3D

Wings 3D is a free, open source polygon modeler that was originally inspired by Nendo and later Mirai (both by Izware).

Once learnt, its clean, no-frills interface and wide-ranging (but unbloated!) toolset lets the user concentrate on their prime purpose: modeling.

The current release is available from the Wings 3D site. Other software is necessary to allow models made in Wings to be (properly) rendered and / or animated, although Wings does have an excellent feature-rich native UV unwrap facility.

Many industry standard import / export options are supported by Wings to allow it to communicate with the 'outside world'

 * /User Manual/
 * /Tutorials/
 * /Useful links/

title: Wings 3D


text:
Galegeeska

Galegeeska is a genus of elephant shrew (or sengi) in the family Macroscelididae.

Members in this genus were formerly classified in the genus Elephantulus, but later studies found the Somali and rufous sengis to be the sister taxa of the clade containing the genera Petrodromus and Petrosaltator; due to this, the genus Galegeeska was coined for the Somali and later the rufous sengi. The split with the Petrodromus-Petrosaltator clade is estimated to have occurred about 20.6 million years ago.

Galegeeska translates to "weasel of the horn". In the Somali language, geeska means corner or horn, as in the Horn of Africa. in Ancient Greek means weasel, and has been used in other small mammal taxa. 'Gale' also honours one of the authors, Galen B. Rathbun (1944-2019) who searched for the Somali sengi and devoted several decades of research into sengi biology.

It contains two species;

 * Somali elephant shrew, Galegeeska revoilii
 * Rufous elephant shrew, Galegeeska rufescens

Research of the Galegeeska genus shows three specific traits (apomorphies) that are unique to the Galegeeska. These three traits includes specifically hairy rhinarium below, fully developed pectoral gland, and y-shaped sulci of the dorsal openings of the stapedial artery. The Galegeeska also tend to have an absence of bicolored tail where the Gelegeeska revoilii have a white tail and the Galegeeska rufescens have a dark brown tail.

title: Galegeeska


text:
Arsenijević

Arsenijević (Арсенијевић) is a Serbian surname, a patronymic derived from the given name Arsenije (from Greek Arsenios). It may refer to:

 * Milorad Arsenijević (d. 1987), Yugoslav Serbian footballer
 * Filip Arsenijević, Serbian footballer
 * Stefan Arsenijević (born 1977), Serbian film director
 * Nemanja Arsenijević (born 1986), Serbian footballer
 * Vladimir Arsenijević (born 1965), Serbian novelist
 * Marina Arsenijevic (born 1970), Serbian-born American concert pianist and composer

title: Arsenijević


text:
Talk:Corey Williams (basketball, born 1977)

External links modified
Hello fellow Wikipedians,

I have just modified 1 one external link on Corey Williams (basketball, born 1977). Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
 * Corrected formatting/usage for http://www.nbl.com.au/news/article/2010/march/homicide-wins-mvp-at-nbl-awards-night/

Cheers.—cyberbot II  Talk to my owner :Online 00:43, 1 April 2016 (UTC)

External links modified
Hello fellow Wikipedians,

I have just modified 1 one external link on Corey Williams (basketball, born 1977). Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
 * Added archive https://web.archive.org/web/20150618011602/http://www.nba.com/dleague/news/transactions_06-07.html to http://www.nba.com/dleague/news/transactions_06-07.html

Cheers.— InternetArchiveBot  (Report bug) 21:08, 30 November 2016 (UTC)

External links modified
Hello fellow Wikipedians,

I have just modified one external link on Corey Williams (basketball, born 1977). Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
 * Added tag to http://www.backpagelead.com.au/index.php/basketball/5755-homicide-williams
 * Added archive https://web.archive.org/web/20070112095435/http://www.nba.com/dleague/news/transactions_05-06.html to http://www.nba.com/dleague/news/transactions_05-06.html

Cheers.— InternetArchiveBot  (Report bug) 13:14, 28 April 2017 (UTC)

External links modified
Hello fellow Wikipedians,

I have just modified one external link on Corey Williams (basketball, born 1977). Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
 * Added archive https://archive.is/20131202153417/http://youth.usab.com/training-room/player-psychology/How-Corey--Homicide--Williams-Became-a-Streetball-Legend.htm to http://youth.usab.com/training-room/player-psychology/How-Corey--Homicide--Williams-Became-a-Streetball-Legend.htm

Cheers.— InternetArchiveBot  (Report bug) 04:06, 13 August 2017 (UTC)


text:
User:Asad0x01/sandbox

Partho Paulinews Folia is a Bangladeshi filmmaker, screenwriter. Films like Opekkha, Jok , Silence, Insomnia gained him popularity around the world and got him many prestigious awards.

= Early Life = Partho was a born on 23rd May 1997 in Dhaka, Bangladesh. His school was  Siraj Mia Memorial Model School and His college was Notre Dame College.

Career
Partho started his career in his school days. His mother wanted him to sing in his early stage and took him to the Bangladesh Sishu Academy, where he learnt singing, but he always wanted to be an actor that is he didn’t complete the full course. In his school days he was always more into art, photography and graphic designing. As he was always into exploring things he started finding what he loves. After trying photography, graphic designing, coding, hacking, music, acting, he realized he loves telling doesn't matter what the medium is. He felt like film is the ultimate medium to tell his stories so he started pursuing film making. He started making films and started telling his stories. He took film making more seriously after winning best drama and best director award for his film Silence in Canadian Film Festival and Delta Moon Student Film festival. After Silence he came up with many successful films like Till the End, Maybe or maybe not and many more. His film Opekkha gained him more popularity starring two youngsters Shoumik Ahmed and Tasnuva Tisha. Children Film Society’s International Children Film Festival is a place what inspired Partho to be what he is today. He wanted to learn more about films that that is why he joined many workshops and short courses. He even worked for many well known companies like Airtel, Robi, Banglalink, Gaanchill Music, Ranks, Grameenphone both as filmmaker and graphic designer. After leaving Sishu Academy he realized he loves music too, and that made his first ever single “Tumi Amar Rani” possible. Tumi Amar Rani was released on all international platforms like Spotify, Apple Music, Google Music. As he worked as an actor in many television dramas, television commercials that made him more keen about film making. He also worked with Asif Iqbal, Asif Akber, Salman Muqtadir, Sabila Noor, Minar Rahman, Pritom Hasan, Tanjib Sarowar and many more.

Filmography
2015 - Insomnia

2016 - Silence

 * Winner, Best Drama - Canadian Film Festival 2016

 * Winner, Best Drama -  Delta Moon Students Film Festival 2016

2017 - Maybe or Maybe Not

2018 - Opekkha

2019 - Jok - It's Not Her Fault

 * Semi Finalist -Deumila30 Film Festival, 2019.

 * Semi Finalist - Cefalù Film Festival 2019.

 * Official selection - 12th International Inter University Film Festival 2019.

 * Official Selection - 12th International Children Film Festival 2019.

 * Official Selection - WOIS Film Fest 2019.

 * Official Selection - Inshort 2019.

 * Official Selection - Lit Off Sessions 2019.

 * Official Selection - First Time Film Maker Session 2019.

 * Official Selection - Global Youth Film Festival 2019.

 * Official Selection - Naari in Many Colors 2019.

title: User:Asad0x01/sandbox


text:
Dharmawangsa

Dharmawangsa, stylized regnal name Sri Maharaja Isyana Dharmawangsa Teguh Anantawikramottunggadewa (died 1016) of the Isyana dynasty, was the last Hindu raja of the Kingdom of Mataram, who reigned from 990 to 1016 CE. He is also known by his posthumous name Wijayamreta Wardhana, which means "powerful in glorious death", which refers to his fight to the death.

Reign
He succeeded Sri Makutawangsa Wardhana. Dharmawangsa was the patron of the translator of the Mahabharata text into Old Javanese. Dharmawangsa was either the son or son-in-law of Sri Makutawangsawardhana, preceding King of Mataram and grandson of Mpu Sindok.

Dharmawangsa conquered several areas, including Bali, and established a colony in West Kalimantan. Dharmawangsa's sister, Princess Mahendradatta, married Udayana, Raja of the Warmadewa Dynasty in Bali, and had a son, Airlangga.

In the year 990, Dharmawangsa launched a naval invasion on Sriwijaya in Sumatra and unsuccessfully attempted to capture Palembang, as Sriwijaya repelled the invaders. Dharmawangsa's invasion was mentioned by both ambassadors to China in 992.

Death
In 1016, Srivijaya launched a retaliation attack and destroyed the Watugaluh Palace in Java. Srivijaya forces assisted the lesser king Haji (king) Wurawari of Lwaram to revolt, attacked and destroyed the Mataram palace, killing Dharmawangsa and most of the royal family. This sudden and unexpected attack took place during the wedding ceremony of Dharmawangsa's daughter, which rendered the court unprepared and shocked. Dharmawangsa follows warrior code of honor and valiantly defends his court to his death. For this, he was honored in his posthumous name Wijayamreta Wardhana which means "powerful (king) in glorious death".

This calamity was recorded in the Javanese account as the pralaya (the debacle) the death of the Mataram kingdom. With the death of Dharmawangsa and the fall of the capital, under military pressure from Srivijaya, the kingdom finally collapsed and fell to chaos. There was further unrest and violence several years after the kingdom's demise.

Dharmawangsa's heir and nephew, Airlangga, son of Mahendradatta and Udayana, was aged only 16 at the time. However, he escaped the invaders and went on to become a founder of the Kahuripan Kingdom, the successor of the Mataram.

title: Dharmawangsa


text:
Compact executive car

A compact executive car, also known as a compact luxury car, is a premium car larger than a premium compact and smaller than an executive car. Compact executive car is a UK term and a part of the D-segment in the European car classification.

An executive car generally needs to be comfortable and well-equipped while also being cheap to run as a company car. They may have performance features and are often viewed as status symbols. A high percentage of the "executive cars" market share consists of corporate-owned cars, or vehicles provided by a firm for the business and sometimes private use by employees.

United States
The "compact executive car" description is not often used in the United States, but it describes certain models imported from Europe.

The Cadillac ATS has been described as a compact executive car. The ATS was succeeded by the Cadillac CT4.

Before the ATS, a heavily badge engineered version of the Saab 9-3 was sold in Europe as the Cadillac BLS (2005–2009). The BLS was both developed and manufactured by Saab in Trollhättan, Sweden. The model was never sold in the Northern American market. Cadillac's previous attempt at a compact executive car for the US market was the Cimarron manufactured in between 1981–1988. The Cimarron is largely considered to be a market failure and also at least partially responsible for the market struggles that Cadillac faced during and after its production.

United Kingdom

The 1971 Triumph Dolomite is an early compact executive car.

Jaguar's first compact executive car (although larger than the 1960s' Jaguar Mark 2) was the 2001 Jaguar X-Type. Sales, however, were disappointing. The X-type was replaced by the Jaguar XE in 2014, competing in the same sector.

Italy

Alfa Romeo's models 75 and 155 are considered compact executive cars in the United Kingdom. The 1996 Alfa Romeo 156 has been classified as such. This was followed by the Alfa Romeo 159 and then the Giulia (Type 952).

An early compact executive car from Lancia is the 1972 Lancia Beta (Type 828). The Beta morphed into the Lancia Trevi, which was produced from 1980 to 1984. Following an absence from the segment for five years, Lancia returned in 1989 when the Lancia Dedra replaced the smaller Lancia Prisma. The Dedra was replaced by the Lancia Lybra, which was produced from 1998 to 2005.

Germany

An early compact executive car produced in Germany was the 1966 BMW 02 Series, followed by the BMW 3 Series in 1975.

In 1965 Audi introduced their first compact executive model Audi 72.

The 1983 Mercedes-Benz W201 range (also known as the "Mercedes-Benz 190") was the first compact executive car from Mercedes-Benz. In 1993, the W201 was replaced by the Mercedes-Benz C-Class range.

France
DS Automobiles offers a compact executive with its DS 4 hatchback. From earlier models also the larger DS 5 (sold until 2018) could be considered a compact executive car. The DS brand used to be a sub-marque of Citroën, and thus earlier model years (before 2015 for the DS 4 and DS 5, but the change depends on the model) carry the Citroën logo. The smallest model offered by DS has been the DS 3 (sold until 2019), which could be considered to be a subcompact or even supermini executive car. The current DS 3 Crossback differs from the earlier model substantially, as it is a small crossover SUV.

Sweden

The Volvo S60 as well as its estate version Volvo V60 are considered to be compact executive cars.

Saab Automobile, which went defunct in 2011, had the 9-3 -model which was a compact executive car. Based on heavily modified GM engines and platforms, the 9-3 was available as a convertible, hatchback (first generation), sedan (second generation) and station wagon (second generation). The 9-3 had a wide variety of both petrol and diesel engine options. Most of the petrol engines were turbocharged and supported the use of ethanol fuel, which were both relatively uncommon features for a mass production car in the 00's. The 9-3 also had high emphasis on car safety, which was a high priority in the design of all Saab cars. Also the previous Saab 99 and Saab 900 could be considered as compact executive cars at some markets, while especially in Northern Europe these models were more commonly seen as ordinary small family cars.

Japan
An early compact executive car produced in Japan was the 1988 Mazda Persona / Eunos 300. The first Japanese compact executive car to be successful in overseas markets is the 1998 Lexus IS / Toyota Altezza.

Other Japanese compact executive cars include the Infiniti Q50 (by Nissan), Acura TLX (by Honda)   and Mazda Xedos 6.

South Korea
Compact executive cars produced in South Korea include the Genesis G70.

Subcompact executive cars
Subcompact executive cars, also called premium compacts, is the category of the smallest premium cars. It is part of the C-segment in the European car classification. Examples include the Mercedes-Benz A-Class and CLA-Class, Audi A3, Volvo S40, BMW 1 Series, and 2 Series. Premium compacts compete with well-equipped mid-size cars, and highly optioned premium compact cars can have pricing and features that overlaps with compact executive cars.

title: Compact executive car


text:
User:Courtney.cem244/sandbox

Epidemiology
This pathogen has a worldwide distribution but is found at the highest density in the North Temperate Zone between the arctic circle and the Tropic of Cancer. Outbreaks have been recorded in many countries including the United States, Canada, Australia, Germany, France, and South Africa and in are most often recorded during the summer and fall. Due to the highly contagious and transmissible nature of this bacterium, the prevalence in bird species is abundant. B. avium can remain in the environment in litter and water for as long as 6 months and has a short incubation of only 7-10 days allowing for rapid transmission.

Prevalence is highest and most well understood in domesticated turkeys, especially in the younger populations consisting of birds 1-6 weeks old, yet, turkeys of all ages are susceptible. In addition, much of the transmission is thought to relate to management practices and outbreaks are often associated with farms with confined spaces and flocks consisting of animals of varying ages. Older animals are thought to be carriers of this bacterium which is why it is recommend that turkey farmers avoid multi-age flocks. Although most common in domestic turkeys, B. avium can transmit to chickens as an opportunistic infection, and wildlife species where prevalence is still being evaluated. It has been suggested that wildlife species act mainly as a reservoir and it is unclear if B. avium acts as part of the normal flora in wild bird populations or is a causative agent of disease. Despite the fact that wild birds are commonly asymptomatic, Bordetellosis has been reported in a variety of wild birds including parrot finches, partridges, cockatiels, and ostriches, among others. In one study by Raffel et.al, in a sample of 46 Canadian Geese, 67% tested positive for B. avium using a serum agglutination test for antibodies. Although many studies have begun to look at characterizing the epidemiology of this bacterium, the understanding of prevalence in different countries and among different species of domestic and wild birds remains to be fully understood.

title: User:Courtney.cem244/sandbox


text:
Concept Classification

Back to Topic: Instructional Design > Cognitive Menu > Concept Classification > Define >  Learn >  Teach >  Routine >  Power >  Try >  References

Objectives
This lesson covers how to design instruction for teaching concept classification tasks. After completing this lesson, you should be able to :

 * Explain what concept classification tasks are and why they are important,
 * Describe the principles for learning concept classification tasks,
 * Prepare instructional tactics to teach concept classification tasks.

Lesson organization
This lesson is organized into the sections listed below. Navigate to each section by following the "Next" link at the bottom of each page. Return to previously viewed pages by following the "Back" button on the bottom of each page or by following the labeled links at the top of each page which correspond to each of these sections :

 * Define:Concept Classification: Defined
 * Learn:Concept Classification: Principles for Learning
 * Teach:Concept Classification: Principles for Teaching
 * Routine:Concept Classification: Routine Tactics for Teaching
 * Power:Concept Classification: Power Tactics for Teaching
 * Try:Concept Classification: Skill Builder Practice

Click the Next button to continue.

Source

 * Concept Classification by Charles M. Reigeluth. Used by Permission.

title: Concept Classification


text:
1995 Bank of the West Classic – Doubles

Lindsay Davenport and Arantxa Sánchez Vicario were the defending champions, but Sánchez Vicario did not compete this year. Davenport teamed up with Irina Spîrlea and lost in the quarterfinals to Kathy Rinaldi-Stunkel and Jill Hetherington.

Lori McNeil and Helena Suková won the title by defeating Erica Adams and Zina Garrison-Jackson 3–6, 6–4, 6–3 in the final.

Seeds
The first two seeds received a bye to the second round. • # 🇺🇸 Lindsay Davenport / 🇷🇴 Irina Spîrlea (quarterfinals)

• # 🇺🇸 Mary Joe Fernández / 🇺🇸 Pam Shriver (semifinals)

• # 🇺🇸 Lori McNeil / 🇨🇿 Helena Suková (champions)

• # 🇺🇸 Erica Adams / 🇺🇸 Zina Garrison (final)

title: 1995 Bank of the West Classic – Doubles


text:
User:Paul Hempstead

Hello, all. I'm Paul Hempstead. My interests are mainly video games, especially Half-Life 2. That's it for now...

title: User:Paul Hempstead


text:
Wikipedia:WikiProject Spam/LinkReports/honkaiimpact3.mihoyo.com

Links

 * honkaiimpact3.mihoyo.com resolves to [//<IP_ADDRESS> <IP_ADDRESS>]
 * Link is not on the blacklist.
 * Link is not on the domainredlist.
 * Link is not on the Monitorlist.
 * None of the mentioned users is on the blacklist.
 * Link is not on the whitelist.
 * Link is not on the monitor list.
 * Link is not on the whitelist.
 * Link is not on the monitor list.

Additions

 * Displayed all 3 additions.


text:
Wikipedia talk:Articles for improvement

=Scheduled weeks=

The AFI article for Week 30 of 2024
The selection for week 30 (starting 22 July 2024) is Cape (geography).

Discussion (week 30)
''Please any comments or concerns about the selection here. If three net members elect to reselect the article, then the article will be reselected and the former one removed from the list of articles.''

The AFI article for Week 32 of 2024
The selection for week 32 (starting 05 August 2024) is Happiness.

Discussion (week 32)
''Please any comments or concerns about the selection here. If three net members elect to reselect the article, then the article will be reselected and the former one removed from the list of articles.''

The AFI article for Week 31 of 2024
The selection for week 31 (starting 29 July 2024) is List of public art in Chicago.

Discussion (week 31)
''Please any comments or concerns about the selection here. If three net members elect to reselect the article, then the article will be reselected and the former one removed from the list of articles.''

=General discussion=
 * Regarding pool, this is excellent news. That article does need some work on it. I'll do what I can, if you have any questions about the intracacies of the different versions of pool, drop me a message. I do have access to Shamos' book, which should be an invaluable source. Also, I've already GA'd nine-ball, so there's some ref ideas on that page.  Lee Vilenski (talk • contribs) 11:24, 22 April 2024 (UTC)

title: Wikipedia talk:Articles for improvement


text:
User:PD428

Hello!

I am a new Wikipedia user! Third year media student interested in photography and film! Be patient with me! :)

title: User:PD428


text:
User:Jezups/sandbox

Blurry Photos is a critically acclaimed skeptical comedy podcast, created by David Flora and David Stecco in 2012. The podcast focuses on lesser known topics with a paranormal aspect, ranging from folklore to conspiracy theories and cryptozoology. It is based in Chicago.

From its debut in August 2012 until February 2018 the podcast was co-hosted by Chicago-based improv artists David Flora and David Stecco, with a characteristic style of sketch comedy combined with free-form discussion and comedic elements. Since the departure of David Stecco the show has taken on a more informational and storytelling-oriented format.

Reception
Blurry Photos was awarded the title “Best Podcast in Chicago” by Chicago Reader, as well as being featured prominently in the Chicago Tribune , and being a finalist in the Parsec Awards for three consecutive years from 2013 to 2015.

title: User:Jezups/sandbox


text:
SS U.S.O.

SS U.S.O was a Liberty ship of the United States during World War II, named after the United Service Organizations, an organization designed to provide morale to servicemen deployed all around the world.

Built at the Bethlehem-Fairfield Shipyard in Baltimore, Maryland under MC contract (hull number 1811), the ship was laid down on 29 September 1943, and launched on 21 October 1943. The ship survived the war and was sold into private ownership in 1947. However, in 1967, the ship was wrecked and subsequently scrapped.

title: SS U.S.O.


text:
A-level Mathematics/OCR/M3/Kinematics

Formulae
You are expected to know the following formulae, as they will not be provided in the formula book:

$$ a = \frac{dv}{dt} = \frac{dv}{dx} \frac{dx}{dt} = v \frac{dv}{dx} $$

title: A-level Mathematics/OCR/M3/Kinematics


text:
Talk:Electronics

Vision, Mission, Scope & Concept
I took the liberty to insert this as a new topic at the beginning of this discussion page, although the topic is not new. I am badly missing an "authoritative" definition of the scope and concept of this book. Such information should be first on this discussion page - where you now read this question - and probably at the book's start page, too.

Would someone please step forward, grasp the authority, appoint himself/herself as the leader (at least for a day), and define the principles for the contents of this book? I am not asking for yet another scope, TOC, whatever discussion. I am asking for a decision, definition, "final answer", consensus, which IMHO is badly needed as the basis for the work:

 * Type of the book? Reference, textbook, self-study course, (application) note collection, tutorial, experiment instructions, etc.?
 * What difficulty level? Beginner, intermediate, advanced level? And
 * level for whom? Hobbyist, professional, college, universiy, scientist? (an advanced level for a hobbyist is something completely different than one for university).
 * What scope? Where to start? Where to end?

Publish this information here, so people can decide if this is the right book they want/can contribute to, or that they should probably do another book.

Please, DON'T DISCUSS, please DECIDE.

'Can anyone Include/Make a "Massive Printable Version" link? I know know much about how Wikimedia works, but I would like to print this out.'

<IP_ADDRESS> 10:58, 2 January 2006 (UTC)

Archive
Because of their length, the previous discussions on this page have been archived. If further archiving is needed, see How to archive a talk page.

Previous discussions:

 * Archive 1 (March 2004 to June 2005):

 * Archive
 * Foreword
 * Contributing [to this book]
 * Table of Contents [for each page]
 * TOC [same]
 * Scope of Book
 * Depth of mathematics
 * Circuit template [circuit diagrams]
 * Quantum physics, Quantum Mechanics
 * A Crossroads [Scope of the book]
 * Unusual circuit visualizations
 * People whining about how bad their physics/electronics textbook is

''I was a bit liberal with the archiving. The same dicussions seem to be neverending, though. Just cut and paste a particular comment from the archive if you want to reply to it. - Omegatron 17:06, 21 July 2005 (UTC)''

Images for deletion
Note to admins: We had some trouble with uploading images, feel free to delete the orphan images.

 * What images specifically? - Omegatron 16:56, 21 July 2005 (UTC)

People working on this book
Name: Goals. What you are working on? Any requests?

Wanderer: I am currently working on the background for this book at Physics in English.

Omegatron: I always wanted to learn electronics when I was a little kid, but none of the books I read provided me with consistent, understandable, correct information. In sixth grade we covered Ohm's law and I was dismayed when my teacher said I would have to wait til college to learn the rest. :-) Now I have my bachelor's in electrical engineering and I want to help write something that is clear and correct.  You shouldn't HAVE to wait til college if you are interested in something enough...  On the other hand, I'm one of the people who adds calculus equations.  :-)  We'll sort it all out eventually...  I also make diagrams using klunky schematic drawer, which I have modified and advertise prominently despite not really caring if you use it. I just like it. See Electronics/Template for the modified (improved?) version.

Theresa knott :I wrote the GCSE electricity book. I don't know a great deal about electronics, but I do know physics. I intend to copy edit, correct physics misconceptions and the like. I am also resonably adept at drawing diagrams. Let me know if there is anything you want drawn.

maxpower: Working on a BS.EE. Suffered through some awful textbooks, want to give something back and help with a simpler, more concise electronics/circuits text. Working on filling in the gaps rather than editing, for the most part.

DavidCary: There's tons of fun electronics stuff that a high-schooler could afford to buy all the parts, and understand well enough to *build*. I'd like this book to inspire people to *build* stuff rather than think this is some sort of "rocket science". I have a BS.EE., so I've also suffered through confusing, misleading explanations. There was no reason for me to suffer through learning Laplace Transforms before building my first simple blinky-light. I'm still trying to really understand Maxwell's equations and how they relate to special relativity.

H Padleckas: I added the Section Voltage, Current, and Power to the Chapter module Basic Concepts in the Electronics book. Up till now, the Chapter stood there pretty much empty. A previous attempt tried to describe Voltage in terms of Coulomb's Law and Electric Field but was too mathematical and apparently not used. I'm thinking of moving the Charge and Coulomb's Law section to the beginning chapter and replacing the glossary in the Introductory chapter or merging it with Definitions. The glossary now stands at the beginning as an un-numbered module. I have almost finished writing* and made the Electronics/Charge and Coulomb's Law section previously in Basic Concepts its own separate module as the first ordered module in the book. I made Basic Concepts redirect to Voltage, Current, and Power which I plan to polish up. I also copied most of the content in the sections on Coulomb's Law and Electric Field into an empty module in Modern Physics called Coulomb's Law and Electric Field.

 * I only wrote the last two sections in that module. Other members wrote all previous sections.H Padleckas

Yossarian : I am currently in an Electronics Engineering MSc, and would like to help out if I can. I like what I am hearing here on the talk page about more how-to elements, and possibly the best way to get people started would be a tutorial in electronics EDA (preferrably open source) to allow people who might not have the equiptment have a play around with circuits. I wrote some of the stuff on basic gates, and am continuing to work on the digital circuits section.

Sraevsky I have a BSEE, and I am interested in putting a little time into this book. We'll see what happens, though. Right now I'm very busy trying to finish up a law degree.

Filip Dominec: I would like to
 * 1) help writing text and synchronize it with the czech project at http://cs.wikibooks.org/
 * 2) upload some electronic diagrams to Commons
 * 3) change the main page to something like

Pdavis68 I'm interested in vacuum tube amps as a hobby. I'm going to try to fatten up the section on tube electronics a bit.

Thanks

 * To those who have contributed to Wikipedia, as large parts of this book are base on the things they have written.

 * Theresa Knott, who wrote the GCSE Science book.

 * The maker of Klunky, the ever useful circuit diagram maker.

 * Everyone who has contributed to this book.

GCSE Electricity
If someone could help merge the basic GCSE electricity textbook parts into here, it would be GREATLY appreciated.

 * Where is that? - Omegatron

 * It is right here: GCSE Science/Electricity - Omegatron

So, we're moving everything from GCSE Science/Electricity to Electronics ?

So Electronics is just one chapter in the GCSE_Science book ? So I can move stuff back and forth until I find a place that "fits", and delete redundancies between them ? -- DavidCary 03:58, 28 Jun 2004 (UTC)

What about FHSST_Physics_Electrostatics:Charge ?

huh Kiogora95 (discuss • contribs) 15:49, 25 February 2017 (UTC)

Common Misconceptions
I will list these here. Feel free to add to them. I want to put little marks next to each one when it has been covered in the book. Or we can make uncovered ones bold or something

also these: http://amasci.com/miscon/elect.html
 * Direction of current flow
 * electron current vs. conventional current
 * charge carriers, holes, etc. etc. etc.
 * I thought in terms of electron flow because I thought it was more "correct". But in reality neither is "correct" (current flow in salt water for example) and conventional current is much easier to think in terms of, precisely because it is the convention.
 * voltage and current have polarity, not just magnitude
 * Fundamental ideas of voltage,
 * current,
 * resistance [[Image:100%.png]]
 * (water pipe analogies? pressure, flow, constriction etc.)
 * "voltage" is a useful myth, but it is not single-valued in a changing magnetic field. I wonder if it would make things easier to understand if we explain stuff in terms of real, measurable quantities such as "electrons" and "electric field".
 * Speed of electron drift vs electric fields and waves (speed and motion of electrons themselves, speed of a signal is not actually the speed of light, electrons don't travel at the speed of light down the wires and back)
 * I thought capacitors charged up until dielectric breakdown, and that this was normal. I thought this was the principle behind timer circuits.  this is more like a spark gap.
 * capacitors only charge up to the voltage supplying them.
 * I figured out that RC circuits had something to do with timers but I couldn't figure out how
 * Transistor is like a resistor that changes value with an input. i read that a transistor is an amplifier and that didn't make any sense to me.  i never grasped it.
 * I didn't understand transistors, but i understood "thyristors" as the electronic switches I wanted to use, even though a transistor can be used as a switch quite easily. transistors were not explained very well.
 * I was intimidated by ICs and basically ignored their existence. i think becuase they didnt explain how a transistor was actually made, and how it could be expanded to a darlington transistor, and then to a chip with lots of transistors on one piece of silicon.
 * digital logic was not explained well at all. logic levels are specific voltages within a certain range, open outputs, pull up resistors, etc.
 * idealized circuit diagrams vs circuit layout diagrams (battery symbol vs perfect voltage source with source resistance)
 * I moved the 'Decoder and Encoders' to 'Digital to Analog & Analog to Digital Converters' as the description did matches these devices instead of the all digital devices that decoders/encoders are. Unfortunately I am still figuring out editing here so I was unable to add a description for those devices.

Combine topics?
It seems that there are too many topics in the TOC. Do resistors, inductors and capacitors really have to be separate topics? Can't we merge some topics, especially under DC electronics?

--Extro

 * I think they should be separate topics. Just my opinion. - Omegatron

 * I'd have to agree. It's good to keep the book modular like this so people won't have to dig around much to find what they're looking for. Besides, capacitors, resistors and inductors are some pretty important and widely used components. - Alex S

 * I disagree. I suspect it's easier to understand the differences between what capacitors do and what inductors do if you put them all on the same page -- otherwise the reader has to flip back and forth to see the subtle differences between RC circuits and RL circuits. --DavidCary 18:14, 3 Jun 2005 (UTC)

 * I agree about capacitors and inductors, and other duals. :-) - Omegatron 18:17, 4 Jun 2005 (UTC)

Another electronics wiki
Another electronics wiki: http://electronicschat.org/echatwiki/ This link dead Aug 22, 2008, if it's still dead in a few months, delete it...

Focus of this book
This is basically turning into a shoddy mirror of various Wikipedia articles. We need to develop a sort of "What the Electronics wikibook is not" to focus people towards writing useful information. I don't see why we can't link to the appropriate wikipedia article for each component/section instead of parroting it here, so the reader can look there for detailed information. Then we can focus on the how to aspects of electronics, which isn't covered in wikipedia and is the point of this book. The book is to teach you basic electrical engineering: how to design and build electronic circuits, not to describe the physics behind them in depth or various bleeding-edge technologies. That's what encyclopedia articles are for. The wikibook should have more how-to, more examples, more teaching, and less barely-related information. - Omegatron 18:43, 4 Jun 2005 (UTC)

 * I agree to some degree but the point of an Electronics is an explanation of how circuits work. For instance, may be this is a once off case, the Op Amps article at wikipedia is nothing short of superb but it does not cover the analysis of Op Amps that an Electronics text book would.  Things like mesh  and nodal analysis, superposition theorem aren't covered either.  Ok Diagnostic Equipment or Measuring Instruments, which incidentally appears to be a mirrored page, should in all likelihood be just be links unless some of the information is more important.  But I think virtually the rest should probably be left because the purpose of this book is more different to an encyclopedia, an encyclopedia what it is.  This text book explains how it is used.  Which now that I've said it appears to be supporting you, but wikipedia is often at a quite a high level.  A level that might be too high for this text book. -IKnowNothing 11:40, 22 Jun 2005 (UTC)

 * I agree. Op-amps are a huge subject, and most of the wikipedia information should be included in this book.  But we need to cover a lot more about them.  I'm talking more about stuff like Electronics/Resistors. ( Not that I think it should be deleted, but we should be focusing on more practical stuff.) - Omegatron

 * That belongs in a Electrical circuits book but is too low level for an Electronics book. So yes it properly shouldn't be deleted. --IKnowNothing 22:04, 22 Jun 2005 (UTC)

 * Now that I've written that. I agree that we need to focus on more how to, more examples. The only problem is that wikipedia, the wikipedia article sometimes have too much information. Is this a digital or analog electronics text book?  --IKnowNothing 11:40, 22 Jun 2005 (UTC)

 * It's an introduction to both. I think we should remove the stubby modules about things like Electronics/ALUs to the talk page until we have finished the basics like Ohm's law.  Let's finish what we have before we start adding all kinds of advanced subjects. - Omegatron 13:36, 22 Jun 2005 (UTC)

 * I agree that we should finish the lower level stuff before carrying on. But what level of completion is required?  75%, 50% and in whose opinion?  Another Question is: does nodal and mesh analysis matter, It is definitely a part of Electrical circuits theory and I could write it after some revision but it is seldom used in Electronics.  More often a less complete more directed analysis is done of electrical circuits. Someone has to assess the development stages.  I also agree that the stubby pages can be removed to the talk pages.--IKnowNothing 22:04, 22 Jun 2005 (UTC)

Separate issue how should the Diagnostic Equipment and Electronics/Measuring Instruments be consolidated. Just a deletion of the less informative one or an integration of the information. --IKnowNothing 22:04, 22 Jun 2005 (UTC)

In order to get a more functional textbook like 'feel' to this. I think a worthwhile addition would be a section containing real functional curciut designs starting at a basic level and moving onto more advanced circuit. For example, the first section could be "A voltage regulator". This would contain a circuit diagram, an etching pattern, an explanation of how and why it works. As well as an explanation of any unusual/ambiguous configurations. --I don't have an account yet (KronicD).

Where to get circuit diagrams
Check here for pictures: commons:Category:Electrical_diagrams. Everything I have ever made (including the common base, etc. diagrams) is up there now, and there are tons of diagrams I didn't make. If you are thinking of a diagram, there is probably one there already.

You can make a link to them and they will be transwikied automatically:

- Omegatron 20:06, 26 Jun 2005 (UTC)

Where to get components for drawing circuit diagrams

You can use components from this image:

It is intended to make drawing of schematics simple, fast and still very flexible, using common vector image editors (as Inkscape).

All components are snapped to 1 mm grid (turn on "node snapping"). Feel free to edit and replace with new version. --Filip Dominec 13:12, 4 February 2007 (UTC)

Merging LearnElectronics
since the aim of both books is the same I'm supposed to merge my book with this one, however as it is hands on and simplistic I don't see how i can merge it with this one. I want the reader to be able to start creating there own electronics very quickly and i only go over basic thoery and equations (Ohm's law and power=volts*current), your book goes over advanced theories and equations that i feel the reader doesn't need to know about when they first start.

does anyone agree with reordering this book so learnelectronics can fit without a lot of advanced talk?

 * V2os has started the book called LearnElectronics (or at least contributed to it). I added a merge tag to the book, because it appeared to have similar aims to that of Electronics. After some discussion, I decided to remove the tag for the time being. But, it would be great if contributes to this book would provide some guidance, so that we can ensure that duplication of material is kept to a minimum. Maybe the addition links between the two books would help. (Donovan|Geocachernemesis|Interact) 05:42, 16 July 2005 (UTC)

I guess we should somehow link both books close together. However I'm not sure if a merge would be the best way. IMHO learn electronics would be aimed at a high school level, while this book is more of a college level book. Perhaps we can get both books to interface with eachother so that learnElectronics would be the beginners introduction to electronics and this book would follow up as a more indepth study? --Patrik 15:38, 21 July 2005 (UTC)

I think the books should be merged. I don't like multiple projects with the same goals. Contribution to the Electronics book is patchy enough already. Also there's Electricity for introductory stuff.

I don't see any reason why we can't format this in a way that people can start building circuits without learning the advanced theory behind it. - Omegatron 16:19, 21 July 2005 (UTC)

Deciding the desired scope of the book I think is the absolute biggest problem we have. On the one hand, some want a book that just tells how to build very simple light bulb and switch circuits with no theory at all. On the other hand, we had a contributor at one point that had an Analog Circuits chapter with subheadings Sound, Brief History of the Universe, The Solar System, Evolution of the Earth's Atmosphere, Earthquakes and natural disasters, and Global Warming.

The Wikipedia doesn't have this problem because it just breaks everything up into individual subjects instead of trying to wrap them up and present them in a teaching order. If you want details, you read other articles that have details. If you want basics, you just read article introductions.

I think the point of this Wikibook should be to focus on the practical "how-to" aspects that Wikipedia doesn't provide, and present the information in order. For theory, just link to Wikipedia articles.

On the other hand, I think it's important to know what the electron fluid is actually doing to be able to design circuits yourself instead of just building from schematics that are provided to you, which is why I was including the concepts of charge in the introductory chapter. I think it's important to think about the charge that flows between two electrostatically charged objects to really understand how it flows in a circuit. We don't need to include any equations for this part at all, but the descriptions I read when I was younger "dumbed it down" so much that I really didn't understand what was actually going on. I always tried to think of circuits in terms of electron flow instead of conventional current because "that's what's actually flowing!" It hampered my understanding a lot. (I see people do this online sometimes and it annoys me.)

I'm sure there's a way to present simple circuits that people can build without actually reading the text, while still providing useful information for people who want to read it, and defer all the advanced theory to the Wikipedia articles. - Omegatron 19:30, 21 July 2005 (UTC)

You could seperate each section so that the basic information needed for understanding is at the top under a "basic information for understanding" heading and then another heading saying "advanced understanding" after that --V2os 21:50, 1 August 2005 (UTC)

This is all talk and no action, getting really annoying.--V2os 17:01, 4 August 2005 (UTC)

 * Yeah, wikibooks is really slow. :-\ - Omegatron 03:13, 5 August 2005 (UTC)

 * I'm getting tired of trying to maintain the LearnElectronics wikibook as no one will post one experiment and it's getting to be a bunch of stuff that should be on wikipedia instead, with no instructions on how to make circuitry, do i have permission to "reorganize" this book until it can be used by high school level readers? order of a chapter would be "basic understanding" "hands on stuff" and "advanced understanding" seriously i'm considering putting LearnElectronics up for deletion or merging to this book. --V2os 22:23, 20 August 2005 (UTC)

 * If you think that will get the book back on track, be bold, you don't need to get permission. As Omegatron said, Wikibooks are really slow. You shouldn't be afraid of jumping in and getting your hands dirty, because explaining electronics to others is a good way of showing that you understand it yourself. Geo.T 03:31, 21 August 2005 (UTC)

 * I agree that this book could stand a serious reorganization, but I am worried about what you mean by "used by high school level readers." I would say that the book in it's current form is a bit heavy on the theory (most of the "charge and coulombs law" chapter for instance) but some theory would be very helpful.  I may have been a bit slow at the mathematics, but I did not understand much calculus in high school, but I would definately question the usefulness of this book if it didn't include basic equations to model capacitors, inductors, et cetera.  I think a good idea would be to divide each section into two parts, one which introduces the basic theory about the chapter, and another which explains some more hands-on material.  For example, when talking about capacitors, the theory section could give a quick rundown on how they work, and the equations that can be used to model them, whereas the hands-on section would have something like "here is an interesting circuit which helps you to understand how they work."  Another problem which I see with the current incarnation of the book is that people tend to ignore the prerequisites.  For example, the term "vector" is explained a number of times in this book, and often not very clearly.  However, in the prerequisites, it says that the book assumes an understanding of algebra, calculus, and geometry.  This book should not explain what a vector is, it should simply assume the knowledge, and provide a link for people who don't know or need a refresher.  It would be much more efficient if there was one place where people focused their efforts on explaining mathematics, and another place for electronics.  Not only does mixing them clutter up the electronics book, but it also does not provide as good of an explanation as a math section would.  Not to argue against myself, but a short appendix with some basic mathematical formulae mae be handy, but I would argue to leave the serious teaching of mathematics to another place.  Furthermore, I think that if the book is well written, it could be understood by someone who doesn't understand or doesn't care about the calculus involved, while still satisfying the curiosities of the more mathematically inclined.  It is just a matter of being clear on which sections are absolutely necessary, and which are the more "advanced" topics.  Sorry for the rant, but I think this book needs a clear direction.  I like the idea of having more hands-on material quite a bit, but I would argue against removing the theory.

What are the goals of this book (hands on experiments, mathematical theory, circuit analysis . . .)?

What math does the book assume of its reader (highschool math, calc, linear algebra, diff eq)?

What other knowledge does the book assume (basic physics . . .)?

What should the structure of the book be, in what order are things presented, and how can theory and application be kept separate, but still be meaningful and useful on their own?

(wow, sorry for the huge rant, but I have been going through this book and reading, sometimes tweaking, for a while now, and I have been thinking about a lot of places where I beleive it falls short. Hopefully I will have some more time to help out jim 02:00 (UTC) 23 Aug 2005)

 * I'm not going to read that entire thing right now, but now i've seen an electronics book, it starts with defining a battery in 2 sentences and putting some pictures of them up, then it does the same thing with resistors, capacitors, inductors, etc.. and multimeter + power supply +signal generator (ocilloscope too but that would be too expensive for beginners) just a few sentances and pictures of parts for the first section of the first chapter. THIS wikibook gives the reader equations for electrostatic charge (no one needs that for learning electronics and wether it should be in the book is questionable.) You may want to delete the first few chapters to the entire book. --V2os 23:24, 26 August 2005 (UTC)

Currently, there are many wikibook "modules" in the "Electronic:" namespace. I agree with Omegatron that they are really outside the scope of an electronics book. But instead of deleting them, is there some other book (or even Wikipedia article) that we could move them to? --DavidCary 06:30, 10 November 2005 (UTC)

 * Electronics/Atmosphere
 * Electronics/Fuel Cell

EE bookshelf
I've recently started work on a number of books at the electrical engineering bookshelf. While many of these books will touch on the same topics as are covered in the Electronics book, i think that the EE books will have a much more limited scope, and a more well-defined target audience. In particular, These books so far are trying to be very "mathematically light", in contrast to some of the pages in this book which can be very equation-dense. Also, I am trying to lay out an entire EE "curriculum" of sorts, in the form of a natural progression of wikibooks that would follow an undergraduate curriculum in EE. I am not really interested in having all the books merged, because a gigantic, hold-all, monolithic book really defeats the purpose of having "bookshelves" at all. Let me know what everybody here thinks. --Whiteknight 22:31, 17 October 2005 (UTC)

A-to-D and D-to-A
The section "Encoding and Decoding" links to a discussion of A-to-D and D-to-A converters. Somebody also added a section title on the main page that is similar. This duplication needs to be resolved.

Orphaned pages
There is a lot of orphaned pages connected to this book:. Merge them here or mark with delete template. --Derbeth talk 13:59, 11 January 2006 (UTC)

 * As an update to this, I've gone through a few of these and marked those that are obvious forks of other material, but there are several pages which I couldn't find already as part of the book, and these need to either be linked or merged with the rest of the book (or deleted if it's a fork I missed). Those with (M) before the name should probably be merged into another page:
 * Electronics/Electric Field
 * Electronics/Frequency Spectrum
 * (M)Electronics/KCL
 * (M)Electronics/KVL
 * (M)Electronics/Mutual Inductance
 * Electronics/Power Conversion
 * Electronics/RCL time domain
 * (M)Electronics/Resonance
 * (M)Electronics/Spin
 * (M)Electronics/Superconductors

 * In addition, there's these two pages which I'm not sure at all what to do with:
 * Electronics/Urban Legends
 * Electronics/Humor

 * Xerol Oplan 22:16, 29 March 2006 (UTC)

 * Three more:
 * Electronics/Conventional Current
 * Electronics/Table of Chemicals
 * Electronics/Charge
 * --hagindaz 01:12, 28 July 2006 (UTC)

Another posibility for the scope of this book.
In my opinion, Wikibooks needs separate books on the following:

 * Basic Electronics (to GCSE/16 year old level), so Ohm's Law, etc.
 * Advanced Electronics or Theoretical Electronics, which takes there reader from the end of Basic Electronics to an advanced level, detailing all the theory needed the understand it (or we have Electronics (quite detailed) and "Advanced Electronics" (very detailed), which I think would be clumsy). This would be quite equation heavy, but could have lighter "in brief" pages, perhaps.
 * History of Electronics, from rubbing amber with a cloth to computers. This could also include how electronics products are made (might need a different name).
 * Practical Electronics, which is how to make circuit work, which IC to use for what, how to solder and lay out a PCB, etc.
 * Electronics Data, containing useful tables and the like applicabe to all the above. Perhaps also a dictionary of electronics and an index for all the above. Maybe "Electronics" could be like an electronics bookshelf, pointing the way to all the above books.

 * Although it looks like Electric Circuits does this already

 * Inductiveload 09:22, 15 September 2006 (UTC)

This way, every reader has access to material that they can understand and use. Otherwise we risk losing usefulness for one end of the spectrum or the other.

Along with specialised books like Semiconductors, Electromagnetics, etc, this should give a broad AND in-depth electronics resource.

 * That sounds great. I agree that there's no need to put everything electronic in one big book -- separate books on the above topics is a good idea.
 * And Subject: Electrical engineering/Descriptions (formerly Electric Circuits ) looks like a nice overview of all the books we have so far on the subject.
 * On the other hand, when I read through the roughly 30 books in Subject: Electrical engineering and the roughly 25 books in its sub-Subject Subject:Computer engineering (some books are in both lists), I suspect that many of those books should be merged together, since the topics and the audience heavily overlap. --DavidCary (discuss • contribs) 02:15, 8 September 2011 (UTC)

Merging Electric Motors
I am against this merge, becasue motors have very little to do with Electronics - they are Electrical devcies. I know it is a small distinction, but it it like computers vs. hoovers. If motors have to be merged with anything (which I oppose, as motors is a very broad subject and can be expanded to a large size anyway - think of all the different types and what would happen if we made a REALLY thoughough examination of how they work from the most physical level) it should be Electromagnetics.

Motor Controller Circuits on the other hand belong either here or in Practical Electronics. Inductiveload 09:14, 15 September 2006 (UTC) (forgot to log in the first time)

Iam also against the idea of merging Electrical machines with Electronics.. Let us have these topics under a hierarchial tree. As there are so many topics in electrical engg, let us have a detailed descibtion about these topics. --Wascool

I am neither in favour of merging the two nor in support of merging the two but i would like to point out that all electronics engineers are required to have some basic idea of electric machines because they are the final objects which are controlled. It might seem a bit redundant to many whose primary objectives are vlsi or chip oriented. But the point remained that wikibooks are supposed to help students and all electronic engineering students need to study electrical machines so it wouldnt be of much harm if the topic is merged those who dont want to read can skip it.

No Merging
Electronics is the study of flow of electrons in some material. Please don't merge it with Electrical Machines.

Conclusion of knowledge
What do we know ? So it looks like motors do have characteristics of electronic parts and should also be treated as.
 * Motors - and however any electromechanical device - can be driven and controlled by electronic circuits.
 * Motors can be used to cool down electronic circuits.
 * Motors can contain electronic circuits.
 * Motors can be a part of electronic circuits.
 * Motors do work trough electromagnetic fields. There are electrical fields and flows of electrons causing magnetic fields which are creating the * rotation effect and so on.
 * Electronic parts can be influenced by electromagnetic fields. A motor in fact can be used to erase the contents of a electronic memory ...
 * Electron flows through Motors are influenced and affected by the inductivity and other things like the rotation speed, the rotation strength and more.
 * Electronic circuits can have influences to motors and vice versa.

'''In fact a electronic circuit is nothing else than e small electrical machine. It is something that has a physical effect by applying a electrical current through it.'''

New design of the main page?
What about copying the design from the-same-but-czech project at ? --Filip Dominec 17:33, 29 January 2007 (UTC) As an electrical engineering graduate and electronics engineering postgraduate with a combined proffessional experience of almost 30 years, I am against this merger, and would suggest a separate line of books on electrical power engineering covering topics such as, electromagnetics, DC machines (generators and motors), AC machines (synchronous and asysnchronous), three phase circuits and machines, transformers, real / reactive power, electrical power generation/ transmission/ distribution, cables, lighting, circuit breakers and ohter switchgear, power electronics/rectifier/invertor/ VFVV drives and much more

Electronics/transistor|chapter 4
Trasistor appears the same in both chapters, chapter 4 and elements of Digital Circuits. I suggest removing the Chapter 4.--Sommacal Alfonso (talk) 18:18, 26 March 2008 (UTC)

Batteries and Cells
There are both Electronics/Batteries and Electronics/Cells. There is a link fron this page to the cells but not to the batteries but the batteries page seems more complete. What is the system of organisation here? Storeye (talk) 08:15, 26 June 2008 (UTC)

LTSpice screens
I asked the people on commons about using screenshots from LTSpice, but they didn't have too much knowledge of the subject.

What are the rules here? If I cannot submit a screen from LTSpice, what am I to do? I could export the plot data, and use GNU plot, but that feels more like a workaround than the ethical solution. <IP_ADDRESS> (talk) 04:42, 15 December 2008 (UTC)

 * Wouldn't Linear be the right party to ask? They own LTSpice, and if they allow you to put screenshots from LTspice  showing your own circuits under the GNU Free Documentation License wouldn't that be ok? An alternative would be to use free software like gEDA's gscheme together with ngspice. However that isn't a very convenient solution.

Chapter One name?
I noticed the heading for chapter one was missing from the ToC and put it back:

Does anyone remember the name of the chapter?

-- hypergeek14 (talk) 21:41, 14 May 2009 (UTC)

 * As you can see in this old revision, the title was "DC Circuits". I've added that back in. -- Adrignola talk contribs 22:24, 14 May 2009 (UTC)

Chapter 2, Section four: Name Change
What do you all think of changing the Steady State section of chapter two to Phasor Analysis? I think it would be great to have a section dedicated to phasor analysis after the audience has reviewed the phasors and impedence chapters. Eng20 (talk) 23:25, 16 December 2010 (UTC)

Lesson 1.7 Needs Simplification
I feel that the inductance formulas are largely unnecessary for lesson 1.7. It's starting to look less beginner-friendly to introductory students in EE. Jimli536 (discuss • contribs) 16:34, 16 October 2016 (UTC)

title: Talk:Electronics