text:
User talk:Luthinya~enwikibooks

Welcome to Wikibooks
Welcome to Wikibooks. We are a group of people working together to write textbooks and other useful original non-fiction literature, and we are glad that you have chosen to spend some time here.

There are a few things that you should be aware of here, and most important, please read some of these pages on this project:

 * What is Wikibooks
 * Welcome, newcomers
 * Help:How to start a book
 * Meta:Help:Editing (about how to use the Wiki markup language here)
 * Community Portal (a collection of useful links to various pages on the project)

I would also ask you to please look at the following discussion pages if you have any questions:

 * Staff Lounge (general Wikibooks discussions)
 * Study help desk (Q & A list for general help on Wikibooks... especially for new users)

I wanted to add that the new Wikibook that you created, Tao te Ching, is likely to be deleted unless you add some details about what you plan to accomplish here. If you want to experiment, please consider editing on Sandbox where you can make a number of changes without worrying about damaging what anybody else may be doing. The content there is regularly deleted, as it is only supposed to be for experiments for people new to this project.

If you are looking for more specific help and want a more personal touch, please consider cotacting one of the active project administrators here. All of them have shown substantial interest in this project, and are familiar enough with how things work around here that they can generally help you out when you just can't figure things out. Good luck and I hope to be seeing more of you soon. --Rob Horning 14:33, 13 January 2006 (UTC)

 * Thanks very much for contacting me. I am serious in my plans for the Tao te Ching - which I hope is within the catogories stated- but I would like to state that this book is not 'original' in the normal sense of the word. It is an ancient scripture concerning the 'Tao' as a Way and the virtues and powers for following such a Way, written by the Taoist sage Lao Tzu around two thousand and five hundred years ago. Many translations have been made available in English but I would like to make yet another translation available for the use of Wikibooks, along with several small sections of interpretation aids found within the books for those who did not know Taoism well. Please tell me if this does not fit the general scheme of Wikibooks- I only made sure that it was not fiction but it is still a mystical and religious text, and as I repeat a new translation is probably not conventionally 'original'. Also I am not quite certain I understood you correctly when you said about 'adding some details' about what I plan to accomplish there- to where am I supposed to add such details, or do you mean that the page I created was simply a manifesto for the book I am about to write? This bring me to another question- Where exactly am I meant to be able to creat my book free and proper? So far all the pages I have known were article pages wholly unlike to that of proper books where one may flip at will. Where exactly are the paper, as they were, upon which I can properly write my book? I thought I would use the page I just found for the time being, but as you contacted me I think you might be able to solve my problem. And many thanks for your attention!

---

If you are interested in doing a translation or simply a transcription of an existing manuscript, there is another project that is a much better place for material like this. You should consider Wikisource, which is a Wikimedia sister project to Wikibooks. On Wikisource they have more of a collaborative effort to make sure the content is added correctly, and groups in place that can help you out to verify the content you are adding, including a slightly stronger multi-lingual atmosphere than exists here on Wikibooks. If you are planning to do the translation yourself, that is certainly an admirable task and something I've attempted to do myself for some documents.

As far as adding details about what your plans on a Wikibook or similar Wikimedia page, make sure you are using the discussion pages to let other contributors know where you are going to go with a similar kind of project. This can be a simple sentance saying "I'm new here and can use some help" to a full manifesto about the book or article.

Once you have the content of the book down and would like some help to turn it into something that is more like a physical paper book like a typical textbook, make a comment on Staff Lounge for more assistance. This has been done to a few books here already, although for the most part we are busy trying to improve the content first and simply trying to get the thoughts organized. Adding the written content down in the first place is by far the most difficult part of the whole task, and once that has been added trying to make a physcial book is considerably easier.

As far as making an annotated text or study aids for a classic text, that is something that can be done on either Wikibooks or Wikisource. If it involves mainly source material, it would be worthwhile to keep most of it on Wikisource, while if the source material is minor compared to the study materials it may be used on Wikibooks. That is a judgement call you would have to make but I would recommend that the source text itself (even a translation) be kept on Wikisource if possible. The two projects are easily linked between each other and have similar policies and philosophies.

I hope that this answers some of your questions. Feel free to contact me if you have any more questions. --Rob Horning 07:27, 14 January 2006 (UTC)

Thank you very much. I am certainly much indebted to you.

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

title: User talk:Luthinya~enwikibooks


text:
Wings 3D/Tutorials/More pipe joints

Wings 3D Wings 3D: Tutorials

General info:

RMB = Right Mouse Button (Single click of the...)

MMB = Middle Mouse Button.

LMB = Left Mouse Button.

So, for example, an RMB option refers to that option (of a tool) available by R clicking on it.

Default hotkeys are shown in bold. eg C for Connect.

Please check the main info line as this contains very useful information about the command / tool you're using.

Using Edge | Intersect to create a pipe joint of any angle......(Advanced Menus required - Edit > Prefs > Adv.)

1.Create cylinder and select all axial edges

2.Edge | Connect to form a new edgeloop.

3.Select end face

4.Rotate face around relevant axis – I used X > 23.36 deg.. Use Tab input for entering weird angles that aren't easily obtained by using Shift (15 deg) or Cntrl (1 deg) constraints. (See 'comments' for how to work out this 'rotate angle')

5.Select edges around lower (undistorted) part of cylinder (select one edge, press G) and apply Edge | Intersect > RMB option (Pick plane) – Select the newly angled face.

6.Execute Intersect – the upper ends of the selected axial edges will now alter in length, until they ‘intersect’ the specified plane.

7.Situation at the top of the cylinder – essentially showing the distortion caused by the original rotate op in (4) – we need to make this one face – select large central face.

8.Press F (or +) to grow the selection. (17 faces selected)

9.Face | Dissolve (Bksp) to get rid of all the separate faces and form a single face.

10.Face | Mirror to get required bend / joint etc.

Comments.

(2) is done to create axial edges that will stay undistorted during the rotate op. Use any system you prefer to achieve this (reference) geometry (Extruding the end face > -Y is useful if you forget (2) prior to rotate op) Whilst the above method will work for any angle, you may have to adjust the position (-Y) of the edgeloop formed in (2) to get it out of the way (of the Intersect plane) if rotating the face thro’ a large angle. (Could also move the rotated face +Y).

Select appropriate faces and use Face | Intrude to 'hollow out' this object to create a 'pipe'.

The expression needed to work out the included angle – for precise, non-eyeball stuff is :

Wings rotate angle = [90 – half the (included) angle required].

Eg for a 130 deg bend

Rotate Angle = [90 – 130/2] >> [90 - 65] >> 25 degrees

So, for a 130 deg bend you’d have to rotate the top face (4) by 25 degrees.

 Using Edge | Intersect to create a pipe T joint of any angle......(Adv. Menus reqd.)

Overview:

Change cylinder end face > 2 semicircular faces.

Rotate (vector) one (face) thro’ half the required included angle for the joint.

Rotate the other (face) thro’ [90 – first angle], to form two faces at right angles to each other.

Use Edge | Intersect to correct distortion issues.

Tidy up faces, mirror and extrude to get required object.

Using Edge | Intersect to create a pipe T joint of any angle.

1.Create default cylinder, select bottom face and Face | Extrude > Y (or normal) a little – amount unimportant (provided you can see it :) ) Select a pair of verts on the ends of a diagonal and apply Vert | Connect (C) to create a diameter edge across the end face (mine’s parallel to the Z axis). Select one of the semicircular faces – either is ok.

2.Apply Face | Rotate > Z > RMB (Pick point for axis to pass thro’) Select either an end vert of this 'diameter edge' (as shown) or the diameter edge itself to specify the origin for the local rotate axis.

3.Execute op, by dragging the appropriate angle – which is half the included angle of the joint. I wanted a 66 deg joint, so I dragged 33 deg – holding cntrl to constrain to 1 deg steps. Use Tab input and enter the appropriate amount if it’s a nasty figure.

4.Select the other semicircular face and basically repeat what you’ve just done with the first face (press D to repeat last (rotate) op – as it’s using the same axis)

5.This pic is redundant if you use D to repeat the op – if you repeat the whole op from the start, use the same ‘anchor’ point (as shown). Drag to [90 - first angle] in this case, [90 - 33] = 57 deg (or use Tab as before).

6.With both semicircular end faces now at their correct angles, it’s time to correct the cylinder distortion caused by the rotate ops. Select the (7) axial edges shown (some hidden) that are equi-spaced around the X axis. (One on X axis, 3 either side, for this setup with a 16 sided default cylinder – eyeball info at top left to check you’ve only got 7 edges selected)

7.Apply Edge | Intersect > RMB option (Pick Plane) and select the semicircular end face on the same side as the selected axial edges.

8.Execute Intersect op – and the upper verts of the selected edges will now lie on the plane specified by the end face.

9.Repeat the whole Intersect op. for the other set of edges. Press Cntrl D to repeat last op – but offering the facility of using different elements. Note that 9 edges are selected this time.

10.Select appropriate end face to specify plane (for Intersect).

11.Execute Intersect – all selected edges now adjusted.

Continued...

12.Select all end faces as shown on one side (either side is ok) – you should have 9 faces selected (with def. cyl.) – be sure you’ve got the little s**s adjacent to the diameter edge – depending on what angles the end faces have been rotated, these small, thin faces can be quite small and difficult to select. Be wary of using certain selection ‘spreading / growing’ techniques as it’s possible to select the similar faces on the other side. Just eyeball info and check you’ve only got 9 :).

13.Apply Face | Dissolve (Bksp) to form a single face – keep this selected.

14.Apply Face | Mirror to form the major part of the joint. (all downhill from here).

15.Select all (18) faces shown and use Face | Dissolve (Bksp) again to form a single face.

16.Apply Face | Extrude > Y and drag to as required.

17.Apply Face | Flatten > Y to sort out the end face.

18.Finished object – If you want to check the angle, select any pair of relevant edges (say, on a centreline) and eyeball ‘Angle’ info, top left display.

Using Edge | Intersect and remote reference to create a pipe T joint of any angle......(Adv. Menus reqd.)

