PiTcl commands: conversion

A list containing the indices of the category names which were renamed by the user. Indices out of the range 0 ... 15 are reported as errors.

A list containing the names given to the 16 possible categories. An empty string indicates a category without name, these are unused. The palm pilot restricts the length of the category names to 15 characters (+ a terminating \0 character). Longer names are automatically truncated during conversion, shorter strings are padded with \0's.

A string, nothing more is known. Well, it is restricted to at most 16 characters, as the name's above.

The numerical id given to the last inserted record (?).

{
    renamed {0 1 2 3}
    name {
	{Nicht abgelegt} Firma
	Privat Einkaufen
	{} {} {} {}
	{} {} {} {}
	{} {} {} {}
    }
    id {}
    lastUniqueId 18
}
        

The text stored in this memo. Its length is restricted to 64 Kbyte of data.

{
    text {Hello world}
}
	

Information about the available categories to memos. A list of key/value-pairs. This information is the same for all standard databases and was already described.

Sortorder, either 0 or 1.

{
    category {
	renamed {3 4 5}
	name {
	    {Nicht abgelegt} Firma Privat
	    Palm Reise Tcl/Tk {} {}
	    {} {} {} {}
	    {} {} {} {}
	}
	id {}
	lastUniqueId 22
    }
    sortByAlpha 1
}
	

Numerical priority of the todo item.

Boolean flag, either 0 or 1. The latter indicates that the item has no due-date.

Boolean flag, either 0 or 1. The latter indicates that the item was done.

Textual description of the things to do.

Additional textual information about the things to do.

Date at which the described things have to be done. The information is in the same format as returned by the tcl-command [clock seconds]. Irrelevant for indefinite = 1.

{
    priority    1
    indefinite  0
    complete    0
    description {Convert $$ to DM}
    note        {}
    due         906415200
}
	

Sortorder, one of

• date,priority
• priority,date
• category,priority
• category,date

A boolean flag, either 0 or 1. The latter indicates that the application information was changed.

{
    category {
	renamed {0 1 2 3}
	name {
	    {Nicht abgelegt} Firma
	    Privat Einkaufen
	    {} {} {} {}
	    {} {} {} {}
	    {} {} {} {}
	}
	id {}
	lastUniqueId 18
    }
    sortMode priority,date
    dirty    1
}
	

Boolean flag. Determines whether phone information is shown for the entry or not.

A key/value-list associating the phone items with their respective titles. Keys are the letters A to E, values are keys into the application information (restricted to phone1 .. phone8).

Last name of the person.

First name of the person.

Name of the company to associate with the person.

First of five possible phone numbers.

Second of five possible phone numbers.

Third of five possible phone numbers.

Fourth of five possible phone numbers.

Fifth of five possible phone numbers.

Name of street, number of house.

Name of the city the street is part of.

Name of the state the city is part of.

Zipcode of the given address.

Name of the country the state is part of.

Title of the person

Textual custom information, part 1.

see above, part 2.

see above, part 3.

see above, part 4.

Additional notes for the entry.

{
    showPhone   0
    phoneLabels {
	A phone1
	B phone2
	C phone3
	D phone4
	E phone5
    }
    lastName    {}
    firstName   {}
    company     {Ascom (Aachen)}
    phoneA      {0241  96806  0}
    phoneB      {}
    phoneC      {0241 }
    phoneD      {}
    phoneE      {}
    address     {Charlottenburger Allee 61}
    city        Aachen
    state       NRW
    zipcode     52064
    country     DE
    title       {}
    note        {}
    custom1 {} custom2 {}
    custom3 {} custom4 {}
}
	

A numerical country code. Nothing more is known.

A boolean flag indicating how the database is sorted.

A list of key/value-pairs. The values are the labels to put to the left of the various entry fields. They are restricted to a length of 16 characters, like the category names. The keys are the same as the keys for a record, with the following exceptions:

• showPhone and phoneLabels are missing.
• phoneA .. E are replaced by phone1 .. 8.

Remark: As was said before, the phoneLabels item in a record associates every phone item in it with one of the eight possible labels, using the appropriate phoneX key, X in {1..8}.

{
    category {
	renamed {0 1 2 3 4 5 6 7}
	name {
	    {Nicht abgelegt} Firma
	    Privat QuickList
	    Freunde Palm
	    Bekannte T-Mobil
	    {} {} {} {} {} {} {} {}
	}
	id {}
	lastUniqueId 24
    }
    country 2048
    sortByCompany 0
    labels {
	lastName  {0 Nachname}
	firstName {0 Vorname}
	company   {0 Firma}
	phone1    {0 B�ro}
	phone2    {0 Privat}
	phone3    {0 Fax}
	phone4    {0 Andere}
	phone5    {0 E-Mail}
	phone6    {0 Firma}
	phone7    {0 Funkruf}
	phone8    {0 Handy}
	address   {0 Adresse}
	city      {0 Ort}
	state     {0 Bundesland}
	zipcode   {0 PLZ}
	country   {0 Land}
	title     {0 Titel}
	custom1   {1 {Geburtstag }}
	custom2   {1 {WWW }}
	custom3   {0 {Definiert 3 }}
	custom4   {0 {Definiert 4 }}
	note      {0 Notiz}
    }
}
        

Day and starting time of the appointment.

Day and end time of the appointment.

The day is the same as in begin, the standard datebook application delivered with a pilot is unable to handle appointments crossing date boundaries.

Textual description of the appointment.

Additional note.

A boolean flag. If set, the appointment is an all-day event, and the time information in begin and end is irrelevant.

A boolean flag. If set, an alarm is scheduled for the event, and the information in advance is valid.

Describes how much in advance the alarm for this event is triggered. It is a key/value-list with the keys value and unit. Possible values for unit are:

• min
• hour
• day

A list of key/value-pairs describing the repeat behaviour of the appointment. This is described in a separate table, see below.

{
    begin       910525500
    end         910528200
    description Mittagessen
    note        {}
    event       0
    alarm       1
    advance {
	value 5
	unit  min
    }
    repeat {
	type       weekly
	freq       1
	weekstart  monday
	forever    1
	end       -1
	day        0
	exceptions {}
	days       0111110
    }
}
	

The general type of repeat, one of:

• none
• daily
• weekly
• monthlyByDay
• monthlyByDate
• yearly

Frequency of the repetition.

Either sunday or monday.

A boolean flag. If set, the value in end is irrelevant.

The date at which the system shall stop repeating the appointment. Not valid for forever = 1.

The day of the month to repeat, valid only for type = monthlyByDay.

A list of days which are exempt to the repeating.

Valid for type = weekly. Defines the days of the week the appointment shall repeat on, as a 7-characters string containing 0 (don't repeat) and 1 (repeat). The value of weekstart must be factored into the interpretation of this string.

{
    type       weekly
    freq       1
    weekstart  monday
    forever    1
    end       -1
    day        0
    exceptions {}
    days       0111110
}
	

Either sunday or monday.

{
    category {
	renamed {}
	name {
	    {} {} {} {} {} {} {} {}
	    {} {} {} {} {} {} {} {}
	}
	id {}
	lastUniqueId 0
    }
    startOfWeek sunday
}