text:
User talk:Panic2k4/Archive1

monolithic versions
Hi Panic. I thought you might be interested to see how the Computer Science:Data Structures book has an Computer Science:Data Structures:All Chapters view of the book, which gives a monolithic version of the same book. As you can see this is accomplished through transclusion. I've made special _content pages for each chapter, so that way there can be a view of the book that is chapter by chapter with a navigation bar, and a view of the book that is all chapters, without navigation bars. I think it would be a good idea to start doing this for the C++ book, so that the C -/- -/- book won't be necessary. MShonle 21:01, 7 September 2005 (UTC)

Fork Warning
Since this issue has been brought to my attention I have reviewed the forking policy. The separate books Programming:C plus plus and Programming:C -/- -/- will be merged into a single book. The monolithic book versus separate chapters conflict shall be resolved by including an All Chapters page that is a transclusion of all of the sub-modules (as I've described above). The book Programming:C -/- -/- and its subpages will be deleted in two weeks (roughly around September 21, 2005). You can request the material can be available (in some form) for a period longer than the two weeks.

Forking can harm Wikibooks in that it divides the community effort into producing a Wikibook, essentially lengthening the time it creates to finish a Wikibook and creating redundant information. This policy aims to encourage community cooperation, unify contributor effort, and reduce the amount of redundant material on Wikibooks.

It is against policy to fork and any re-creations of the same module (or similar) will become a candidate for speedy deletion. I think it's unfortunate that concensus couldn't have been reached on this issue that had a technical solution. I encourage you to keep on contributing to the C++ book and I appologize that for a long time you have been sent mixed and ambiguous messages from the Wikibooks administration. I hope that we can serve you better by being more consistent with the application of our policies. MShonle 02:18, 8 September 2005 (UTC)

Panic, I appreciate that you are working on the merge, however I must ask you to stop using the name Programming in C -/- -/- or any other name that uses those hyphens and slashes. The correct name to use is "plus plus". I've move-protected the pages now so you will not be able to revert. MShonle 18:58, 10 September 2005 (UTC)

LISP
BTW, what do you have against Lisp? Both Scheme and CLOS are quite excellent. :-) --MShonle 01:20, 11 September 2005 (UTC)

Lisp is hard to write, the logic is hard to fallow and reading in not so easy also, the major problem is there aren't any good IDEs for the language, as for Scheme I have not used it but have looked at it, it seems to provide more ease of use but again at the time I didn't find a compiler for it, a problem I have with Scheme is that it is being used as an introductory language in many Universities in place of Pascal and C... CLOS I don't know at all... (I'll check it out)--Panic 01:55, 11 September 2005 (UTC)
 * A great Scheme environment is PLT Scheme (the site also has references to great books, although the real classic book is The Structure and Interpretation of Computer Programs, also available on the web). I've seen some hard to follow Scheme programs, but then again, I've seen hard to follow programs in any language that I've had to work with. I recommend you start reading SICP... after the first 150 pages your mind might be blown. :-)
 * I think the first undergraduate course in programming should be Scheme, just as Berkeley, UofChicago, and MIT do. I TAed this introductory Java course last year, and I have to say that most of the time was wasted on little details, such as the difference between while and for, or what break is, or that super-constructors are called by default, or what public, private, and protected are. These are important concepts, but they missed the whole idea of what abstraction was. Learning Scheme, on the other hand, all you really have to work with is abstraction. The language itself is much simpler and that forces you to write better abstractions. I think for the second course students should learn all of the little details of the current "fad" language. So C++ or Java is appropriate then, but only after they learned abstraction, not Programming Complex Things Through a Bunch of Complex Examples and Exceptions I've Seen. MShonle 02:54, 11 September 2005 (UTC)

Minor Edits
Panic,

I have noticed that all your edits are flagged as "minor". Is that indendet? because i believe adding a new comment to a discussion is not minor. What is your view on minor / non-minor edits? --Max 16:44, 23 September 2005 (UTC)

Programming:C plus plus/Charter
I edited the charter page of the "C plus plus" book to use a table and some fancy-shmancy CSS. This way the text will automatically center in each browser, and doesn't depend on the resolution or the size of the browser window. If you don't like the change, you are free to revert it and it won't hurt my feelings at all. I also just used some simple grayscale coloring, so you can change that as well if you want some more "pizzaz". -- 21:21, 8 December 2005 (UTC)

Page renaming
I see you are discussing renaming of C++ book. If you want to have a tool making such renaming automatic, please visit Staff lounge and sign your support vote. Today we have to move all pages manually and then fix all the links. tsca.bot does it automatically. --Derbeth talk 19:45, 13 January 2006 (UTC)

Deleting pages
When you are attempting to delete pages, I would like to ask you to use the markup template   instead of blanking the page. Page blanking is more commonly used by vandals, and it is harder for us to keep track of where everything is at when you do that. It also allows us to review the content of the page for a second opinion as to if it was legitimate to remove the content.

BTW, thanks for trying to help clean up Wikibooks. That is appreciated. --Rob Horning 18:52, 23 January 2006 (UTC)

C++ Programming/All Chapters
I noticed you reverted my small change and added a print friendly version, however there was one already at C++ Programming/Print so now there's a duplicate. Your version is more maintainable since it includes from the other page which is good, I was thinking though, one page would make more sense for people who have a slow connection since having to go to yet another page would require long waiting again. Is your issue with the licence and print template? The print template could be removed and the license could be made to show up only when printed that way on screen it would look just as it does now yet includes the license when printed. --darklama 17:27, 16 September 2006 (UTC)

I use the monolithic version to get the feel of the flow of the work, check the basic format, see duplications, stuff out of order and from time to time run a spell check see that wikipedia links are done only once (and in reading order), if you can remove the toc and the license on a single page and provide the license on printing of the page I don't have any objection...--Panic 22:49, 16 September 2006 (UTC)

I noticed you readded Multi Paradigm chapter. Did you not notice that it was removed because I added its contents to Programming Paradigms once I cleaned up that chapter? So now the contents is on All Chapters twice. --darklama 04:09, 18 September 2006 (UTC)

Sorry its been hard to keep up with your esthetic changes to the book, the chapters are to be split into smaller parts not aggregated, btw I feel very strongly about the use of the phrase "The statically-typed free-form multi-paradigm programming language" it was used in a sub chapter but as your changes have removed the by point explanation, I would like to keep it in the main since C++ is a statically-typed free-form multi-paradigm programming language and chapter one deals in explaining what C++ is...--Panic 10:34, 18 September 2006 (UTC)

I have no intension of combining everything into one big page, thats what All Chapters is for. I do though see no need to split one concept across different pages if there small, as was the case with Programming Paradigm and Multi Paradigm. I think "statically-typed free-form multi-paradigm programming language" is a bit long for a chapter/section/part name and only one chapter explains what this is. I used "What is Programming?" because the chapters in this section/part deal for the most part with general programming concepts not tied to a specific programming language. My changes for the most part are esthetic right now, because I'm trying to clean up whats already there, by rearrange, clarifying and removing duplicate explanations, before adding new material.

BTW, I see you didn't like my changes to the names of the appendixes because I used C++ in their names. I did that for people printing out the wikibook, so that on paper it would be easier to tell it belongs to a book on C++. I think "Internal References" and "External References" didn't make much since either. Whats in "External References" isn't references at all, but resources for tools, websites and books, which is why I had changed it to "C++ Resources", then there was no need to make a distinction between "External" and "Internal". I changed "Source Code Examples" to "C++ Examples" because I don't think there needs to be emphases on the examples being source code. I didn't change "Extra Concepts" because I'm not sure that these things should even be part of this wikibook, maybe different wikibooks and linked to from the Resources appendix. --darklama 15:12, 18 September 2006 (UTC)

I haven't said that it was your intention but that was "our" intention (editors) as specified under the conventions, to reduce page sizes, I had done a bit of the indexing of what was on each part to the "main" page, up-to the classes...

I do agree that "statically-typed free-form multi-paradigm programming language" is a bit long and I don't like a separation of the book in Parts like Basic and Advanced, I can live with the separation in parts but I strongly object to the removal of the phrase being evident on the book/toc. It was my intention of voting for the rename of the book in a future stage (there is old cover image)...

The "Internal References" are the reference pages already included on the book, no more no less, they were on an Appendix just to give some logic structure and be easier to see.

"External References" is self evident, it refers to any non wikibook reference, some are real references some are just resources but as people tend to add to that list it's just easier to aggregate all there, I don't like to see IRC channels under Web References as you have done but I can live with it.

I will reformat the changes you made on the examples to preserve the navigation, but they will still exist under the /examples/ ...

As for the use of "C++", I try to hunt down every extra use of the qualifier since it's self evident that the content is about C++ and removing it can make parts of the book easier to use on other works, and it's just visually UGLY to see it repeated over and over, and saves space in wikibooks :) ...

ie: "the C++ programming language" -> "the programming language" "C++ objects" -> "objects" etc...

Btw I didn't like your over-simplification of the Paradigms part, you removed some logical steps that exist on the original "wikipedia" article that gives the reader not only the evolution of the concepts but removes the identification of layers of the OOP model that can of use to the coder/reader... In C++ we are free to do as we like, that was the NPOV that the "statically-typed free-form multi-paradigm programming language" phrase transmits, many people argues that we should use only one model, I for one like to mix all as to produce the simpler solution to problems...--Panic 19:10, 18 September 2006 (UTC)

