Palm::Datebook(3pm)

🌸 NAME 🌸

okay so bestie, welcome to Palm::Datebook — it's the handler for Palm OS DateBook and Calendar databases 💖 and yes, that's the whole vibe. palm pilot era representation, no cap.

---

✨ VERSION ✨

This doc is describing version 1.400 of Palm::Datebook, released March 14, 2015, and it shipped as part of Palm version 1.400. 🎀

---

🦋 SYNOPSIS 🦋

use Palm::Datebook;

that's it. that's the whole synopsis. iconic honestly.

---

💅 DESCRIPTION 💅

So the Datebook PDB handler is a helper class for the Palm::PDB package, and what it does is parse DateBook and Calendar databases. main character behavior fr fr.

🎀 AppInfo block 🎀

The AppInfo block starts off with the standard category support — see Palm::StdAppInfo for the details, bestie, it's all there. ✨

🍓 Sort block 🍓

$pdb->{sort}

This is a scalar — literally just the raw data of the sort block. no thoughts, head empty, raw bytes.

🧚 Records 🧚

$record = $pdb->{records}[N]

$record->{day}
$record->{month}
$record->{year}

These are the day, month and year of the event. The day and month start at 1 (so for January, $record->{month} is set to 1). The year is a four-digit number (for dates in 2001, $record->{year} is 2001).

For repeating events, these fields specify the first date at which the event occurs. first impression date, yk?

$record->{start_hour}
$record->{start_minute}
$record->{end_hour}
$record->{end_minute}

The start and end times of the event. For untimed events, all of these are 0xff. all four. every single one. 💀

$record->{when_changed}

This is defined and true iff the "when info" for the record has changed. And honestly? I don't know what this means. 😭 the docs said it, so I'm saying it.

$record->{alarm}{advance}
$record->{alarm}{unit}

If the record has an alarm associated with it, then the %{$record->{alarm}} hash exists. The unit subfield is an integer: 0 for minutes, 1 for hours, 2 for days. The advance subfield says how many units before the event the alarm should ring — e.g., if unit is 1 and advance is 5, then the alarm will sound 5 hours before the event.

If advance is -1, then there is no alarm associated with this event. New records created via new_Record have a 10 minute alarm set by default. So undef $record->{alarm} to remove this alarm before writing. 🫶 And heads up: an alarm icon will still show up in the Datebook if the alarm field exists, even with advance set to -1. it's giving haunted alarm.

%{ $record->{repeat} }

This exists iff this is a repeating event. that's the whole bit.

$record->{repeat}{type}

An integer which specifies the type of repeat:

• 0 — no repeat. rest era.
• 1 — a daily event, one that occurs every day.
• 2 — a weekly event, one that occurs every week on the same day(s). An event may occur on several days every week, e.g., every Monday, Wednesday and Friday.

For weekly events, the following fields are defined:

• @{ $record->{repeat}{repeat_days} } — This is an array of 7 elements; each element is true iff the event occurs on the corresponding day. Element 0 is Sunday, element 1 is Monday, and so forth.
• $record->{repeat}{start_of_week} — Day the week starts on (0 for Sunday, 1 for Monday). This affects the phase of events that repeat every 2nd (or more) Sunday.

• 3 — a "monthly by day" event, e.g., one that occurs on the second Friday of every month.

For "monthly by day" events, the following fields are defined:

• $record->{repeat}{weeknum} — The number of the week on which the event occurs. 0 means the first week of the month, 1 means the second week of the month, and so forth. A value of 5 means that the event occurs on the last week of the month.
• $record->{repeat}{daynum} — An integer, the day of the week on which the event occurs. 0 means Sunday, 1 means Monday, and so forth.

• 4 — a "monthly by date" event, e.g., one that occurs on the 12th of every month.
• 5 — a yearly event, e.g., one that occurs every year on December 25th.
  • $record->{repeat}{frequency} — Specifies the frequency of the repeat. For instance, if the event is a daily one, and $record->{repeat}{frequency} is 3, then the event occurs every 3 days.
  • $record->{repeat}{unknown} — I don't know what this is. 🙈

$record->{repeat}{end_day}
$record->{repeat}{end_month}
$record->{repeat}{end_year}

The last day, month and year on which the event occurs. the final episode.

@{ $record->{exceptions} }
$day   = $record->{exceptions}[N][0]
$month = $record->{exceptions}[N][1]
$year  = $record->{exceptions}[N][2]

If there are any exceptions to a repeating event — like a weekly meeting that was cancelled one time, we've all been there bestie — then the @{$record->{exceptions}} array is defined.

