text:
Talk:Electronics/Archive01

'''DO NOT EDIT OR POST REPLIES TO THIS PAGE. THIS PAGE IS AN ARCHIVE.'''

This archive page covers approximately the dates between March 2004 and early June 2005.

Post replies to the main talk page, copying the section you are replying to if necessary. (See How to archive a talk page.)

Please add new archivals to Talk:Electronics/Archive02. Thank you. Omegatron 16:47, 21 July 2005 (UTC)

Archive
This Talk page Module was too long and so I split it into 2 pages. The first half remains here. The second half was moved to Talk Electronics 2. I you don't like what I did, you can re-unite them, but then you get a page which is excessively long again. I don't suggest re-uniting them until it is decided what to delete. H Padleckas 23:25, 13 Jul 2004 (UTC)

 * Let's combine them back together and create an archive for the old discussions, as is normally done on big talk pages on wikipedia. - Omegatron 19:09, 10 Jun 2005 (UTC)

 * Should this be on two separate pages? That seems strange to me.  Maybe just archive the old discussions or combine them all on this page. - Omegatron 18:17, 4 Jun 2005 (UTC)

Delete "talk" sections that no one has commented on in over 6 months old -- move signed comments them to the user's talk page, delete anonymous comments outright. OK ? --DavidCary 07:00, 10 Jun 2005 (UTC)

 * Just archive them normally. - Omegatron 19:07, 10 Jun 2005 (UTC)

Foreword
Couldn't the three foreword sections be combined into one "article"? - Omegatron 15:56, 22 Oct 2004 (UTC)

 * I agree. These three sections are very short - might as well combine them into one "Forward" module.  H Padleckas 19:37, 27 Jan 2005 (UTC)

Contributing
Hi, since you're a DSP engineer, perhaps you would be interested in helping out with the Electronics wiki-textbook. http://wikibooks.org/wiki/Electronics

 * Yes, I would love to. How do I start?  I am not too familiar with Wikibooks - Omegatron 20:48, Mar 19, 2004 (UTC)

A starter would be grabbing some articles from wikipedia and modifying them to be an educational text. I already started a basic lesson on RC circuits so far. The aim of this text is to educate someone with no previous experience in electronics to a one or two year level.

As for editing, wikibooks are almost exactly the same as editing wikipedia articles. The only difference is the structure of the books and their modules, but most of the required chapters and topics are set up. If you have any more things that you think should be covered, by all means add them to the main page of the textbook, then we can begin fleshing out the details. oh, and by the way, do you have a template you use for your electronics diagrams? It would be good if we could have a template, which we could use to standardize all our circuit diagrams. - Anonymous Contributer, 22:58, Mar 19, 2004 (GMT)

 * I don't have a template for them. Here is a short description and some examples: Wikipedia:user:Omegatron

 * I have been using Arial size 10 (and then size 9 dropped down 3 pixels for the subscripts), but that could be made prettier. There is no template for how the labels are arranged, etc. but there could be.  I often edit the diagrams from Klunky so that they are more compact and easy to read.  Do you have any suggestions for them?  I would love some feedback.

 * Just try to remember what it was like when you first learned electronics and what you had trouble with. I tried to teach myself electronics several times when I was in elementary/high school, and never had much luck until college.  I will try to write this like the book I wish I had at the time.  Some misconceptions I had:

(see below.)

 * just a few. :-)  what are the differences to wikipedia?  obviously you don't make links to other encyclopedia articles.  do you include external links or is it meant to be like a printable standalone book? - Omegatron 15:56, 21 Mar 2004 (UTC)

 * You can include links to other book pages. For the most part, the wikibooks project is the exact same format as the wikipedia with only minor changes. For instance, all the electronics articles are written with names of Electronics/Pie for instance. Make sure you do that, because if we just used standard words, there could be crossing over of a topic. Besides that, add articles and edit mine without mercy! - Alex S 18:00, 21 Mar 2004 (UTC)

Table of Contents
Do you want to add a table of contents to each page, as in:

http://wikibooks.org/wiki/Wikibooks:Manual_of_Style#Tables_of_Contents

It should at least have a back button at the bottom of each page or something.

>>I think that the current TOC for each page works good enough. I don't think there's a need for another TOC on the title page, that can be seen in one screen-viewing...

Who is working on this book? It looks like it is just Alex. - Omegatron 19:02, 22 Mar 2004 (UTC)

I'm sure some people from wikipedia would be interested. We just need to messag e them to get their attention.

 * Umm .. well, I went ahead and made a TOC for the book. To link into it just include this code at the top of each page: I did so on a couple of pages but did not go though each page to add the code. --Karl Wick

TOC
Hmm... I started adding TOC to each page, and realized that the pages already have titles at the top.

 * 1) Do we want redundant titles? As in Electronics/Diodes
 * 2) Is there a way to make TOC default on each page like the titles?

 * I don't get the point of the TOC. At the bottom and top of the pages. Why do we need those if any browser you use has a back button? If someone is reading about diodes, will they want to click up on the TOC and go read up on the section about static electricity? - Alex S

 * Having to use the back button is sometimes annoying. Some browsers don't go to the same place in the page when you press back, requiring you to scroll down to wherever you were to go to the next section.  Back-->Scroll/Find-->Click, just to go to the next section.  But yeah, I thought the TOC would have a link to each section, and maybe back and forward buttons (is that possible?), so you can just click on the next section in one click, which is conveniently located at the bottom of the page, which is where you are after reading that section.  This example is more what I was thinking:

 * Basic Concepts ? 1 - 2 - 3
 * DC Electronics ? 1 - 2 - 3
 * Chapter 3 ? 1 - 2 - 3

or

 * Basic Concepts ? Electrons - Static Electricity - Voltage and Current
 * DC Electronics ? Chap2Page1 - Chap2Page2 - Chap2Page3
 * Chapter 3 ? Chap3Page1 - Chap3Page2 - Chap3Page3

though this could get messy

- Omegatron

 * I say keep it simple for now. Those current TOCs dont really serve a purpose, and the most useful thing to have would be a 'next chapter' or 'previous chapter' button. But that isn't very feasable at the moment as we're just starting up the book. Should we remove the redundant TOCs?

- Alex S

 * The way they are now is basically useless, but a little better than just using the back button. I vote for a table like I included above.  Maybe we can make it even smaller, but it would serve kind of like next and previous section buttons.  who is the developer of wikibooks?  Maybe we can make forward and back buttons?  we can definitely just add them in by hand.  but automated would be better. - Omegatron

Also when you arrive at a page through another page through another page that you edited, etc etc and you want to go back to the electronics TOC, there is no easy way to get to it. - Omegatron 18:44, 29 Mar 2004 (UTC)

 * I far prefer page names that describe what the page is about. If I want to read about electrons,

 * Basic Concepts ? Electrons - Static Electricity - Voltage and Current
 * tells me right where to click.
 * Links like

 * Chapter 3 ? Chap3Page1 - Chap3Page2 - Chap3Page3
 * are, in my opinion, useless.
 * --DavidCary 18:14, 3 Jun 2005 (UTC)

 * I agree. Did someone add links like that? - Omegatron 18:17, 4 Jun 2005 (UTC)

Unfortunately, yes. Several other books have this unfortunate style. For example,
 * Electronics/History/Chapter 1
 * Electronics/History/Chapter 5
 * Geometry: Chapter 1: Section 1
 * Geometry: Chapter 6
 * Computer Science:Algorithms:Chapter 6
 * SA NC Doing Investigations:Chapter 10
 * European History:Chapter 2
 * Home Remedies/Chapter 2
 * Japanese History/Chapter 9

Is there a better place than "Talk:Electronics" for discussing how to name chapters in a wikibook ? -- --DavidCary 07:00, 10 Jun 2005 (UTC)

 * You mean Staff lounge? - Omegatron 19:07, 10 Jun 2005 (UTC)

''Do we want redundant titles? As in Electronics/Diodes?''

I don't know. I think it might be nifty if we eliminated some redundancy and had everyone focus on polishing one really, really good explanation of capacitors and inductors at capacitors and inductors. That one explanation would somehow be "included" in both the electronics textbook and the physics textbook. On the other hand, having independent pages in the electronics textbook and the physics textbook might let us focus on just the properties relevant to the particular subject we are studying. (In particular, when designing electronic circuits, we just care about the electrical properties at the terminals, the "imaginary impedance" stuff. If we want to learn details about how they work, how to make and modify them, then we need to learn the physics underlying them -- the electric field, the magnetic field, etc.) But I certainly don't think we need 5 different pages on capacitors:
 * Electronics/Capacitors,
 * Electronics/Capacitor Construction,
 * FHSST Physics Electronics:capacitive and inductive circuits,
 * Modern_Physics:Electromagnetism:Contents,
 * capacitor

--DavidCary 07:00, 10 Jun 2005 (UTC)

Scope of Book
This is the second part of the Electronics book. It deals with topics that are related to Electronics but don't quite fit into an Electronics book. As this is the second part editors can stop showing restraint towards math. Long live Greek.

Cyberman: I would help on this wikibook except all of you have made it too physics intense. There isn't a basic setting. Right away people are thrown into physics.. jeeze people. This isn't a physics book, it should be an introduction into electronics, and then once you establish the basis of introduction, you can start laying on formulas and equations. I understand that physics is the hardcore study of electronics, but I think it should be more of a basic introduction, not intense.

A lot of the physics is covered in the physics textbooks.. Eh, I don't really know.

''It is true that these subjects are covered elsewhere, but this part of the book talks about them in terms of Electricity and Magnetism. A good example is Optics. Normally when people talk about Optics they talk about visible light. My question is how optics works throughout the entire electromagnetic spectrum. For instance at higher frequencies light will destroy mirrors rather than being reflected by it.''

See, I was hoping to make more of a practical book about electronics and about the subject. Now it seems this book has become practically everything but? Hoped to cover things like design and understanding of electrical circuits and systems, etc. Your thoughts?

<Narrow the focus. There's a proposed physics with calculus that can cover the wider shores of EM. For this book, just stick to circuits; without much maths in the first half, with maths in the expanded section: resistance, capacitance, inductance, batteries and electrolysis, generators and motors, and semiconductors. Don't explain how semiconductors work, or details about magnetism; stick to what's need for studying circuits. Possibly a final chapter saying, without maths, 'This is how circuits fit into EM and beyond. Now go and read these other books'>

I agree with person. If we concentrate more on the field of ELECTRONICS and less on the field of ELECTRICITY, we should fare well with a good textbook. If a reader can design a radio transmitter or digital circuit by the end of the book, we can give our selves a pat on the back. However, learning how electron spin and the function of n-doped semiconductor materials only gets you so far.

