Free bath and body works software for linux

The Diary of Hercules is a personal workout diary program for body builders and fitness enthusiasts. The Diary of Hercules can be helpful in creating training plans and storing data about gym progress.
Enhancements:
- Created brand new calendar control.
- Added methods for adding and deleting training plan.
- Added ability to show training days on a calendar control.

Ara is an automatic editor of RSS feed. Only the links towards the Web pages must be given to him. The project is able to retrieve the title and the description of the pages and to produce a syndication file in the RSS format.

It enables you to select the pages to be syndicated instead of publishing the last articles systematically as the generators included in content managers do it.
The Ara term means "Atom and RSS API", it is also the name of a species of parrots from South America.

Using Ara

The program is a set of PHP scripts which have to be stored on a Web site. One creates a feed from the browser by entering the URL of the interface, ara.php.
It is easier to use the program with two browsers, one to display the pages to include and to copy the URLs from the URL input field, the other to edit the RSS file. Thus by just a cut and paste action one transfers the URL from the field to the interface and one clicks on "Add" to add it to the list.

The EDIT button on the left of the link makes it possible to modify the title and description if one wants.

To generate the feed, one enters the nam.

Warning
Ara is not a simple editor, when a page is added, it is reads for extracting useful information and for this purpose Ara makes use of Ajax (with the Anaa framework ), but Ajax can read files only from the site where it is installed. Actually the goal is to build the feed of the site, just avoid to give URL to other sites.

How it works

It is an Ajax script with a backend in PHP 5. In the current version only the pages of the website where it is installed can be added to the feed.

It is necessary to be authenticated to use it, to this goal the install.php program allows to register a login and a password. This file must absolutely be be erased. Once registered, the user remains registered for the whole session, even if he reads other pages meanwhile.

To generate the contents automatically, the program loads the pages given in the list and reads in the head section the contents of the title and description tags. If they are missing, the first H1 tag in the body of the page will be used for the title instead.

The same if description misses, the text of the synopsis will be taken from the page instead.

Mail::Message::Body is the data of a body in a message.

INHERITANCE

Mail::Message::Body has extra code in
Mail::Message::Body::Construct
Mail::Message::Body::Encode

Mail::Message::Body
is a Mail::Reporter

Mail::Message::Body is extended by
Mail::Message::Body::File
Mail::Message::Body::Lines
Mail::Message::Body::Multipart
Mail::Message::Body::Nested
Mail::Message::Body::String

Mail::Message::Body is realized by
Mail::Message::Body::Delayed

SYNOPSIS

my Mail::Message $msg = ...;
my $body = $msg->body;
my @text = $body->lines;
my $text = $body->string;
my IO::Handle $file = $body->file;
$body->print(*FILE);

my $content_type = $body->type;
my $transfer_encoding = $body->transferEncoding;
my $encoded = $body->encode(mime_type => text/html,
charset => us-ascii, transfer_encoding => none);n";
my $decoded = $body->decoded;

The encoding and decoding functionality of a Mail::Message::Body is implemented in the Mail::Message::Body::Encode package. That package is automatically loaded when encoding and decoding of messages needs to take place. Methods to simply build an process body objects are implemented in Mail::Message::Body::Construct.

The body of a message (a Mail::Message object) is stored in one of the many body types. The functionality of each body type is equivalent, but there are performance differences. Each body type has its own documentation with details about its implementation.

FLV::Body is a flash video file data structure.

METHODS

This is a subclass of FLV::Base.

$self->parse($fileinst)

Takes a FLV::File instance and extracts the FLV body from the file stream. This method throws exceptions if the stream is not a valid FLV v1.0 or v1.1 file.

There is no return value.

$self->serialize($filehandle)

Serializes the in-memory FLV body. If that representation is not complete, this throws an exception via croak(). Returns a boolean indicating whether writing to the file handle was successful.

$self->get_info()

Returns a hash of FLV metadata. See File::Info for more details.

$self->get_tags()

Returns an array of tag instances.

$self->count_video_frames()

Returns the number of video tags in the FLV stream.

$self->count_audio_packets()

Returns the number of audio tags in the FLV stream.

$self->count_meta_tags()

Returns the number of meta tags in the FLV stream.

$self->last_start_time()

