OpenLLM-France/wikimedia huggingface dataset:
# XForms/Search Amazon
## Motivation

Here is an example web service provided by Amazon. It also uses the custom control to bind images from the output to the screen.

## Link to XForms Application

Load Form

## Discussion

Note: If you get the following error:
You will have to remember to escape the ampersand before after you copy and paste this example into your text editor. You can get around this by doing a copy from the edit panel or just putting the following into the separator field:

## References

This program was based on an example provided by formsPlayer .
# XForms/Search with Load
## Motivation

You want to build a web form that does a search using the xf:load element. This allows you to rewrite the URL to the search application.

## Discussion

Note that you must use the xf:value attribute of the resource element.
# Using and accessing MATE/Sommaire

Welcome
* MATE Basic concepts
* Writer, word processing
* File manager
* Get help using MATE
* System configuration
* Introduction to the Internet
Shortcuts list
# Using and accessing MATE

Template:NavDébut Template:Page de garde
Table of contents
Welcome
* MATE Basic concepts
* Writer, word processing
* File manager
* Get help using MATE
* System configuration
* Introduction to the Internet
Shortcuts list
# Using the 3D Connexion SDK/Getting Started
### About 3D Connexion

3D connexion is a Logitech company which produces 3D input devices for personal and professional use. WikiBooks is not a place to advertise products, so for those who wish to find out more about 3D connexion products, please visit the 3D connexion Website

### Pre-Requisites

Before getting started, you will need to download Microsoft Visual Basic. I would recommend the free express edition, available from Microsoft. Mac users will need to improvise at this stage (edit- any suggestions?).
You will also need to register with 3D connexion to gain access to the SDK files for free. VB.zip will form the template for the visual basic programs on this tutorial.
* Next: A Quick Introduction to programming and Visual Basic
* Home
# Using an Abacus/Multiplication

Multiplication is, by definition, the addition of some number so many amount of times. Therefore, to multiply a number by a desired number requires the same principle.
To multiply:
* Display the original number.
* Think of desired multiplier.
* If multiplier has more than one digit, multiply by digits separately
* Add the original number however many times desired.
* Move to the next digit and repeat step 4 if multiplier has more than one digit.
Example: (4×5)
Here is another example with one number having two digits: (5×2.5)

## External links

* Multiplication on a Japanese abacus selected from Abacus: Mystery of the Bead
# Using the 3D Connexion SDK

For many people, developing software based on a specific piece of hardware can be a daunting task. This book is aimed at those with one year or less experience in programming. It is ideal to inspire those new to programming through practical exercises based on a real world example.
The main language used in this book will be Visual Basic. Many experienced programmers will pick up the basics of the SDK quickly and soon begin making their own software. Please feel free to add a chapter on your program—the more the merrier.
Some of the content of this book goes above the level of understanding required to effectively use Visual Basic. These paragraphs will be clearly identified using a different color

## Contents
### Section 1

Getting Started

### Section 2

Chapter 1: An Introduction to Visual Basic
Chapter 2: Hello World: Your First Program
Chapter 3: Using Variables
Chapter 4: Procedures

### Section 3

Chapter 1: Introducing the 3D Connexion SDK
Chapter 2: Getting Variables: Live Readout
Chapter 3: Creating Events: The Burglar Alarm
Chapter 4: Controlling an object: Image Scrolling
Chapter 5: Photo Browser
Chapter 6: Web Browser
Chapter 7: Pong
Chapter 8: Getting 3D
Chapter 9: Remote Control
# Using the 3D Connexion SDK/A Quick introduction to Visual Basic
## A Quick introduction to programming and Visual Basic

There are many excellent references for learning to program in Visual Basic. Sites such as the Microsoft Developer Network provide a good overview, and the WikiBook [Visual Basic] provides an excellent guide for those with some experience in programming.
It may be useful for those new to programming to read the following section, however, those with experience in Visual Basic Programming should skip to the next section.

### Getting Ready

Let's get started and open up Visual Basic Express (In the Prerequisites section). The program should look like this (arrangements of toolbars may vary): (IMAGE1) Hit CTRL+N to start a new project. This window allows you to choose a project to start.
(IMAGE2)
Most courses start on Consoles (text only), but we're going to start with a Windows Forms Application. We want to create something which looks good (rather than a console window). Double Click the 'Windows Forms Application' to open a new application. You should see this:
(IMAGE3)
Look at the 'Solution Explorer' Panel. This shows all the parts of the program. We have "Windows Application 1", a default name for the program. This contains "My Project" and "Form1.vb". My Project is a set of instructions which tell the computer to run your 'form' (programmer jargon for a window). Form1.vb is a form which you can edit. This has 2 parts: Design and Code. You can switch between these by using these buttons in the Solution Explorer:
(IMAGE4)
Let's look at the code by pressing the View Code Button. (IMAGE5) You can see a text document. This contains some instructions already built in. It should say:
This is simply a way to start and stop the code. Form 1 is a "Class", basically this means that it can contain other bits of code. Making it Public means that other bits of code can refer to it (e.g. If you made another form it could get information from form1). You'll come across Private code later; this is code which can only be accessed by things in the same form.
# Using an Abacus/Subtraction
## Subtraction