This book seems to be getting a lot of information added to it that is really not too relevant to electronics. Table of chemicals, extensive frequency spectrum, history. If you want to change the name of the book to an Electromagnetics book or Physics of Electricity book, that is fine, but it seems there is too much information here for anyone to complete it in a reasonable amount of time and learn anything useful about practical electronic circuits in the process. I think they should know a little about the physics of charge, voltage, current first, so they have a foundation to understand what they are actually manipulating, and then learn how to apply them with the various components available and build circuits, then you can go into radio a bit, and in the process explain some electromagnetics, but leave the heavy electromagnetics and physics and chemistry for another book. The good thing about Wikipedia is that you can link to something without going in depth about it, and people who are interested can read, and people who are not interested don't have to. Let's not overburden the book with irrelevant information. Let's just link to it, and stick to the topic. Interested readers can find it themselves. Frankly, it is overwhelming, and I find it hard to help editing. - Omegatron 13:40, 19 Apr 2004 (UTC)

This is getting ridiculous
Sound, Brief History of the Universe, The Solar System, Evolution of the Earth's Atmosphere, Earthquakes and natural disasters, and Global Warming?

As sections in the chapter Analog Circuits?

Stick to the topic, please!

Saying "the earth behaves like a conductor", "the ionosphere behaves like a conductor and can reflect radio waves" is plenty. There is no need at allllll to go into the details like this. That should be in a radio book anyway, not a basic electronics book. This is supposed to be a book about electronic circuits for beginners, not about life, the universe, and everything.

- Omegatron 21:09, 20 Apr 2004 (UTC)

Ok, I will admit that my writing does suffer a bit from feature creep. I like to be through, and there are certain subjects that are not taught in school. I have moved the offending sections to the Expanded Edition. If you see anything else that seems excessive I will move it to the Expanded Edition.

Wanderer

Good compromise. I just don't see a point of including all kinds of unrelated information when you can just link to Wikipedia articles on each topic. - Omegatron 14:12, 22 Apr 2004 (UTC)

 * I disagree. Expanded edition is bad idea. We should put all thing in FULL edition. That's what books are.

Not true. Books 'don't' try to cover everything in one go, because people can't. Everything includes stuff for people 12 or younger, and the full rigors of QED. No twelve year old can possibly open a book, knowing nothing, and learn QED in a few weeks. Nor will anyone studying QED want to begin by reading about static electricity. They already know that.

Textbooks are aimed at specific targets, 12-16,16-18, undergraduate, etc, which lets them make good assumptions about what the reader already know, and they only cover a limited range of topics, enough to help the reader onto the next stage.

We should do likewise.

This book can, as Wanderer said, cover Electronics with light maths, say 16-18, and the expanded edition cover topics just beyond that scope, including the full maths.

Similarly the expanded edition will also be of limited scope, stopping short of QED. A full account of that topic belongs in a quite different book, for people who've already read Quantum Mechanics and Undergraduate Calculus, among other prerequisites. Carandol

Road map
Anyway, does anyone else agree that this should have a charge and basic electron section? I don't want to go into crazy physics or anything, but we should teach about charge, electrons, holes, potentials, charge flow, etc. so that people understand what it is we are manipulating, what is being stored in a capacitor, etc. This was my original road map from the Talk:Electronics/Aim page:

 * Electricity
 * Charge
 * Voltage
 * Current
 * Resistance
 * Ideal circuits & real circuits (and a description of the difference between schematics that just show wiring between real components, and schematics which show the ideal functioning of components)
 * Ideal voltage and current sources
 * Ideal nodes and meshes
 * Capacitors
 * Inductors
 * Introduce magnetism here or in the electricity section?
 * Transformers
 * Controlled voltage and current sources
 * Other types of components

...

How does this compare with what other people are thinking? I see the charge section got removed to the expanded edition... - Omegatron 01:26, 1 Jun 2004 (UTC)

I definitely agree on this. Perhaps a section called 'Basic Electricity Concepts' or something similar could cover charge, current, and voltage. This section could be VERY basic however. One thing that should be stressed is that current is not just a magnitude, but also a direction (similar idea for voltage too!). I think that list should also contain 'Fundamental Laws' - Ohm, KVL, KCL. - maxpower 17:07, 1 Jun 2004 (UTC)

Alright, so how are we going to do this? Having to cover the laws and all. I suggest we have two sections. One explaining the physics nature of charge and electron flow, then another explaining ohm's law, KVL, KCL. Then for more complex things, such as multiple current sources and capacitors and inductors, another chapter? or we will explain the behavior of the components in their own chapters?

 * For more complex things, there are a lot of different techniques/things to know. Nodal/Mesh analysis work well for circuits with multiple voltage/current sources.  The Inductors/Capacitors sections should also include DC transient analysis.  (Well, this is math heavy, and I don't know if it's really essential for the hobbyist.  Perhaps in the 'expanded' edition.  Simple RC and RL circuits may be enough...probably don't need to consider multiple sequential transients in a single circuit.)  If transients don't get covered, then inductors/capacitors are only useful in the 'AC circuits' chapter.  If this is the case, they should be moved here.

 * Regardless, we could introduce Ls and Cs in one chapter, talk about their transient behaviour elsewhere, resonance in the RLC circuits section, and impedance in the AC chapter. This may make more sense, because no one really wants to know 'everything about capacitors'; they want to know how to use them in a specific context. - maxpower 21:41, 1 Jun 2004 (UTC)

 * Good ideas. We talked about this in the depth of mathematics section, too. - Omegatron 01:01, 2 Jun 2004 (UTC)

 * Rereading the depth of mathematics section gave me a chance to look at the electron device modelling book. I suspected that simple models for diodes would be covered there, and they are, but in a very superficial way.  If the coverage there was more comprehensive, we could just link there...but it isn't.  The ideal diode concept and ID model, Constant Voltage Drop model, and Piecewise Linear model should be covered in our diode section.

 * In general, the Electronics sections on diodes and MOSFETs are lacking. The kind of qualitative information given in these sections, while useful in understanding, gives no basis for circuit analysis.  While diode and FET models do, of course, contain MORE MATH, there's really no point in covering these topics without attaching some useful info.  None the less, understanding how these devices work on an electron scale is totally unnecessary.  Models useful for circuit analysis should suffice.  Another useful area to delve into would be CMOS logic.  Virtually no math (except boolean algebra), makes MOSFETs useful.  - maxpower 16:51, 2 Jun 2004 (UTC)

 * Yes, we should cover all of those models. There are a few people who are paranoid of math, it seems, and we can certainly explain how things work without it.  But really, that isn't useful for anything.  You can't do anything with your knowledge without knowing the math.  We should try to present the math as accessibly as possible, though.  Presenting transistors as simple switches first and then as "amplifiers" might be a good idea...  As I have mentioned before, I don't like the term amplifier, because a transistor is not an amplifier by itself.  The circuit it is built into is the amplifier.  The transistor is just an electronically controlled valve. - Omegatron

 * Ok. Now here is another question: do people prefer lots of chapters, or few? I personally would rather have full, worthwhile chapters than many small ones. How about this:

- Basic Electricity Concepts (charge, attraction) - Basic DC Electronics (KVL, KCL, Ohm's law) - Resistors - Capacitors - Inductors

rest falls into AC and analog electronics. Perhaps we merge these sections??

 * I agree with concepts, and fundamental laws, but the rest of the merging goes too far. Full worthwhile chapters are great, but this arrangement is not helpful in learning the material.  As I said earlier, no one wants to know everything about capacitors.  They are useful in many contexts, and should be covered in each context, rather than grouping all capacitor information together.

 * Ohm's law needed to go into the fundamental laws section, but circuit components is not a logical part of the fundamental laws section. Also, covering components before laws makes more sense to me. This is a case where I feel that starting small and building up (rather than top-down) really works.

 * BTW, "the rest" does not fall into AC and analog electronics. There are several worthwhile topics that aren't covered in the scheme above: transients, nodal/mesh, Thevenin/Norton. If less chapters does in fact equals better (intentional), nodal/mesh can become one chapter. - maxpower 00:23, 3 Jun 2004 (UTC)

Depth of mathematics
"Dear people editing this book, while math is useful and does have its place in an electronics textbook, it makes it very hard for people to understand electronics."

 * Understood. On the other hand, I had huge amounts of trouble understanding electronics until I got the math background.  When I used to read books on the subject I would skip any equations as being too hard, and hence didn't get a very good understanding of it.  It is almost a form of applied mathematics in several ways.  We should try to make it very intuitive how things work, without needing the math background, but we should also provide the math (in the simplest forms possible), because it really is necessary. - Omegatron 14:30, 26 Mar 2004 (UTC)

 * I don't have problems with math, I enjoy it. However, when people write pages upon pages of equations that have little to no explanation, it turns the electronics textbook from a learning book into a formula table. The rule of thumb for most math related textbooks: 1 equation -> 100 words explaining it. - Alex S 14:30, 26 Mar 2004 (UTC)

 * Certainly. I was intimidated by lots of math, especially when it involved calculus, which I hadn't learned yet (how are we going to handle this?) and skipped over parts in books that had heavy math, my loss.  I mostly learned from a book I still have, by Forrest Mims or something like that.  I will read over it and highlight the parts that led me in the wrong direction. - Omegatron 21:38, 26 Mar 2004 (UTC)

 * I wrote the part on RCL circuits. This contains a lot of math.  I agree that more explanation is required.  And this is still a work in progress.  Can you explain this topic without the math?  You can do it in the frequency domain with Laplace transforms, but its still not that simple.  You can ignore the zero in the pole/zero diagram and deduce a similar, however wrong equation. It often annoys me when textbooks skip lots of steps in the derivation of their equation or make assumptions without explicitly saying so.  So I have tried to include all the steps, which makes the math appear more complex. Would a compromise be to include both simplified and full explanation?  Peterblockley 00:05, 27 Mar 2004 (UTC)

 * And what are laplace transform pairs? - Alex S 14:30, 26 Mar 2004 (UTC)

 * Laplace transforms are used to calculate a transient response from the frequency response. Peterblockley 00:05, 27 Mar 2004 (UTC)

 * Yeah that definitely needs to be included. However, I can't remember Laplace transforms at all.  I think I do everything with Fourier transforms now.  Am I thinking about this correctly?  That Fourier can replace Laplace? If so, which should we cover?  I guess the aim of the book should be clarified.  Do we want to teach something that a 10 year old could understand, without really giving them the tools to build or do anything themselves?  Or do we want to teach them as if they were taking a college class?  Should we try to be all things to all people?  (Basic ideas and water pipe analogies at the beginning of a section with calculus and transforms at the end?)  It says in the intro that it should teach the first two years of electronics, but starting with what knowledge? Should we even assume that the reader can understand algebra?

 * On an unrelated note, I think I will start stubifying sections, so that people feel compelled to add more, without being daunted by starting a new section. - Omegatron 01:32, 27 Mar 2004 (UTC)

 * Laplace transforms are a transform to the S-domain which you may be familiar with from pole-zero diagrams in filter analysis. Fourier transforms are a transform to the frequency domain.  They are similar, but i wouldnt say one replaces the other.  For filter design laplace transforms are best.

 * I have updated the format of the RCL circuit Electronics/RCL_time_domain_simple. what do people think?  Is this simple enough? Peterblockley 03:22, 27 Mar 2004 (UTC)

 * To be honest, I have only a basic understanding of calculus (basic derivative calculus) and have little to no idea about those equations. Peter, you might want to kick it down a notch mathematics wise, and add some more explanations to the articles to help people understand. And Omegatron, I think if we made this book start from 0 knowledge and work your way up it would be good. Assuming people have basic algebra knowledge. Maybe we should even have a prerequisite page directing them to other math wikibooks? -Alex S

 * Hmm... I do remember that I used to do Laplace transforms, of course, and I remember pole-zero plots and root-locus diagrams, but I always found them confusing and nonintuitive. bode plots and frequency responses make more sense to me, and were just as easy to use.  Can you give an example of a filter design that is easier in laplace domain?

 * I looked at the simple RCL circuit. I understand now why alex is concerned.  We should start each section with a few sentences that explain the situation in a way that even a child with 4th grade math could understand, and then work our way up from there.  even if "working our way up" means we need to jump right into calculus, that's ok, as long as we have given the reader a basic idea of how charge and charge pressures are flowing. - Omegatron

 * I'm sorry I've to make a comment about the RCL analysis. How is it possible to analyse a RCL circuits without differential equations or in the Laplace or Fourier Domain?  The other choice would be only focussing on steady state but it also comes with the problem of complex maths or at least some maths that might seem a bit strange to someone with any mathematical knowledge.IknowNothing

"In reading A Brief History of Time by Steven Hawking he said (and I paraphrase) that his editor told him that for each formula that he included in his book the readership would drop by one half. As a result the only formula he included was the one Einstein is famous for.  I would suggest you keep that in mind as you add math equations.  Decide if the equation you are adding really adds enough value to the work to justify the loss of half the readers being able to comprehend the passage.  Not saying to leave them out, but don't add them for their own sake."

 * I'm sorry, but electronics is a very math-heavy subject. We will try our best to explain the way things work without math, but most of these equations are completely necessary, unless we want to rename the book "electronics for kids" and not really explain any of it. - Omegatron

Circuit template

 * 1) Circuit-Creation Template

moving this here, since it seems to be more for editors than readers. i recommend klunky for drawing schematics anyway, as i have said before. - Omegatron 01:36, 27 Mar 2004 (UTC)

Quantum physics, Quantum Mechanics
I've noticed a lot of references to QM and QP in many articles. For some people it is a more clear system of understanding things. That being said, it also can be irrelevant at times. Sometimes it is a good way to show off how smart you are (I don't mean this in a negative way, however I see this more and more often). What are your thoughts about this?

