Free calendar templates software for linux

kmail templates is a patch for current 3.5 branch of kdepim package which replaces Phrases configuration with more rich templates engine.

Templates use template syntax of well-known Thebat! mail client and allow construct a little more complicated messages than now.

Calendar is a web-based calendar tool that produces pretty, readable calendars. NEW! Rewritten in Java for MySQL! Calendar project began out of frustration with other web-based calendar tools inability to display a readable calendar format. It was very much a project to "scratch an itch" -- to meet an immediate need that the author had. Since then, it has evolved considerably into a very useful tool that produces prettier calendars than those printed by most organizer software.
Main features:
- NEW! Subscriptions can be created to periodically fetch events from remote calendars, just like iCal and Sunbird can do.
- Events on the calendar appear exactly as typed in the admin tool -- the descriptions are not cut off in the display. This makes the calendar just as useful when its printed.
- The entire calendar is rendered in HTML -- no Flash or Java is used.
- Single-day, multi-day and occassional events are all supported. ("Occasional" events are those events that occur multiple times but dont necessarily follow a regular pattern.)
- Repeating events are supported and can repeat on a daily, weekly, monthly or yearly basis.
- Events may be categorized for easy administration.
- Nearly everything about the display is themable -- colors, fonts, border styles, first day of the week, weekday column widths, categories, etc.
- A calendar may be setup as a "private" calendar, so the user must be logged in to see it.
- NEW! A calendar may be setup as a "semi-private" calendar, so the user will only see the scheduled times but no event details.
- The admin tool is password protected and different users can be assigned different permission levels.
- Apple iCal and Mozilla Sunbird users can subscribe to the calendar with one click.
- A really bland, unimaginative name makes it easy to discuss this project without being overheard by foreign intelligence agents.
The first version of this software was written in ASP (VBScript) and ran on IIS 4.0 or higher with a database on SQL Server 7.0 or higher. The current version has been completely rewritten in Java to run on Tomcat 5.5 or higher with a database on MySQL 3.3 or higher. The feature set has grown immensely since then. The two versions have no code in common.

Milo Calendar is a SuperKaramba script that reads the dates stored by KOrganizer and displays them on your desktop in a clear, neat calendar.

The calendar also displays todays date and it can move back/forward months. the descriptions of the events are shown via tooltips.

The images for this theme should be very customizable. In the next versions I will try to make them compatible with rainlendar themes found all over the net!

I must thank DeVoeSquared.com for the iCal module, and rainy (rainlendar) for the theme.

Note: if you have multiple KOrganizer resources, you can change the name of the file that milo calendar reads:

the default is:
reader = iCal.ICalReader(std)
in the dir: ~/.kde/share/apps/korganizer/std.ics

Holidays or other events can be configured to be highlighted in a special way (using CSS styles). The days of the month can rendered with a form checkbox or radio buttons so they can be selected by the user.

Rendering of the different calendar elements can be configured using CSS styles. The names of the months and days of the week can be configured, so that they’re displayed in a language other than English.

This class is licensed under the GNU Lesser General Public License (LGPL), so feel free to use it, modify it as you want, although a little credit is always welcome.

HTML::Template module attempts to make using HTML templates simple and natural.
HTML::Template library extends standard HTML with a few new tags for variables, loops, if/else blocks and includes.
A file written with HTML and these new tags is called a template. Using this module you fill in the values for the variables and loops declared in the template.
This allows you to seperate design (the HTML) from the data, which you generate in the Perl script. While there are many other HTML template systems available, this module is simple and fast.
It doesnt try to reinvent Perl CGI, it just augments HTML with a few new and very useful abilities.
Enhancements:
- A new option was added to enforce Taint mode for unescaped variables.
- Several long-standing bugs were fixed.
- The enhanced tests produced by the Phalanx project are now part of the module.

Pod::Template is a Perl module for building pod documentation from templates.

SYNOPSIS

### As a module ###
use Pod::Template;
my $parser = new Pod::Template;
$parser->parse( template => documentation.ptmpl );

print $parser->as_string


### As a script ###
$ podtmpl -I dir1 -I dir2 documentation.ptmpl


### A simple module prepared to use Pod::Template ###
package My::Module;

=Template print_me
=head2 print_me( $string )

Prints out its argument.

=cut

sub print_me { print shift; return 1 }


### A simple pod file named Extra/Additional.pod ###
=pod
=Template return_vals

This subroutine returns 1 for success and undef for failure.

=cut


### A simple Pod::Template template ###
=Include My::Module
=Include Extra/Additional.pod as Extra

=pod

=head1 SYNOPSIS

use My::Module

My::Module::print_me(some text);

=head2 Functions

=Insert My::Module->print_me

=Insert Extra->return_vals

=cut

Writing documentation on a project maintained by several people which spans more than one module is a tricky matter. There are many things to consider:

Location
Should pod be inline (above every function), at the bottom of the module, or in a distinct file? The first is easier for the developers, but the latter two are better for the pod maintainers.

Order
What order should the documentation be in? Does it belong in the order in which the functions are written, or ordered by another principle, such as frequency of use or function type? Again, the first option is better for the developers, while the second two are better for the user.

References
How should a function in another file be mentioned? Should the documentation simply say see Other::Module, or should it include the relevant section? Duplication means that the documentation is more likely to be outdated, but its bad for a user to have to read numerous documents to simply find out what an inherited method does.

Headers & Footers
What should be done with standard headers and footers? Should they be pasted in to every file, or can the main file be assumed to cover the entire project?

Pod::Template offers a solution to these problems: documentation is built up from templates.