Overview:

Create a cube and rotate it half the required included angle.

Create cylinder and change one end face > 2 semicircular faces.

Use Edge | Intersect to extend cylinder Axial edges to the remote reference faces.

Tidy up faces, mirror and extrude to get required object.

An alternative to the previous method which might be worth considering if joint construction is taking place at the origin – rather than ‘in situ’ – somewhere on the model, away from the origin.

1.Create cube and apply Object | Move > X > 1 unit (hold shift to constrain).

2.Apply Object | Rotate > Z > RMB option (Pick point for axis to pass thro’) Select the upper edge immediately above the Z axis or either end vert) > Execute op. by dragging half the required included angle of the joint. I wanted a 66 deg joint, so dragged (holding cntrl for 1 deg steps) thro’ 33 deg. This image (View Z, Ortho) shows situation after rotate op – Important – note that upper (pivot / hinge) edge is exactly on the YZ plane, ie above the origin.

3.Create a cylinder (default here), Apply Object | Move > -Y (enough to ‘clear’ the cube) and use Vert | Connect (C) to form the diameter edge across the upper end face (as shown). Select the 9 axial edges (centre one on X axis and 4 either side) and Apply Edge | Intersect > RMB option (Pick plane) > select the cube face above these selected edges (as shown).

4.Execute the Intersect op – upper ends of selected edges extend to the selected reference plane.

5.Select the remaining (7) edges around the cylinder and re-apply the same Intersect op. Use Cntrl D to repeat this op, but letting you choose a different plane (as shown). (Or repeat the op from scratch – your choice).

6.Situation after the op’s been completed.

7.Cylinder with its 2 end faces formed as needed. Hide / dump cube.

8.Select either angled face and apply Face | Mirror. Select the 2 faces shown and Dissolve (Bksp).

9.Apply Face | Extrude > Y to create the remaining stub and use Face | Flatten > Y to tidy end face.

10.Finished object.

Comments:

In the above description, I used a cube and moved > X >1 unit. There’s no doubt many other ways of achieving the same result (eg,select all X edges, connect, loopcut, dump other half – for one) – use whatever approach fits your workflow (and hkeys?) best.

This (cube) move and the consequent vector rotate op isn’t absolutely necessary – you could just Rotate > Z in the cube’s default position. Doing this, however will entail 2 different Intersect ops (first RMB, second MMB) as the planes are at the correct angle but not intersecting at the same point as the main description. (It would also remove the possibility of using Cntrl D for repeating the RMB option)

Using Edge | Intersect to create a 90 deg T joint......(Adv. Menus reqd.)

Using Edge | Intersect to create a T joint.

1.Create cylinder, Scale Y > (anything positive … I used 200%). Select all axial edges and apply Edge | Connect to form a new edgeloop.

2.Select a vert and move Y > -1 unit (any vert will do, I used the one opposite the +X axis to keep things tidy.

3.Select the 3 edges (if using a def. cyl.) either side of the edge where the vert has just been moved.

4.Apply Edge | Intersect > RMB option (Pick plane) Select the 3 verts shown. The left and right ones in this image both lie on the Z axis. These 3 verts describe a plane at 45 deg to the Y axis.

5.A different view ( View Z, Ortho), showing the vector (normal) associated with the required plane.

6.Execute the Intersect op – the lower ends of all the selected edges now lie on the required plane.

7.Select all the faces on the upper part of the object and apply Face | Dissolve (Bksp) to create a single face. (Could also have used LoopCut to chop the thing in half etc.

8.Select the 2 relevant verts and use Vert | Connect (C) to create the new edge shown. This forms the necessary mirror face.

9.Select face shown and apply Face | Mirror.

10.Select both faces shown, apply Face | Dissolve (Bksp) to form a single one.

11.Apply Face | Extrude > X > and drag to suit. Tidy the end by using Face | Flatten > X.

Comments:

In (1) I only scaled Y to provide ‘room’ for the new pipe diameter – as a def. cyl is also 2 units long – same as the diameter. In (2) I moved the vert 1 unit. This, of course will only work (for a 90 deg T joint) if you’re using a default cylinder with a radius of 1 unit. If you’re using a different diameter cylinder – measure the radius (diameter) and use the appropriate figure. In general, you could have connected the verts of a def. cylinder (same verts as used in (8)) and then used a similar intersect procedure on one of the semicircular faces of this ‘block’ – ie no need to dump the upper half as I’ve done here.

Using Vector scale op to correct distortion / form a joint......(Adv. Menus reqd.)

Using Vector scale for a pipe joint

1.Create cylinder, select end face.

2.Face | Rotate > X > 45 degree (hold shift to constrain to 3 x 15 deg steps).

3.Apply Face | Scale Axis > RMB option (Pick axis to scale along) select the 2 verts shown – this is to correct the projected view of the end face when viewed along the Y and Z axes.

4.Start dragging, press Tab, enter 141.42% in the data entry box. (141.42 = square root 2 x 100% - a figure that (together with its derivatives [70.71, 29.29] etc) is extremely useful and well worth remembering – imo.

5.Use Face | Mirror to get required object.

Comments:

In (3) – for a general situation, it should be fairly clear (hopefully) which 2 verts you have to select to re-size (rmb axial scale) the end face, as the face essentially needs to be ‘stretched’ along one axis only. Use 115.47% scaling factor if you rotate thro’ 30 deg.

Use 200% scaling factor if you rotate thro’ 60 deg.

To get a 90 deg T joint. Vector flatten the outer (semicircular) edges of the joint. Use Edge | loopcut to remove unwanted geometry. Mirror

Similar for a 4 way joint – after connecting relevant verticies for a centre line.

Making a 90 deg corner joint from a sphere.

1.Create default sphere and select whole object.

2.Object | Scale Radial > Y > 141.42% (drag slightly, press Tab to get data entry box, enter 141.42 and accept)

3.All (8) cross-sectional edgeloops of the sphere are now ellipses of the correct ratio (major / minor axes) for the purpose in hand. Whilst a 90deg joint could be made from any of these loops, selecting either the one shown, or the one at right angles to it make the job easier (no vector extrude op required).

4.View X Ortho, showing the projected shape of the ellipse as a circle – exactly what’s needed. (View Z would be similar)

5.Apply Edge | LoopCut to selected edgeloop and delete unwanted half – select elliptical face.

6.Apply Face | Extrude > Z (or X), drag to suit.

7.Apply Face | Flatten > Z (or X, if extrude X used)

8.Apply Face | Mirror to get required object.

Making a 90 deg corner joint from a torus.

1.Get primitives menu and open data entry box for the Torus (click on small box or RMB on listing if using Advanced Menus) Enter the data shown. Three fields need changing from the default settings:

Sections > 4

Slices > 16

Minor Radius > 0.7071

(can enter 0.707107 – half the figure above in Major Radius field – if you’re really keen and after even more precision – but it’s hardly worth it imo :) ) You’ll get the figure shown – 4 joints, in essence.

2.To get rid of unwanted junk, create the 2 new edgeloops shown. Select an axial edge on each portion, press G (edge rinG) to get the rest, C (Edge | Connect) to connect them.

3.Apply Edge | LoopCut and delete the unwanted portion. This looks ok – but it’s not – because it needs to be scaled (Y).

4.Shows why it needs scaling – unless you want elliptical pipes.

5.Select whole object and apply Object | Scale > Y > 70.71% (use Tab entry box as described earlier).

6.Finished item.

Comments:

The figures I’ve used above will produce an object with 16 sides, having a (pipe) diameter of 1 unit (or very nearly so, anyway) – if you want other sizes you’ll have to use other figures. If you want to change the absolute minimum number of fields – then don’t bother with the last (min Rad) – the absolute essential one to change is the Sections > 4 (assuming you want a 90 deg joint – other figs will produce joints with different included angles)

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

title: Wings 3D/Tutorials/More pipe joints


text:
Georgia Water/Policy/Erosion and Sedimentation Control

See also: Georgia Erosion and Sedimentation Act and  /Recommendations/

Manual for Erosion and Sediment Control
The Technical Advisory Planning Committee was established to "develop policies and procedures for use in updating and maintaining the information included in the Georgia Soil and Water Conservation Commission's Manual for Erosion and Sediment Control. The ultimate objective of the Committee is to provide information on best management practices based on sound scientific principles, that will best help Georgians to control erosion and sedimentation."

Organizations
The goal of this section is to provide, for each major organization (EPD, SWCC, DCA, EPA, USDA, NRCS) or organization category (such as county sediment control programs, Soil and Water Conservation Districts, citizen environmental groups, lake property owner associations, etc.), a brief summary of the organization’s legal responsibility, concerns, capabilities and funding; with copies of relevant statutes, rules and regulations, forms, and procedures used in their sediment related programs; and with ideas from people working in the organization for improving sediment and erosion control and for increasing their organization’s capabilities and potential.

New EPD Procedures
In January, 2006, the Georgia Environmental Protection Division]] published new procedures regarding role of EPD and the local issuing authorities: Source: Georgia Environmental Protection Division and as quoted above from Augusta Chronicle, 13Jan06.
 * Recognizing that the Georgia Environmental Protection Division does not have staff or funds to replace local erosion control programs, the agency will try to support local programs through education and guidance.
 * Local governments are the first line of authority, and EPD will serve as a "backstop."
 * However, if EPD investigates a site and finds violations, it must seek enforcement actions that could include penalties.
 * EPD can issue stop-work orders even in areas where a local government program is in effect.
 * Complaints to EPD in areas with local programs will be referred to local authorities, who must respond to EPD in writing as to how the complaint was resolved.
 * Failure to respond can trigger EPD enforcement actions against the violator and could result in suspension of the local government program.
 * In situations where a local government issues permits for activities EPD deems inappropriate, EPD will not punish the developer but will require the local government to correct its procedures for future permits.
 * Local governments can be decertified to issue development permits if their programs are inadequate, but they will be given time to correct their problems.


text:
MATLAB Programming/Psychtoolbox/Howto get Psychtoolbox pre-releases & bug fixes