Not all pages listed under "Internal References" are included on some page like is claimed. I didn't add IRC channels to Weblinks, someone else did. I simply think based on how "External References" is currently being used, it makes more sense to refer to the contents as a collection of resources rather then as a reference. I don't have a problem with "C++" being removed from the contents of the pages, I think it just makes sense in the title of the Appendixes. By making the pages under "Getting Started" more general and more of an introduction to general programming concepts less reference to "C++" should be needed to make clear weither whats being discussed is specific to C++ or not.

My intention was to simplify the explanations of the different paradigms used by C++, while waiting to get into the specifics of how C++ implements the OOP layers or other programming concepts until later chapters. I don't have a problem with identifing and explaining different programming modules if they are explained in more general terms in "Programming Paradigms" and/or fully explaining in later chapters, such as in the "Object and Object-Oriented Programming" section, once the C++ OOP concepts thats relied on have been explained. This way concepts aren't explained twice and readers aren't forced to jump around in the text in order to understand whats being said, which just looks ugly to me. I hope you understand my issue was not with the different layers of the OOP model being explained, but with when and where its explained. --darklama 22:04, 18 September 2006 (UTC)

Sorry but all pages listed under "Internal References" are included on some page like is claimed on the index, or they were when I've added and listed them ... I didn't say you have added non web links to the web resources in the "External References", but I've noticed that you named them as "web" references in one of your edits... Is there a technical text that doesn´t involve the readers to jump around in the text in order to understand concepts ? tech. books aren't to be read like a novel, most are used as reference books, some parts are for and needed to beginners and others are needed to refresh even the most experienced user or one that was using a similar technology or just to keep up with need concepts. Of course that a logical structure must be enforced but for instance I really don't agree in moving the debugging concept to the end of the book any beginner needs to know how to do it and for what purpose... What hirks me is that as you say "I'm trying to clean up whats already there, by rearrange, clarifying and removing duplicate explanations, before adding new material.", you surely understand that as the only editor that has been contributing to the book in a non-punctual way, I tend to see it as mostly "my" work, and it is with some pain that I see you doing major restructuring without contributing real content or debating the matter, even removing or shuffling parts that I see as important, I agree that this is a community effort but you can also try to see it from my point of view.--Panic 22:16, 20 September 2006 (UTC)

Could you be more specific on what edit(s) involving "External References" your referring to? I'm not sure what you mean and its hard for me to address them without context (a history link would be helpful). I agree technical text books are used by all kinds of audiences from beginners to the more experienced as references, to learn from and to refresh on and are not novels. I was speaking of some logical structure in which concepts are built on one another in some natural flow when speaking of not having to jump around. I think first time readers may have some trouble understanding this wikibook and those readers who are trying to refresh or use this wikibook as a reference may have trouble quickly finding what it is they are looking for. This is why my focus right now is not on adding much in the way of new material. I mean no offense to you and everyone else who has contributed their time, energy and work on this wikibook. I see this as just being a common accurance of an incomplete/unfinished work.

I have added lots of redirects from Programming:C plus plus that are no longer referenced to speedy deletion in hopes of making it easier to find what remaining information is under this wikibook name, so that it may be moved to the "C++ Programming" wikibook if appropriate. All the redirects make it a bit hard to locate the trees from the forest, so this should make it easier. --darklama 17:47, 21 September 2006 (UTC)

The merge is completed, all of the Programming:C plus plus should have been deleted some time ago at least 2 people said they would do it, it seems none did... but if you can now mark them for deletion at least someone removed the write protection ,see the discussion area for more info... --Panic 18:53, 21 September 2006 (UTC)

Ya I saw some of the discussion area where it said it would be done which seemed dated and I could see they were still present for whatever reason. The discussion area is a bit disoragnized and is hard for me to tell what still applies or not. I decided to go ahead and at lest attempt to get deleted, what looks like could be safely deleted. Some pages are still locked however, perhaps this is the time to try to get that changed. --darklama 20:10, 21 September 2006 (UTC)

title: User talk:Panic2k4/Archive1


text:
User talk:205.211.112.3

Hi! welcome to Wikipedia!

Hope you enjoy contributing to Wikipedia. Be bold in editing pages, but please don't vandalise the hacking page. Here are some links that you might find useful:

 * Try the Tutorial. If you have less time, try How to edit a page.
 * To sign your posts (on talk pages, Votes for deletion page etc.) use 	 ~ (four tildes). This will insert your name and timestamp. To insert just your name, type (3 tildes).
 * You can experiment in the test area.
 * You can get help at the Help Desk
 * Some other pages that will help you know more about Wikipedia: Manual of Style and Policies and Guidelines, Neutral point of view, Civility, What Wikipedia is not
 * If you made IP edits before creating a user account, you can attribute your IP edits to your account at Changing attribution for an edit.

I hope you stick around and keep contributing to Wikipedia. Drop a note at New user log.

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

title: User talk:205.211.112.3


text:
User:Bduttabaruah

I am listed as Bduttabaruah in Wikipedia.

At Wikibooks I am presently working on
 * contributing to Orthopedic Surgery
 * creating and organising Health Sciences
 * cleaning up Medicine.

title: User:Bduttabaruah


text:
Cookbook:Pastry Bag

A pastry bag, also known as a piping bag, is used to pipe (extrude) semi-solid foods. Pastry bags are often coupled with piping tips or nozzles, which shape the extruded material. This is generally a matter of aesthetics, most famously cake decoration. Aside from icing, pastry bags are commonly used to shape meringue and whipped cream, and to fill donuts with jelly or custard. When presentation is especially important, fluted tips can be used to shape savory foods such as filling for deviled egg, whipped butter, and mashed potatoes.

Many foods (including frosting and pressurized "spray can" whipped cream) can be purchased in disposable packaging designed to serve the function of a pastry bag.

Bags
Pastry bags can be either reusable or disposable. High-quality, reusable pastry bags are often made from waterproofed cloth. Disposable bags are typically made of food-grade plastic. Both can be coupled with reusable piping tips—when using disposable bags, the tip is simply removed before discarding the bag.

A simple pastry bag can be made by rolling cooking parchment or wax paper into a cone, filling it, folding the wide end several times to close it, and then cutting the tip into whatever shape is desired. This is especially useful for small quantities of melted chocolate, since a very small hole can be cut and the bag can be discarded when it cools and becomes clogged.

Tips and nozzles
Piping tips are cone-shaped, with a base too large to fit through the small opening in the bag; they are to be inserted through the larger opening before food is spooned in. Many types of piping tip are available, coming in an array of shapes and materials. Tips are typically made of stainless steel, chrome-plated metal, or food-grade plastic. Circular nozzles are quite useful for making round shapes. The tip shown in the far left of the photo is a hypodermic-shaped one for filling pastries such as cream puffs, and many other types of nozzle are available for making star, leaf, and flower-petal shapes.

Tips may be inserted directly into the pastry bag or used with a coupler. Use of a coupler allows the chef to change the tip without needing to empty and refill the bag.

How to use
Once the proper tip is installed, fill the bag through the end with the wider opening, roll or twist it closed, and then squeeze it like a tube of toothpaste (from the top down, keeping the lower portion bulged out) to pipe its contents.

title: Cookbook:Pastry Bag


text:
User talk:SamuraiClinton~enwikibooks

Come introduce yourself at the new users page. If you have any questions, you can ask there or contact me personally. Kellen T 06:47, 25 September 2005 (UTC)
 * For the dance listings, you may wish to look at Naming policy, and try to use the subpage notation, e.g. Dance/Salsa instead of a top-level Salsa module.

 * Well, the Salsa article was made before the List of dances article was made. --Wikamurai 23:28, 25 September 2005 (UTC)

 * That's fine. Just seems more logical to have all of the dance pages under a single book namespace. Kellen T 23:38, 25 September 2005 (UTC)

Gmail
Why did you nominate this page for speedy deletion? It's a cover page, a common practise in Wikibooks. --Derbeth 11:38, 26 September 2005 (UTC)
 * As you can see, your nomination for speedy deletion was rejected by a sysop. Don't you understand what a book cover is? See German, our Collaboration of the Month. --Derbeth 18:48, 26 September 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 SamuraiClinton. To make sure that both of you can use all Wikimedia projects in future, we have reserved the name SamuraiClinton~enwikibooks that only you will have. If you like it, you don't have to do anything. If you do not like it, you can pick out a different name.

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

Sorry for the inconvenience.

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

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

title: User talk:SamuraiClinton~enwikibooks


text:
Cookbook talk:Pastry Bag

This module was originally adapted from a wikipedia module.

title: Cookbook talk:Pastry Bag


text:
CAT-Tools/DéjàVu X/get file navigator or autosearch portions found windows back

Write the following lines in any editor and save them in a file called "anyname.reg"

REGEDIT4

[HKEY_CURRENT_USER\Software\ATRIL\DejaVuX] "MenuLayout"=-

[HKEY_CURRENT_USER\Software\ATRIL\DejaVuX] "MenuUsage"=-

Then double-click on this file and accept adding it to the registry. You're done :)


text:
Orthopaedic Surgery/Upper Limb

CHAPTER 2: Upper Limb

Shoulder

 * Disorders of The Rotator Cuff
 * Impingement Syndrome
 * Calcification of Rotator Cuff
 * Disorders of Biceps Tendon
 * SLAP lesions
 * Adhesive Capsulitis
 * Instability of The Shoulder
 * Anterior Instability
 * Posterior Instability
 * Multidirectional Instability
 * Disorders of the Glenohumeral Joint
 * Tuberculosis
 * Rheumatoid Arthritis
 * Osteoarthritis
 * Rapidly Destructive Arthropathy
 * Osteonecrosis
 * Glenohumeral Arthroplasty
 * Disorders of Scapula and Clavicle
 * Scapular Instability
 * Grating Scapula
 * Septic Arthritis of Sternoclavicular joint
 * Sternoclavicular Hyperosteosis
 * Osteoarthritis of Acomioclavicular Joint

