raw sand-wiki
This wiki is for testing wiki in the oddwiki-hive. Try wiki out and play with it so you understand how it works. A sand-wiki is a SandBox - that’s the classical page for testing on wikis - extending to the horizon. The raw sand-wiki remains “raw”, that means it has no css installed.
Also see the formatting rules, please.
{{ hafdasfasdf }}
новая вики система.
Пробуем ее в работе!
There are more sand-wikis to try out. Find the most appropriate one for your testing and have fun.
Our wiki-node connects to our neighborhood. First “hellos”, weird ideas, news and such stuff are best put in the forum.
Journal
I’m planning on using a wiki as a chat room where students post questions and I (the teacher) drop in every so often to answer them. Alternatively, if another student visits before me, that student is welcome to answer the question. If that happens, I will indicate whether the reply is correct, and if not, I’ll fix it up. What do you think?
This is a new page. It is the famous blank faced by writers. Or it was.
getestet
dieses Jahr
January 2007 Su Mo Tu We Th Fr Sa 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31
February 2007 Su Mo Tu We Th Fr Sa 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28
March 2007 Su Mo Tu We Th Fr Sa 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31
April 2007 Su Mo Tu We Th Fr Sa 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30
May 2007 Su Mo Tu We Th Fr Sa 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31
June 2007 Su Mo Tu We Th Fr Sa 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30
July 2007 Su Mo Tu We Th Fr Sa 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31
August 2007 Su Mo Tu We Th Fr Sa 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31
September 2007 Su Mo Tu We Th Fr Sa 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30
October 2007 Su Mo Tu We Th Fr Sa 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31
November 2007 Su Mo Tu We Th Fr Sa 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30
December 2007 Su Mo Tu We Th Fr Sa 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31
zum Ausprobieren
Monat mit Terminen
May 2012 Su Mo Tu We Th Fr Sa 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31
Math test
$$ \int_0^2 x^2 $$
\[ \int_0^2 x^2 \]
<m> \int_0^2 x^2 <m>
la la la la la
non so se è chiaro ma ci si prova
<ohh… swiss vandals – from ticino?>
MY 2 CENTS: I wonder how this will show up…..
abc 123
********************** PRINCE EDWARD ISLAND CANADA **********************
PEI??
[[x_2?]]
Esto es un ensayo
[sOme:thing something]
Moo!
| col1 | col2 | col3 |
| a | b | c |
한글 테스트
The Korean displays correctly. How about Native American characters? qwi·qwi·diččaq Yes!
日本語が通るかテスト
<math>\alpha</math>
[image:bloomycat.jpg]?
– by bloomycat
I have yet to find out the markup for this wiki
– what is this
Below we use internal transclusion to include a page.
This page is transcluded internally to demonstrate how transclusion works.
When DateBk?3 was first written, it did not handle ToDo’s?, but instead offered its own flavor of tasks: Floating Events. Even after ToDo’s? were incorporated into DateBk?3, many users preferred floating events and even with DateBk?6 that now offers alarms, icons, simple repeats etc. on ToDo’s?, floating events still remain very popular. In fact their popularity was one of the reasons why Handspring insisted on retaining floating events when Pimlico Software licensed a light version of DateBk?3 to Handspring for their Datebook+ application.
A floating event is a bit like an Undated Todo in that it has no due date. However, it can be scheduled on an future date, but once today catches up to it, the event then “floats” forwards day by day until checked off. Floating events display a circle instead of a box so they can be readily distinguished from ToDo’s?. Floating events will appear as regular, untimed events in the Desktop calendar application’s datebook database as opposed to ToDo’s? which are often stored in a separate task list. Floating events also show up in the yearly view while ToDo’s? do not.
Like a regular event, a floating event can also have a time and an alarm, so floating events can appear at certain hours of the day and have durations—in fact they can have almost all the attributes of a regular event (advances are an exception as you cannot put advances on floating events).
You may choose to ignore floating events, or you may choose to use them instead of ToDo’s?. A few people use both and take advantage of their differences in how they use them. A menu option makes it easy to convert a float to a ToDo? and vice-versa.
| Function | Floating Events | ToDo’s? |
| Database | Stored in the appointment database | Stored in the ToDo? Database |
| Priority | None—although you can start each event with a digit and a hyphen | Priority from 1 (high) to 5 (low) |
| Date | Can be dated in future, but then floats with today’s date. No concept of past due | Can be dated or undated. If dated, becomes past due when today passes. |
| Repeats | Shows all future occurrences of the repeat | Shows only the current/next occurrence of the repeat. |
| Beaming | Can be beamed directly from DateBk?6 | DateBk?6 switches you to the ToDo? application to beam |
| On Desktop | Appears as untimed event in calendar | Appears in desktop task list database |
| Attributes | Can have time and duration and appear at that time in calendar | Can have time but only to set alarm and still appears in untimed timeslot |
| Time zone | Time is adjusted by time zone logic | Time is independent of time zone logic |
When you put a repeat on a floating event, DateBk?6 handles it in a special manner that provides some very useful functionality. A typical repeat event is suitable for something that has to be done on a fixed day at regular intervals (say a Doctor appoint- ment on the first Tuesday of each month). But suppose you have something that needs to be done at regular intervals, but not necessarily on a specific day. For example, you may have to give your dog a worm pill once a month. It’s not critical that it be given on a specific day and in fact if you don’t get around to doing it on that scheduled day, you really want a reminder that will remind you each day until it gets done.
This is exactly what repeat floating events are designed for. You set up a repeat floating event and when that day comes around, DateBk?6 moves the repeat floating event to the next occurrence and leaves behind a non-repeat occurrence that by itself will then float forwards until you check it off.
This also has the advantage that you maintain a record in your calendar of exactly what day you completed the task.
If a repeat event has no further occurrences, it will be deleted (so only set an end date if you expect to have the event eventually disappear).
If you tap directly on the circle in the daily view on a repeat floating event to change its status, DateBk?6 creates a non-repeat copy of the repeat event, toggles its status to mark it complete, links it to the repeat event and then advances the start date of the repeat event to the next occurrence. If you want to toggle the status of ALL occurrences of a repeat floating event (clearly not something you would normally do), you must call up the repeat event by tapping on the Details button so you can change the status in the Details dialog and then specify that the change is to be made to all occurrences of the repeat event.
Note that you would not normally want to make a repeat floating event a daily repeat as the separate occurrences created by DateBk?6 will start to pile up quickly unless they are diligently checked off each day. Also, if you start a repeat floating event for the current day, no non-repeat occurrence will be created (they are created only at the start of each day or at the floating advance time). You can use the Make Exception command (Record Menu) to quickly make a non-repeat occurrence if you need one, or you can go to the details dialog to mark it done, and then select CURRENT in the exception dialog to just mark today’s occurrence as completed.
On occasion, you might want a type of repeat task that repeats at an interval from when it was last checked off as opposed to a fixed schedule (example: you cut your hair every 45 days or so—if you wait 60 days one time, you want to count 45 days from when you last had it cut). For that you use a daily repeat and check the Reschedule from Checkoff checkbox.