Setup Instructions

 * 1) Install subversion client software from: http://metissian.com/projects/macosx/subversion/
 * 2) Download the m-file DownloadPsychtoolbox.m
 * 3) This file is the Psychtoolbox-Installer.
 * 4) Save the installer into your Psychtoolbox path.
 * 5) Change Matlab working directory to a folder were you want to download the latest release of PTB.
 * 6) Enter either DownloadPsychtoolbox('beta') or DownloadPsychtoolbox('stable'), depending which flavor of Psychtoolbox you want to use.

Description of Stable and Beta
'beta' gives you the equivalent of my past pre-releases: Early access to bug-fixes, enhancements and new features. Tested and found to be working properly on our own machines, but not yet sufficiently tested by real users in real applications.

'stable' consists of former 'beta' releases that have received additional real- world testing by end-users, so it is considered final code that will be released in the next upcoming official release.

Obviously, 'stable' releases will have a much longer delay, until features are added or bugs are fixed -- it's your choice.

As of today, 'beta' contains an improved DrawText function and experimental support for Quicktime movie playback, as well as new functions for transformations like scaling, translation and rotation. MacOS-X 10.3.9 or later + Quicktime-7 is required for 'beta' to work. MacOS-X 10.2 and earlier are not supported anymore.

'stable' is identical to the 1.0.6 release and will stay that way for a while, until all the new features in beta have received sufficient testing by real users and more refinements and polishing by us.

What else? You need to perform this procedure only once. After that, you can simply use the new command 'UpdatePsychtoolbox' to keep your copy of PTB up to date with the latest changes in the 'beta' or 'stable' release whenever you want.


text:
User talk:Phil Boswell

Hello and welcome to Wikibooks!

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

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

Good luck! -- LV (Dark Mark) 17:45, 13 January 2006 (UTC)

title: User talk:Phil Boswell


text:
Cookbook:Cantonese Roast Duck

| Cuisine of China

This is a recipe for Cantonese roast duck or goose (烧鸭\烧鹅).

Marinade

 * 2 Tbsp light soy sauce
 * 2 Tbsp dark soy sauce (optional, can use light soy sauce instead)
 * 2 cups (450 ml) of white wine, sherry, or Chinese cooking wine
 * 1 tsp Chinese five spice powder

Glaze

 * 2 Tbsp Hoisin sauce
 * 2 Tbsp dark soy sauce

Duck

 * 3–6 lb (1.3–2.6 kg) whole duck or goose
 * 3 green onions or 1 onion

Preparation

 * 1) Mix all marinade ingredients together.
 * 2) Mix all glaze ingredients together.
 * 3) Brush the marinade mixture all over the duck, inside and outside.
 * 4) Brush some glaze mixture inside the duck cavity.
 * 5) Sit duck breast-up on a rack in an open container.
 * 6) Put in the refrigerator to chill overnight.

Cooking

 * 1) Preheat oven to 450°F (220°C)
 * 2) Put ½–1 inch (2.5 cm) of water in a roasting pan—this catches the grease that comes out from the duck while roasting and prevents it from smoking.
 * 3) Place green onions inside the duck cavity.
 * 4) Place the duck on a roasting rack in the roasting pan. Roast the duck for 15 minutes.
 * 5) Turn the duck breast-up, and roast for another 15 minutes.
 * 6) Turn oven heat to 375°F (190°C), and roast the duck until the internal temperature reaches a minimum of 180°F (test between the thigh, the thickest part of the duck/goose, being careful not to touch the bone)
 * 7) Brush the duck with glaze, turn oven up to 450°F (200°C), and roast again for about 10 minutes.
 * 8) Carve and serve!

title: Cookbook:Cantonese Roast Duck


text:
Cookbook:Hoisin Sauce

| South-East Asian cuisines

Hoisin or Hoi Sin sauce is a sweet bean sauce made from fermented soy beans. It can be found in most Asian supermarkets. It is one of the most widely known of the sauces, liked for its balance of sweetness, saltiness, garlic and five-spice powder. It is a staple of many Asian cuisines such as Chinese, Vietnamese, and Taiwanese.

title: Cookbook:Hoisin Sauce


text:
User:ArkansasTraveler

I typically spend quite a bit of spare time at Wikipedia's English edition, but cooking has always been one of my interests. Here at Wikibooks, I look forward to contributing mostly to the Cookbook.

title: User:ArkansasTraveler


text: User talk:Babyc

title: User talk:Babyc


text:
POV-Ray/Getting Started

Lesson Plan Outline
Materials: Objectives: Intro Activities Closure Assignment Analysis
 * Computer/POV-Ray
 * Sample Artwork
 * Sample Animation
 * Introduce the Big Goals to motivate
 * Launch the application create first drawing
 * Show sample artwork
 * Show sample animation
 * Talk about elements camera, light, objects
 * Create the first program
 * Change the color of the object
 * Change the light
 * Change the camera
 * Question: What three things do we need
 * Question: What does rgb stand for
 * Create a picture with three different cones in three different locations not touching

title: POV-Ray/Getting Started


text:
Talk:C++ Programming/Conventions/Archive 2

Headings
This would allow for a nice-looking one-page version. I will do that anyways with the exising modules (of course, I'll wait on the -/- -/- modules), but I'd like to have it in here for future authors --Max 01:20, 22 September 2005 (UTC)

Web Link Policy
Try to add relevant WEB links to the text in a way that it facilitates the transformation of the book into  (ASCII) format without the loss of that "relevant" information, also enabling copy-paste operations from the readers.

Proposed: 18 Sept 2005

Authors Section
Every person making non-trivial changes may add themselves to the Authors section. Please add your full name. You may add zero or one of each:
 * link to your wikimedia page
 * link to your web-page
 * email address

Proposed: 19 Sept 2005

The proposal as stated above is just my idea. I am very open to and changes, but I do belive that we should agree on a format. --Max 23:07, 19 September 2005 (UTC)

Humm should, couldn't it be changed to -may- or -if the author wishes to...- as no one is obliged to do it, as for the information we should limit what is acceptable but not ask for particular info to be added (as for other works for what I understand of the GFDL)--Panic 00:10, 20 September 2005 (UTC)

changed should to may. As for the info: I did not mean to ask the people for it, but rather to allow them to add that info, but not more. Maybe i need to re-word that? --Max 00:25, 20 September 2005 (UTC)

CALL 4 VOTES ( 05:58, 21 September 2005 (UTC) ) Please indicate by your vote if you are participating in this project.

Yes
--Panic 06:00, 21 September 2005 (UTC) --Max 16:55, 21 September 2005 (UTC)

Linkbar
I propose adding this info to the mainpage since all this wikibooks do relate to C++ in some way or another and it provides a quick way to move from book to book.

--Panic 03:26, 17 September 2005 (UTC)

I see so reason not to do that. --Max 16:35, 18 September 2005 (UTC)
 * It's redundant with our bookshelves. Perhaps we could link to the programming bookshelf, but such a large banner is going too far. MShonle 18:47, 18 September 2005 (UTC)

It only to facilitate the aggregation of similar readers/editors if (as there existed) every similar or related book links to each other it's easier to port/use similar content and give the reader a broader view of the possibilities...--Panic 17:57, 18 September 2005 (UTC)

I we are going the way of moving contents to different books (e.g. a whole book on STl, a whole book on boost, etc.) then we should definitely link these from the main page. Otherwiese people will be asking: Where is such-and-such content? --Max 20:19, 18 September 2005 (UTC)
 * We could put those links in a further reading section that's either on the main page or a subpage. While we want to provide links to other useful resources, we don't need to make an extra effort to draw attention to them. (I was also opposed to this linkbar being spammed on other books, partially because it only promoted the C -/- -/- fork (and not the original book) and partially because it's just too distracting of a banner.) --MShonle 20:56, 18 September 2005 (UTC)

Since Panic voted no and was the originator, does that make this obsolete? I could live with either one --Max 18:13, 21 September 2005 (UTC)

CALL 4 VOTES ( 05:58, 21 September 2005 (UTC) ) Please indicate by your vote if are participating in this project.

No
--Panic 06:00, 21 September 2005 (UTC)

Links to wikipedia
Comments:

I was not sure, but I think this is the way it was anyways, so i'd go with it --Max 00:36, 18 September 2005 (UTC)

Navigation
To support a good navigational scheme, the actual content should be on a page with the name Pagename_Content and included from the actual pagename. This allows including the same content from the one-page version and from a chapter version of this book.

Proposed: 18 Sept 2005

Replaced by:

To support navigation, each page should link to the previous and next page, using the tags. A navigational template will follow

Proposed: 21 Sept 2005

 * Given this idea I've tried on the Algorithms book to great effect. The (marginal) nav bar I had no longer shows up in the full text view (and thus I've included I link to it now). I suppose the only reason I missed using it before was because it wasn't an option before. :-) As for generating the "next" and "prevous" arguments for each use of the template it could either be done by hand, or by a bot that reads in the order of the all chapters view. I haven't tried out bots yet, but it could save time and avoid errors. Until then, prev and next could be done manually, unless there's another trick I don't know about. --MShonle

 * One other note: I don't have much time available lately, so if there are any high-level issues, like renaming a locked page, just leave a note on my user page. --MShonle

Navigation
Pro:
 * Chapter-to-chapter naviagtion makes it easier --Max 00:36, 18 September 2005 (UTC)

Con:

 * TOC would have to be maintaned in 3 places --Max 00:36, 18 September 2005 (UTC)

 * Selecting "edit" on a content does not open the right page (is this true? please verify) --Max 00:36, 18 September 2005 (UTC)
 * If you select "edit" on a h2, h3, etc heading you get the right page. That includes if you click on the first h2, which should be the chapter name, effectively giving you the whole page. For the Computer Science:Data Structures chapters there is also a link at the bottom that says "edit this chapter." I assume that for most editors they will either make minor modifcations and use the heading edit buttons, or they will contribute a lot and already have the _content pages on their watch lists. MShonle 01:33, 18 September 2005 (UTC)

Comments:

If my last argument is false, i'd vote to do it --Max 00:36, 18 September 2005 (UTC)
 * See above. MShonle 01:33, 18 September 2005 (UTC)

Replaced by: I just found out that MediaWiki supports the tags. Put in a page things inside will not show up when the page is included (such as from the all_chapters page). So here's the idea:
 * Create a navigational template with forward and back
 * have a on every page. Either on the top, the bottom or both.

Comments? --Max 04:40, 22 September 2005 (UTC)

Common Programming Errors
Comments:

Paddu said " ", proposed to look into Infoboxes
 * NOTE : Dysprosia agreed but proposed a different book ( Programming:Improving programming skills ), didn't start one and doesn't seem to be a "major" contributor to CPP and never replied if she misunderstood the proposal.
 * Paddu did not advance the idea further.

P1 - Last action -> 17 Oct 2004
 * Panic implemented a limited reference note on possible errors/styles.

 * There are now some limited references on errors/styles so the proposal is dead (will add this to the conventions and remove proposal as adopted, I do think that it can be improved maybe Paddu takes on the idea again)

belongs into every book. There should be a template with a nice icon :). Right now the template should just be panics old one, since it worked. --Max 00:36, 18 September 2005 (UTC)