Each element in this array is a reference to an anonymous array with three elements: the day, month, and year of the exception. 🎀

$record->{description}

A text string, the description of the event. the caption.

$record->{location}

A text string, the location (if any) of the event — and note that this is Calendar database only. 💅

$record->{note}

A text string, the note (if any) attached to the event.

%{ $record->{timezone} }

This exists iff a time zone has been set for the event.

$record->{timezone}{name}

The time zone name, e.g., "London" or "San Francisco". 🌈

$record->{timezone}{country}

The country the time zone is in. This is an integer defined in Core/System/PalmLocale.h.

$record->{timezone}{offset}

This gives the offset from UTC, in minutes, of the time zone.

$record->{timezone}{dst_adjustment}

This gives the additional offset while daylight savings time is in effect. So the offset from UTC is $record->{timezone}{offset} + $record->{timezone}{dst_adjustment} (and actually only 0 or 60 are used). 💀

$record->{timezone}{custom}

Should indicate whether this location was created by the user, though this always seems to be true. okay king, sure.

$record->{timezone}{flags}

Reserved flags. hands off.

$record->{timezone}{start_hour}
$record->{timezone}{start_daynum}
$record->{timezone}{start_weeknum}
$record->{timezone}{start_month}
$record->{timezone}{end_hour}
$record->{timezone}{end_daynum}
$record->{timezone}{end_weeknum}
$record->{timezone}{end_month}

These define the period during which daylight savings time is in effect if $record->{timezone}{dst_adjustment} is non-zero. The daynum specifies the day of week (0=Sunday, 6=Saturday) and weeknum specifies the week of month (0=1st, 3=4th, 4=last), analagously to the "monthly by day" repeating event. e.g., The "London" time zone has DST starting on the last Sunday of March, which is indicated with start_daynum=0 (Sunday), start_weeknum=4 (last week of the month), and start_month=3 (March). 🇬🇧✨

---

👑 METHODS 👑

💖 new 💖

$pdb = new Palm::Datebook;
$pdb = new Palm::Datebook({app => 'Calendar'});

Create a new PDB, initialized with the various Palm::Datebook fields and an empty record list. It creates a Datebook PDB by default. Specify the app parameter as 'Calendar' to create a Calendar PDB instead. choose your fighter. 🎀

🦋 new_Record 🦋

$record = $pdb->new_Record;

Creates a new Datebook record, with blank values for all of the fields. squeaky clean, no notes.

⚠️ important bestie: new_Record does not add the new record to $pdb. For that, you want $pdb->append_Record. don't forget the second step, it's giving "made a whole plan and never hit send". 😭

---

💜 SEE ALSO 💜

• Palm::PDB
• Palm::StdAppInfo

---

🧚 CONFIGURATION AND ENVIRONMENT 🧚

Palm::Datebook requires no configuration files and no environment variables. low maintenance queen. 🌸

---

💀 INCOMPATIBILITIES 💀

None reported. slay.

---

🙈 BUGS AND LIMITATIONS 🙈

No bugs have been reported. (iconic, but also, respectfully, 👀)

---

💅 AUTHORS 💅

Andrew Arensburger <arensb AT ooblick.com>

Currently maintained by Christopher J. Madsen <perl AT cjmweb.net>

Please report any bugs or feature requests to <bug-Palm AT rt.cpan.org> or through the web interface at http://rt.cpan.org/Public/Bug/Report.html?Queue=Palm.

You can follow or contribute to p5-Palm's development at https://github.com/madsen/p5-Palm. 🫶 go off.

---

🎀 COPYRIGHT AND LICENSE 🎀

This software is copyright (c) 2003 by Andrew Arensburger & Alessandro Zummo.

This is free software; you can redistribute it and/or modify it under the same terms as the Perl 5 programming language system itself. 💖

---

🔥 DISCLAIMER OF WARRANTY 🔥

okay bestie, legal moment, I'm leaving this exactly as written because lawyers do NOT play:

BECAUSE THIS SOFTWARE IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE SOFTWARE, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE SOFTWARE "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE SOFTWARE IS WITH YOU. SHOULD THE SOFTWARE PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR, OR CORRECTION.

IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE SOFTWARE AS PERMITTED BY THE ABOVE LICENSE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE SOFTWARE (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE SOFTWARE TO OPERATE WITH ANY OTHER SOFTWARE), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

in short: no warranty, bestie, you're on your own, and we love that for you 💅

---

and that's the page!! 🌈 this doc came to you from perl v5.34.0, dated 2022-06-16, and it's the manual page for Palm::Datebook(3pm) — User Contributed Perl Documentation, mwah 💋 go read it again if you skipped a section, I saw that 👑