Help:Sandbox
If you are here, you are probably trying to test something ... so before you jump into the trial-and-error (or after ;) you may also try to see some of the documentation found at WikiMedia:
- Help for Editors — covering things like lists, tables, images, html usage, etc.
- And more general: Help - Editing and Help - Contents
Please note that not all functionality detailed in the media wiki is available in this wiki...
Test Lists
*list item followed by plain text line
- list item followed
by plain text line
plain text line *followed by list item
plain text line
- followed by list item
Bold text Italic text
heading 2
test test test
Test Nested Lists
*Bullet *Bullet *#Bullet Numbered *#Bullet Numbered **Bullet Bullet **Bullet Bullet ##Numbered Numbered ##Numbered Numbered #Numbered #Numbered
- Bullet
- Bullet
- Bullet Numbered
- Bullet Numbered
- Bullet Bullet
- Bullet Bullet
- Numbered Numbered
- Numbered Numbered
- Numbered
- Numbered
Collapsing Table Rows
| Always displayed header |
|---|
| Optionally displayed text; optionally displayed text |
| Always displayed header |
|---|
| this table has style="width:90%"; optionally displayed text |
| name | number |
|---|---|
| a | 123 |
| b | 6 |
| c | 45 |
| name | number |
|---|---|
| a | 123 |
| b | 6 |
| c | 45 |
| Camera manufacturer | Panasonic |
|---|---|
| Camera model | DMC-TZ3 |
| Orientation | 0 |
| Horizontal resolution | 72 dpi |
| Vertical resolution | 72 dpi |
| Software used | Picasa 3.0 |
| File change date and time | 01:33, 18 January 2008 |
| Y and C positioning | 2 |
| Exposure time | 1/30 sec (0.0333333333333) |
| F Number | f/4.7 |
| Exposure Program | Normal program |
| ISO speed rating | 160 |
| Exif version | 2.21 |
| Date and time of data generation | 01:33, 18 January 2008 |
| Date and time of digitizing | 01:33, 18 January 2008 |
| Image compression mode | 4 |
| Exposure bias | 0.33 |
| Maximum land aperture | 3.44 |
| Metering mode | Pattern |
| Light source | Unknown |
| Flash | 16 |
| Lens focal length | 16.9 mm |
| Color space | 65535 |
| Sensing method | One-chip color area sensor |
| Custom image processing | Normal process |
| Exposure mode | Auto exposure |
| White Balance | Auto white balance |
| Digital zoom ratio | 0 |
| Focal length in 35 mm film | 103 |
| Scene capture type | Standard |
| Contrast | Normal |
| Saturation | Normal |
| Sharpness | Normal |
| Unique image ID | 2f33ad89c119e4a51c07d32fa73483ef |
hello!
i started this new page so i could experiment a bit, i hope it's ok.
|
This is a little test of some stuff that might make a smaller box around some text. |
i see we have some nice editing buttons, including one for bold and another for italic. it would be better if those worked as we expected, and modified the selected text in the edit-field itself, rather than requiring the writer to jump through some hoops, but i guess as reminders they're better than nothing.
in general, i think "wiki markup" is the type of system that would give the _easy_editing_capability_ described on this "wiki as e-books" page as your fundamental goal.
but i believe that "wiki markup" is still too complicated...
i'll write more on this later, but for now, let's make sure this page works correctly, and doesn't screw things up...
-bowerbird
William Overington
28 March 2006
I am trying to restructure the Other Ideas page.
At its edit a few days ago three lines, one blank, were added at the start and a lot of text was clipped from the end, clipping starting from within a word.
I suspect that this was because the page went over 32 kilobytes.
I am now going to try to split the Other Ideas page into two pages, namely Other Ideas and a new Rollout and Community Building page, while retaining the three line addition of a few days ago.
I am not entirely sure how to do it at present, so please help out if it goes wrong!
To begin, the three lines added the other day are preserved here in the sandbox for later use.
FROM HERE
VoIP
Skype or somesuch? TO HERE
2004-04-26 0920Z
The changes have now been made. In the event I did not need to recover the new message from the storage space above.
Along the way I generated the page Rollout and Community Building and later realized that it should have been Rollout and Community Building Ideas, so the Rollout and Community Building page is surplus and may get deleted, unless it becomes used as an official policy page.
So, the desired result has been obtained, though with a hiccup along the way!
Trying to work out if the main page could be structured so that the two items are side by side.
The main page has the following.
OLPC Wiki
Enter the wiki here: One Laptop per Child.
View the Table of Contents.
Seymour's Corner: Seymour Papert's weekly column on Learning Learning
Suppose that it were restructured as follows.
OLPC Wiki
|
|
|
|
Enter the wiki here: One Laptop per Child, |
or visit Seymour's Corner (Seymour Papert's weekly column on Learning Learning) |
|
View the Table of Contents. |
Thank you for fixing my attempt at the markup and showing how to do it.
Thank you also for answering the question in the About page.
Original
Original colours, space added at start
White on Blue
White on Orange
White on Green
Blue on Green
color bars
Note : you can change the color of a link by adding color specification inside the linktext
2006-06-15
The latest version of the green that was actually used in the OLPC template.
Made a little nearer towards a white background.
Made a little nearer towards a white background.
Made a little nearer towards a white background.
Made a little nearer towards a white background.
The later colours are not traditional web-safe colours: does that matter?
Testing of the latest colour above with the text.
Color bars again
- This is actually more in tune with the colors on the wiki.
- BTW, I was originally trying for a pale green in order to highlight the statement without being too garish. I wanted to use a background color to waste less vertical space on the page, especially important on the main page. Also, I wanted people to take note of this statement, try out the "Talk" link, and learn that there is a discussion page for every wiki page.
Experimenting with colors to work with the new logo
A. raw logo colors
Using the colors from the logo:
B. lighter logo colors
Using lighter versions of the same:
C. lighter background / darker font color
And darker versions for font colors:
D. lighter background / even darker font
And even darker versions for font colors:
E. lighter background / raw font colors
Same light background, but using the 'raw' logo color fonts...
possible link colors
And as possible link colors:
This is a possible link color. [f #800155]
This is a possible link color. [f #2a8c00]
This is a possible link color. [f #944f00]
This is a possible link color. [f #004f78]
xavi review
- A - is nice and strong, although has to be used sparcely... I (mistakenly) tried using the green in News/lang-es#MILESTONES and a lighter tone would be better.
- B - the black lettering makes the colors to feel washed out
- C - keeping font & background in the same tone is nice (see D)...
- D - ... in even darker fonts I like it better
- E - just had to try :)
The link colors feel fine, but should be careful which ones are set and how they mingle with the wiki (ie: a missing link is red—attention caller & fine with me—so the 'child' color would probably have to be discarded (unless the base wiki colors are changed).
I would probably try to keep blue as the default, not traversed link—although it denotes a high conservatism with the dawn of the web - green could be a better 'non-traditional' alternative and goes well with the laptop's color. For a traversed link, either green or brownish (green reminds me of a 'good' link, while brownish is more discrete and blends better with black letters).
BTW, do you think the colors could be set to some wiki-variables? like have something {{COLOROLPC}}, {{COLORCOMMUNITY}}, and such? So that we can embed it in the templates and then 'forget' about them? (My alternative would be to create a subpage... ok, ok... I'll try not to! :P )--Xavi 22:46, 9 April 2007 (EDT)
OLPC News
The first working prototype of the $100 Laptop was unveiled at the Country Task Force Meeting, 23 May 2006. (See Flickr for more images.) This was first time we had combined the industrial design with the hardware (A-TEST board). Both the ID and the hardware had been shown separately in the past; pictured is the working laptop, completely self-contained, running Fedora Core 5.0.
One thing that might be somewhat misleading is the display; we plan to ship a display that is bigger and of a higher resolution than the one pictured. We plan to ship a 7.5-inch diagonal display with 1200×900 pixels vs. the 7.0-inch diagonal display with 800×480 pixels seen in the prototype.
About One Laptop per Child
This is the wiki for the One Laptop per Child association. The mission of this non-profit association is to develop a low-cost laptop—the "$100 Laptop"—a technology that could revolutionize how we educate the world's children. Our goal is to provide children around the world with new opportunities to explore, experiment, and express themselves.
Why do children in developing nations need laptops? Laptops are both a window and a tool: a window into the world and a tool with which to think. They are a wonderful way for all children to learn learning through independent interaction and exploration.
It's an education project, not a laptop project -- Nicholas Negroponte
The Special:Allpages page lists 265 pages that are in this wiki. That does not include the Talk pages nor the User pages. 2006-06-15 1818Z
Facility for producing pages for learning how to use the translations template system. That is, to have some pages to be the targets of the links.
The numbers are from the international telephone codes. The numbers specify countries not languages yet are used so that the names of the pages do not explicitly have the abbreviations for the languages in them.
http://en.wikipedia.org/wiki/International_telephone_codes
Sandbox for translations template tests 34
Sandbox for translations template tests 351
Sandbox for translations template tests 44
Please note that the Template:Sandbox page already exists.
Do we need a page to be the original page which links to the translated versions?
Sandbox for translations template tests 0
Is this the way to do a thumbnail size picture?
Anchor Testing
(div id="Current technique")(/div)
Although translations could be structured and done in many ways, I (Xavi) am currently using sub-pages. This structure has the advantage that no matter what page has been translated, it'll be found in the originalPageName/lang-xx (usually spanish).
(div id="The problem")The Problem(/div)
The problem arises when a link leads into a sub-section of the original page. Although it's quite simple to just reword the link into the translated version after the target section has been translated, future translations or references could pose some problems such as:
- what was the translation used for Rollovers?
- what was the capitalization sequence?
- was it typed with or without accents?
Given that those issues (except for the accent one) had to be thought out in the original verstion, it would be handy and less error-prone if the original anchors could be preserved despite of whatever translation mangling was performed.
(div id="Idea"/)
Thus, a link referring to say Bitfrost#Goals would just be translated as Bitfrost/lang-es#Goals... no need to check if Goals was translated as Objetivos, Metas, singular, plural, kept in english or whatever...
(div sytle=display:none id="The solution")(/div)
Given that <A> markup is not allowed in the wiki, the solution could be according to Wimikedia's Help on Anchors to use div markups... unfortunately, they don't seem to be working... that's why I'm in the Sandbox!
Lets see how it goes...
Sample links
Sample local page links
- Fully qualified wiki links
- Sandbox, Sandbox#Current technique, Sandbox#The Problem, Sandbox#Idea, and Sandbox#The solution
- Local reference links
- #Current technique, #The Problem, #Idea, and #The solution
Inlined anchors
Don't work and they mess up the whole layout of the page!
==== <div id="pre-inlined"/> Inlined pre-anchors ==== testing to see if we can inline the original and the translated section header (btw, the inlined anchor id text is <tt>#pre-inlined</tt>;so the link would be [[#pre-inlined]] or [[#Inlined pre-anchors]])
php5 sandbox
Sample external links
- Original section anchor links
- Bitfrost#Introduction and summary, Bitfrost#The Bitfrost approach, Bitfrost#Principles, Bitfrost#Goals
- Translated div anchor links
- Bitfrost/lang-es#Introduction and summary, Bitfrost/lang-es#The Bitfrost approach, Bitfrost/lang-es#Principles, Bitfrost/lang-es#Goals
Activities for Download
General Search and Discovery
|
Journal: Object and activity browser and history integration in process, always on |
Download: Journal-58.xo (v.?) Source: Build: All |
Mime types: Internationalization: l10n resources Tags: none Development Status: ? |
math test
Truth: <math>e = \sum_{n=0}^\infty \frac{1}{n!}</math>
imagemap test
<imagemap> Image:Foo.jpg|200px|picture of a foo poly 131 45 213 41 210 110 127 109 Display poly 104 126 105 171 269 162 267 124 Keyboard rect 15 95 94 176 Foo type A
- A comment, this line is ignored
circle 57 57 20 Foo type B desc bottom-left </imagemap>
<googlemap lat="41.079351" lon="-71.015625" zoom="5" width="600" height="600" controls="large"> 41.244772, -76.728516, Test 44.496505, -76.201172 </googlemap>
Testing a definition table template
Dr. Seuss
| One |
| |
| Two | Fish | |
| Red | Fish | |
| Blue | Fish |