Subtraction is the second most basic function of the abacus. The subract, the user displays the original number and takes away the desired amount of beads from the original number.
Example: (12-4)

## External links

* Subtraction on a Japanese abacus selected from Abacus: Mystery of the Bead
# WebObjects/Mailing Lists

The most active WebObjects mailing lists are hosted by Apple.
* Apple hosted discussion about WebObjects development
* Apple hosted discussion about deploying WebObjects applications
* Apple hosted announcements relating to WebObjects
* Omni Group WO-dev mailing list
* WOLips Mailing Lists
* Project WONDER mailing list
* Google group for WebObjects Tips
# WebObjects/Overview/History

The contents of this wikibook are out of date and have now moved to http://wiki.objectstyle.org/confluence/display/WO/Home.
WebObjects was initially created at Next. There was a framework called DBKit, which provided a way to abstract legacy databases to an object-relational graph. This framework later became the Enterprise Objects Framework.
EOF was used to build nibware, runnable applications for NextStep/OpenStep that were built with Project Builder and which used interfaces that were designed in Interface Builder. If this sounds familiar, it is because the ideas from that time have only been refined, and not fundamentally changed, to become the Cocoa frameworks for applications running on Mac OS X today.
WebObjects was built on top of DBKit/EOF to provide a way to create applications for the World Wide Web. The first versions of WebObjects were created at Next around the latter half of 1992.
(This information can be fleshed out and corrected when the information from the 2007 WWDC is more widely available.)
# WebObjects/Overview/Key Value Coding

The contents of this wikibook are out of date and have now moved to http://wiki.objectstyle.org/confluence/display/WO/Home.
If you familiar with OGNL then key value coding is a bit like that. We'll call key value coding KVC in the context of this page to abbreviate. KVC also exists in the Cocoa infrastructure shipped with MacOS-X as well as the OPENSTEP infrastructure. In this page we will focus on KVC in the context of WebObjects and java.

## Conceptual Aspects

Consider the following model segment;
This model shows a number of entities and the lines between the entities show relationships. For example, the Organisation entity has a to-one relationship with a Worker called "workerAccount" and it also has a "to-many" relationship to "OrgRegion" called "orgRegions".
The term "instance" here is referring to a specific organisation. For example, "The Corn Flour Company" and "Aqua Breweries" might be instances of the Organisation entity.

### Value For Key

An instance of an Organisation can supply values for the keys "address", "countryIso", "email" etc... and they will return a value for the key. It is essentially acting like an NSDictionary or a Map object. This is how data is extracted from an object.

### Take Value For Key

This is where an instance of an entity is asked to "take up" some value for a key. For example, an instance of an organisation might be told to take the value "foo@foo.co.nz" for the key "email". This is how data is loaded into an object using KVC.

### Value For Key Path

Using a dotted path, it is possible to traverse relationships to access data in other entities. For example, if you have an instance of "OrgExpertise", it is possible to get the value for the key path "organisation.workerAccount.name". This is how you can extract data from the interconnected network of object instances.

### Take Value For Key Path

Using a dotted path, it is possible to get an object in the interconnected network of object instances to "take up" some piece of data. For example, if you have an instance of "OrgExpertise" then it is possible to get the object to "take up" a value of "Joe Smith" for the key path "organisation.workerAccount.name".
# WebObjects/Overview/Naming Conventions

The contents of this wikibook are out of date and have now moved to http://wiki.objectstyle.org/confluence/display/WO/Home.
The naming convention for objects in WebObjects is that names are written in what is now called "camel case".
The various prefixes are not hard to explain. The "NS" stands for "NextStep", the "EO" for "EnterpriseObject", the "WO" for WebObjects.
# WebObjects/Overview/Objective-C to Java Transition

The contents of this wikibook are out of date and have now moved to http://wiki.objectstyle.org/confluence/display/WO/Home.

### Windows