In order to really understand electronics you need to understand E&M and some parts of Quantum (Spin, electrons, photons, and some random other stuff). Spin is responsible for magnetism, electrons are orbitals, and photons are carrier particles for E&M. This is not to say that we need to teach all the math involved. The main reason things seem irrelevant at times is that they are not well enough explained to show their relevance. Overall electronics is a much bigger field than most people realize, with lots of far ranging implications. Afterall E&M is one of the four fundamental forces in the universe. So what do radio waves have to do with ether?

A Crossroads
Ok. We seem to have run into a crossroads here. We have people pushing for a book more oriented on information about almost everything and how it works, and other people pushing for a book on electronics design with heavy calculus. What are your thoughts? Personally I would want a book that gives useful information about how to design electronics, explaining LAWS and THEOREMS. I mean, learning how the atmosphere works is good -

If I wanted to be a meteorologist.

 * Exactly. - Omegatron

So you really want something that looks like this?

 * Yes. Something that focuses entirely on electronics; not on all related disciplines, with a certain amount of detail.  Electron Device Modelling could list the Electronics book as a prerequisite, for instance, for people who want to know in-depth semiconductor info.  The electronics book won't have that much detail about semiconductors.  A book on electroacoustics or bioacoustics or electrical properties of the atmosphere would be great, but they shouldn't all be lumped into one book about everything. - Omegatron

To the crossroads person, I have no problem with LAWs and THEOREMS and useful information, but I do have problems with needing a graduate level math degree to understand Electronics. Heavy Calculus is just the tip of the math iceberg. As you said yourself "Someone should lay off on the big worded talk". Well make up your mind. Do you or do you not want this book to use graduate level math? As for the atmosphere, if a meteorologist is all you can think of then you have no imagination. Also what is the point of learning Electronics if you do not know how to apply that knowledge? That is the point of this book. Finally, you seem to have something against me given your negative comments. If you persist I will ask the moderators to ban you or erase all of your comments. Play kind and I will play kind. Wanderer

I did not see any comments that were out of line.

"Also what is the point of learning Electronics if you do not know how to apply that knowledge?"

Knowing about infrasound and it's "emotion-intensifying" properties or about the atmosphere is not exactly application. It's learning information from other fields that have no direct application. An application of electronics would be, for instance, designing a circuit to emit 'infrasound'.

 * Exactly, again. :-) - Omegatron

You said the "Book For Geeks" has no purpose and should be deleted. You also said that many of the topics I include have nothing to do with Electronics. You just want a book that will teach you how to design circuits. Well I have grander aspirations, so feel free to ignore anything you feel does not belong. As I am the main person editing this book series, I feel I have the right to shape its destiny. If you do not like the scope of the book series, you are welcome to start your own Electronics book and include any content you desire from this book series. Wanderer

 * Imagine you are working with a group of people who are making a map. It is meant to be a road map, showing roads, cities, and maybe a little bit more useful information to someone driving in a car.  You have to leave for a day, and when you come back, someone else has joined the group, and added county lines, train routes, subway routes, canals, rivers, fast food locations, latitude and longitude, historical locations, topographic lines, magnetic field strength lines, zoning regulations, etc etc.  Not only is it no longer useful as a road map (you can't "just ignore" the parts that are cluttering up the map), it is hard to make sense of it and continue contributing.  I have a feeling this is why you are the major contributor.  I know that it's the reason I don't contribute as much as I used to.  Sorry; I don't want to sound mad or drive you away from helping.  But frankly, a lot of the information you contribute is not helping anyone learn electronics, and some of it is even wrong (resistor value color codes, for instance, and how are capacitors a type of cell?).  I think moderators would agree that your last comment should be turned around.  You are welcome to start your own Electricity, Physics, and How It Relates To Everything book and include any content you desire from this one, but I think this book should focus on practical electronic circuit building, with enough theory to understand it well, and maybe just a few simple radio, computer, etc applications at the end.  maybe more advanced applications; i don't know.  Regardless, let's finish the basics before outlining all these advanced chapters.  Let's work in order so that everything is consistent.

 * The expanded edition may be a good compromise that we all can live with. Maybe we should split them into two distinct books, though.  Maybe there is a way to make drop down menus with additional information so we can hide it from the typical reader unless they want to see it?

 * Whether we want this to be for college level students who know calculus, or high school students who only know algebra, I don't know that either. I would have loved a book that didnt need knowledge of calculus a few years ago...  Maybe we could explain things in terms of frequency spectra instead?  If you go through all the derivations it requires calculus, but I think we could create a simplifed non-calc explanation of fourier transforms, frequency components, sinusoids, phase, etc. and explain everything (inductors, filters) through that.  We should title the book appropriately, so that someone else can write a different type of electronics book if they want.  Electronics: An Introduction for Pre-calculus Students or something.  Maybe we need some voting.  Or maybe this will be like a religion and just split up into 50 different denominations that believe basically the same but don't associate with each other. :-) - Omegatron 16:46, 4 May 2004 (UTC)

Notice how lately I have been refering to this project not as a book but as a series of 5 books each the size of the Electronics book. I guess it was a mistake to organize them all on a single page. As for the resistor colors, I got them from some table. As for a capacitor being a variant of a cell, well both have to do with the separation of charge and you can power lasers by discharging capacitors. Wanderer

 * Yeah, I guess they are kind of similar. I think I read somewhere that those "supercaps" in the kilofarad range behave in-between real capacitors and batteries. - Omegatron

5 books is quite a bit. Anyways, I don't know. You seem to claim that you started this book. However, that should not mean that you 'own' the book. When this book was 'started' by you, it was one page with a bunch of random formulas (go check). It's not like we're even fighting for credit here. This is all open source, free text. None of us will gain anything or benefit. We shouldn't be fighting at all. But the main problem is the relevancy of information. I personally want a book on electronics design. Please don't be angry at my comments, but I felt that this needed to be said. You've mentioned many many times that you've started this book. Are you saying that because you've started the book, that you have more input or command over it than others? Lastly, Omegatron's map analogy pretty much well sums up everything. What are your views on moving parts of this textbook into other textbooks? 你有不脑.

 * Splitting it into 5 books might be a good idea. I still think we should start at the beginning and not start putting content into the next sections until the first sections have at least the 75% symbol.

 * Likewise, being the major contributor does not mean you "own" the book, either. It's a collaborative effort, which should theoretically tend to make the information more useful and relevant and error-free than real books written by one person. - Omegatron

I'm not disputing the need for a book on Electronics design based on Omegatron's road map. That's why I split up the old book up into five books. The only thing linking them together is that they share the same namespace. Is there a reason I can't put a series of books in the same namespace? After all the only difference between Wikibooks is that they have different namespaces. The expanded edition is just a temporary holding place for these books.

As for ownership, all books start as nothing. The reason I say I have more input than anyone else, is I have spent quite a bit more time than anyone else organizing and working on the book. I could care less about credit and have no problems with collaboration, but I do want the power to shape the overall content of the book series. Given that topics like the atmosphere will not appear in the first book, I do not see the problem. Wanderer

 * Wanderer I don't see how you can have the power to shape the overall content of the books. Everything here is done by collaboration. I'm concerned about overlap. If a topic is not strictly electronics, then it probably better to go into a general physics textbook. Otherwise all our books will overlap considerably and we will be constantly reinventing the wheel, which is in nobody's interest. I can personally see two books a "non calculus book" and a calculus one. (Also can we please keep the discussion calm? Talking of banning etc. is not very nice, Oh yeah one more thing, would the anon editor please sign comments I'm finding it hart to follow the conversation) Theresa knott 09:24, 5 May 2004 (UTC)