Reduce the page size more
30k is still awfully large. Pages should actually be much smaller.

Proposed: 18 Sept 2005

This isn't signed, I don't think 30K is a problem should a vote be made on this point (readers should be allowed to vote)--Panic 04:48, 17 January 2006 (UTC)

TODO Boxes
Pro:

 * People see imediately what is missing --Max 00:36, 18 September 2005 (UTC)

Con:

 * May scare readers (this book is not done yet) --Max 00:36, 18 September 2005 (UTC)

Comments:

If not used too often, i'd go with it. --Max 00:36, 18 September 2005 (UTC)

Its like stubs there are no defined rules on how to use them, and I think of the book as never-ending work, there will be always things to add to it...--Panic 02:01, 18 September 2005 (UTC)

Links to wikipedia
Links to wikipedia should be sparse. The should only be uses like other references, e.g. at the end of a chapter: "For further reading, see ..."

Proposed: 18 Sept 2005

This isn't signed, I do agree with the use of space references but not in aggregating them at the end of the book, references should be used to let readers explore some concepts,etc... that do not relate directly with the book topic, or used in a TODO box for future content mining...--Panic 04:56, 17 January 2006 (UTC)

Rename Book + Namespace for this page
I think that we should follow the Wikipedia naming conventions and rename this article to "C Plus Plus" as in Wikipedia:C Plus Plus. Suggestions? --Dionyziz 16:05, 18 Jun 2005 (UTC).

Hy Dionyziz...

Herr, There is already a C plus plus book (I have forked it to build this one) with another filosofy on its order and content, so a rename/merge isn't workable at least at this time... --Panic

Perhaps calling it "CPP" (as in Programming:CPP) then, since that's technically a correct way to name C++? "C -/- -/-" just seems funny/weird.… —qrc July 9, 2005 17:41 (UTC)

You are free to try to centralize the C++ books with a front page and link and try to merge every work (into a new) structure. (that would/should be done in the future)... --Panic 00:58, 27 July 2005 (UTC)

Prehaps you should read the Naming policy. The current name is running under WB:NP. So if at all a new name should be somthing like:

 * Cpp Programming
 * How-To programm in C plus plus
 * Programming in C -/- -/-

Otherwise you end up being not a book but only chapter in a very very big Programming book.

--Krischik 17:57, 6 September 2005 (UTC)

PS: with a good browser/internet connection you can rename about a 100 pages per hour.

Grummbll, it's hard to fallow all the policies as they get changed / created all the time (even if you really don't care about it, my main problem is content not reformatting the books every 4 months because some new order of the bookshelf was adopted, that is real annoying, it's the 3rd time I have to pass that ordeal first in C Plus Plus) I will comply with:

The hyphen convention: Bookname - Chaptername

if no one objects, I'll do the renames as I go along editing stuff (if n1 helps that would be great, but check the dependencies and remember that templates seem to notice page name changes), as for the name I do like the -/- -/- it's the closes to ++ one can get... the problem is with wikimedia not the name in itself, as for CPP (I really don't like it, not even as a file extension for C++ source files) and C Plus Plus only sounds better because it's the name adopted by Wikipedia... so the best option available seems Programming in C -/- -/-

Since I read the page I've noticed The colon convention I'll use that on the Index also...

Finished ... not 100 pages but it took some time... --Panic 04:20, 9 September 2005 (UTC)

--Panic 18:32, 6 September 2005 (UTC)

The suggestion was only for the case that there is an actual rename. You are always free to leave erverything as it is - after all: content is more important.

--Krischik 07:23, 7 September 2005 (UTC)

PS: The hyphen convention is a WB:NP as well.

This page even if it relates to the C plus plus book is only Wikibooks related and should not be in the same namespace of the book, it should be on the talk: --Panic 02:14, 18 September 2005 (UTC)
 * Really? Could you list that policy? I think you're mistaken. MShonle 08:58, 18 September 2005 (UTC)

Hm. I would have liked one page in the main namespace (with the adopted and proposed issues) and one in the talk: namespace with the discussion. I guess we'll have to find the right policy on this one (could you please link it). --Max 03:12, 18 September 2005 (UTC)

I think I saw it, I've looked again and couldn't, but ok let's look at it logically.

What is the difference in the normal namespace or root if you prefer and the Talk: ?

If contributing to the Talk: does it make you an author of the book (and benefit from the rights and obligations of the GFDL ?)

Why are pages that only deal with the structure and local framework of a given work included on an that same book? They can be easily considered off topic, and do not contribute content to the book in itself.--Panic 19:33, 18 September 2005 (UTC)

 * Contributing to the talk does not make you an author, nor would I say would making minor spelling or grammatical fixes make you an author. But that's beside the point. Wikimedia projects are free form, there are no hard and fast rules that claim any page under a given name must be part of the book. This free form nature gives great freedom to contributors. For example, the whole vote for deletion process on wikipedia is just people editing a file, there's no formal voting buttons or things like that. Life changes too much to encode things in the software like that. But even if there were a policy like that, the need for a style-guide would be enough evidence that the policy should change. But this is all moot, considering that (1) style guides are entirely appropriate, (2) it does not matter in any sense if they are or are not part of the book, and (3) many other books do this already. MShonle 19:45, 18 September 2005 (UTC)

I think this discussion belongs into the main wikibooks discussions, until some common policy, ideally for all wikibooks, is reaching. Just the fact that everyone of us three has a different option on what is meant "unspokenly" means that it'll finally have to be spoken. --Max 20:32, 18 September 2005 (UTC)

Done, please check if I've missed any of the related points--Panic 02:24, 19 September 2005 (UTC)

The discussion is in Staff lounge

First, the Programming namespace should be dropped as it is unnecessary and not a real namespace. We don’t have Games:Chess or Languages:Japanese so why Programming:C plus plus?

Second, the + character is now valid for names and should be used for the title of this book.

Gerard Foley 22:18, 10 January 2006 (UTC)

 * I totally agree on both issues! :) --Orderud 00:25, 11 January 2006 (UTC)

I also agree and it's on the naming proposal or guides, but I had some troubles last time defending this view point... I don't agree in calling the book only "C++" --Panic 02:24, 11 January 2006 (UTC)

 * I agree with you here. It should be a book name and not the name of a programming language. See: Ada Programming, C# Programming, Java Programming. Off corse you don't have to follow that lead and can invent your own name. --Krischik T 12:19, 12 January 2006 (UTC)

 * What's wrong with calling the book only C++? Gerard Foley 16:02, 11 January 2006 (UTC)

It's the same as calling all your children Joe... Differentiation...--Panic 17:13, 11 January 2006 (UTC)

 * I don't get you, C++ is fine for Wikipedia and for the Main Page, why not this book? C++ is what people are naturally going to type into the search box. What do you think if should be called? Gerard Foley 00:36, 12 January 2006 (UTC)

 * Look again: those books which have allready moved out of Progamming: use there full name on the Main page. As for search: just hack in "Ada" in the search box an see what happens :-). --Krischik T 12:19, 12 January 2006 (UTC)

C++ is a reference to the language object, it's like calling a C++ compiler "C++ " and justify it's name with a similar logic that you are applying to a book name, a variation of the name should be fine, like "Programming C++" or "C++ Programming" a simple addition to the language name would not only clarify immediately that we are not referring to the C++ Language in itself but to something related (an action or a view point) for example; I'm also contributing to the wikibook "The World of Peer-to-Peer (P2P)" I could have named it "P2P" or "Peer-to-Peer" but I was limiting the usefulness of the book name, adding something to the subject matter will provide a simple extension to the object/objective of the book and give a reader some more info... That said, I don't object to the "C++" name but find it to be limited in itself, and can generate some confusion in the reader... You could check the book covers already submitted for this book for example, the change of the plus for the "+" is a battle I have been having for some time, heck, I have already moved the book 2 or 3 times the last one I was using "-/-" :)... --Panic 03:14, 12 January 2006 (UTC)

 * But you agree that the Programming namespace should go and the plus (+) symbol should be used. Gerard Foley 18:44, 12 January 2006 (UTC)