Returns the start timestamp of the last tag, in milliseconds.

$self->get_meta($key);
$self->set_meta($key, $value);

These are convenience functions for interacting with an onMetadata tag at time 0, which is a common convention in FLV files. If the 0th tag is not an FLV::MetaTag instance, one is created and prepended to the tag list.

See also get_value and set_value in FLV::MetaTag.

Smarty and MIME message integration is a PHP class library that can send e-mail messages using Smarty templates.

This package can be used to compose and send e-mail messages using Smarty templates.

It wraps around Smarty and MIME message class by Manuel Lemos, and prepares the body and headers of the messages to send.

It can set several message options at once passing an array of options values.

Currently it supports options to define HTML or text message template files, the sender, recipient, bounce and reply names and addresses, whether to send messages in plain text, HTML or both, whether to automatically wrap the message text, message character set, and the bulk precedence header to prevent that notification messages be returned due to temporary delivery errors.

Once the message options are set, the class composes and send message according to the specified option values.

IAM OPML Parser Class parses an OPML file (provided its URL) and returns an array.

OPML (Outline Processor Markup Language) is an XML format for outlines. Originally developed by Radio UserLand as a native file format for an outliner application, it has since been adopted for other uses, the most common being to exchange lists of web feeds (RSS) between web feed aggregators. The OPML specification defines an outline as a hierarchical, ordered list of arbitrary elements. The specification is fairly open which makes it suitable for many types of list data.

The XML elements in an OPML document are:

< opml version=”1.0″ > This is the root element. It must contain the version attribute and one head and one body element. Currently, there’s active work in OML 2.0, which is mainly aimed at solving some of v1.o’s shortcomings.

< head > Contains metadata. May include any of these optional elements: title, dateCreated, dateModified, ownerName, ownerEmail, expansionState, vertScrollState, windowTop, windowLeft, windowBottom, windowRight. Each element is a simple text element. dateCreated and dateModified contents conform to the date-time format specified in RFC 822. expansionState contains a comma-separated list of line numbers that should be expanded o and size of the display window. An OPML processor may ignore all the head sub-elements. If the outline is opened inside another outline then the processor must ignore the window elements.

< body > Contains the content of the outline. Must have one or more outline elements.

< outline > Represents a line in the outline. May contain any number of arbitrary attributes. Common attributes include text and type. The outline element may contain any number of outline sub-elements. While there are many tools to create and/or read OPML files, there are few PHP libraries/functions to work with these files.

This PHP class parses an OPML file (provided its URL) and returns an array with all the parsed data. This array contains, for each of the OPML file’s elements the following attributes: link_url, link_name, link_target, link_description, link_rss, created (date of creation), type (link type: RSS, HTML, etc.). The class uses file_get_contents() to retrieve the contents of the OPML file and then the XML extension is used to parse and store the file’s data in an associative array, where each outline element is stored using a different array index. The array has the following structure:

0 : Array:
{
names => Preface
urls => http://www.php.net/manual/en/preface.php
targets =>
feeds =>
descriptions =>
created => Nov 28 2005 21:05:49 GMT
type => link
}
1 : Array:
{
names => I. Getting started
urls =>
targets =>
feeds =>
descriptions =>
created =>
type =>
}

DadaDodo project is a program that generates random sentences based on input files.
Sometimes these sentences are nonsense; but sometimes they cut right through to the heart of the matter, and reveal hidden meanings.
DadaDodo works rather differently than Dissociated Press; whereas Dissociated Press (which, incidentally, refers to itself as a ``travesty generator) simply grabs segments of the body of text and shuffles them, DadaDodo tries to work on a larger scale: it scans bodies of text, and builds a probability tree expressing how frequently word B tends to occur after word A, and various other statistics; then it generates sentences based on those probabilities.
The theory here is that, with a large enough corpus, the generated sentences will tend to be grammatically correct, but semantically random: exterminate all rational thought.
This kind of probability histogram is called a Markov Chain, after Andrei Markov, the fellow who invented it. It turns out that Markov Chains can actually be used for things other than generating random text.
They are used in image processing, for feature recognition; and can be used to analyze finite-state machines for bottlenecks and critical paths: the states which occur most often are where the bottlenecks are.
Enhancements:
- Fixed some crashes by using "unsigned char" everywhere.