Elbow

 * Acquired Deformities
 * Cubitus Varus
 * Cubitus Valgus
 * Pulled Elbow
 * Osteochondritis Dissecans
 * Loose Bodies
 * Tuberculosis
 * Rheumatoid Arthritis
 * Gout and Pseudogout
 * Osteoarthritis
 * Neuropathic Arthritis
 * Stiffness of Elbow
 * Recurrent Elbow Instability
 * Repetitive Strain Sydromes
 * Lateral Epicondylitis
 * Medial Epicondylitis
 * Baseball Pitcher's Elbow
 * Bursitis

Wrist

 * Wrist Pain
 * Acquired Deformities
 * Chronic Instability of The Wrist
 * Instability of Distal Radio-Ulnar Joint
 * Longitudinal Instability of Radio-Ulnar Joint
 * Disorders of Triangular Fibrocartilage Complex
 * Carpal Instability
 * Kienbock's Disease
 * Tuberculosis
 * Rheumatoid Arthritis
 * Osteoarthritis
 * Radio-Carpal Osteoarthritis
 * Distal Radio-Ulnar Arthritis
 * Carpometacarpal Osteoarthritis
 * Scapho-Lunate Advanced Collapse
 * Tenosynovitis
 * De Quervain's Disease
 * Intersection Syndrome
 * Flexor Tendinitis
 * Repetitive Syndromes
 * Ganglions
 * Simple Ganglion Cysts
 * Compound Palmar Ganglion
 * Carpal Tunnel Syndrome
 * Distal Radius Fractures

Hand
See Hand and Microsurgery

title: Orthopaedic Surgery/Upper Limb


text:
Computer Programming/Agent Oriented Programming