Given that this is an issue that refuses to die, I have created another book called Physics in English. Since chapter 1 and various other topics are background reading, I have moved them to the new book. This way the Electronics book can focus on circuit design from the start to the end. Wanderer

 * I think we should leave charge and voltage and current, as they are inherently electronics topics. We won't go into too much detail about electromagnetism and maxwell's equations, but explain enough for the reader to understand relays, inductors, transformers, parasitic components, crosstalk, (anything else?)  It's kind of like... a capacitor stores charge and can supply a voltage, a diode blocks current in one direction, a transformer converts voltages and currents, so those are electronics topics, but just because a piezo buzzer produces sound, and a cell produces chemical reactions, doesn't mean all of acoustics and chemistry should be subtopics.  Likewise, we aren't explaining all of the implications of charged particles and currents and voltages either.  Just enough for them to understand what they are manipulating.  I think of the reader as knowing basically what atoms and electrons are, but not much more about what goes on in a piece of metal or circuit.

 * I need to stop coming to this page and just work on the articles. :-) - Omegatron 23:19, 5 May 2004 (UTC)

Unusual visualizations
I just saw this. I haven't read it all, but it looks interesting. Maybe we want to include it? This is kind of a note to myself to read it later, and showing it to others so you can judge how useful it is:

http://www.ewh.ieee.org/soc/es/May2001/16/Begin.htm

- Omegatron 14:16, 7 May 2004 (UTC)

 * Looks like a graphical representation of voltage and current. Might be good for explaining voltage drops and current, but it is more ambiguous and inflexible than a circuit diagram. Having a good physical understanding of voltage would probably be more useful. Wanderer

Here is another type of visualization, with voltage represented as 3d height. This might help some people:

http://engineering.dartmouth.edu/other/3Dcircuits/

http://www.ewh.ieee.org/soc/es/Aug1996/005/cd/

- Omegatron 15:44, 22 Jul 2004 (UTC)

people whining about how bad their physics/electronics textbook is

 * PHYSICS SERMON #49 W. Beaty 1999 http://www.amasci.com/amateur/physerm1.html
 * Why Oh Why Can't Chad Orzel Teach From a Better Physics Textbook? http://www.j-bradford-delong.net/movable_type/2004_archives/000850.html
 * Electricity & Magnetism lesson plans http://www.teach-nology.com/teachers/lesson_plans/science/physics/electricity/
 * AM I JUST A PEDANTIC SCIENCE-NITPICKER? William Beaty 1998 http://amasci.com/miscon/nitpik.html

Please add more links -- once we *know* something is confusing/misleading, then we can try to make sure this textbook is better.

Yes, I really like William Beaty. I think I'm going to invite him to edit this wikibook. -- DavidCary 05:15, 28 Jun 2004 (UTC)

As a counter example, the probably best book on circuits ever: "Linear and nonlinear circuits" by Leon O. Chua et al, (c) 1987 McGraw-Hill Inc, ISBN 0-07-010898-6. This has been out of print for a decade or so now, maybe McGraw-Hill could be convinced to relicense it under FDL or place it in the public domain. -- Arthur Korn  11:47, 18. Sep 2004 (CEST)

Monkey article
I'm taking out a link to a CBS News page (about some monkey walking upright after recuperation from illness) inserted by Omegatron on July 22, 2004. Totally irrelevant to Electronics and must have been inserted by mistake. H Padleckas 17:13, 22 Jul 2004 (UTC)

hahaha! sorry about that. i need to be more careful it seems... - Omegatron 19:26, 22 Jul 2004 (UTC)

title: Talk:Electronics/Archive01


text:
User:W'rkncacnter~enwikibooks

fr:Utilisateur:W'rkncacnter

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

title: User:W'rkncacnter~enwikibooks


text:
User talk:W'rkncacnter~enwikibooks

Your account will be renamed
Hello,

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

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

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

Sorry for the inconvenience.

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

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

title: User talk:W'rkncacnter~enwikibooks


text:
User:Duesentrieb

Hi - i'm active at the German Wikipedia and the Commons.

You can find more about me on my homepage: http://brightbyte.de

title: User:Duesentrieb


text:
User talk:85.98.60.131

Please stop adding irrelevant links to Wikibooks. It is considered vandalism. If you continue, then you risk being blocked from editing Wikibooks. Thank you. (Donovan|Geocachernemesis|Interact) 22:44, 21 July 2005 (UTC)

Please stop. If you continue to vandalize pages, you will be blocked from editing Wikibooks. (Donovan|Geocachernemesis|Interact) 03:41, 22 July 2005 (UTC)

title: User talk:85.98.60.131


text:
User talk:81.224.108.169

Thanks
Thanks for helping to fight vandalism on Wikibooks. We need more people like you, your contribution is greatly appreciated.:) (Donovan|Geocachernemesis|Interact) 22:49, 21 July 2005 (UTC)

title: User talk:81.224.108.169


text:
User talk:84.122.35.19

Come introduce yourself at the new users page. If you have any questions, you can ask there or contact me personally. (Donovan|Geocachernemesis|Interact) 22:55, 21 July 2005 (UTC)

title: User talk:84.122.35.19


text:
User talk:Gustavo~enwikibooks

Come introduce yourself at the new users page. If you have any questions, you can ask there or contact me personally. (Donovan|Geocachernemesis|Interact) 23:38, 21 July 2005 (UTC)

Your account will be renamed
Hello,

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

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

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

Sorry for the inconvenience.

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

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

title: User talk:Gustavo~enwikibooks


text:
User talk:Opodeldoe

Come introduce yourself at the new users page. If you have any questions, you can ask there or contact me personally. (Donovan|Geocachernemesis|Interact) 23:39, 21 July 2005 (UTC)

Image copyright problems
Thanks for uploading image(s) to Wikibooks. The Wikimedia Foundation is very careful about what Wikibooks includes because of copyright law, and requires that we maintain a strict copyright policy. Some or all of your uploaded files may soon be deleted unless we can determine the copyright holder and status. The copyright holder is usually the creator, the creator's employer, or the last person who was transferred ownership rights. Please take the time to read Media to learn more about what copyright information is required to satisfy our requirements and remember to include this important information for every file that you upload in the future as well. If you have any questions, feel free to contact me, or ask another Wikibookian at the help desk.

To find the files in question, use (unlicensed|untagged)