I do...--Panic 23:11, 12 January 2006 (UTC)

 * Then let me make a suggestion here: Talk:Ada_Programming/New_Name_needed. Of corse I would expect that a main stream language will draw more votes then just 4 :-(. Still we got a result and anyone is happy with it now. --Krischik T 07:44, 13 January 2006 (UTC)

Since we all agree that a rename is in order, I would like to see some names so we can go ahead with a vote on them, even if no other active contributor (author) seems be contributing to this discussion... Just add a list of possible names and I will archive the prev. discussion...--Panic 04:40, 17 January 2006 (UTC)

Votes
All options with redirection from C++ (except the first) and Programming:C_plus_plus. Multiple votes are allowed. Just vote don't discuss, please. Closing day is: 14 March 2006 Closed: --Panic 06:57, 15 March 2006 (UTC).

 C++

(Current books using a similar name: Concurrent Clean, Fortran, Linoleum, Visual Basic .NET, x86 Assembly).

 C++ 2003

(Just kidding...)

 C++ Programming

(Current books using a similar name: Ada Programming, Bourne Shell Scripting, C# Programming, Java Programming, REBOL Programming).

 * Krischik T 07:15, 18 January 2006 (UTC)
 * NickWhaleyIsSexy 02:25, 14 February 2006 (UTC)
 * Panic 03:55, 14 February 2006 (UTC)
 * Merrheim 15:10, 6 March 2006 (UTC)
 * ArnTracks 21:37, 6 March 2006 (UTC)

C++ Programming Language

Programming in C++

How to Program in C++

The votes are now closed, the book shall be renamed as  C++ Programming  action should be initiated as soon as possible by the proponent (try to use a bot if possible so not to break to many things). I'll move the discussion and the topic to the proper sections in a few days and send/post a message to the parts if no reply is made here so to let them know about the result...--Panic 06:57, 15 March 2006 (UTC)

Move protection
Why is this page protected from moves? Gerard Foley 17:14, 15 February 2006 (UTC)

I meen the module page not this this page. Gerard Foley 17:15, 15 February 2006 (UTC)

The page may have been protected by MShonle, I can't remember a reason but probably as result of the merge the book went trough.--Panic 03:18, 17 February 2006 (UTC)(edited)--Panic 03:20, 4 March 2006 (UTC)

This thread was moved from the main wikibook main page talk page to the active book talk page, the correction Gerard Foley makes in his comment is not affected by the move.--Panic 03:31, 4 March 2006 (UTC)

Programming:C plus plus/Hello world, Programming:C_plus_plus/Idioms , Programming:C plus plus/FAQ , Programming:C plus plus/Data Types , Programming:C plus plus/Variables and Expressions are protected--Panic 04:23, 27 March 2006 (UTC)

 * I lifted the protection from those pages, so that any user can move them to their new places. (The protect/unprotect screen gave no reason for the protection; apparently it was before the wiki added a protection log.) --Kernigh 05:33, 29 March 2006 (UTC)

IDE's
A section on various IDE's would be nice... FLOSS ones would be especially nice :) I have no programming experience (although I hope to change that) so I'm not sure which ones would be good for someone learning for the first time, or even if IDE's differ that much from one another. Anyway, just an idea. --AK7 05:53, 25 March 2006 (UTC)

Some IDE information is already present if it grows a stand alone section can be created as it is, it seems to work ok... As for commenting on the IDEs... that doesn't seem possible without using a personal point of view, but you can as users or find on the web other pages that discuss that topic, see the web links section of this book for a place to start ... --Panic 02:18, 15 May 2006 (UTC)

Navigation template
I propose using Template:TopNav or similar minimalistic navigation template to ease navigation throughout the book. Any comments on this? --Orderud 01:01, 2 June 2006 (UTC)

I've seen the examples and can't see the any dif. Parts of the book are already using the / format so top navigation is provided by wikipedia, what is the change in your template? --Panic 16:32, 2 June 2006 (UTC)

 * The links to the next and previous module in the top-right corner makes to easier to navigate through the book. --Orderud 21:50, 2 June 2006 (UTC)

Proposal to add: Your rights
 Your Rights

Contributors will always have the right to RightToFork and the RightToLeave and you must keep in mind Wikibooks Forking policy (we would prefer that you don't but you may find you must).

Proposed: 18 Sept 2005

This are rights given to any author so we should not hide them, they should be made Wikibooks stated policies in the future, why not give this information to future authors ?!?--Panic 02:10, 18 September 2005 (UTC)
 * Wikibooks policy nor the GNU FDL require this at all. It's a very bad idea to tell users they have the right to leave before they've even read what the book was about. Also, the information about WEB addresses isn't even appropriate.. MShonle 04:00, 18 September 2005 (UTC)

I think this is good as a policy (on this page), but not in the actual book page --Max 02:47, 18 September 2005 (UTC)

I think avery effort to clarify the content use and protect authors is welcome, I know that this isn't required by the GFDL (I never said it was), but since the framework of the Wikibooks can make it difficult for a newcomer to obtain the info, the access to it should  facilitated... Max, yes the idea is to keep it on the conventions, it could be more elaborated with the proper references to the Wikipolicies so to facilitate discussion of this and future conventions.--Panic 19:27, 18 September 2005 (UTC)

New presentation
What about changing the look of the book to have something like this Programmation C or Programmation C++ (debutant) in french sorry. Merrheim 19:52, 3 March 2006 (UTC)

Looks great, I think you can do it with no need for a vote on the subject, just add the link to the new display/order on the top next to the single page version of the book or make a selection/entry point menu to the dif. ways a user can access the content and substitute the "cover" page with it. As of using a single finished "look" as the main entry to the book that is another thing (and will probably be voted on as soon as the book "seems" complete, still, we have to remember that this is an ever evolving framework), every reader is a potential contributor to the book, "hiding" the structure/modules and working pages may do more harm than good, the final objective is to have the GFDL content, the visualization or order can have many implementations as we make the content more modular.--Panic 03:15, 4 March 2006 (UTC)
 * I have done a new version of the look of this book see Programming:C plus plus/V2 What's your opinion about this (the previous content is automatically include). (Sorry I can not speak english very well) Merrheim 15:57, 4 March 2006 (UTC)

Humm looks great here the problem could be users with a low resolution have you tried it with the basic 800x600 ?--Panic 01:08, 5 March 2006 (UTC) I think it is possible to have a readable version at each resolution perhaps with small modifications. Merrheim 09:47, 5 March 2006 (UTC)

An other possibility is Programming:C plus plus/V3. I prefere this one (still under construction)! Merrheim 08:26, 7 March 2006 (UTC)

A template for C++ Programming Hello I propose to use this kind of template Programming:C plus plus/V3 with a link to the text version. I don't know if you like this. Merrheim 11:13, 15 March 2006 (UTC)

It looks nice but it isn't finished, is it ? There are some duplication of links and visual information, I can see C++ Programming in 3+ places at the same time with no benefit to a reader (only a bit confusing). --Panic 18:26, 15 March 2006 (UTC)

It is not finish. I will reorganise the plan and correcte the errors. Verify my work please Merrheim 07:32, 16 March 2006 (UTC)

Any update on this... if not I will move discussion and update links so future contribution to the design can be made...--Panic 02:20, 15 May 2006 (UTC)

I notice pages still in the old namespace. I've moved them and fixed links accordingly. Everything should now reside under C++ Programming/V2 and C++ Programming/V3 including the templates that were specific to this book and there should be no pages that refer to the old page names. I've also managed to reduce the number of templates needed for C++ Programming/V3 to just one for the header and chapter listing sidebar. I've also requested speedy deletion of all the old pages since none are needed. --darklama 12:19, 14 September 2006 (UTC)

Is this dead... ?--Panic 16:47, 28 September 2006 (UTC)

It would appear so. As you know I just fixed them up some. I only did it in case they were being used still. I wouldn't have any objections to them being removed. Merrheim hasn't contributed any changes since March 20th from the looks of things, so I think its safe to say that Merrheim is probably not going to be contributing any more work to them. --darklama 14:25, 1 October 2006 (UTC)

There is a proposal to add a new look for this book : see V2 or this one V3

I've removed this from the main page as the statement that this would auto-update is not correct and I don't intend on maintaining more that one TOC, it's sad as some users liked the setup. If no one takes charge of it, I'm moving for a deletion.--Panic 17:27, 20 October 2006 (UTC) - I don't intend on maintaining it either. I'm game for requesting its deletion if you are. If nobody wants to maintain it there really is no need to keep it. --darklama 19:11, 20 October 2006 (UTC)

Lets give it more 7 days if no one speaks up we can proceed with the deletion. --Panic 19:20, 20 October 2006 (UTC)

Almost time. There is also a GUI one that was being worked on, I think by the same person, that seems to have not been mentioned and is in the same boat as V2 and V3. --darklama 18:32, 25 October 2006 (UTC)

Ok darklama will you do it or do you want me to clear them out (there are a set of templates also), the marking for deletion list will include v2, v3 and GUI frameworks, and will include removing references from other pages. --Panic 15:20, 26 October 2006 (UTC)

I think they are only self referencing so it should only be a matter of marking the templates for deletion to have them all be so. I'm just wondering if we should mark them for speedy deletion due to general agreement or for Votes for Deletion to give people one last chance to offer to maintain it. --darklama 19:52, 26 October 2006 (UTC)

Ops, to late, just removed tagged them all for delete... Propose a policy to only accept auto maintainable visualizations of the book, or dictate that the maintaining user must be reached within a limited time frame or the view/bookframework will be marked to speedy deletion. Comments.--Panic 01:48, 31 October 2006 (UTC)

I don't think its compleatly possible to have auto maintainable visualizations. I think the best we can do is try to limit complexity of different views to ones that are more easly maintained. Such as the two table of contents and print views we got now, but I don't think this is currently going to be a problem since there aren't that many people contributing to this book right now to make this worth having some book convention on. --darklama 03:14, 31 October 2006 (UTC)

v2, v3 and GUI have all been deleted along with most of what was left of Programming:C plus plus, Programming: C plus plus, Programming:C -/- -/- and Programming in C plus plus after merging in edit histories for pages that had been copy-pasted. --darklama 20:10, 7 November 2006 (UTC)


text:
Talk:Blender 3D: Noob to Pro/Texturing Basic Seawater

When I render my objects, I'm getting the colors okay, but there is no texture being used. The preview display shows color and texture, but the view window, and the render window do not show texture.

Yafray and Yafaray
This tutorial is out of date because Yafray has been replaced with Yafaray (note additional 'a' after the 'f'). Unfortunately whilst Yafray could be integrated with Blender as an alternative rendering engine, the only way I have found to get Yafaray working with Blender 2.48a on Windows Vista was:

1. to download Yafaray and the QT libs from the Yafaray site,

2. ensuring Python 2.5.2 (and no other version) and MSVC++ 2005 SP1 were installed (as per instructions on Yafaray page),

3. load the Yafaray render script using the menu: Scripts->Render->YafaRay 0.0.3 Export (also installed in the Render menu according to instructions), and clicking on the big render button in the scripts window,

Unfortunately to render with Yafaray the scene materials need to be modified using the YafaRay 0.0.3 Export script settings - it will not use Blender materials. This puts the use of Yafaray outside the scope of tutorials at this level.

In short - use the Extra Practice tutorial at the bottom of the page instead.


text: Template:Grey Warning

title: Template:Grey Warning


text:
ILife/iTunes/The iTunes Interface

The best way to start learning a new application is to take a quick look at its interface. This sub-chapter tells you what's what in the iTunes window.

Toolbar
Like almost every other Mac program, iTunes has a toolbar right under its title bar. It includes some of the most important controls you'll use.

 * Playback Controls - The three circular buttons on the left-hand side of the toolbar control the playback of music and video files. Directly to their right is a volume slider for adjusting the sound volume.

 * Display - iTunes has a pale yellow "display" smack in the middle of the toolbar. This display can show the currently playing song, a level meter, or the status of ongoing tasks such as updating an iPod. To cycle through the available things to display, click the small right-arrow button on the left side of the display. More information about this display

 * View Controls - These three conjoined buttons let you select a view for your media. You'll learn about views later on.

 * Search Field - This Spotlight search field lets you find your media fast.

Status Bar
iTunes has a status bar running along the bottom of its window. In the middle, iTunes puts a bit of text telling you just what you're viewing: how many files, how long it would take to listen or watch them all, and how much space they're taking up on your hard drive. Buttons appear at either end of the status bar. The ones on the left side are always there, and the ones on the right come and go depending on what you're doing. We'll tell you about the buttons here as we go.

Source list
The source list is to the left of the screen, right under the playback controls. The source list is divided into several sections that keep the various sources organized. The headings disappear if there are no sources of that type, so you might not see all of them. The following sections are organized to mimic iTunes' organization.

Library
Every media file on your computer that iTunes knows abou shows up in the library. Depending on what type of media it is, it will show up in different sources. These include: movies, TV Shows, Podcasts, Audiobooks, iPod Games, Radio, and Party Shuffle. You can use the iTunes Preferences (under the "General" tab) to hide sources you aren't using. The libraries for each media type have all of that type of file in them.

Store
The icons in this section are all green for easy identification. The first icon is a link to the iTunes Store, just like it says. The second icon is a playlist of all the files purchased from the iTunes Store, though it can be rearranged just like any other playlist. The third icon is the download menu, which appears only if your computer is downloading a file from the iTunes Store. It can be used to stop, restart, and organize downloads.

Devices
This section holds the controls for all of the devices currently hooked up to your computer that iTunes recognizes. This includes iPods, and also Apple TV and iPhone, two upcoming Apple products. Each device can be managed individually.

Shared
Your computer can connect to other computers connect to yours on a wired or wireless network and listen to music from their library. This music is streamed from their hard drive to yours. It is not permanently stored on your computer. Each shared library appears as a different icon.

Playlists
While most of the other sources are generated automatically, Playlists are customizable lists of media that will play sequentially. You can have as many or as few Playlists as you like; iTunes gives you a starter set. You can even put different Playlists into folder trees (folders can be created in the File menu), and these folders transfer to iPods they are synced to.

Smart Playlists are special Playlists that you cannot edit directly. They are similar to the Finder's Smart Folders, in both function and icon. They contain all songs that meet one (or all) of criterion set by you. Smart Playlists can also be based on albums, genre, ratings, play count, or utter randomness.

title: ILife/iTunes/The iTunes Interface


text:
ILife/iTunes/Getting Music In

Before you can organize and listen to your digital music, you'll need to get it into your iTunes library. The steps you must follow vary depending on where your music is currently stored.

From Music CDs
If you're like most people, you've already accumulated a large collection of music on CDs. It would be a real shame if a new way to store music came along, rendering your CDs useless. The next way to store music has arrived...but keep your CDs! iTunes lets you take existing CD collection and copy the songs right to your computer with the push of a button. Follow the two steps below and you'll be up-to-date in no time.

Step 1: Setting Up
Before you "import" (copy) your collection into your Mac, you should take a moment to set up. Choose iTunes > Preferences, click the "Advanced" tab (labeled with a gear), and then choose the "Importing" tab underneath.

Picking an Encoder
First of all, you must choose which encoder iTunes should use when importing a CD. An encoder is a set of instructions the computer uses to make a certain type of file out of a song on a CD. We recommend that you use the AAC encoder, which generates a kind of music file called... an AAC file! These files take up very little hard drive space, but have impressive sound quality. You may also prefer the more popular but less high-tech MP3 encoder, which generates MP3 files. MP3 files take up more room than similar AAC files, but you'll find that more programs support them.

Picking a Quality Setting
Next you must set the quality you wish to use to import your music. The AIFF, Apple Lossless, and WAV encoders do not let you choose a quality setting, but the MP3 and AAC encoders discussed above do. It is strongly reccomended that you keep quality at or above the "High Quality" setting. Below this, flaws in the sound quality become apparent even without close inspection.

The "Custom" option is for audiophiles only, and lets you mess with variable bit rate settings, frequency filtering, etc.

Step 2: Importing the Music
Now that you have your encoder set up to your liking, it's time to do the actual importing. Insert a CD, and it will appear in the "Devices" section of the source list. Select it, and you should see a list of songs. If you see generic "Track 1, Track 2..." names, read the warning above.

You can preview any song simply by double-clicking its title. Check the little boxes next to the songs you wish to import, and make sure the songs you don't want to import aren't checked. Now press the button labeled "import" in the lower-righthand corner and iTunes will go through and copy the songs to your computer. This might take a few minutes.

When all the songs you picked are done importing, your CD has been successfully imported! The songs are now in your library. Please refer to the next chapter to find out what to do next!

From your Hard Drive
If you already have digital music files lying around your hard drive, you can add them to iTunes very easily. Simply select "Music" in the Library section of the Source List. Then drag and drop files into the contents pane. Done! The file is now in your library. Note that you will have to enter the information for the file manually, because the Gracenote CD Database, as the name implies, works only for CDs.

title: ILife/iTunes/Getting Music In


text:
ILife/iTunes/Organizing Media

Organizing your Media
iTunes was the first application to introduce Apple's famous "Library/Collections" method for organizing items. All music you add to iTunes is stored in a central storage area called your "Library". You can then create lists of music called playlists, which include only links to songs that live in your library.

Playlists
To create a new blank playlist, press the + button below the sidebar.

Folders
Folders are a convenient way of keeping playlists organized. They also act like playlists themselves, becoming a sort of playlist of playlists. Selecting a folder in the sidebar will display every song in every playlist contained within it in the contents pane. With a little imagination this can prove to be a powerful feature.

title: ILife/iTunes/Organizing Media


text:
ILife/iTunes/The iPod

You probably know that the iPod is Apple's popular portable digital music player. These days, you can spot the signature white earbuds everywhere you go, and you've probably know that the latest models can play movies and photos in addition to music. But can you handle using an iPod, or should you let the technically inclined have all the fun? One of the reasons the iPod is so successful is that it's very easy to use. If you ever feel uncertain, just use this chapter.

Determining your iPod's model
There are six different models of Apple's flagship iPod. While their branding refers to them all simply as "iPod", Apple's support team refers to them by most important new trait in each new model:

 * iPod with Scroll Wheel - This iPod's wheel actually moves under your finger. It is white.
 * iPod with Touch Wheel - This iPod's wheel is white and touch sensitive, but its buttons are not. It is white.
 * iPod with Dock Connector - This iPod has four touch-sensitive buttons lined up above the wheel. It is white.
 * iPod with Click Wheel - This iPod has its buttons inside the wheel, which is grey. It has a black and white screen. It is white (except U2 edition, see below).
 * iPod with Color Display - This iPod is identical to the iPod with Click Wheel, but has a color screen. It is white (except U2 edition, see below)
 * iPod with Video Playback (current) - This iPod supports video playback, and has a large color screen. It comes in black or white (plus U2 edition, see below),

In addition, Apple has produced three spin-off iPods:

 * iPod mini - This iPod is made of silver, blue, pink, green, or gold-colored aluminum. It has a black-and white screen.
 * iPod shuffle (current) - This iPod does not have a screen.
 * First Generation - White, and about the size of a stick of gum.
 * Second Generation (current) - Made of silver, blue, pink, green, or orange-colored aluminum. It has a built-in clip.
 * iPod nano (current) - This iPod is as thin as a pencil and has a color screen.
 * First Generation - White or black front with a mirror-like back.
 * Second Generation (current) - Made of silver, blue, pink, green, or black-colored aluminum.

It is important to know your iPod's model when setting it up or using it with iTunes.

iPods with a Screen
The iPods with a screen are the iPod, iPod Video And the iPod Nano. The first iPod was released in 2003. A computer is needed to use an iPod (if you have an iPod, but no software you can download iTunes Now at http://www.apple.com/itunes/overview/

The 30g iPod Video holds 7,500 songs & 40 videos, The 80g iPod Video holds 15,500 songs & 60 videos, The 1g iPod Nano holds 100 songs & 1 12min video and The 2g iPod Nano holds 180 songs & 2 12min videos.

title: ILife/iTunes/The iPod


text:
User talk:213.218.243.204

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:213.218.243.204


text:
User talk:201.235.199.119

Hello, Gary. Welcome to Wikibooks, Wikiversity, and the School of Magic! Maybe you would like to create an accout? If so, follow this link. It's helpful a lot, and it gives you more privacy. --George D. Bozovic talk 22:57, 13 January 2006 (UTC)

authors: Ђорђе Д. Божовић~enwikibooks

title: User talk:201.235.199.119


text:
Talk:Microsoft Certified Professional Developer

Naming policy
I suggest renaming like this:
 * Microsoft Certified Professional Developer (MCPD) -> "Microsoft Certified Professional Developer"
 * Exam 70-536 -> "Microsoft Certified Professional Developer/Exam 70-536"
 * Microsoft Certified Technology Specialist/Exam 70-536/Value types -> "Microsoft Certified Professional Developer/Exam 70-536/Value types"

See Naming policy. The problem with Exam 70-536 is that the module name does not start with the name of its book. Modules like Microsoft Certified Technology Specialist/Exam 70-536/Value types have a different problem: now the module starts with the name of a nonexistant book, "Study Guides", further it mixes colons with backslashes.

Using forward slashes like/these/will allow easier linking, for example you will be able to write /Value types/ at the Exam 70-536 page to link to the Value types page, if the names are as I suggested above.

I think that the "(MCPD)" is redundant, so my suggestions removed it. --Kernigh 01:47, 14 January 2006 (UTC)

The instructions for renaming pages are at Help:Pages. --Kernigh 01:48, 14 January 2006 (UTC)

Changes the links because the renaming were done --Jacques (talk) 20:23, 6 December 2007 (UTC)


text:
User:AmethystAngel~enwikibooks

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

title: User:AmethystAngel~enwikibooks


text:
User:SCEhardt

I am usually found on Wikipedia, where I have the same username.

title: User:SCEhardt


text:
User talk:SCEhardt

I have no idea how often I will be here, so drop me a note at my Wikipedia talk page if you'd like a quicker response!

title: User talk:SCEhardt


text:
User talk:Cshank

Hello and welcome to Wikibooks!

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

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

Good luck! -- LV (Dark Mark) 06:15, 14 January 2006 (UTC)

title: User talk:Cshank


text:
Java Programming/Throwing and Catching Exceptions

Language compilers are adept at pointing out most of the erroneous code in a program, however there are some errors that only become apparent when the program is executed. Consider the code listing 6.1; here, the program defines a method divide that does a simple division operation taking two integers as parameter arguments and returning the result of their division. It can safely be assumed that when the divide(4, 2) statement is called, it would return the number 2. However, consider the next statement, where the program relies upon the provided command line arguments to generate a division operation. What if the user provides the number zero (0) as the second argument? We all know that division by zero is impossible, but the compiler couldn't possibly have anticipated the user providing zero as an argument.

Such exceptional code that results in erroneous interpretations at program runtime usually results in errors that are called exceptions in Java. When the Java interpreter encounters an exceptional code, it halts execution and displays information about the error that occurs. This information is known as a stack trace. The stack trace in the above example tells us more about the error, such as the thread —  — where the exception occurred, the type of exception — , a comprehensible display message —  , and the exact methods and the line numbers where the exception may have occurred.

Exception object
The preceding exception could have been created explicitly by the developer as it is the case in the following code:

Note that when  equals zero, there is no return value. Instead of a  generated by the Java interpreter itself, it is an exception created by the coder. The result is the same. It shows you that an exception is an object. Its main particularity is that it can be thrown. An exception object must inherit from. Standard exceptions have two constructors:
 * 1) The default constructor; and,
 * 2) A constructor taking a string argument so that you can place pertinent information in the exception.

This string can later be extracted using various methods, as you can see in the code listing 6.2.

You can throw any type of Throwable object using the keyword. It interrupts the method. Anything after the throw statement would not be executed, unless the thrown exception is handled. The exception object is not returned from the method, it is thrown from the method. That means that the exception object is not the return value of the method and the calling method can be interrupted too and so on and so on...

Typically, you'll throw a different class of exception for each different type of error. The information about the error is represented both inside the exception object and implicitly in the name of the exception class, so someone in the bigger context can figure out what to do with your exception. Often, the only information is the type of exception, and nothing meaningful is stored within the exception object.

Oracle standard exception classes
The box 6.1 below talks about the various exception classes within the  package.

/ statement
Try/Catch is straight up better. By default, when an exception is thrown, the current method is interrupted, the calling method is interrupted too and so on till the  method. A thrown exception can also be caught using a / statement. Below is how a /  statement works:

The executed code lines have been highlighted. When no exception is thrown, the method flow executes the  statement and not the   statement.

As there is a thrown exception at line 5, the line 6 is not executed, but the exception is caught by the  statement so the   block is executed. The following code is also executed. Note that the  statement takes an exception as parameter. There is a third case: when the exception is not from the same class as the parameter:

It is as if there is no /  statement. The exception is thrown to the calling method.

blocks
A /  statement can contain several   blocks, to handle different exceptions in different ways. Each  block must take a parameter of a different throwable class. A thrown object may match several  block but only the first   block that matches the object will be executed. A catch-block will catch a thrown exception if and only if: This means that the  block order is important. As a consequence, you can't put a  block that catches all the exception (which take a   as parameter) before a   block that catches a more specific exception as the second block could never be executed.
 * the thrown exception object is the same as the exception object specified by the catch-block.
 * the thrown exception object is the subtype of the exception object specified by the catch-block.

At line 14, we use a multi-catch clause. It is available since the JDK 7. This is a combination of several catch clauses and let's you handle exceptions in a single handler while also maintaining their types. So, instead of being boxed into a parent Exception super-class, they retain their individual types.

You can also use the  class here, since Throwable is the parent class for the application-specific Exception classes. However, this is discouraged in Java programming circles. This is because Throwable happens to also be the parent class for the non-application specific Error classes which are not meant to be handled explicitly as they are catered for by the JVM itself.

block
A block can be added after the   blocks. A  block is always executed, even when no exception is thrown, an exception is thrown and caught, or an exception is thrown and not caught. It's a place to put code that should always be executed after an unsafe operation like a file close or a database disconnection. You can define a  block without   block, however, in this case, it must be followed by a   block.

Example of handling exceptions
Let's examine the following code:

In the code section 6.7,  is invalid. Because  and   pass (or throw) exceptions,   must be prepared to handle them. This can be handled in two ways: a - block, which will handle the exception within the method and a clause which would in turn throw the exception to the caller to handle. The above example will cause a compilation error, as Java is very strict about exception handling. So the programmer is forced to handle any possible error condition at some point.

A method can do two things with an exception: ask the calling method to handle it by the declaration or handle the exception inside the method by the - block.

To work correctly, the original code can be modified in multiple ways. For example, the following:

The  from   will be handled locally, while   and   will be thrown to the caller to handle it. Most of the developers are embarrassed when they have to choose between the two options. This type of decision should not be taken at development time. If you are a development team, it should be discussed between all the developers in order to have a common exception handling policy.


text:
Talk:Java Programming/Throwing and Catching Exceptions

Examples
It would be much better if we could use a real-life example that the reader could compile and test himself instead of the general examples I gave --Mikm 07:39, 14 January 2006 (UTC)
 * The page has been completed with other usable examples. Ftiercel (discuss • contribs) 18:46, 9 August 2013 (UTC)

Missing info
Using the try-with-resources statement ("try (...){...}..."):
 * The opened resources will auto-close at the end of the code block.
 * If the resources doesn't open, an error will be thrown. --NoToleranceForIntolerance (discuss • contribs) 15:22, 12 May 2017 (UTC)
 * I agree. It should be added. Ftiercel (discuss • contribs) 18:09, 15 May 2017 (UTC)


text:
Cookbook:Sinigang (Philippine Sour Soup)

| Cuisine of the Philippines

Sinigang, the famous sour soup of the Philippines, is a fruity sour-based soup boiled with either pork, beef, chicken, fish or seafood. A variety of vegetables can be included, but onions and tomatoes are required. Root vegetables are too starchy and not recommended, with the exception of taro root, which adds a milky and starchy texture. Okra can also provide a pleasant thickness, although it is more clear or transparent. The most common souring agent for the soup is tamarind, but unripe mango, calamansi juice, unripe watermelon, starfruit, cane vinegar, citrus juice, guava, and kamias can also be used. The meat and tomato provide a savory umami flavor, while fatty meat tempers the sourness. Semi-hot chile peppers add mild spice and make the soup aromatic.

Sinigang was often compared to Tom Yam of Thailand, but Sinigang is more sweeter and lighter in spice, contrast to strong flavor of Thai variety. Some critics say Sinigang should be considered a national food of the Philippines, since it originates in the local cuisine.

Ingredients

 * Sampaloc (tamarind) fruits or ready-to-use tamarind paste
 * 1 onion, chopped
 * 4–6 tomatoes, quartered
 * ½–1 kg pork belly, cubed
 * 250 g taro root, diced or sliced into chunks
 * 3–4 horseradish, sliced
 * 200 g string beans, cut in 1-inch pieces
 * 1–3 onions, quartered
 * 250 g kangkung (water spinach) leaves or other leafy yet crunchy vegetable even when cooked.
 * 5 Tbsp fish sauce
 * Salt
 * Pepper
 * MSG (optional)
 * 3 green chiles (e.g. serrano or any other fragrant and mild variety)

Procedure

 * 1) If using whole tamarind, boil it in water until the shells crack, then work the flesh away from the seeds and strain, reserving all the liquid for the soup. Skip this process if using packed tamarind base.
 * 2) Sauté the chopped onions in another large pot.
 * 3) Add the tomato and pork to the onions, and sauté until the pork is no longer pink.
 * 4) Add enough water or boiled tamarind stock to cover the contents of the pot. Boil until tender.
 * 5) Add taro root, and simmer until soft and tender. The soup should to thicken at this point.
 * 6) Add the horseradish, and simmer until tender-crunchy.
 * 7) Add the string beans, quartered onions, and water spinach. Simmer for another 2–3 minutes.
 * 8) Check to make sure all ingredients were cooked enough, then add the tamarind pack if using.
 * 9) Add fish sauce, salt, pepper, and MSG to taste. Top with green chillies.
 * 10) Serve hot.

