Free structure of an atom software for linux

XML::Structured is a simple conversion API from XML to perl structures and back.

SYNOPSIS

use XML::Structured;

$dtd = [
element =>
attribute1,
attribute2,
[],
element1,
[ element2 ],
[ element3 =>
...
],
[[ element4 =>
...
]],
];

$hashref = XMLin($dtd, $xmlstring);
$hashref = XMLinfile($dtd, $filename_or_glob);
$xmlstring = XMLout($dtd, $hashref);

The XML::Structured module provides a way to convert xml data into a predefined perl data structure and back to xml. Unlike with modules like XML::Simple it is an error if the xml data does not match the provided skeleton (the "dtd"). Another advantage is that the order of the attributes and elements is taken from the dtd when converting back to xml.

MKDoc::Text::Structured::Inline is a Perl module to convert text to HTML without handling block-level tags.

SYNOPSIS

my $text = some_structured_text();
my $this = MKDoc::Text::Structured::Inline::process ($text);
my $that = MKDoc::Text::Structured::Inline::process_entities_only ($text);

Insurrection provides an advanced Web interface for Subversion.
Insurrection is a Web interface and RSS and Atom feed generator for Subversion that uses modern browser features while being as browser agnostic as possible. It has some repository rights administration features and a reasonably good-looking interface that can be customized. RSS and Atom feeds of updates to the project are available.
Main features:
- Easily browse the repository
- Access any version of any file
- View revision histories
- View differences at various revisions
- Annotate files with respect to author and revision
- Get RSS and Atom feeds of changes in a repository or part of a repository or a specific file
- All repository features are via repository consistent URLs
- Administrate user access to repositories
Enhancements:
- The way the filter for non-XSLT browsers works was changed such that it is possible to detect the upcoming Apple Safari update that fixes its XSLT implementation.
- A way to browse the repository at any revision was added.
- To enable the user to enter this mode, there is a link on the revision change log pages.
- The pre-commit hook was fixed to deal with the trailing "/" on directory entries.

Rubytree is a simple to use general purpose tree data structure implementation in Ruby.
It provides easy access methods for navigating the hierarchy, as well as for accessing the nodes. Rubytree project also provides ability to marshal the entire tree structure.
Enhancements:
- Minor changes were made to the documentation.

PloneAtom provides Atom support for Plone.

This is a Plone product (that could probably be trivially modified for the CMF itself) which provides Atom support for Plone. Currently it provides the Atom syndication format for folderish objects, in the same way as RSS syndication is implemented.

Enabling Atom syndication

Atom syndication is enabled in exactly the same way as RSS syndication. To enable syndication on the site in general:

.Login as an admin user.

.Go to Plone Setup and choose Zope Management Interface

.Select the Properties tab in the portal_syndication tool.

.Click enable syndication. Then, to enable syndication support for a particular folderish object:

.Login as a user who has Owner/Manager permission for the folder.

.Surf to that folder and select the syndication tab.

.Click Enable syndication. Dont worry about the syndication options it gives you -- they are not used by atom (and ignored in most RSS clients, from what Ive seen).

Rsync::Config::Blank is a basic atom object.

SUBROUTINES/METHODS

new

FIXME: constructor

to_string

returns a stringified version of the comment.

name

Unused here. Useful for derivated classes, as "name" accessor/mutator.

value

Unused here. Useful for derivated classes, as "value" accessor/mutator.

Log::Dispatch::Atom is a Perl module to log to an atom feed.

SYNOPSIS

use Log::Dispatch::Atom;

my $log = Log::Dispatch::Atom->new(
name => foo,
min_level => debug,
file => file.atom
);
$log->log_message( level => error, message => A problem happened );
$log->log_message( level => debug, message => Got Here );

This class implements logging backed by an Atom feed so that you can subscribe to the errors produced by your application.

You should not use this object directly, but should manage it via a Log::Dispatch object.

IMPLEMENTATION NOTES

In order to safely write to the log file, the entire file must be locked each time that an entry is logged. This probably makes it unsuitable for high volume log files.
The log file is opened and closed on each call to log_message().

METHODS

new()

Takes a hash of arguments. Returns a new Log::Dispatch::Atom object. The following parameters are used:

name [mandatory]

The name of the logging object.

min_level [mandatory]

The minimum logging level this object will accept. See Log::Dispatch for more information.

max_level [optional]

The maximum logging level this object will accept. See Log::Dispatch for more information. The default is the highest possible level (ie: no maximum).

file [mandatory]

Specifies the location of the file to read/write the feed from.

feed_id [optional]

Specifies the identity of the feed itself. Normally, this should be set to the published URI of the feed.
If not specified, it will be omitted, which is in violation of the Atom specification. For more information, see http://www.atomenabled.org/developers/syndication/#requiredFeedElements.

feed_title [optional]

The title of the feed. This should probably be set to the name of your application.

If not specified, it will be omitted, which is in violation of the Atom specification. For more information, see http://www.atomenabled.org/developers/syndication/#requiredFeedElements.
XXX This should probably just use the name parameter. What do you think? Let me know.

feed_author [optional]

The author details of a feed. This is specified as a hash reference, which must contain one or more of the three keys name, email and uri.

In order to create a valid Atom feed, you must either supply an author in every single entry (log message), or ensure that the feed itself has an author. The latter is probably the easier solution, so I recommend this parameter be supplied.

NB: The feed_* parameters will only be used when a new feed is being created. If you are creating a new object for an existing feed, they will be ignored.

log_message()

Takes a hash of arguments. Has no return value. The following parameters are used.

message [mandatory]

The actual log message.

level [mandatory]

The level of the message. See Log::Dispatch for a full list.

id [optional]

Each entry requires an id in order for the feed as a whole to be a valid Atom document. Its used by readers of Atom documents to determine whether or not an entry has been seen previously.

If not specified, this will default to an URL comprising the current time plus the pid plus the hostname plus a monotonically increasing integer. eg: tag:fred.example.com,2005-12-07:1133946771/20827/2. This should be good enough for a uniqueness test.

author [optional]

You can specify author details for an individual entry if desired. The author parameter is expected to be a hash reference, which must contain one or more of the keys name, email or uri.