Agent Oriented Programming
'''Agent-oriented programming is a fairly new programming paradigm that supports a societal view of computation. In AOP, objects known as agents interact to achieve individual goals. Agents can exist in a structure as complex as a global internet or one as simple as a module of a common program. Agents can be autonomous entities, deciding their next step without the interference of a user, or they can be controllable, serving as a mediary between the user and another agent.

An agent, according to (Shoham, 1993) is "an entity whose state is viewed as consisting of mental components such as beliefs, capabilities, choices, and commitments". This definition is cryptic at best and useless at worst. In his paper, Shoham narrows this definition by applying the criterion of Dennet and McCarthy. Dennet recognized that many simple, inanimate objects can be viewed as falling into this framework (which he calls the intentional stance). McCarthy suggests that mental attributes should be ascribed to objects when they are "useful".

Consider, for example, the agent 'gravity'. Gravity can be viewed as an entity that is capable of applying force to objects and chooses to do so to every object it encounters. Taking the example even further, we can say that gravity can choose to apply this force in any direction and with any strength; it merely chooses to do so in a 'down' direction at 9.8m/s2 (on Earth when the second object has negligible mass compared with the first). This is not too far from the belief of many individuals before Galileo's experiments. These days, however, this view gains us nothing; it is not useful.

Consider, now, an autonomous rover on the surface of Jupiter's moon, Europa. The robot can be viewed as an agent that believes that the places with the roughest ice patches are the thinnest layers of ice. It might desire to set up drilling in those areas. It might not be capable of navigating very rocky terrain, and might therefore want to avoid such situations. These are reasonable, and possibly useful, ascriptions of mental attributes. Indeed, it might be useful to produce code with this perspective in mind. This is the reasoning behind agent-oriented programming.

Shoham suggests that an AOP system needs each of three elements to be complete :

 * A formal language with clear syntax for describing the mental state. This would likely include structure for stating beliefs (e.g. the predicate calculus), passing messages, etc. Most of the research in the field has been on this portion and stresses the semantic issues related to artificial intelligence.
 * A programming language in which to define agents. The semantics of this language should be closely related to those of the formal language. In many situations, functionality will be difficult or impossible to implement and further limitations will be introduced. We will see this in more than one case.
 * A method for converting neutral applications into agents. This sort of tool would allow an agent to communicate with a non-agent by attributing intentions much the same way as we did with the inter-planetary rover above. This portion of the specification is not related to the language issues and will not be discussed here.


text:
Cookbook:Marinara Sauce

| Cuisine of Italy | Sauces

Marinara (mariner's) sauce is a southern Italian tomato sauce usually made with tomatoes, garlic, herbs (such as basil), and onion. However, there are many variations. Some of these include the addition of capers, olives and spices.

There are at least two folk theories as to the origin of this sauce: One says cooks aboard Neapolitan ships invented marinara sauce in the mid-16th century after Spaniards introduced the tomato (a New World vegetable) to Europe. This meat-free sauce was easy to make and resisted spoiling due to the high acid content of tomatoes. This made it ideal for lengthy sea voyages hundreds of years before refrigeration methods were invented. Another theory states this was a sauce prepared by the wives of Neapolitan sailors upon their return from sea. Historically, however, we know the first Italian cookbook to include tomato sauce, Lo Scalo alla Moderna (The Modern Steward), was written by Italian chef Antonio Latini and was published in two volumes in 1692 and 1694. Latini served as the Steward of the First Minister to the Spanish Viceroy of Naples.

Traditional southern Italian cuisine utilizes this sauce to add flavor to pasta, rice, seafood and pizza. This sauce is also widely used in Italian-American cuisine which has diverged significantly from its Old World origins. Italians refer to marinara only in association with other recipes. For instance, spaghetti alla marinara literally translates to mariner's spaghetti. However, tomato sauce alone in Italy is called salsa al pomodoro or pummarola.

The recipe below is based on the one by world-renowned chef Mario Batali cited in the references section below.

Ingredients

 * 6 tablespoons virgin olive oil
 * 225 grams (8 ounces) Spanish onion, diced
 * 4 cloves garlic, thinly sliced
 * 2 teaspoons fresh thyme leaves (or ½ teaspoon dried)
 * 4 teaspoons fresh basil leaves (or 1 teaspoon dried)
 * 85 grams (3 ounces) red bell pepper, diced
 * 1.3 kilograms (1 pound and 14 ounces) skinless plum tomatoes, crushed by hand
 * 1 tablespoon sugar
 * Salt to taste

Preparation

 * 1) Heat the oil in a saucepan over medium heat until it shimmers.
 * 2) Add the onions and garlic, and sauté them for about 2 minutes until the onions are translucent.
 * 3) Add the thyme, basil and bell pepper. Cook 5 minutes more.
 * 4) Add the tomatoes and sugar. Bring to a boil and then lower to a light simmer, stirring occasionally for 30 minutes.
 * 5) Season with salt to taste.
 * 6) Serve hot by ladling over pasta, seafood or rice.

title: Cookbook:Marinara Sauce


text:
Cryptography/Prime Curve/Affine Coordinates

<Cryptography

Point Doubling (1I + 2M + 2S)
Let (x,y) be a point (unequal to the point at infinity) on the elliptic (prime) curve given by the equation y^2 = x^3 + ax + b. Then the point (x',y') := 2*(x,y) can be computed by

if (y == 0) return POINT_AT_INFINITY else l = (3*x^2 + a) / (2y) x' = l^2 - 2x y' = l(x - x') - y  return (x', y')

Point Addition (1I + 2M + 1S)
Let (x1,y1) and (x2,y2) be two points (both unequal to the point at infinity). Then the point (x3,y3) := (x1,y1) + (x2,y2) can be computed by

if (x1 == x2) if (y1 != y2) return POINT_AT_INFINITY else return POINT_DOUBLE(x1, y1) l = (y2 - y1) / (x2 - x1) x3 = l^2 - x1 - x2 y3 = l(x1 - x3) - y1 = l(x2 - x3) - y2 return (x3, y3)

Point decompression
The following algorithm calculates for a given x a value y, such that (x,y) is a point on the elliptic curve. t = x^3 + ax + b if (t|p) >= 0 return y = sqrt(t) (the result y = -sqrt(t) would be correct, too) else return POINT_NOT_EXPANDABLE

Notes:
 * (t|p) denotes the Legendre symbol of t, which decides whether t is a square number or not.
 * 1) The square root can be calculated using the Algorithm of Shanks & Tonelli.


text:
Cryptography/Prime Curve/Standard Projective Coordinates

<Cryptography

Introduction
Standard Projective Coordinates are used to represent elliptic curve points on prime curves y^2 = x^3 + ax + b. Their usage might give a speed benefit over Affine Coordinates when the cost for field inversions is significantly higher than field multiplications. In Standard Projective Coordinates the triple (X, Y, Z) represents the affine point (X / Z, Y / Z).

Point Doubling (7M + 5S or 7M + 3S)
Let (X, Y, Z) be a point (unequal to the point at infinity) represented in Standard Projective Coordinates. Then its double (X', Y', Z') can be calculated by if (Y == 0) return POINT_AT_INFINITY W = a*Z^2 + 3*X^2 S = Y*Z B = X*Y*S H = W^2 - 8*B X' = 2*H*S Y' = W*(4*B - H) - 8*Y^2*S^2 Z' = 8*S^3 return (X', Y', Z')

Note: if a = -3, then W can also be calculated as W = 3*(X + Z)*(X - Z), saving 2 field squarings.

Point Addition (12M + 2S)
Let (X1, Y1, Z1) and (X2, Y2, Z2) be two points (both unequal to the point at infinity) represented in Standard Projective Coordinates. Then the sum (X3, Y3, Z3) can be calculated by U1 = Y2*Z1 U2 = Y1*Z2 V1 = X2*Z1 V2 = X1*Z2 if (V1 == V2) if (U1 != U2) return POINT_AT_INFINITY else return POINT_DOUBLE(X1, Y1, Z1) U = U1 - U2 V = V1 - V2 W = Z1*Z2 A = U^2*W - V^3 - 2*V^2*V2 X3 = V*A Y3 = U*(V^2*V2 - A) - V^3*U2 Z3 = V^3*W return (X3, Y3, Z3)

Mixed Addition (with affine point) (9M + 2S)
Let (X1, Y1, Z1) be a point represented in Standard Projective Coordinates and (X2, Y2) a point in Affine Coordinates (both unequal to the point at infinity). A formula to add those points can be readily derived from the regular standard projective point addition by replacing each occurrence of "Z2" by "1" (and thereby dropping three field multiplications).


text:
Cryptography/Prime Curve/Jacobian Coordinates

<Cryptography

Introduction
Jacobian Coordinates are used to represent elliptic curve points on prime curves $$y^2 = x^3 + ax + b.$$ They give a speed benefit over Affine Coordinates when the cost for field inversions is significantly higher than field multiplications. In Jacobian Coordinates the triple $$(X, Y, Z)$$ represents the affine point $$(\frac{X}{Z^2}, \frac{Y}{Z^3})$$.

Point Doubling (4M + 6S or 4M + 4S)
Let (X, Y, Z) be a point (unequal to the point at infinity) represented in Jacobian Coordinates. Then its double (X', Y', Z') can be calculated by if (Y == 0) return POINT_AT_INFINITY S = 4*X*Y^2 M = 3*X^2 + a*Z^4 X' = M^2 - 2*S Y' = M*(S - X') - 8*Y^4 Z' = 2*Y*Z return (X', Y', Z')

Note: if a = -3, then M can also be calculated as M = 3*(X + Z^2)*(X - Z^2), saving 2 field squarings.

Repeated Doubling ((4m-1)M + (4m+2)S)
Let P=(X, Y, Z) be a point (unequal to the point at infinity) represented in Jacobian Coordinates. Then, in the case a = -3, its "m-fold double" (2^m)P can be calculated as follows: Y = 2*Y W = Z^4 while(m--) if (Y == 0) return POINT_AT_INFINITY A = 3*(X^2 - W)  B = X*Y^2 X = A^2 - 2B Z = Z*Y if (m) W = W*Y^4 Y = 2*A*(B - X) - Y^4 Y = Y/2 return (X, Y, Z)

An alternative repeated doubling routine with costs (4m)M + (4m+2)S for any value a can be derived from the Modified Jacobian doubling routine. For small values a (say 0 or -3) the costs reduce to (4m-1)M + (4m+2)S, competing nicely with the algorithm showed above.

Point Addition (12M + 4S)
Let (X1, Y1, Z1) and (X2, Y2, Z2) be two points (both unequal to the point at infinity) represented in Jacobian Coordinates. Then the sum (X3, Y3, Z3) can be calculated by

U1 = X1*Z2^2 U2 = X2*Z1^2 S1 = Y1*Z2^3 S2 = Y2*Z1^3 if (U1 == U2) if (S1 != S2) return POINT_AT_INFINITY else return POINT_DOUBLE(X1, Y1, Z1) H = U2 - U1 R = S2 - S1  X3 = R^2 - H^3 - 2*U1*H^2 Y3 = R*(U1*H^2 - X3) - S1*H^3 Z3 = H*Z1*Z2 return (X3, Y3, Z3)

J + J -> J ( 12M, 2S) (secp256k1 has 12M, 4S)
U1 = Y2 * Z1 U2 = Y1 * Z2  V1 = X2 * Z1  V2 = X1 * Z2  if (V1 == V2) if (U1 != U2) return POINT_AT_INFINITY else return POINT_DOUBLE(X1, Y1, Z1) U = U1 - U2 V = V1 - V2  W = Z1 * Z2  A = U ^ 2 * W - V ^ 3 - 2 * V ^ 2 * V2  X3 = V * A  Y3 = U * (V ^ 2 * V2 - A) - V ^ 3 * U2  Z3 = V ^ 3 * W  return (X3, Y3, Z3)

Mixed Addition (with affine point) (8M + 3S)
Let (X1, Y1, Z1) be a point represented in Jacobian Coordinates and (X2, Y2) a point in Affine Coordinates (both unequal to the point at infinity). A formula to add those points can be readily derived from the regular jacobian point addition by replacing each occurrence of "Z2" by "1" (and thereby dropping four field multiplications and one field squaring).

Mixed Addition (with chudnovsky point) (11M + 3S)
Let (X1, Y1, Z1) be a point represented in Jacobian Coordinates and (X2, Y2, Z2, Z2^2, Z2^3) a point in Chudnovsky Coordinates (both unequal to the point at infinity). Then the sum (X3, Y3, Z3) can be readily calculated using the addition formula given above (saving one field multiplication and one field squaring).


text:
Cryptography/Prime Curve/Chudnovsky Coordinates

<Cryptography

Introduction
Chudnovsky Coordinates are used to represent elliptic curve points on prime curves y^2 = x^3 + ax + b. They give a speed benefit over Affine Coordinates when the cost for field inversions is significantly higher than field multiplications. In Chudnovsky Coordinates the quintuple (X, Y, Z, Z^2, Z^3) represents the affine point (X / Z^2, Y / Z^3).

Point Doubling (5M + 6S or 5M + 4S)
Let (X, Y, Z, Z^2, Z^3) be a point (unequal to the point at infinity) represented in Chudnovsky Coordinates. Then its double (X', Y', Z', Z'^2, Z'^3) can be calculated by if (Y == 0) return POINT_AT_INFINITY S = 4*X*Y^2 M = 3*X^2 + a*(Z^2)^2 X' = M^2 - 2*S Y' = M*(S - X') - 8*Y^4 Z' = 2*Y*Z Z'^2 = Z'^2 Z'^3 = Z'^2 * Z' return (X', Y', Z', Z'^2, Z'^3)

Note: if a = -3, then M can also be calculated as M = 3*(X + Z^2)*(X - Z^2), saving 2 field squarings.

Point Addition (11M + 3S)
Let (X1, Y1, Z1, Z1^2, Z1^3) and (X2, Y2, Z2, Z2^2, Z2^3) be two points (both unequal to the point at infinity) represented in Chudnovsky Coordinates. Then the sum (X3, Y3, Z3, Z3^2, Z3^3) can be calculated by U1 = X1*Z2^2 U2 = X2*Z1^2 S1 = Y1*Z2^3 S2 = Y2*Z1^3 if (U1 == U2) if (S1 != S2) return POINT_AT_INFINITY else return POINT_DOUBLE(X1, Y1, Z1, Z1^2, Z1^3) H = U2 - U1 R = S2 - S1 X3 = R^2 - H^3 - 2*U1*H^2 Y3 = R*(U1*H^2 - X3) - S1*H^3 Z3 = H*Z1*Z2 Z3^2 = Z3^2 Z3^3 = Z3^2 * Z3 return (X3, Y3, Z3)

Mixed Addition (with affine point) (8M + 3S)
Let (X1, Y1, Z1, Z1^2, Z1^3) be a point represented in Chudnovsky Coordinates and (X2, Y2) a point in Affine Coordinates (both unequal to the point at infinity). A formula to add those points can be readily derived from the regular chudnovsky point addition by replacing each occurrence of "Z2" by "1" (and thereby dropping three field multiplications).

Mixed Addition (with jacobian point) (11M + 3S)
See ../Jacobian Coordinates/ for further details.


text:
Talk:International Relations/War and Peace in a Globalised World

I find the title fairly misguiding, as the text deals very little with war and peace. This is easily demonstrable by the fact that a search for "war" in the text only found it used 9 times, 5 of which is in reference to time periods - all of them in connection with the World Wars (eg. "in the post-World War II era"), 3 of them as parts of words with no direct connection to war ("toward", "warrant", "global warming") and 1 time in reference to the war on Iraq. The same search for "peace" turns up no(!) hits. I suggest a renaming is in order. --Kissekatt 10:15, 25 September 2005 (UTC)


text:
User talk:24.253.59.60

Kellen T 10:22, 25 September 2005 (UTC)
 * Please also check out the Cookbook policy page and the Cookbook talk pages.

title: User talk:24.253.59.60


text:
French/Grammar/Verbs

Pronominal verbs
Pronominal verbs are verbs that include pronouns. These pronouns are me, te, se, nous, and vous and are used as either direct objects or indirect objects, depending on the verb that they modify. When pronominal verbs are conjugated in perfect tenses, être is used as the auxiliary verb.

The following table shows which reflexive pronoun to use with each form of the verb:

Reflexive verbs
Reflexive verbs reflect the action on the subject.

 * Je me lave. - I wash myself.
 * Nous nous lavons. - We wash ourselves.
 * Ils se lavent. - They wash themselves.

Reflexive verbs can also be used as infinitives.

 * Je vais me laver. - I'm going to wash myself.

Either the conjugated verb or the infinitive can be negated each with slightly different meanings.

 * Je ne vais pas me laver. - I'm not going to wash myself.
 * Je vais ne pas me laver. - I'm going to not wash myself (for some period of time, e.g.).

In perfect tenses, the past participles agree with the direct object pronoun, but not the indirect object pronoun, in gender and plurality. Therefore it would only agree when the reflexive pronoun is the direct object. Also remember that the past participle does not agree with the direct object if it goes after the verb.

 * Elle s'est lavée. - She washed herself.
 * Nous nous sommes lavé(e)s. - We washed ourselves.
 * Elle s'est lavé les mains. - She washed her hands.
 * Nous nous sommes lavé les mains. - We washed our hands.

Here is an example conjugation of a reflexive verb:

1. The futur simple, passé simple, imperfect, conditional and subjunctive are all conjugated with the reflexive pronoun in the same position as in the present.

2. All reflexive verbs take être in the passé composé and therefore have an e added to the past participle for females and an s for plural.

3. When a reflexive verb is put as an infinitive behind any other verb (e.g. vouloir, pouvoir, aller...) it still takes the appropriate reflexive pronoun.

Reciprocal verbs
With reciprocal verbs, people perform actions to each other.

 * Nous nous aimons. - We like each other.

Like reflexive verbs, the past participle of reciprocal verbs agrees in number and gender with the direct object if it goes before the verb. It therefore agrees with all reciprocal pronouns that function as direct objects.

 * Nous nous sommes aimé(e)s. - We liked each other.

The reciprocal pronoun can also function as an indirect object without a direct object pronoun.
 * Nous nous sommes parlé. - We spoke to each other.
 * Elles se sont téléphoné. - They telephoned one another.
 * Vous vous êtes écrit souvent? - You wrote to each other often?

Naturally pronominal verbs
Some verbs are pronominal without performing a reflexive or reciprocal action.

 * Tu te souviens? - Do you remember?

In perfect tenses, these verbs agree with the direct object if it goes before the verb. Otherwise, the past participle agrees with the subject.

 * Elle s'est souvenue. - She remembered.

Some verbs have different meanings as pronominal verbs.

 * rendre - to return, to give back
 * se rendre (à) - to go (to)

ne..pas

 * Simple negation is done by wrapping ne...pas around the verb.
 * Je ne vole pas. - I do not steal.
 * In a perfect tense, ne...pas wraps around the auxiliary verb, not the participle.
 * Je n'ai pas volé. - I haven't stolen.
 * When an infinitive and conjugated verb are together, ne...pas usually wraps around the conjugated verb.
 * Je ne veux pas voler. - I do not want to steal.
 * ne pas can also go directly in front of the infinitive for a different meaning.
 * Je veux ne pas voler. - I want not to steal.
 * ne goes before any pronoun relating to the verb it affects.
 * Je ne l'ai pas volé. - I did not steal it.
 * Nous ne nous aimons pas. - We do not love each other.

Other negative expressions

 * ne...personne wraps around the entire verb set.
 * Je ne l'ai donné à personne. - I did not give it to anyone.
 * Je ne veux le donner à personne. - I do not want to give it to anybody.
 * ne...ni...ni requires two objects, either direct or indirect, and comes before them.
 * Je ne l'ai donné ni à mon frère, ni à ma sœur. - I gave it neither to my brother nor my sister.
 * Je ne peux voir ni mon frère ni ma sœur. - I am able to see neither my brother nor my sister.
 * In ne...aucun(e), aucun(e) goes before an object.
 * Il n'a aucun ami. Aucun. - He has no friend. None.
 * Il n'a aucune feuille de papier. Aucune. - He has no sheet of paper. None.
 * Il n'a qu'une feuille de papier. - He has only one piece of paper.
 * Je ne peux guère voir mon frère et ma sœur - I can hardly see my brother and sister.

Spoken French
Now, the 'ne' sometimes disappears when one speaks. However, it is always used in written French and for formal conversations.

 * Je ne l'ai donné à personne -> Je l'ai donné à personne (I didn't give it to anyone)
 * Je ne sais pas -> Je sais pas (I don't know)

Summary
To say not, never, or other negative verbs, you have to 'sandwich' the negative words around a verb.

Example:

 * Il n'y a pas de cinéma. (meaning: "There is no cinema")
 * On ne peut jamais aller en boîte. (meaning: "You can never go partying")
 * Il n' y a rien à faire ici. (meaning: "There is nothing to do here")

If " ne " is before a vowel then it changes to " n' ".

Francés/Gramática/El verbo フランス語/文法/動詞

title: French/Grammar/Verbs


text:
Template:High School Mathematics Extensions/Solutions/TOC

'''At the moment, the main focus is on authoring the main content of each chapter. Therefore this exercise solutions section may be out of date and appear disorganised.'''

If you have a question please leave a comment in the "discussion section" or contact the author or any of the major contributors.


text:
User:Nowicjusz~enwikibooks

I'm new here.

I'd like to contribute to this project and I hope you bear with me.

title: User:Nowicjusz~enwikibooks


text: CAT-Tools/Transolution

title: CAT-Tools/Transolution


text:
User:Rafikk~enwikibooks

Rafikk - EN Rafikk - PL

title: User:Rafikk~enwikibooks


text: Category:User rexx

title: Category:User rexx


text: Category:User html

title: Category:User html


text: Category:User sql

title: Category:User sql


text:
Template:Usersprogram

This category sorts programmers by expertise ( [ 1 = beginner], [ 2 = intermediate], [ 3 = advanced], [ 4 = expert] ).

This template displays the various programming language skill levels associated with a particular programming language, the syntax for adding a userbox to one's user page to indicate one's skill level, and also provides links to jump to a particular skill level in the resulting listing of users proficient in that programming language.

Usage
where "language" corresponds to the language code listed at Userboxes/Programming.

Example
produces the following:

title: Template:Usersprogram


text: Template:User blank-4

title: Template:User blank-4


text:
Talk:Rhetoric and Composition/Oral Presentations

--Mattbarton.exe 18:36, 25 September 2005 (UTC) This page has some good advice, but I think we need more paragraphs here and less bullets. It reads too much like a list of rules.


text:
Talk:Rhetoric and Composition/Writing in Business

--Mattbarton.exe 18:38, 25 September 2005 (UTC) This page seems to be coming along well.

This page looks almost there. I think it's a little heavy on resume/cover letter and a little light on the actualy foundation of business - memos, emails, proposals, reports. A little "beefing up" there would be good. Also, it might pay off to do a little editing. Whoever put this together did a very solid job, but sometimes their claims are a little vague, or their phrasing could be tightened up a little bit. --tigerrat29 21:35, 11 October 2006 (UTC)

Anyone know what happened to proposals and business plans?

useless pictues
Why are there pictures in this page? It's possible pictures might make it visually more pleasant but they currently don't, and have little to do with the content. liblamb 19:06, 8 November 2005 (UTC)

I agree. I don't get it. --Mattbarton.exe 21:35, 10 November 2005 (UTC)

I think an example email and more on business proposals would be helpful. --Brttnyrhea 19:10, 4 November 2007 (UTC)


text:
Talk:Rhetoric and Composition/Editing

--Mattbarton.exe 18:40, 25 September 2005 (UTC) This page would benefit from the addition of section headings like the other pages.

-- 01 Dec Dennis G. Jerz. What about reorganizing this section to specify the difference between substantive editing and proofreading? Both are editing tasks, but I make a big deal about how substantive editing is vital in the early stages, and proofreading is a waste of time until your paper is in good shape. I prefer to use the word "revision" when I mean "making big changes in the structure" and "editing" only when I mean proofreading.

I think that's an excellent idea, Dennis. I do the same thing when I teach editing. --Mattbarton.exe 16:47, 7 December 2005 (UTC)

We're back in action
We're back to make this wiki #1.--Mattbarton.exe 23:45, 22 February 2007 (UTC)

--Peabody33 23:47, 22 February 2007 (UTC)== Nice to see Wiki again... ==

Hello, Wiki.

Editing vs. Revision
I was reading the comment about being sure to define the difference between editing and revising. I see that there is a section about that difference in the revision section of the book. I am wondering if students might automatically check out only the editing section rather than the revision section. My suggestion would be to include the same definition of the difference between editing and revision in BOTH sections... --Kyoung 00:38, 3 November 2007 (UTC)

I agree, Kim. I also wonder if we shouldn't rearrange the order of topics on the Rhet/Comp homepage. I think "Revision" should follow "Drafting," and "Editing should follow "Revision."--Joshboyd 23:54, 7 November 2007 (UTC)

I was wondering if "Editing Tips" should follow "Macro and Micro Level Editing" I was also wondering if we could maybe change Macro and Micro-Level Editing" to something like "Proofreading and Editing" or "The Difference Between Proofreading and Editing" or "Editing vs. Proofreading"  Just an idea. --Faithmarie22 04:57, 28 November 2007 (UTC)

I also think maybe we should delete that entire paragraph on the "Professor and the Madman." I don't think it relates because it is really neither about introductions nor editing, but I'm afraid to hit the trigger. Anyone with me?--Faithmarie22 18:44, 28 November 2007 (UTC) Update:  I did delete it, I suppose if anyone is opposed they can bring it back. --199.17.19.212 20:27, 28 November 2007 (UTC)

Macro/micro
I agree with you, Faith. The micro/macro editing section needs some work. I agree with both of your suggestions. I'm wondering if some of that first paragraph called micro/macro editing needs to be removed all together. What do you all think? It seems like a lot of mumble jumble (kind of like this posting of mine :-) ).--Kyoung 05:21, 2 December 2007 (UTC)

Also, overall do some sections seem to be more about composing than actually editing. Perhaps we need to rework some of these sections so they focus more on editing.--Faithmarie22 00:36, 3 December 2007 (UTC)

--Joshboyd 23:46, 5 December 2007 (UTC) I think we should move the first sections (i.e. Introductions, thesis statements, etc.) into a section on either composing or revising. When I think of editing, I think of small changes, not rewriting my introduction or even evaluating my introduction to see if it makes sense. Anyone opposed? If not, let's clean out this section.

I am not opposed, I do not think they belong in the editing section -- but I don't think we can ignore overall editing either - the overall structure, meaning, clarity, organization, etc.. Not JUST minor changes. I'm not sure if that's what you meant.--Faithmarie22 (talk) 20:23, 13 December 2007 (UTC)

Matt's Thoughts
I'm a bit short on time here, but I've made some changes to this chapter's overview to hopefully better explain the distinction between editing, revising, and reviewing. They are obviously closely related, but it seems worthwhile to consider them independently, since they have different problems associated with them. Briefly:

Editing - going over a document and deciding what should be changed. Usually this is limited in composition textbooks to mean writing style (sentence structure, word choice, tone, etc.), though in the industry it could mean any kind of changes (an editor at a newspaper could ask for a re-write or reject a piece outright). It seems most useful here to go with the traditional understanding, just focusing on how to improve sentences, check for offensive tone, adding helpful examples, reading aloud to eliminate harsh-sounding prose, etc.

Revising - actually making the changes. I separate this because it is easy to introduce new errors when you are trying to fix old ones. The basic advice is this: If you change one word, re-read the whole sentence and edit accordingly. If you change a sentence, re-read the whole paragraph and edit accordingly; you get the idea. I also like to focus on revising the intro, since most writers introduce new ideas as they draft and forget to go back and include them in the introduction.

Reviewing - editing another writer's work. Most of what is in the editing section will apply here, but it's worth focusing on how to be diplomatic here and not offend someone. It's basically a chapter on how to offer constructive criticism.

Hope this helps!!! --Mattbarton.exe (talk) 23:16, 13 January 2011 (UTC)

Matt H's thoughts
“The actual process of changing the introduction is called revising and comes with own set of difficulties.” – should be “with *its* own set of difficulties.” (So is this a potential edit, or revision?)

I would also rewrite the following:

“A book written by Richard Lanham titled Analyzing Prose is a great tool for writers looking to pick up ideas for new styles.”

… as:

“Richard Lanham’s Analyzing Prose is a great tool for helping writers generate ideas for new styles.”

--Matt.helm (discuss • contribs) 02:51, 27 January 2011 (UTC)

Emily's Thought(s)
Could the "Editing Checklist" contain links to examples?

In general, does it make sense to have all the external links at the bottom? Or should they be included throughout the section? --Emily.isackson (discuss • contribs) 20:52, 27 January 2011 (UTC)

Karl's Thoughts
I agree with Emily that the "Editing Checklist" might benefit from links to examples. In my own case, I prefer external links included throughout each section, links that expand upon a subject if so desired.

title: Talk:Rhetoric and Composition/Editing


text:
User talk:Nateji77~enwikibooks

Come introduce yourself at the new users page. If you have any questions, you can ask there or contact me personally. Kellen T 18:45, 25 September 2005 (UTC)
 * Please also check out the Cookbook policy page and the Cookbook talk pages.

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

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

title: User talk:Nateji77~enwikibooks


text:
CRE Loaded Features

CRE Loaded
CRE Loaded is a content management program for creating online shops - from products to payments. For short this is simply known as "shopping cart" or "cart" software.

CRE Loaded is derived from another shopping cart called osCommerce - it has inherited all of its features and has added many more. This book aims to act as a reference for CRE Loaded users, imparting a thorough understanding of the all the features of CRE Loaded including those it shares with its parent. It assumes that the user does not look after the internet server on which it runs or the underlying code for the site. The book assumes users have already got a CRE Loaded Site up on the server and ready to go.

The version of CRE Loaded this book refers to is 6.15 throughout.

Contents

 * 1) /Introduction/
 * 2) /Administration/
 * 3) /Configuration/
 * 4) /Catalog/
 * 5) /Info System/
 * 6) /NewsDesk/
 * 7) /FAQDesk/
 * 8) /Modules/
 * 9) Vouchers/Coupons
 * 10) Customers/Orders
 * 11) /Affiliates/
 * 12) Locations/Taxes
 * 13) /Localization/
 * 14) /Design Controls/
 * 15) /Links Manager/
 * 16) /Reports/
 * 17) /Tools/
 * 18) /Appendix Administrator/

title: CRE Loaded Features


text:
Category:Clove recipes

Recipes involving cloves.

title: Category:Clove recipes


text:
Talk:Voice over IP

I was wondering if dividing this page up into individual pages would be helpful. --Mattwj2002 20:33, 25 September 2005 (UTC)
 * Done! (Albiet quite a bit later) --Mbrickn (discuss • contribs) 08:24, 5 November 2021 (UTC)

title: Talk:Voice over IP


text:
English Criminal Law

{| style="width:65%;"
 * style="background-color: cream; border: solid 1px gray; padding: 1em;" valign="top" |

Part 1: Theory

 * /Introduction/
 * /Actus reus/
 * /Mens rea/
 * /Defences/

Part 2: Offences

 * /Non-fatal general offences/
 * /Non-fatal sexual offences/
 * /Offences against property/
 * /Murder/
 * /Manslaughter/
 * /Inchoate offences/

Part 3: Appendices

 * /Bibliography/
 * /Glossary/
 * /Style Guide and Authors/
 * }

title: English Criminal Law


text:
Ada Programming/Attributes/'Identity

Description
X'Identity is an Ada attribute where X is any task. This attribute returns a unique identifying string (of type "Task_ID"). This string is used in some Ada tasking libraries for task identification. It may also be used directly by the user for output purposes, to determine if two tasks are the same task, etc.

Example
My_Task; My_Other_Task; ... My_Task'Identity = My_Other_Task'Identity ;

Wikibook

 * Ada Programming
 * Ada Programming/Attributes

Ada Reference Manual

|Identity

title: Ada Programming/Attributes/'Identity


text:
User talk:70.82.241.102

Please stop. If you continue to blank pages, you will be blocked from editing.

title: User talk:70.82.241.102


text:
Talk:C++ Programming/Programming Languages/C++/Code/Style Conventions

25x80 related to 0 means success
There should be some clarification on how these two rules are related:

"This recommended practice relates also to the 0 means success convention for functions, that we will cover on the Functions Section of this book."

I suspect the original author was implying that short functions generally encourage having only one exit point, but this relationship is not very clear from the text itself (and furthermore, "0 means success" and "one exit point" seem like notably different rules to me). If someone wants to revise the text to clarify this relationship, please do so; otherwise, I'm tempted to remove it to avoid confusion.

--Autumnfields (talk) 11:13, 30 November 2010 (UTC)

Links to Style Guides
I've edited the introduction with links to style guides, and the got the following reply: Max 22:45, 25 September 2005 (UTC)

if in place of adding references to other pages (your last edits on Conventions (Source Code Style)), we created a section on Code Style pages in the external the references and point to it ? PS: Some of them are of C and Java ?!?

Ok, I guess you're right, the links should not go here, but in the reference section. However, the most comon styles should still be named here.

As for they are in C and Java: Yes, unfortunately they are for C and Java, but they are still the most widely used. (at least K&R, GNU and Java). Do you know of any equivalents in c++? --Max 22:45, 25 September 2005 (UTC)

Bjarne Stroustrup's C++ Style and Technique FAQ http://www.research.att.com/~bs/bs_faq2.html

The C++ Style Sweet Spot A Conversation with Bjarne Stroustrup, Part I by Bill Venners http://www.artima.com/intv/goldilocks.html

KDE Binary Compatibility Issues With C++ http://developer.kde.org/documentation/other/binarycompatibility.html

C++ portability guide version 0.8 originally by David Williams, 27 March 1998 http://www.mozilla.org/hacking/portable-cpp.html

Programming in C++, Rules and Recommendations FN/Mats Henricson and Erik Nyquist Copyright © 1990-1992 by Ellemtel Telecommunication Systems Laboratories http://www.chris-lott.org/resources/cstyle/Ellemtel-rules-mm.html

Wildfire C++ Programming Style With Rationale by Keith Gabryelski http://www.chris-lott.org/resources/cstyle/Wildfire-C++Style.html

Musings on Good C++ Style (Technology) By GoingWare Fri May 10th, 2002 at 03:08:38 AM EST http://www.kuro5hin.org/story/2002/5/9/205040/3918

there are more I have one that is very good but it's in PDF and I can't remember were I've put my copy or were did I get it... most can be mined without infringing copyright by simply changing the wording and simplifying, see the talk page on how to avoid abusing (and the limits of) copyrights, other we can contact the authors and get a license to use them I have done so as time allowed on some of the works I've added references, I've kept the emails so to have proof if any problem arises. see also my urls on my page (del.icio.us) btw if you also have a url page I would like to "monitor" it :) --Panic

Just looked at these links. They are all nice, but most of them go into a different direction. When I talk about coding style (especially to beginners), it I mean indentation, naming, comments, things like that (just as are on the page). Stroustrup recommends K&R style (and so do I :) ).

Here's an idea: We mention coding styles, give the list in the reference section, and during the explanation, recommend to use K&R style (maybe as a note: We will recoomend K&R, and then another note: We recommend using 2 chars as indentation), but emphasize that persistence is the most important key. --Max 20:37, 26 September 2005 (UTC)

 * I would instead call that "formatting" which is only a minor piece of style. (To me, style implies more questions like: how are things communicated, what gets communicated, what doesn't get communicated?) I go with mostly K&R, except I put the "else {" on its own line instead of sharing it with the "then"s close curly (as in "} else {") --MShonle 20:46, 26 September 2005 (UTC)

We should agree that we will never agree about the content of this section we should just say what can be done and leave it to the users interpretation, focusing in, as Max said on the persistence and common agreement,(ie:I could comment code in Mandarin if I would be the only reader), I don't think we should try to sell our tastes or interpretation today that is pointless there are code beautifiers out there, it's like debating the use of tabs or spaces, just pointless, spaces should be used as most of today editors will convert them easily to tabs, another point is the divergence with the use of single char vars names (i,z etc) they can lead to var shadowing and in "running code" (not optimized) can be very hard to find the problem.--Panic 22:55, 26 September 2005 (UTC)

C style comments
I wanted to change this coloring is awful:

int function /* This is a comment /* {              return 0; }             and this is the same comment */ so this isn't in the comment, and will give an error*/ The "isn't" starts a red line for some reason, is this a wiki issue? 203.214.123.244 (talk) 13:21, 19 January 2010 (UTC)

 * I've opened some time ago a similar bug report also on the code highlight filter that Wikibooks use (at sourceforge) IIRC this was not the same bug you have detected now. Go to Reading room/Technical Assistance and ask where to place the bug report (I can't remember the project's name). Thanks for detecting and reporting it. --Panic (talk) 02:10, 20 January 2010 (UTC)
 * So when I stumbled upon this page 8 years later this problem still hasn't been resolved yet?--140.180.246.217 (discuss) 20:52, 1 June 2018 (UTC)
 * I believe so but I haven't contributed or edited any code for more than a year now. A greater problem is that source code in Wikibooks is very prone to vandalism or introduction of errors, as only a small subset of editors may understand the content and even a smaller one would be inclined to check each edit. I proposed sometime ago a source code protection for only register editors with the review flag but I guess no one cared about to address the issue also. --Panic (discuss • contribs) 05:31, 2 June 2018 (UTC)


text:
User talk:138.88.164.196

Thanks for experimenting with Wikibooks. Your test worked, and has now been removed. Please use Sandbox for any other tests you want to do, since testing material in modules will normally be removed quickly. Please see the welcome page if you would like to learn more about contributing to our project. Thanks.

title: User talk:138.88.164.196


text:
Arabic/YesNoQuestions

Yes/no questions are those questions which can be answered with either a yes or a no in English. For example "Did you go to school today?". That was a yes/no question because someone answering could answer "yes" or "no" and be perfectly understood. An example of a non-yes/no question is: "How was school today?". If your friend asked you that question and you answered "yes" or "no" your friend would think you did not hear him.

So how do yes/no questions work. In English yes/no questions start with an auxiliary verb. There are many of these. In English yes/no questions can start with "have", "do", "did", "will", or other auxiliary verbs.
 * "have" ex. Have they come?
 * "do"  ex. Do they sleep?
 * "did" ex. Did they jump?
 * "will" ex. will you go away?

In Arabic yes/no questions are much simpler to understand, and to make. Every "yes/no" question usually starts with one of two words/semi-words. So

 * هل (hal)
 * a hamza (either a "أ " (a) OR ء (a))

Both of these work the same way. Both go at the beginning of a question sentence.

The difference in meaning between هل(hal) and hamza:
 * 1) For making "X=Y" sentences into questions.
 * هل (hal) is put at the beginning.
 * 1) For making "X!=Y" sentences into questions.
 * ء (a) hamza is put at the beginning.
 * 1) For "X does (something)" sentences
 * A hamza is used when talking about the present
 * A hamza would start this sentence: "Are you crying?".
 * hal is used when talking in the non present tense.
 * هل (hal) would start this sentence: "Do you cry?".

So how do we make a question. In Arabic a question can easily be made from a statement(a sentence, that is not a command, nor an exclamation, nor a question).

X=Y Sentences
For example, how do we transform the following sentence into a yes/no question. الولد صغير

al-waladu Sagheer(un) al-wa-la-du-Sa-gheer The boy is small.

Simple, just add  هل (hal) to the beginning.

هل الولد صغير؟

hal al-waladu Sagheer hal-al-wa-la-du-Sa-gheer Is the boy small?

Now don't forget the basic Arabic word for yes is نعم (na`am) and the basic word for no is لا (laa).

X!=Y
أليس كذلك؟

a laisa kadhaalik a-lai-sa-ka-dhaa-lik Isn't it like that? OR Right?

X does (something)
هل تعمل؟

hal ta`mal hal-ta`-mal Do you work?

title: Arabic/YesNoQuestions


text:
User:Klowner

Me type perty words!

My website

title: User:Klowner


text:
User:Nateji77~enwikibooks/ESL

Learn
It's a cat.

It's a dog.

Review
highlight with compter mouse to see words

It's a cat.

It's a dog.

Colors
highlight with compter mouse to see words RED BLUE GREEN BLACK

title: User:Nateji77~enwikibooks/ESL


text:
French/Grammar/Articles

The definite article agrees with a specific noun in gender and number. Like other articles (indefinite, partitive) they present a noun. In English, the definite article is always the (the noun). Unlike English, the French definite article is used also in a general sense, a general statement, or feeling about an idea or thing.

In French, the definite article is dependent on the noun's: There are three definite articles and an abbreviation. Le is used for masculine nouns, La is used for feminine nouns, Les is used for plural nouns (both masculine or feminine), and L' is used when the noun begins with a vowel or silent h (both masculine or feminine). It is similar to English, where a changes to an before a vowel.
 * 1) gender
 * 2) plurality
 * 3) first letter being a vowel

In English, the indefinite articles are a and an. While some is used as a plural article. In French, indefinite articles take on the gender of the noun it precedes if singular, but also has a plural form that is used for either gender.

Note that des, like les, is used in French before plural nouns when no article is used in English. For example, you are looking at photographs in an album. The English statement "I am looking at photographs." cannot be translated to French as "Je regarde photographies" because an article is required to tell which photographs are being looked at. If it is a set of specific pictures, the French statement should be "Je regarde les photographies." ("I am looking at the photographs."). On the other hand, if the person is just randomly browsing the album, the French translation is "Je regarde des photographies." ("I am looking at some photographs.")

Partitive article
The partitive article de indicates, among other things, the word some. As for prepositions, de le contracts (combines) into du, and de les contracts into des. Also, de l' is used in front of words starting with vowels.

When speaking about food, the partitive article is used sometimes, while the definite article (le, la, les) is used at other times, and the indefinite article (un, une) in yet another set of situations. In general "de" refers to a part of food (a piece of pie) whereas the definite article (le) refers to a food in general (I like pie (in general)). The indefinite article refers to an entire unit of a food (I would like a (whole) pie).

When speaking about preferences, use the definite article: When speaking about eating or drinking an item, there are specific situations for the use of each article.

If the noun taken in a partitive sense happens to be preceded by a qualifying adjective, or a negative verb, then de is used alone.
 * un, une, du, de la, des change to de.
 * for specific quantities;however, the quantity rather than de is used.

フランス語/文法/冠詞

title: French/Grammar/Articles


text:
Software Engineers Handbook/Language Dictionary/Smalltalk

Smalltalk
Here is the wikipedia entry.

Type
Smalltalk is a full procedural object oriented language.

All arguments are conceptually references to objects. All implementations, however, represent small integers within the pointer rather than allocating a physical object for each.

The language does not require implementations to support proper tail recursion, and none of them do.

It was in connection with Smalltalk that the term "object-oriented" first appeared, although the first object-oriented language was Simula 67.

Execution Entry Point
Smalltalk programs typically don't have a single entry point but are saved as image files (object memory snapshots). When started, such image files just continue to do whatever they were doing when they were saved.

General Syntax
Smalltalk expressions consist of message sends and variable assignments. a := b := c + 2 * (x even ifTrue: [y] ifFalse: [z negated]). Message sends can be either Unary messages bind most strongly, then come binary messages, then keyword messages. Binary messages are evaluated from left to right, there is no operator precedence. Assignments are evaluated right to left. Message expressions can be parenthesized. Angle brackets [] denote blocks. Blocks are first-level objects and can be assigned and passed as parameters.
 * unary (in example above: even, negated)
 * binary (+, -, etc.)
 * keyword (ifTrue:ifFalse:)

Comments
Smalltalk comments are delimited with the double quote character: "This is a comment" They can span multiple lines.

Variable Declarations
Variables have to be declared, but they don't have type information. Method arguments often have their intended role or the expected class in their name.

Temporary variables: | x y total subtotal | Method arguments: addAmount: aDecimalNumber purpose: aString Block arguments: [:a :b | a < b] Block execution: [:a :b | a < b] value:1 value: 2 Instance and class variables are declared within the class definition message (details vary between implementations): Object subclass: #MyClass instanceVariableNames: 'name owner additionalData' classVariableNames: 'DataRepository' Statically scoped variables (globals and class variables) are declared by executing expressions which create them in the system. Examples for this are the class definition messages.

Method Declaration/Implementation
Programmers write methods on classes. A class is a Platonic pattern of which objects can be made as instances. In Smalltalk, each class is also realized as an object, supporting the protocol to make and return a new instance (new). Classes have global names; all global names start with capital letters.

Note that programming language Self inherits many of the good features of Smalltalk but is conceptually simpler by eliminating the concept of a class.

Scope
Smalltalk has global variables, instance variables, temporary variables (to methods), and parameters (to methods). Blocks also can have parameters. In most modern implementations, blocks can also have their own temporary variables. There is also something called pool variables, they have the same lifetime as global variables, but just aren't accessible except in classes that explicitly include the pools (and in hiers of those classes). Instance variables are not accessible outside the object they belong to; however, programmers often provide access methods, even to variables intended to be private.

In practice, pool and global "variables" are often used for constants.

Conditional Statements
Conditional statuements are normal message expressions. The message receiver is a Boolean value (true or false), and the arguments are blocks. a < 10 ifTrue: [self handleSmallValue].

self hasValidInput ifTrue: [self processInput] ifFalse: [self displayInputFormatError]

Looping Statements
Loops are done by sending messages to blocks: [stream atEnd] whileFalse: [self process: stream nextLine]

[a < limit] whileTrue: [a := a + 1]

Iterations over collections are performed with 'do:' anArray do: [:each | self doSomethingWith: each]

Counting loops look like this: 1 to: 10 do: [:i | Transcript show: i printString; cr]

Output Statements
As most Smalltalk systems are not command-line oriented, output to "stdout" as such is not normally used. However, Smalltalk systems normally have a logging window (the Transcript) into which output can be written: Transcript show: 'Hello, world!'; cr

Containers
The standard Smalltalk library includes an extensive collection of classes of mutable collections: Array, OrderedCollection (in which it is efficient to append or delete from either end, and in which storage is economical (as an array rather than a linked list or a tree), Set, Bag, Dictionary, IdentityDictionary, SortedCollection. Collections support useful second-order functions collect: (like map in Lisp), select:, detect:, and reject:, and the second-order procedure do:.

Since Smalltalk is dynamically typed, so are its containers; they may point to any mix of objects of any types.

Algorithms

Garbage collection
Garbage collection is automatic.

Some implementations support weak references.

Physical Structure
Traditional Smalltalk-80 systems consist of:
 * runtime engine (interpreter or JIT plus primitives and platform interfaces)
 * image file
 * 'changes' file (log of source code and evaluated expressions)
 * 'sources' file (source code for the methods in the initial image)

More modern systems often split up the runtime engine into an executable plus shared libraries, and may have additional files for version control systems etc.

Tips
Don't try too hard to keep your old habits. You can write Pascal-style programs in Smalltalk, but they won't be good Smalltalk programs.

Keep behavior with those objects most central to it. It's often good to anthropomorphize your objects and write comments in the first person such as:

addEntry: anEntry "Add anEntry to my list of entries. If the entry conflicts with another entry, I will drop the older one." entries removeAllSuchThat: [:oldEntry | anEntry conflictsWith: oldEntry]. entries add: anEntry

Web References
A great resource of Free Books on Smalltalk

Books and Articles

Goldberg and Robson

Byte Magazine special issue on Smalltalk, 1979.


text:
Talk:Lucid Dreaming/Reality Checks/Breathing

"check if you can breathe underwater"??? I imagine this is going to be quite painful when it turns out that I'm not dreaming. Please clarify. Thanks.


text:
User:LA2

LA2 is the username for Lars Aronsson, Sweden. See for example m:user:LA2 and w:user:LA2.

title: User:LA2


text:
Rueda de Casino/Exhíbala

This is half a dile que no (or cross body), followed by a sharp right turn for the followers under the leader's left arm, to return to where it started.

This is a fast right turn, and feels strange to followers who are used to either Cuban or New York style salsa, so the leaders need to be clear, and patient. The follower's footwork is similar to a right turn in New York style, or a right-handed hammerlock in Cuban.

title: Rueda de Casino/Exhíbala


text:
EXELearning

This is the User Guide for eXeLearning, a program for creating courses for electronic distribution. The program can be found at http://exelearning.org and new releases from http://exelearning.net

Backgrounding eXe
The eLearning XHTML editor (eXe) is a web-based authoring environment designed to assist teachers and academics in the design, development and publishing of web-based learning and teaching materials without the need to become proficient in HTML, XML or complicated web-publishing applications.

The Web is a revolutionary educational tool because it presents teachers and learners with a technology that simultaneously provides something to talk about (content) and the means to hold the conversation (interaction). Unfortunately, the power of this hypertext medium is constrained in educational settings because the vast majority of teachers and academics do not have the technical skills to build their own web pages, and must therefore rely on the availability of web developers to generate professional looking online content. The eXe is being developed to overcome a number of identified limitations:

 * Traditionally web-authoring software entails a steep learning curve; it is not intuitive and the applications were not designed for publishing learning content. Consequently teachers and academics have not adopted these technologies for publishing online learning content. eXe aims to provide an intuitive, easy-to-use tool that will enable teachers to publish professional web pages for learning;
 * Currently, learning management systems do not offer sophisticated authoring tools for web content (when compared to the capabilities of web-authoring software or the skills of an experienced web developer). eXe is a tool that provides professional web-publishing capabilities that will be easily referenced or imported by standards compliant learning management systems;
 * Most content management and learning management systems utilize a centralized web server model thus requiring connectivity for authoring. This is limiting for authors with low bandwidth connectivity or no connectivity at all. eXe will be developed as an offline authoring tool without the requirement for connectivity.
 * Many content management and learning management systems do not provide an intuitive wysiwyg environment where authors can see what their content will look like in a browser when published, especially when working offline. eXe will mimic wysiwig functionality enabling users to see what the content will look like when published online.

Overview of eXe tools
With the eXe, users can develop a learning structure that suits their content delivery needs and build a resource that is flexible and easily updated. The Outline pane of the eXe Control Panel enables users to design an outline that reflects their own preferred hierarchical structure and taxonomy, i.e. topics-sections-units, or books-chapters-verses, etc. This can be established at the outset or can develop as the resource is built.

The iDevice (instructional device) pane consists of a collection of structural elements that describe learning content. Some of these include, objectives, pre-knowledge, case studies, free text. Learning content is compiled by selecting iDevices from the iDevice menu and entering your learning content. A learning resource may consist of as few or as many iDevices as required to deliver the learning content effectively. New iDevices are in development and recommendations for additional iDevices are being sought from the wider learning community. An iDevice editor enabling users to design their own iDevices and templates has been released in an experimental format as work continues on its development.

eXe offers the ability for users to customise their published content by selecting from a range of graphical style sheets. eXe’s Export facility allows content to be packaged in two ways. Learning resources can be packaged as a self contained web site for publishing to a web server, or as a SCORM Content Package which will enable the resource to be imported into any SCORM enabled learning management system (LMS).

Windows
To start the eXe, double-click the eXe icon that should have appeared on your desktop after installation. If you don't have an eXe icon on your desktop you will need to find the application's icon in your Windows start menu under Programs. You should probably maximise the eXe window to utilise all the space you have available to work in.

Linux
Type run-exe.sh (all lower case) from the command line. This will launch eXe.

Chapter 3 - Building a resource
This chapter is designed to guide you through using the tools in this application to produce your own learning resources. Submit

Objectives
At the conclusion of this tutorial you will be able to:

 * Use the outline tool set to structure a resource
 * Select iDevices and add content to a resource
 * Apply a new style to a resource.

Section 1 - Defining Properties
The Properties tab allows you to record general details about your project e.g. Title, Author, and Description. It also allows you to define the taxonomy you may prefer to use to describe the different components or levels within the resource.

Activity
To begin this activity with eXe open (see Chapter 3- Starting eXe).

1. Select the Properties tab (at the top of the authoring workspace) 2. Type a title for this resource in the Title field e.g. eXe Tutorial. 3. Type in the author details and a brief description of the resource in the space provided 4. Change the taxonomy to Module, Section, Map. (The taxonomy determines the naming convention for the different levels in the outline.) 5. Click  6. Return to the Authoring tab.

Preknowledge
You should have completed Section 1 - Defining Properties and set the properties for your package.

The Outline tool set allows you to define the structure your project will take. This is particularly useful for large or complex projects that contain many parts or topics. On startup the authoring pane displays to the right of the eXe sidebar. The outline pane displays two defaultdnodes, draft and home.

Home
The Home node is the first page displayed when the project is exported to the web or an LMS. This is a parent node and additional child level nodes can be added under this node.

Adding nodes
To add additional nodes select the parent node by highlighting the parent level and click the Add Child button (on some systems this is shown as "Add Page").

Delete nodes
To delete a node select the node you want to delete and click the delete button. A dialogue message displays to check this action. Click OK to continue.

Renaming nodes
Select the node you want to rename and double click. A dialogue message prompts you to enter the new name. Enter the name and click OK. This action can also be done using the Rename button

Promote/Demote arrows
The promote/demote arrows are located beneath the outline pane. Selecting a node and clicking on one of the arrows will change the position of that node with the outline structure.

Activity
Now try adding a new Module to your project. To do this click on the parent node you want the new "child" module to be associated with and click the  button. Select the new module and double click or click . Add a title, in this case call it eXe Tutorial.

Preknowledge
You should have completed Section 2 - Defining an outline.

iDevices are instructional elements that provide a framework within which to set your content.

To demonstrate iDevices in action take a look through the examples below.

Multiple Choice Question
Which iDevice would you use to describe the learning outcomes of a learning resource?
 * Reflection
 * Multiple choice Question
 * Objectives
 * Preknowledge

Move on to Sub-section1 of this section Entering content into the iDevice to enter content.

title: EXELearning