Sinigang na Baboy


text:
Cookbook:Cirdingis (Chechen Meat and Dumplings)

Cirdingis (pronounced as "jirdingish") is a traditional Chechen meal consisting of dumplings and meat served with accompanying sauces. It may also be called "galnish".

Ingredients

 * 1 kg red meat
 * ½ kg flour
 * 3 cloves garlic
 * Salt
 * Tomato paste
 * Oil


text:
Cookbook talk:Cirdingis (Chechen Meat and Dumplings)

This was transwikied from the English Wikipedia. Here is its history: * (cur) (last) 03:39, 27 December 2005 Bunchofgrapes (afd) * (cur) (last) 06:02, 9 September 2005 Kel-nage m (Removed unneeded last comment) * (cur) (last) 18:27, 26 May 2005 Skorkmaz * (cur) (last) 18:30, 5 May 2005 Skorkmaz * (cur) (last) 18:30, 5 May 2005 Skorkmaz * (cur) (last) 18:33, 4 May 2005 Skorkmaz * (cur) (last) 18:33, 4 May 2005 Skorkmaz * (cur) (last) 18:32, 4 May 2005 Skorkmaz * (cur) (last) 18:25, 4 May 2005 Skorkmaz * (cur) (last) 18:24, 4 May 2005 Skorkmaz * (cur) (last) 18:23, 4 May 2005 Skorkmaz * (cur) (last) 17:52, 24 March 2005 Lectonar m (stub sorting) * (cur) (last) 01:13, 23 March 2005 Skorkmaz * (cur) (last) 01:08, 23 March 2005 Skorkmaz * (cur) (last) 01:04, 23 March 2005 Skorkmaz * (cur) (last) 00:56, 23 March 2005 Skorkmaz * (cur) (last) 00:56, 23 March 2005 Skorkmaz * (cur) (last) 00:51, 23 March 2005 Skorkmaz * (cur) (last) 00:50, 23 March 2005 Skorkmaz * (cur) (last) 00:48, 23 March 2005 Skorkmaz * (cur) (last) 00:41, 23 March 2005 Skorkmaz * (cur) (last) 00:39, 23 March 2005 Skorkmaz Johnleemk 13:34, 14 January 2006 (UTC)