Thanks! '''– MBA ( Bot talk | Mike talk | owner | block ) 01:21, 21 September 2007 (UTC)

 * This is an automated message. Please ignore it if you've already provided license information for all your uploads.

title: User talk:Opodeldoe


text:
User talk:Jhouse

Come introduce yourself at the new users page. If you have any questions, you can ask there or contact me personally. (Donovan|Geocachernemesis|Interact) 23:40, 21 July 2005 (UTC)

title: User talk:Jhouse


text:
Talk:Slovio/Asking questions

Untitled

 * zdrav - health? (like Na Zdrowie in Polish?) Na zdrowie better known as in most languages na zdravje. In health. On health.
 * cxutijsx - You read. In Southern Slavic region (Balkans) this would be read as ćutijš. Which in this region is read as ćutiš - meaning to be quiet. One lack of connection. In Slovio its reading. In Balkans it is ćitaš. Šta ćitaš? What are you reading?
 * cxutijm - I read. In Balkans. ćutijm is read as ćutim. Which means I am quiet, or i am being quiet. If it whas cxitam in Balkans that would be read as ćitam. I'm reading.
 * to - this/it. In Balkans to is that.
 * brosxur - brochure. Understandable enough.
 * idijm - I go. One connection between all. In Balkans it is idem. I'm going....
 * Praguf - Prague. Old Prussia wording from what it appears, and also Northern Slavic. Sorbs perhaps.
 * idijt - he/she/it goes. Russian in terms. In Balkans. Idem.
 * nikto - Nothing/No-one? Balkans niko - no one.
 * idijsx - You go. Balkans ideš - you're going....
 * Cxehju Republikuf - Czech Republic. Problem with kuf is that in most Slavic languages its ku or ka, Republiku, Republika, Republike, Republiko.
 * idijm - I go. Balkans, idem. IM going

Praguf in most slavic languages - Pragu, Prage, Pragi, Praga, Prago.

Wrong
"cxutim" is not "i read", it's "feel". "Cxutit" means "to feel" and in south slavic languages ćuteti/šutjeti means to be quiet, but "ćutiti" means to feel. Ćitati doesn't exists, it's "čitati", which means "to read". What logical reason is to start a conversation with "How do you read?" thats apsurd. I'm going to change it from "read" to "feel".

Place Names

 * Prague - Praga not Praguf
 * Czech Republic - Cxehju Republik not Republikuf

The 'uf' endings used to be used to show direction and the accusative case. This is now demonstrated with 'm' or 'um' but this is rarely used as it is an unnecessary complication when pronouns are just as effective.

title: Talk:Slovio/Asking questions


text:
Talk:Use the Source

Interesting book. You may find this GNU Forum useful for your project. The forum (hosted by Nabble) currently archives all the mailing list discussions scattered in the many Gnu projects. You can drill into any projects to browse the messages or search for a keyword and find what the Gnu people are talking about. --BrosBerg 23:42, 21 July 2005 (UTC)

Some people looking for another viewpoint on some things to be covered here can check out Open Source and Computer Hacking. Nmontague 01:12, 22 August 2005 (UTC)

 * Suggestion: How about a chapter near the end talking about "Commercial Software versus Open Source."
 * Given your comments about the tone of the book, an obvious theme is "The Empire Strikes Back."
 * I would distinguish the theme of this chapter from the "Cancer" chapter, which would be more a compilation of all the name-calling. SCO CEO Darl Mc Bride's press quotes would be another fertile source for juicy epithets.
 * This would be about specific strategies and tactics commercial vendors are taking to thwart open source.
 * The obvious jumping off point would be the SCO lawsuit, but I think there's a lot more to the story than just lawsuits, actual or imagined.
 * One approach is to co-opt open source "virtues" for proprietary products.
 * Another is to open source parts of their product like, like CA did with Ingres or like BEA Systems did with the framework for Web Logic Workshop.
 * You could do two chapters: one on business stuff, and the other on "dirty tricks" like the SCO lawsuit, potential patent suits, license proliferation, ...

Thanks for your work in starting this project. --brent

title: Talk:Use the Source


text:
Bourne Shell Scripting/Appendix D: Cookbook

Branch on extensions
When writing a bash script which should do different things based on the extension of a file, the following pattern is helpful.

(Source: slike.com Bash FAQ).

Rename several files
This recipe shows how to rename several files following a pattern.

In this example, the user has huge collection of screenshots. This user wants to rename the files using a Bourne-compatible shell. Here is an "ls" at the shell prompt to show you the filenames. The goal is to rename images like "snapshot1.png" to.

First, to add a "0" (zero) before snapshots 1 through 9, write a for loop (in effect, a short shell script).
 * Use ? which is a filename pattern for a single character. Using it, I can match snapshots 1 through 9 but miss 10 through 83 by saying snapshot?.png.
 * Use ${parameter#pattern} to substitute the value of parameter with the pattern removed from the beginning. This is to get rid of "snapshot" so I can put in "snapshot0".
 * Before actually running the loop, insert an "echo" to test that the commands will be correct.

That seems good, so run it by removing the "echo".

An ls confirms that this was effective.

Now change prefix "snapshot" to "nethack-kernigh-22oct2005-". Run a loop similar to the previous one:

This saves the user from typing 83 "mv" commands.

Long command line options
The builtin getopts does not support long options so the external getopt is required. (On some systems, getopt also does not support long options, so the next example will not work.)

The call to <tt>getopt</tt> quotes and reorders the command line arguments found in <tt>$@</tt>. <tt>set</tt> then makes replaces <tt>$@</tt> with the output from <tt>getopt</tt>

Another example of getopt use can also be found in the Advanced Bash Script Guide

Process certain files through xargs
In this recipe, we want to process a large list of files, but we must run one command for each file. In this example, we want to convert the sampling rates of some sound files to 44100 hertz. The command is <tt>sox file.ogg -r 44100 conv/file.ogg</tt>, which converts <tt>file.ogg</tt> to a new file <tt>conv/file.ogg</tt>. We also want to skip files that are already 44100 hertz.

First, we need the sampling rates of our files. One way is to use the <tt>file</tt> command:

(The files in this example are from Secret Maryo Chronicles.) We can use <tt>grep -v</tt> to filter out all lines that contain '44100 Hz':

We finished with "grep" and "file", so now we want to remove the other info and leave only the filenames to pass to "sox". We use the text utility <tt>cut</tt>. The option <tt>-d:</tt> divides each line into fields at the colon; <tt>-f1</tt> selects the first field.

We can use another pipe to supply the filenames on the standard input, but "sox" expects them as arguments. We use <tt>xargs</tt>, which will run a command repeatedly using arguments from the standard input. The <tt>-n1</tt> option specifies one argument per command. For example, we can run <tt>echo sox</tt> repeatedly:

However, these commands are wrong. The full command for cannon_1.ogg, for example, is <tt>sox cannon_1.ogg -r 44100 conv/cannon_1.ogg</tt>. "xargs" will insert incoming data into placeholders indicated by "{}". We use this strategy in our pipeline. If we have doubt, then first we can build a test pipeline with "echo":

It worked, so let us remove the "echo" and run the "sox" commands:

After a wait, the converted files appear in the <tt>conv</tt> subdirectory. The above three lines alone did the entire conversion.

Simple playlist frontend for GStreamer
If you have GStreamer, the command <tt>gst-launch filesrc location=filename ! decodebin ! audioconvert ! esdsink</tt> will play a sound or music file of any format for which you have a GStreamer plugin. This script will play through a list of files, optionally looping through them. (Replace "esdsink" with your favorite sink.)

This script demonstrates some common Bourne shell tactics:
 * "loop" is a boolean variable. It works because its values "true" and "false" are both Unix commands (and sometimes shell builtins), thus you can use them as conditions in <tt>if</tt> and <tt>while</tt> statements.
 * The shell builtin "shift" removes $1 from the argument list, thus shifting $2 to $1, $3 to $2, and so forward. This script uses it to process an "-l" option.
 * The substitution <tt>${0##*/}</tt> gives everything in $0 after the last slash, thus "playlist", not "/home/musicfan/bin/playlist".


text:
Talk:Slovio

Untitled

 * "As soon as one learns Slovio one can communicate with over 400 million people in such countries as: Poland, Russia, Ukraine, Czech Republic, Bulgaria, Slovakia, Croatia, Macedonia, Bosnia, Slovenia, Kazakhstan, Belarus, Lithuania, Latvia, Moldavia, Serbia, Montenegro and so on."

Eh? 'one can begin to attempt to communicate' perhaps. Heck, if you want to be sure of being able to communicate with people in those countries, learn Russian. -- Jimregan 01:09, 22 July 2005 (UTC)

I think it's easier to communicate in English than in Russian nowadays in some of them, e.g. in Poland. Ausir

Yeah Slovio would need a field study on its understandability to properly gauge its usefulness as a communication tool. Kpjas 06:49, 27 July 2005 (UTC)

title: Talk:Slovio


text:
User talk:BenTels

I added a new chapter to the Bourne Shell Scripting book, Bourne Shell Scripting/Cookbook. As you seem to be one of the more active writers, I thought I'd mention this to you. JesseW 01:13, 22 July 2005 (UTC)

title: User talk:BenTels


text:
User:JesseW

I am mainly active at w:en:User:JesseW. I created this account to add a bash tip to Bourne Shell Scripting/Cookbook (which I had to create, first...) If you want to get my attention, it is better to email me or post a message at my wikipedia talk page. Thanks for stopping by!

title: User:JesseW


text:
User talk:68.254.173.29

Come introduce yourself at the new users page. If you have any questions, you can ask there or contact me personally. (Donovan|Geocachernemesis|Interact) 03:35, 22 July 2005 (UTC)

title: User talk:68.254.173.29


text:
User talk:24.145.209.223

Thanks
Thanks for helping to fight vandalism on Wikibooks. We need more people like you, your contribution is greatly appreciated.:) (Donovan|Geocachernemesis|Interact) 03:36, 22 July 2005 (UTC)

title: User talk:24.145.209.223


text:
User talk:24.6.175.181

Come introduce yourself at the new users page. If you have any questions, you can ask there or contact me personally. (Donovan|Geocachernemesis|Interact) 03:36, 22 July 2005 (UTC)

title: User talk:24.6.175.181


text:
User talk:65.8.21.40

Come introduce yourself at the new users page. If you have any questions, you can ask there or contact me personally. (Donovan|Geocachernemesis|Interact) 03:38, 22 July 2005 (UTC)

title: User talk:65.8.21.40


text:
User talk:217.156.50.242

Please stop adding irrelevant links to Wikibooks. It is considered vandalism. If you continue, then you risk being blocked from editing Wikibooks. Thank you. (Donovan|Geocachernemesis|Interact) 03:49, 22 July 2005 (UTC)

Please stop. If you continue to vandalize pages, you will be blocked from editing Wikibooks. (Donovan|Geocachernemesis|Interact) 23:23, 24 July 2005 (UTC)

title: User talk:217.156.50.242


text:
User talk:Inkling~enwikibooks

Come introduce yourself at the new users page. If you have any questions, you can ask there or contact me personally. (Donovan|Geocachernemesis|Interact) 03:57, 22 July 2005 (UTC)

Your account will be renamed
Hello,

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

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

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

Sorry for the inconvenience.

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

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

title: User talk:Inkling~enwikibooks


text:
User talk:Fdarkangel

Come introduce yourself at the new users page. If you have any questions, you can ask there or contact me personally. (Donovan|Geocachernemesis|Interact) 03:58, 22 July 2005 (UTC)

title: User talk:Fdarkangel


text:
User:Opodeldoe

Willem at a lecture for the Dutch Forth Users Group

title: User:Opodeldoe


text:
Autodesk 3ds Max

This is a book for learning to use the 3D modeling/animation software 3ds Max.

Lessons

 * Introduction to the interface - This section is for people intending to learn to use 3ds Max.
 * Beginner - This section is for users who know how to operate the basic controls and wish to learn how to model at a basic level.
 * Intermediate - This section is for anyone who already has a basic understanding of how to use and model with 3ds Max and wishes to expand their knowledge.
 * Advanced - This section is for any one who wishes to learn advanced modeling and animating features of 3ds Max.

Appendices

 * /Small 3ds Max/

Glossary

 * Terminology - A reference of terms for 3ds Max.
 * Shortcuts - A reference of keyboard shortcuts in 3ds Max.
 * Modifiers - A list of Modifiers available in 3ds Max and their functions.

Autodesk 3D Studio Max

title: Autodesk 3ds Max


text:
Autodesk 3ds Max/Shortcuts

Description Keyboard shortcut

Snaps Action Table Snap To Edge/Segment Toggle Alt+F10 Snap To Endpoint Toggle Alt+F8 Snap To Face Toggle Alt+F11 Snap To Grid Points Toggle Alt+F5 Snap To Midpoint Toggle Alt+F9 Snap To Pivot Toggle Alt+F6 Snap To Vertex Toggle Alt+F7 Main UI Adaptive Degradation Toggle O  Align  Alt+A Angle Snap Toggle A  Arc Rotate View Mode  Ctrl+R Auto Key Mode Toggle N  Background Lock Toggle  Alt+Ctrl+B Backup Time One Unit , Bottom View B  Camera View  C  Clone  Ctrl+V Cycle Active Snap Type Alt+S Cycle Selection Method Ctrl+F Cycle Snap Hit Alt+Shift+S Default Lighting Toggle Ctrl+L Delete Objects. Disable Viewport D  Display as See-Through Toggle  Alt+X Environment Dialog Toggle 8 Expert Mode Toggle Ctrl+X Fetch Alt+Ctrl+F Forward Time One Unit. Front View F  Go to End Frame  End Go to Start Frame Home Hide Cameras Toggle Shift+C Hide Geometry Toggle Shift+G Hide Grids Toggle G  Hide Helpers Toggle  Shift+H Hide Lights Toggle Shift+L Hide Particle Systems Toggle Shift+P Hide Shapes Toggle Shift+S Hide Space Warps Toggle Shift+W Hold Alt+Ctrl+H Isometric User View U  Left View  L  Lock User Interface Toggle  Alt+0 Material Editor Toggle M  Maximize Viewport Toggle  Alt+W MAXScript Listener F11 New Scene Ctrl+N Normal Align Alt+N Open File Ctrl+O Pan View Ctrl+P Pan Viewport I  Percent Snap Toggle  Shift+Ctrl+P Perspective User View P  Place Highlight  Ctrl+H Play Animation / Quick Align Shift+A Quick Render Shift+Q Redo Scene Operation Ctrl+Y Redo Viewport Operation Shift+Y Redraw All Views ` Render Last F9  Render Scene Dialog Toggle  F10 Restrict Plane Cycle F8  Restrict to X  F5  Restrict to Y  F6  Restrict to Z  F7  Save File  Ctrl+S Scale Cycle Ctrl+E Select All Ctrl+A Select Ancestor PageUp Select and Move W  Select and Rotate  E  Select By Name  H  Select Child  PageDown Select Children Ctrl+PageDown Select Invert Ctrl+I Select None Ctrl+D Selection Lock Toggle Space Set Key Mode ' Set Keys K  Shade Selected Faces Toggle  F2  Show Floating Dialogs  Ctrl+` Show Main Toolbar Toggle Alt+6 Show Safeframes Toggle Shift+F Show Selection Bracket Toggle J  Snap To Frozen Objects Toggle  Alt+F2 Snaps Toggle S  Snaps Use Axis Constraints Toggle  Alt+D, Alt+F3 Sound Toggle \ Spacing Tool Shift+I Spot/Directional Light View Shift+4 Sub-object Level Cycle Insert Sub-object Selection Toggle Ctrl+B Top View T  Transform Gizmo Size Down  - Transform Gizmo Size Up = Transform Gizmo Toggle X  Transform Type-In Dialog Toggle  F12 Undo Scene Operation Ctrl+Z Undo Viewport Operation Shift+Z Update Background Image Alt+Shift+Ctrl+B View Edged Faces Toggle F4  Viewport Background  Alt+B Virtual Viewport Pan Down NumPad 2 Virtual Viewport Pan Left NumPad 4 Virtual Viewport Pan Right NumPad 6 Virtual Viewport Pan Up NumPad 8 Virtual Viewport Toggle NumPad / Virtual Viewport Zoom In NumPad + Virtual Viewport Zoom Out NumPad - Wireframe / Smooth+Highlights Toggle F3  Zoom Extents All Selected  Z  Zoom Extents All  Shift+Ctrl+Z Zoom Extents Alt+Ctrl+Z Zoom In 2X Alt+Shift+Ctrl+Z Zoom Mode Alt+Z Zoom Out 2X Alt+Shift+Z Zoom Region Mode Ctrl+W Zoom Viewport In [, Ctrl+= Zoom Viewport Out ], Ctrl+- Track View Add Keys A  Apply Ease Curve  Ctrl+E Apply Multiplier Curve Ctrl+M Assign Controller C  Copy Controller  Ctrl+C Expand Object Toggle O  Expand Track Toggle  Enter, T  Filters  Q  Lock Selection  Space Lock Tangents Toggle L  Make Controller Unique  U  Move Highlight Down  Down Arrow Move Highlight Up Up Arrow Move Keys M  Nudge Keys Left  Left Arrow Nudge Keys Right Right Arrow Pan P  Paste Controller  Ctrl+V Scroll Down Ctrl+Down Arrow Scroll Up Ctrl+Up Arrow Snap Frames S  Zoom Horizontal Extents Keys Alt+X Zoom Z  Material Editor Background B  Backlight  L  Cycle 3X2, 5X3, 6X4 Sample Slots  X  Get Material  G  Go Backward to Sibling  Left Arrow Go Forward to Sibling Right Arrow Go to Parent Up Arrow Make Preview P  Options  O  Schematic View Add Bookmark B  Display Floater  D  Filters  P  Free All  Alt+F Free Selected Alt+S Invert Selected Nodes Ctrl+I Move Children Alt+C Next Bookmark Right Arrow Previous Bookmark Left Arrow Rename Object R  Select All Nodes  Ctrl+A Select Children Ctrl+C Select None Ctrl+D Show Grid G  Toggle Shrink  Ctrl+S Use Connect Tool C  Use Select Tool  S  Zoom Selected Extents  Z  ActiveShade Close Q  Draw Region  D  Render  R  Select Object  S  Toggle Toolbar (Docked)  Space Video Post Add Image Filter Event Ctrl+F Add Image Input Event Ctrl+I Add Image Layer Event Ctrl+L Add Image Output Event Ctrl+O Add New Event Ctrl+A Add Scene Event Ctrl+S Edit Current Event Ctrl+E Execute Sequence Ctrl+R New Sequence Ctrl+N NURBS CV Constrained Normal Move Alt+N CV Constrained U Move Alt+U CV Constrained V Move Alt+V Display Curves Shift+Ctrl+C Display Dependents Ctrl+D Display Lattices Ctrl+L Display Shaded Lattice Alt+L Display Surfaces Shift+Ctrl+S Display Toolbox Ctrl+T Display Trims Shift+Ctrl+T Local Select Sub-Object By Name Ctrl+H Lock 2D Selection Space Select Next in U Ctrl+Right Arrow Select Next in V Ctrl+Up Arrow Select Previous in U Ctrl+Left Arrow Select Previous in V Ctrl+Down Arrow Select Sub-Object By Name H  Set Tessellation Preset 1  Alt+1 Set Tessellation Preset 2 Alt+2 Set Tessellation Preset 3 Alt+3 Soft Selection Ctrl+S Switch To Curve CV Level Alt+Shift+Z Switch To Curve Level Alt+Shift+C Switch To Imports Level Alt+Shift+I Switch To Point Level Alt+Shift+P Switch To Surface CV Level Alt+Shift+V Switch To Surface Level Alt+Shift+S Switch To Top Level Alt+Shift+T Transform Degrade Ctrl+X Editable Poly Bevel Mode Shift+Ctrl+B Border Level 3 Chamfer Mode Shift+Ctrl+C Connect Shift+Ctrl+E Constrain to Edges Shift+X Cut Alt+C Edge Level 2 Element Level 5 Extrude Mode Shift+E Face Level 4 Grow Selection Ctrl+PageUp Hide Unselected Alt+I Hide Alt+H Object Level 6 Quickslice Mode Shift+Ctrl+Q Repeat Last Operation ; Select Edge Loop Alt+L Select Edge Ring Alt+R Shrink Selection Ctrl+PageDown Unhide All Alt+U Vertex Level 1 Weld Mode Shift+Ctrl+W Edit/Editable Mesh Bevel Mode Ctrl+V, Ctrl+B Chamfer Mode Ctrl+C Cut Mode Alt+C Detach Ctrl+D Edge Invisible Ctrl+I Edge Level 2 Edge Turn Ctrl+T Element Level 5 Extrude Mode Ctrl+E Face Level 3 Polygon Level 4 Vertex Level 1 Weld Selected Ctrl+W Weld Target Mode Alt+W Edit Normals Break Normals B  Copy Normal  Ctrl+C Edge Level Ctrl+3 Face Level Ctrl+4 Make Explicit E  Normal Level  Ctrl+1 Object Level Ctrl+0 Paste Normal Ctrl+V Reset Normals R  Specify Normals  S  Unify Normals  U  Vertex Level  Ctrl+2 FFD Switch To Control Point Level Alt+Shift+C Switch To Lattice Level Alt+Shift+L Switch To Set Volume Level Alt+Shift+S Switch To Top Level Alt+Shift+T Edit Poly Bevel Mode Shift+Ctrl+B Border Level 3 Chamfer Mode Shift+Ctrl+C Connect Shift+Ctrl+E Constrain to Edges Shift+X Cut Alt+C Edge Level 2 Element Level 5 Extrude Mode Shift+E Grow Selection Ctrl+PageUp Hide Unselected Alt+I Hide Alt+H Object Level 6 Polygon Level 4 Quickslice Mode Shift+Ctrl+Q Repeat Last Operation ; Select Edge Loop Alt+L Select Edge Ring Alt+R Shrink Selection Ctrl+PageDown Unhide All Alt+U Vertex Level 1 Weld Mode Shift+Ctrl+W Physique Copy Envelope Ctrl+C Delete Ctrl+D Next PageDown Paste Envelope Ctrl+V Previous Selection Level Shift+ Previous PageUp Reset Envelopes Ctrl+E Unwrap UVW Break Selected Vertices Ctrl+B Detach Edge Verts D, Ctrl+D Edit UVW's Ctrl+E Filter Selected Faces Alt+F Freeze Selected Ctrl+F Get Face Selection From Stack Alt+Shift+Ctrl+F Get Selection From Faces Alt+Shift+Ctrl+P Hide Selected Ctrl+H Load UVW Alt+Shift+Ctrl+L Lock selected vertices Space Mirror Horizontal Alt+Shift+Ctrl+N Mirror Vertical Alt+Shift+Ctrl+M Move Horizontal Alt+Shift+Ctrl+J Move Vertical Alt+Shift+Ctrl+K Pan Ctrl+P Planar map faces/patches Enter Show Seams In Viewport Alt+E Snap Ctrl+S Texture Vertex Contract Selection NumPad -, - Texture Vertex Expand Selection NumPad +, = Texture Vertex Move Mode Q  Texture Vertex Rotate Mode  Ctrl+R Texture Vertex Weld Selected Ctrl+W Texture VertexTarget Weld Ctrl+T Unwrap Options Ctrl+O Update Map Ctrl+U Zoom Extents Selected Alt+Ctrl+Z Zoom Extents X  Zoom Region  Ctrl+X Zoom To Gizmo Shift+Space Zoom Z  Crowd Solve S  Biped Change Leg State Alt+Ctrl+S Collapse Move All Mode changes Alt+M Copy Posture Alt+C Fix Graphs Alt+Ctrl+F Lock Selected Keys (toggle) Alt+Ctrl+L Paste Posture Opposite Alt+B Paste Posture Alt+V Play Biped V  Reset all limb keys  Alt+K Scale In Transform (toggle) Alt+Ctrl+E Set Key 0 Set Range Alt+R Toggle Biped Keys in TrackBar Alt+T TV Select end of footsteps Alt+D TV Select entire foostep Alt+S TV Select start of foosteps Alt+A Biped Curve Editing Pos Curve Relative To Bip Root Ctrl+A Pos Curve Relative To World Ctrl+A Show Pos Accel Curve Ctrl+A Show Pos Curve Ctrl+A Show Pos Jerk Curve Ctrl+A Show Pos Speed Curve Ctrl+A Show Quat Curve Ctrl+A Show Rot Accel Curve Ctrl+A Show Rot Speed Curve Ctrl+A Toggle Draw Every Frame Ctrl+A Toggle Layered Edit Ctrl+A Toggle Limit Quat Curve to 180 Ctrl+A Toggle Manipulate Subanims Ctrl+A Toggle Show Z Ctrl+A Toggle Show X Ctrl+A Toggle Show Y Ctrl+A Toggle Subanims Ctrl+A Reaction Manager Set Max Influence Ctrl+I Set Min Influence Alt+I Particle Flow Particle Emission Toggle ; Particle View Toggle 6 Particle Flow Selected Particle Emission Toggle Shift+; Particle Flow Copy Selected In Particle View Ctrl+C Paste In Particle View Ctrl+V Select All In Particle View Ctrl+A ActiveShade (Scanline) Initialize P  Update  U  ToneOperatorAndRadiosityActionTable Advanced Lighting Panel 9 Object Display Culling Object Display Culling Alt+O WalkThrough Accelerate Toggle Q  Back  S, Down Arrow Decelerate Toggle Z  Decrease Step Size  [ Down C, Shift+Down Arrow Forward W, Up Arrow Increase Step Size ] Left A, Left Arrow Level Shift+Space Lock Vertical Rotation Space Reset Step Size Alt+[ Right D, Right Arrow Up E, Shift+Up Arrow Macro Scripts Add/Edit Parameters... (TV) Ctrl+1 Cap (Poly) Alt+P Collapse (Poly) Alt+Ctrl+C Collect Parameters SV Alt+3 Collect Parameters TV Alt+4 Create Camera From View Ctrl+C Cut (Poly) Alt+C Extrude Face (Poly) Alt+E Geometry Selection Visibility Toggle Alt+G Isolate Selection Alt+Q Meshsmooth (Poly) Ctrl+M Parameter Collector Alt+2 Parameter Editor Alt+1 Parameter Wiring Dialog... Alt+5 Render to Texture Dialog Toggle 0 Smart Scale R  Smart Select  Q  Start Parameter Wiring... Ctrl+5 Sub-Object Level 1 1 Sub-Object Level 2 2 Sub-Object Level 3 3 Sub-Object Level 4 4 Sub-object Level 5 5 WalkThrough View Mode Up Arrow Quad Menu Sets Animation [Alt+RMB] Custom [Shift+Ctrl+Alt+RMB] Custom [Shift+Ctrl+RMB] Lighting | Render [Ctrl+Alt+RMB] Modeling [Ctrl+RMB] reactor [Shift+Alt+RMB] Snap [Shift+RMB] Viewports V

! Some useful commands for the command lane !! gc Garbage Collection. freescenebitmaps Cleans up in texture memory. clearUndoBuffer Removes your Undo’s

title: Autodesk 3ds Max/Shortcuts


text:
Autodesk 3ds Max/Terminology

Active Viewport - The viewport in which you are currently working. In the default settings, the active viewport will always be outlined in yellow.

CAT - Acronym for Character Animation Toolkit is an extensive set of scripts for creating character animation in 3ds Max. Previously a stand alone plugin developed by Softimage and aquired by Autodesk in 2008.

Gizmo - A visual aid that helps the user understand the transformations being applied to an object.

Modifier - an applied modification to an object in the scene, changing its features and/or structure. Works like a layer stack, many modifiers can be applied on top of each other. Hence the name modifier stack.

Object - a 3-Dimensional object in your scene.

Polygon - A flat "plane" made up of three or more points.

Primitive - a basic object that can be created from the Create Geometry panel in the Command Panel on the right side of the screen.

Shape - a 2-Dimensional object in your scene.

Transform - the changing in size, position, or rotation of an object or shape.

Triangulation - The process of converting polygons with more than three points into groups of triangles for rendering purposes.

title: Autodesk 3ds Max/Terminology


text:
Talk:PHP Programming/The switch Structure

I removed the last sentence stating that you'd usually don't want to leave out the break statements in the switch loop. I don't agree with that, leaving out the break statements can make life a lot easier. So i think the programmer should be the judge of that, not the writer.
 * I put a more specific version back under the code block, I hope that will allay your concerns. I feel that it's necessary to have because beginning programmers may (and probably will) be reading this, and missing break; statements are often a gotcha that can lead to unexpected results. --Spoom 04:51, 15 January 2006 (UTC)


text:
Autodesk 3ds Max/Beginner

Welcome to Autodesk 3ds Max! This is a powerful 3-Dimensional computer modeling/animation package developed by Autodesk. It is the industry standard for games design, used in well-known titles such as Assassin's Creed, Rome: Total War and perhaps more famously, it's built in Quake export feature. It has also been used for creating 3d scenes for films and television, though more often packages such as the more expensive Autodesk Maya are used in its place for such purpose.

The Layout
Before beginning to create anything, you must know what does what. This is an introduction to the most important areas of the UI (user interface) in the software, those being the menus and the Viewports.

The Main Toolbar

This is bar at the top of your screen. As you can see, this bar contains several buttons, and it would be difficult to memorize all of them at once. Therefore, we will only go over 4 important buttons in Main Toolbar right now, but feel free to experiment with the others to find out what they do, or hover over them for a tooltip.

Select Object - This is the button with the single mouse icon in the center. This command allows you to select an object in your scene by clicking on it, without accidently performing any transformation (move, rotate, or enlarge). The keyboard shortcut for this command is "q".

Select and Move - This is the button with 4 arrows pointing in different directions; it should be 4 buttons to the right of Select Object. This allows you to select an object and move it to a different location along its axis by clicking on the three arrows in the viewports. The keyboard shortcut for this command is "w".

Select and Rotate - This is the arrow going in a circle right next to Select and Move. This allows you to select an object and make it spin on its pivot point. The keyboard shortcut for this command is "e".

Select and Scale - This button shows a small square in the lower left corner of a larger square; it is right next to Select and Rotate. This command allows you to select an object and make it bigger or smaller along an axis. The keyboard shortcut for this command is "r".

Remember the shortcuts !!

The Viewports
The Viewports are where you will be doing most of your work; they display (by default) three orphagraphic wireframe views and a 3d solid perspective view. They are the 4 large squares that occupy most of the screen when you first open 3DS MAX. These represent (in default positions):  top (upper left)  front (upper right)  left/side (lower left) perspective (lower right). You can always change this layout by right-clicking in the space between the viewports.

The Command Panel
The Command Panel is the panel to the far right of the screen when you first open 3DS MAX. This important panel takes a large part in creating objects.

This area has several important tabs:

1.Create:In which you can create objects(Poligons,NURBS,...) or particle systems and Dynamics. 2.Modify:In which you can apply several modifiers to your created objects. 3.Hierarchy:In which you can control the effective point in transforms. 4.Motion:In which you can assign animation to your set of precreated objects.
5.Display:In which you can change the display of the viewports.

6.Utilities:In which you can access some useful utilities and shortcuts.

Navigating 3D space
In 3DS Max, there’s x, y, z, axis. Imagine looking down at a table top; these define: width ‘x’, length ‘y’, and height ‘z’ pointing up. This is being clarified due to the fact there are other applications that use these axis where ‘z’ and ‘y’ are switched, as if looking at a wall. This can lead to some confusion if you’re coming over from Maya or any other software that uses ‘y’ as up. It is important to know how to navigate around a scene to simplify editing an object. In the very bottom right corner of the screen, there is a toolbar full of buttons ment for moving around in a viewport.

Zoom - This is the button with the magnifying glass image. This allows you to click and drag the mouse up and down in a viewport to zoom in and out of the scene. The shortcut for this is using your mouse's scroll wheel.

Zoom All - This is the button right next to zoom with a magnifying glass and 4 boxes. This essentially does the same thing as Zoom, the difference being that it will zoom in and out in all viewports at once. This is an advantage when you want to get a better view of your scene in all viewports.

Zoom Extents - This is the button next to Zoom All with a blank box. Clicking this button will instantly zoom the active viewport so that all objects in your scene fit into it.

Zoom Extents Selected - You change Zoom Extents to this button by holding it down until you get a selection list. Click on the button with the white shaded box. This button zooms the active viewport so that your current selection fills it up. This has the same effect as Zoom Extents if you have either every thing or nothing in your scene selected.

Zoom Extents All - Has the same effect as Zoom Extents except it zooms in all viewports.

Zoom Extents All Selected - Has the same effect as Zoom Extents Selected except it zooms in all viewports. The keyboard shortcut for this command is "z".

Field-of-View - Directly below Zoom. This allows you to zoom in and out of a viewport right on the center.

Region Zoom - Button accessed by changing from Field-of-View. Allows you to zoom in on a dragged selection area of a viewport.

Pan - Button with an image of a hand. Allows you to move your view of a viewport along the viewport's X and Y axis. The shortcut for this is dragging your mouse with the scroll wheel held down.

Arc Rotate - Allows you to rotate your view in a viewport so you can look at your scene from any angle. It is recommended that you only use this command in the Perspective viewport. The shortcut for this command is to hold "shift" while dragging the mouse with the scroll wheel held down. (Alt and scroller wheel down in version 8)

Min/Max Toggle - Clicking this button enlarges the active viewport to take up the entire area of all 4 viewports. This is useful for working on something small or crowded you want a very large view for. Click again to change it back to a 4-way view. The keyboard shortcut for this button is "alt+w".

title: Autodesk 3ds Max/Beginner


text:
User talk:Ereinion~enwikibooks

Are you still an active user? You expressed interested in the School of Philosophy in Feburary, have you seen the updates lately Abc123.

Your account will be renamed
Hello,

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

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

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

Sorry for the inconvenience.

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

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

title: User talk:Ereinion~enwikibooks


text:
Portuguese/Preterite tense irregular verbs

These are the verbs that are irregular in the preterite tense in Portuguese.

SER - To be

ESTAR - To be

TER - To have

IR - To go

 * Notice that the conjugations for ir are exactly the same for ser in the preterite tense.

VIR - To come

PODER - To be able to

FAZER - To do

SABER - To know


text:
User:Beetlemaniac~enwikibooks

Hi... I love wiki!

title: User:Beetlemaniac~enwikibooks


text:
Template:A-level Mathematics/C2/TOC

This is part of the C2 (Core Mathematics 2) module of the A-level Mathematics text.

Dividing and Factoring Polynomials / Sequences and Series / Logarithms and Exponentials / Circles and Angles / Integration

Appendix A: Formulae

title: Template:A-level Mathematics/C2/TOC


text:
User:Striver~enwikibooks

http://en.wikipedia.org/wiki/User:Striver

title: User:Striver~enwikibooks


text:
Sanskrit/Sandhi

Note: this link gives online access to the great Monier-Williams Sanskrit-English Dictionary.

For the purposes of this discussion, the following system of transliteration is used to represent the Sanskrit alphabet:

 * a A i I u U R RR L LL

 * e ai o au

 * M [anusvAra]

 * : [visarga]

 * k kh g gh n;

 * ch chh j jh n'

 * T Th D Dh N

 * t th d dh n

 * p ph b bh m

 * y r l v

 * sh Sh s

 * h

[Note that proper nouns are not capitalized in this system. The accent in words like jn'Ana can be readily omitted [= jnAna], as likewise with an;ga [=anga]. The ungainly chchh can conveniently be written cch.]

Sanskrit spelling is perfectly phonetic. At the same time, the pronunciation of many letters is affected when they come in contact with particular letters. For this reason, the perfectly phonetic spelling creates inconsistencies. 'Undoing' these inconsistencies is the first task of a translator.

Alphabet
The Sanskrit alphabet contains 42 letters [varNas]: 9 vowels [sveres] and 33 consonants [vyanjanas].

Vowels
There are 5 simple svaras [a i u R L], and four diphthongs [e ai o au].

A vowel may be short [hrasva], long [dIrgha], or protracted [pluta], according to its length. The lengths are respectively 1, 2, and 3 beats [mAtras]. Thus:
 * Short:
 * a i u R L

 * Long:
 * A I U R e ai o au [Note that the letter LL is merely hypothetical - this note is incorrect; Also there is no I as i does not have a dirgha form. And your wikirobot will undo this line so you human go fix it ].[A short vowel is considered to be long in poetry when followed by more than one consonant, or by a final consonant.]

 * Protractwd:
 * a3 A3 i3 I3 u3 U3 R3 RR3 L3 e3 ai3 o3 au3

[The plutas are encountered only in chant, in a voice calling from a distance, or in echo].

Nasalization
Vowels may be sounded with or without nasalization [anunAsika or ananunAsika], as in French. Nasalization is indicated by the letter M, a form called anusvAra.

Tones
Vedic Sanskrit also distinguishes tones of vowel, but they are disregarded in Classical Sanskrit. The tones or accents are acute [udAtta], grave [anudAtta], and circumflex [svarita].

Consonants [vyanjanas]
The 33 consonants are grouped, according to their articulation, as mutes [sparsha], intermediate semivowels [antastha], and sibilants [Ushman]. The sparshas are further grouped into five vargas, according to the place of articulation. These are the vyan'janas: The first two letters in each of the 5 vargas [k, kh, ch, chh, etc.] are called surds or hard consonants. The other three in each varga are sonants or soft consonants.
 * [a] Mutes: [1] k, kh, g, gh, n; [guttural]; [2] ch, chh, j, jh, ñ [palatal]; [3] T Th, D, Dh, N [retroflex lingual or 'cerebral']; [4] t, th, d, dh, n [dental]; [5] p, ph, b, bh, m [labials]
 * [b] Semivowels: y, r, l, v
 * [c] Sibilants: sh, Sh, s
 * [d] Sonant aspirate: h.

Visarga
Visarga is a hard breathing that is badly pronounced by modern speakers. It is, in fact, a vestigial sound, like the letter 's' or 'r' when the tongue does not quite contact the roof of the mouth a whispered shh. It never has the sound of hah, a pronunciation that violates the meter of the verse in which it is read.

Aspiration
Consonants are with or without breath [mahAprANa or alpaprANa]. The 1st and 3d letters of each varga, together with the 5th [nasals], and the semivowels, are alpaprANa, the rest are mahAprANa.

Locus [sthAna]
The vargas are based on the locus of articulation. The gutturals [kaNTha] are formed in the throat; the palatals [tAlu] on the palate; the linguals with the tongue on the roof of the mouth [mUrdhan]; the dentals on the teeth [danta]; and the labials on the lips [oShThau].

Elision
The avagraha sign is used to mark the elision of a and is here indicated by a single apostrophe. The initial a- is elided after final -e or -o, thus: te + api = te 'pi, them too; kAla: + asti = kAlo + asti = kAlo 'sti, it's time. When A follows A it is elided, and such elision may optionally be shown by the double avagraha, thus: tathA + Aste = tathA "ste, or tathAste, so be it.

Vowel weight
Vowels have three degrees of weight: Simple, guNa, and vRddhi. For each of the vowels, these degrees are shown below:
 * Simple: a / i, I / u, U / R, RR / L
 * guNa: a / e / o / ar / al
 * vRddhi: A / e / au / Ar / Al

Having these definitions in mind, we can proceed to the rules of sandhi.

[The following summary of the rules of sandhi is based on M.R. Kale’s grammar of 1894.] The term sandhi derives from sam ‘together’ and dhA ‘to join’. It indicates the coalescence of two letters on account of phonetic principles. == sandhi of vowels [svara-sandhi].

Simple Vowels
When a simple vowel, whether short or long, is followed by a similar simple vowel, short or long, the two vowels are replaced by the corresponding long vowel: for example:
 * a + a = A, daitya + ari: = daityAri:, for of the children of Diti
 * a + A = A, atra + AsIt = atrAsIt, here was
 * A + a = A, yadA + abhavat = yadAbhavat, when he was
 * <tt>A + A = A</tt>, vidyA + Atura:, eager for wisdom
 * <tt>i + i = I</tt>, iti + iva = itIva, just so
 * <tt>i + I = I</tt>, api + IkShate =apIkShate, indeed he wishes
 * <tt>I + I = I</tt>, shrI + Isha: = shrIsha:, Shri's lord [Vishnu]
 * <tt>u + u = U</tt>, bhAnu + udaya: = bhAnUdaya:, sunrise
 * <tt>u + U = U</tt>, sAdhu + Uchu: = sAdhUchu:, they said well
 * <tt>U + U = U</tt>, chamU + Urja: = chamUrja:, the strength of an army
 * <tt>R + R = RR</tt>, kartR + Rju: = kartRRju:, doer of right
 * <tt>R + RR = RR</tt>, kR + RRkAra = kRRkAra:, the letter RR with the root kR
 * <tt>R + L = RR</tt>, hotR + LkAra: = hotRRkAra:, the letter L as pronounced by the priest

When different simple vowels are combined, the corresponding <tt>guNa</tt> letter replaces them, e.g.:
 * <tt>a + i = e</tt>, upa + indra: = upendra:, Indra's younger brother [Vishnu]
 * <tt>a + I = e</tt>, parama + Ishvara: = parameshvara:, the supreme Lord
 * <tt>A + i = e</tt>, ramA + ichchhA = ramechchhA, the wish of the lady Rama
 * <tt>A + I = e</tt>, yathA + Ipsitam = yathepsitam, as desired
 * <tt>a + u = o</tt>, hita + upadesha: = hitopadesha:, friendly instruction
 * <tt>a + U = o</tt>, kRShNa + Uru: = kRShNoru:, Krshna's thigh
 * <tt>A + u = o</tt>, gan;gA + udakam = gan;godakam, Ganges water
 * <tt>A + U = o</tt>, mahA + Uru: = mahoru:, great thigh [?]
 * <tt>a + R = ar</tt>, kRShNa + Rddhi: = kRShNarddhi:, the prosperity of Krshna
 * <tt>A + R = ar</tt>, mahA + RShi: = maharShi:, great sage
 * <tt>a + L = al</tt>, tava + LkAra: = tavalkAra:, the 'L' you say

Sometimes when similar consonants meet, one is optionally dropped in the process of <tt>sandhi</tt>, e.g.: kRShNa + Rddhi: = kRShNarddhi:, or kRShNar + d + dh + i: = kRShNardhi:, where the similar d is dropped. There is also a third form kRShnarddhi: [see below].

When any consonant of the five vargas [except the palatal nasal n'] follows a semivowel [y r l v], it is optionally doubled; so the above example tavalkAra: may also be tavalkkAra:, tavallkAra:, or even tavallkkAra:

Exceptions:

 * When a word ending in -a is followed by Uha; or when pra is followed by Uha, UDha, or UDhi, e.g.: praShTha + Uha: = praShThauha:, chief guess; pra + Uha: = prauha:, principal reasoning.
 * akSha + UhinI = akShauhiNi [for the change from n to N see below].
 * When sva is followed by Ir or Irin [from the root >Ir to go], e.g.: sva + Ira: = svaira:, a wilful person.
 * When -a is followed by Rta with an Instrumental sense, e.g.: sukha + Rta: = sukhArta:, blessed with happiness.
 * Some compounds with -RNa, e.g.: pra + RNam = prArNam, principal debt; RNa + RNam = RNArNam, a second mortgage.
 * When a preposition ending in -a precedes a > root beginning with R-, as upa- + Rchchhati = upArchchhati.

When a or A is followed by e or ai and o or au, then ai and au are the substitutes, e.g.: kRShNa + ekatvam = kRShNaikatvam, oneness with Krshna; deva + aishvaryam = devaishvaryam, divine majesty; sA + eva = saiva, she alone; bhava + auShadham, medicine against reincarnation; vidyA + autsukyam = vidyautsukyam, longing for wisdom.

Exceptions

 * When a preposition ending in -a precedes a >root beginning either e- or o-, then e or o is the substitute, e.g.: pra + ejate = prejate, quakes severely.

title: Sanskrit/Sandhi


text:
Cookbook:Colcannon

| Cuisine of Ireland | Cuisine of Scotland

Colcannon is a rich mashed potato dish with cabbage, butter, and other ingredients. It's very easy to make and is a nice change from ordinary mashed potatoes. Its sloppiness is balanced by the crunch of the cabbage, and it should taste a little peppery.

Ingredients

 * 450 g potatoes (floury Maris Piper or Golden Wonders are best; leave skin on if you want)
 * 150 ml single cream
 * Mace
 * Ground paprika
 * 450 g white or savoy shredded cabbage
 * 2 small leeks or 1 bunch of spring onion tops, chopped
 * 125 g unsalted butter
 * 200 g mature Gouda cheese, grated
 * Salt
 * Pepper

Procedure

 * 1) Boil or steam the potatoes until soft, then shake the drained spuds in a deep pot with the lid on, until they crumble.
 * 2) Mash the crumbled potatoes up with a fork and season with the salt, pepper, and mace/paprika, before stirring in the cream.
 * 3) Add 100 g of the butter in pieces and put the lid back on, leaving the butter to melt, then stir. Transfer the mix to a clean bowl.
 * 4) Blanch the cabbage in boiling water for 2 minutes and drain.
 * 5) Fry the leeks in the remaining butter for a few minutes, then add the cabbage and toss around for a few more minutes.
 * 6) Spoon the cabbage into the bowl and mix with the mashed potatoes.
 * 7) Stir the gouda into the mix, leaving a little to coat the top. Put the bowl in an oven on 2/3 heat for 20 minutes or until the cheese is melted.

Notes, tips, and variations

 * The mixture may be turned into a greased pie dish, sprinkled with grated cheese, dotted with butter or margarine, and browned in a hot oven.
 * Is especially good with dark greens such as savoy cabbage or kale.
 * The Gouda is an innovation—leave it out, if you don't want the dish too rich.
 * The oven heating is ideally done along with the final stage of your roast meat.
 * Seasoning is very important: bear in mind that the cheese has plenty of salt.
 * The perfect colcannon has a butter sogginess at the bottom of the bowl when removed from the oven.

title: Cookbook:Colcannon