WebObjects 5 projects will require converting with the JavaConverter, whether or not they are already written entirely in Java. This is best run from a Bourne Shell, and is at $NEXT_ROOT/Library/WebObjects/JavaApplications/JavaConverter.woa/JavaConverter.cmd. Run it with the full path of your chosen project and it will create a new project, whose name will be the original name with "Java" appended.
You should then be able to open the new project and browse the source code. The Java Converter has non-trivial tasks to perform, more so if you've come from Objective-C, so you'll want to read through your source code and check it's done a job you're happy with. As an alternative, you could search merely for its comments (labelled JC_WARNING or JC_ERROR) and review each one.
Note that the Makefile will be removed by the conversion process, and for some reason best not asked about, Project Builder will recreate the Makefile only if files are added or removed from the project - and not in the rather more obvious case where you try to build and there is no Makefile. So you'll need to add and remove a dummy class, for example, before your project will build.
EOModels will need converting to the JDBC adaptor. Since JDBC is itself a multiple-database protocol, the JDBC adaptor itself does not have the usual knowledge of external types - but if you give it an appropriate database URL and it can locate the appropriate plugin, it will then know which types are possible, so you can use the external type pulldown list to get them right. The JDBC adaptor and EOF 5 is, of course, a whole new learning curve of little fiddly bits, so expect to have to spend a bit of time experimenting and reading up in order to make all your database types work correctly, especially if it is complex. As the community (and the database vendors) discover more about the environment, this stage is becoming easier and easier.
Once your application is built you can run it, of course. Be aware WebObjects 5 uses some bizarre scripts to launch applications, and these are worse than usual on Windows, where the command line has a maximum length, so your classpath may not fit. My personal opinion (MalcolmCleaton) is that this is an extremely ill-conceived method for launching Java applications, and you'd be best off doing away with it as soon as possible, but that's another discussion.
# WebObjects/Project WONDER

If you've ever been working on a WebObjects project and thought to yourself "I wonder if anyone has written this?" or "Gee, this seems like it could be easier," then Project WONDER is the thing for you. Project WONDER is a massive open source Java project designed to ease the development of WebObjects applications. The project contains many subsystems -- reusable components, frameworks, database plugins, TONS of utilities, and a set of sample apps that show off some of Wonder's features.
The power, size, and scope of Project WONDER are both a blessing and a curse. To the initiated, the answer to most WO questions is "Project WONDER." However, many people seem to be turned off by the apparent complexity of using WONDER. With the deployment of the nightly build server, though, these fears are mostly unfounded. Installing and using Project WONDER requires adding a handful of Frameworks to your project and changing your Application, Session, and DirectAction superclasses to be ERXApplication, ERXSession, and ERXDirectAction, and you're done. WONDER will do the rest for you, bringing in patched, enhanced, and just-plain-better versions of various core WO components, and providing a huge number of prebuilt components and technologies to pull from to build your WO applications. It is WELL worth the time to start using it if you do anything beyond the simplest of applications.
For a slightly dated, yet still good, walkthrough you can check out Jonathan Rentzsch's 2002 CAWUG presentation.
The project itself is hosted as SourceForge under the project name Wonder, and has a nightly build server at http://webobjects.mdimension.com/wonder.
The latest javadoc is available at http://webobjects.mdimension.com/wonder/api .
A downloadable version of the latest javadoc is available at http://webobjects.mdimension.com/wonder/Wonder-latest-Documentation.tar.gz
Any questions can be directed to the Project WONDER mailing list.
Wonder Community Tutorials available at: ObjectStyle Confluence Wiki WOnder Tutorials
# WebObjects/Noxymo Core/Overview

NoxymoCore is no longer available
# WebObjects/Overview/Licensing

The contents of this wikibook are out of date and have now moved to http://wiki.objectstyle.org/confluence/display/WO/Home.

## License

As of WebObjects 5.3, the deployment of WebObjects built server applications is now permitted on any platform. The XCode license (within which WebObjects is included) reads:
   D. WebObjects Software. Subject to the terms and conditions of this License, you may use, install and permit others to access the WebObjects deployment software included with the Developer Software to deploy application programs developed using Apple’s WebObjects Software. You may also reproduce and distribute: (1) over a network, components of the WebObjects deployment software for installation and use by others (“Java Client End Users”) on any remote computer’s volatile memory (e.g. RAM) to enable Java Client functionality for the sole purpose of communicating with Apple’s WebObjects Software that may be installed and executed on the same Apple-labeled computer on which you have installed the Developer Software (the "Licensed System"); and (2) both manually and automatically over a network, components of the WebObjects deployment software for installation and use by Java Client End Users on any remote computer’s non-volatile memory (e.g. ROM) to enable Java Client functionality for the sole purpose of communicating with Apple’s WebObjects Software that may be installed and executed on the Licensed System; provided that all distributions to Java Client End Users are made under terms that are at least as restrictive as those set forth in this License and contain the disclaimers and limitations set forth in Sections 6 and 7 of this License. Subject to the terms and conditions of this License, you may also deploy server applications built with the WebObjects Software on any platform.