text:
User:Johnleemk

Please see w:User:Johnleemk.

title: User:Johnleemk


text:
User talk:Johnleemk

'Welcome to my talk page''; feel free to leave any enquiries/comments/brickbats you feel like leaving here. I am not active on this project, so if you need a quick reply, please contact me at the English Wikipedia.'''

title: User talk:Johnleemk


text:
Talk:PHP Programming/The if Structure

Random PHP Code at Bottom of Page
There was a random non-formatted line of PHP at the bottom of the page within the more info section. I deleted it.

Using AND and OR in examples
In my years of doing PHP programming, I have not seen anyone using the long forms 'and' and 'or'; rather, developers seem to prefer using && and || (I know I do). I think the short forms should be substituted, though both work. Thoughts? --Spoom 04:23, 15 January 2006 (UTC)

Discussion on logic
Does this belong here or elsewhere? I don't think a discussion on logic pertains only to if statements; it's more of a discussion on boolean logic, which also relates to whiles, do whiles, and the boolean type. 63.194.85.39 02:45, 25 February 2006 (UTC)

Printing alphabet example
I removed the following example, since it demonstrates an example of how to use while, not if. 217.211.181.209 22:29, 24 July 2006 (UTC)

printing alphabet in php Example

title: Talk:PHP Programming/The if Structure