Sections 6 and 7 are standard Apple license disclaimers of warranty and limitations of liability clauses. Deployment to other platforms requires WebObjects software be built as Java servlet for deployment on a servlet compatible server such as Apache Tomcat.
# WebObjects/Project WONDER/Frameworks/Ajax
### Overview

When the subject of Ruby on Rails vs WebObjects comes up, invariably the first topic discussed is Ajax support, or rather the lack-thereof in WebObjects core.
The Ajax framework in Project Wonder provides many of the features that Rails users have come to expect, but written in a style that fits well with "The WebObjects Way" of doing things. An attempt is made to avoid writing javascript whenever feasible, as well as providing as much support for component actions as possible.
The majority of Ajax framework is written without dependencies on ERExtensions (the core framework in Project Wonder). This means that for most Ajax capabilities, you can use the framework without making your Application extend any Project Wonder classes. A handful of advanced capabilities, however, could only be written with supporting classes that are only available in the ERExtensions framework or with your application extending Project Wonder classes (like ERXSession). These cases are documented below.

### Adding Ajax Support

For any features that don't require ERExtensions, you can add the Ajax framework to your application by simply downloading the latest Project Wonder from the nightly build server and just installing the Ajax.framework and ERJars.framework in your /Library/Frameworks folder.
If you are intending to use any of the advanced features that require ERExtensions, then you should follow the Project Wonder Quickstart guide. The quickstart guide is only a few quick steps and you will be able to take full advantage of Wonder.

### Available Components

This list of components should not be considered authoritative. Project Wonder changes often, particularly in Ajax.framework, with new features and components being added all the time. Right now, the only place to see the complete list is in the framework itself.
* AjaxAccordian
* AjaxAccordianTab
* AjaxAutoComplete
* AjaxDraggable
* AjaxDroppable
* AjaxHighlight
* AjaxInPlaceEditor
* AjaxRoundEffect
* AjaxSlider
* AjaxSortableList
* AjaxUpdateContainer
* AjaxUpdateLink
# Zulu/Exercise/Lesson 4

Welcome to the exercises related to Lesson 4.
Click "▼" to check your answers.

## How long have you been working for?

How would you respond to: (Assume for these questions that your name is Lebohang Ndlovu and that you're a student in Pretoria in your 3rd year. But you come from Johannesburg. You are 22 years old. Your mother is a cook. Your brother is teacher. You have two friends called Sipho and Mfanafuthi. Sipho stays in Cape Town.)

## Do you know...

Translate the following Zulu sentences into English:
Translate the following English sentences into Zulu:
Odd one out:

## Dialogue

Try translating the following dialogue:

## Next step

* If you would like, review this lesson: Lesson 4
* Otherwise, continue to the next lesson: Lesson 5
# Zulu/Exercise/Lesson 3

Welcome to the exercises related to Lesson 3.
Click "▼" to check your answers.

## How long have you been working for?

How would you respond to: (Assume for these questions that your name is Zipho Mtembu and that you're a student in Cape Town in your 3rd year. But you come from Johannesburg. You are 23 years old. Your brother works at Crispy Chicken as a cook. Your mother is a nurse. Your sister is teacher.)

## Age and Where do you...

Translate the following Zulu sentences into English:
Translate the following English sentences into Zulu:
Odd one out:

## Dialogue

Try translating the following dialogue:

## Next step

* If you would like, review this lesson: Lesson 3
* Otherwise, continue to the next lesson: Lesson 4
# Zulu/Exercise/Lesson 2

Welcome to the exercises related to Lesson 2.
Click "▼" to check your answers.

## Where do you live?

How would you respond to: (Assume for these questions that your name is Sipho Tshabala and that you're a doctor who works at Johannesburg Hospital, in Johannesburg. But you come from Durban.)
Fill in the missing letters.
Spot the error.

## Professions and Places

Translate the following Zulu sentences into English:
Translate the following English sentences into Zulu:
Odd one out:
Fill in the blanks
Spot the error. Fill in the blanks

## Dialogue

Try translating the following dialogue:

## Next steps

* If you would like, review this lesson: Lesson 2
* Otherwise, continue to the next lesson: Lesson 3 I