text:
Talk:Robotics/Types of Robots/Wheeled

needs more info abt caster wheels and a whole lot more.the page is a bit too specific abt the actuators (servo,IC engines) which is not good IMHO.--Sahodaran 16:55, 14 January 2006 (UTC) You're welcome to add one or more section on caster wheels. I'm not sure what you mean with being too specific. IMO the page covers only the concepts and doesn't contain much detail at all. --Patrik 19:40, 14 January 2006 (UTC)

title: Talk:Robotics/Types of Robots/Wheeled


text:
General Chemistry/Nomenclature

Naming Ions and Ionic Compounds
Ionic compounds consist of cations (positive ions) and anions (negative ions). The nomenclature, or naming, of ionic compounds is based on the names of the component ions. Here are the principal naming conventions for ionic compounds, along with examples to show how they are used:

Roman Numerals A Roman numeral in parentheses, preceded by the name of the element, is used for elements that can form more than one positive ion.

This is usually seen with transition metals. Iron (II) Iron (III) Copper (I) Copper (II)

-ous and -ic Although Roman numerals are used to denote the ionic charge of cations, it is still common to see and use the endings -ous or -ic. These endings are added to the Latin name of the element (e.g., stannous/stannic for tin) to represent the ions with lesser or greater charge, respectively. The Roman numeral naming convention has wider appeal because many ions have more than two valences. Ferrous Ferric Cuprous Cupric

-ide The -ide ending is added to the name of a monoatomic anion of an element. Hydride

Fluoride Oxide Sulfide Nitride Phosphide

-ite and -ate Some polyatomic anions contain oxygen. These anions are called oxyanions. When an element forms two oxyanions, the one with less oxygen is given a name ending in -ite and the one with more oxygen is given a name that ends in -ate. Nitrite Nitrate Sulphite Sulphate

hypo- and per- In the case where there is a series of four oxyanions, the hypo- and per- prefixes are used in conjunction with the -ite and -ate suffixes. The hypo- and per- prefixes indicate less oxygen and more oxygen, respectively. Hypochlorite Chlorite Chlorate Perchlorate

bi- and di- hydrogen Polyatomic anions sometimes gain one or more ions to form anions of a lower charge. These ions are named by adding the word hydrogen or dihydrogen in front of the name of the anion. It is still common to see and use the older naming convention in which the prefix bi- is used to indicate the addition of a single hydrogen ion. Hydrogen carbonate or bicarbonate Hydrogen sulfate or bisulfate Dihydrogen phosphate

Naming Binary Acids
Binary acids are compounds containing Hydrogen and an anion (non-metal ion).

When these compounds are in solution in water, oxonium ions are formed giving rise to the properties that we associate with 'acids'.

In general, when the binary acid is not in solution the name is as follows: 'Hydrogen' followed by the anion name ending in '-ide'.

e.g. Hydrogen chloride

When the binary acid is in solution (aq) the name is as follows: 'Hydro-' followed by the anion name ending in '-ic' then add the word 'acid' to the end.

e.g. Hydrochloric acid

title: General Chemistry/Nomenclature


text:
User:Dirtyliberal~enwikibooks

I don't really use wikibooks as much as I do wikipedia. Check out my userpage at Dirtyliberal

title: User:Dirtyliberal~enwikibooks


text:
ZK

Collection of articles from community collaboration for the ZK framework.

Contents

 * /How-Tos/
 * /Examples/

ZK

title: ZK


text:
Java Programming/Arrays

An array is similar to a table of objects or primitive types, keyed by index. You may have noticed the strange parameter of the default  method  since the beginning of the book. It is an array. Let's handle this parameter:

In the code listing 3.15, the array is. It is an array of  objects (here those objects are the words that have been typed by the user at the program launching). At line 4, One contained object is accessed using its index in the array. You can see that its value is printed on the standard output. Note that the strings have been put in the array with the right order.

Fundamentals
In Java, an array is an object. This object has a given type for the contained primitive types or objects (, ,  , ...). An array can be declared in several ways:

Those syntaxes are identical but the first one is recommended. It can also be instantiated in several ways:

At line 1, we instantiate an array of 10 items that get the default value (which is 0 for ). At lines 2 and 3, we instantiate arrays of 10 given items. It will each be given an index according to its order. We can know the size of the array using the  attribute:

Arrays are allocated at runtime, so the specified size in an array creation expression may be a variable (rather than a constant expression as in C). However, the size of an instantiated array never changes. If you need to change the size, you have to create a new instance. Items can be accessed by their index. Beware! The first index is 0:

If you attempt to access to a too high index or negative index, you will get an.

Question 3.20: Consider the following code:

What will be printed in the standard output?

Indexes start at 0. So the index 1 point at the second string. There are 4 items so the size of the array is 4. Hence the item pointed by the index 3 is the last one.

Two-Dimensional Arrays
Actually, there are no two-dimensional arrays in Java. However, an array can contain any class of object, including an array:

It's not exactly equivalent to two-dimensional arrays because the size of the sub-arrays may vary. The sub-array reference can even be null. Consider:

Note that the length of a two-dimensional array is the number of one-dimensional arrays it contains. In the above example,  is 3, whereas   is 5.

In the code section 3.58, we defined an array that has three elements, each element contains an array having 5 elements. We could create the array having the 5 elements first and use that one in the initialize block.

Question 3.21: Consider the following code:

Print the whole alphabet in the standard output.

will be the indexes of the main array and  will be the indexes of all the sub-arrays. We have to first iterate on the main array. We have to read the size of the array. Then we iterate on each sub-array. We have to read the size of each array as it may vary. Doing so, we iterate on all the sub-array items using the indexes. All the items will be read in the right order.

Multidimensional Array
Going further any number of dimensional array can be defined. or

de:Java_Standard: Felder Programación en Java/Arrays Programmation Java/Tableaux Programmeren in Java/Arrays Java/Vetores

title: Java Programming/Arrays


text:
Talk:Physical Activity/Strength Training

if you push a muscle past its limit, it breaks. Typically during a workout, a person keeps the muscle within its limits, possibly only pushing it to its limit, where it would fail. It would then not be possible to push the muscle any more. It is possible to push a muscle past its limit. This occurs when an ankle is sprained, or any other muscle is pulled.CatastrophicToad 23:11, 14 January 2006 (UTC)


text:
User:Geoking66~enwikibooks

About Me
I'm a student who is a firm believer in Wikipedia and Wikibooks. I have a Wikipedia user account of the same name.

title: User:Geoking66~enwikibooks


text: User talk:66.31.130.21

title: User talk:66.31.130.21


text:
User:ThePacker

Hi folks,

 * my home de:Benutzer:ThePacker - but you can still talk in english to me.

regards, ThePacker

Contributions to Wikibooks

 * Translation of Wikijunior Solar System into german on german wikibooks de:Wikijunior_Sonnensystem.
 * A book on datacompression in german de:Datenkompression

__NOINDEX__

title: User:ThePacker


text:
Template talk:Unreferenced

No one was using unreferenced, so I tried an experiment and replaced it with a template that might be useful. --Kernigh 01:56, 15 January 2006 (UTC)

title: Template talk:Unreferenced