Free rich site summary software for linux

Mail::Summary is a Perl module that can scan read your mail!

SYNOPSIS

my $ms = Mail::Summary->new({ maildir => /home/mwk/Maildir });

my @mail_summaries = $ms->summaries;

Too busy to read your mail? Subscribe to too many mailing lists? Take two folders into the shower? Well, for the busy on the go geek of today, here is the answer! Get all your messages summarised, to save you having to read them, or to read them by which summary looks better!

new

my $ms = Mail::Summary->new({ maildir => /home/mwk/Maildir });

This will make a new Mail::Summary object.

maildir

my $maildir = $ms->maildir;

This is the mail directory as defined by the user.

summaries

my @mail_summaries = $ms->summaries;

This will return a list, with every entry in the list being a summary of an individual message.

Hierarchical Grid Site Managment is a front-end to the database that keeps information about the grid sites (clusters), their admins, email and phone contacts, other contact people, site nodes and resources, downtimes etc.
These sites are organized by country and countries are organized by regions. The admins of each site can also update the information about the site.
To summarize the design, the applications supports only one GOC (Grid Operation Center), assuming that it is used for only one grid. It can have several ROCs (Regional Operation Centers), each ROC can have several countries, and each country can have several sites.
Each ROC, country and site can have one (or more) admins, which are able to modify the data of the structure (record) which they admin (ROC, country or site), and to manage substructures as well.
Managing substructures means that they can also validate/appoint the admins of the substructures, e.g. a country admin can validate/appoint the site admins. The admins are recognized automatically by their certificate (without the need to use passwords).
For each structure (ROC, country, site), contact info about it are stored, including email and phone. For the sites, general info about it are stored, contact info, info about its resources and capacities, site contacts, site downtimes, and info about its nodes. For more details see the DB design: hgsm_design.sql.
In the pages where a user has edit rights (in the node where he is admin and in all the subnodes), an Edit button is displayed. Clicking in this button, the page will be displayed in the edit mode, where the fields of information can be modified, the rows of the lists can be edited or deleted, new rows can be added in the lists, etc. The id and the admins of a node can be modified only by an admin of the parent node.
Main features:
- Has a database with information about a hierarchical structure (GOC-->ROCs-->Countries-->Sites-->Nodes).
- This information is published to the www by a web application.
- Each node of the tree has also one or more admins, which can modify the data of the node which they admin, and also the data of the subnodes.
- The admins of a node can appoint (set/modify/delete) the admins of the subnodes and leave up to them the modification/update of the subnode information (to make their job easier and for decentralization).
- Authentication (recognizing that somebody is admin of a node and has the rights to modify it) is done automatically by the application, using personal certificates, which are issued and verified by a certain certification authority. This means that everybody that is an admin, must have a valid certificate installed in his browser.
- The application also supports i18n and l10n (is multilingual, can be translated into several languages).
Enhancements:
- This release includes full internationalization and localization support for Albanian and Croatian.
- It also contains bdii.php?type1+type2+type3 and ldap2mysql.py the scripts.
- Some small improvements and bugfixes were made.

PHP/Mysql Site Builder is a PHP/Mysql tool for managing your homepage, you can create dinamyc and static version of your site.
PHPBuilder is free software, released under GNU GPL Licence version 2.0
(see COPYING file for details).
PHPBuilder is the result of many ideas, and code write by Luis Claudio
Gamboa Lopes.
For installation instructions, go and read INSTALL file, also remember
to read CREDITS file to know from where comes the things. The TODO file
is the list of features that Ill add in future versions, read it also.
Please, enjoy PHPBuilder and remember that this is free GPL software and
comes without any warranty and without technical support.
PHPBuilder isnt perfect, but your suggestions and feedback can help all
us to have a very well site builder system!
Enhancements:
- PHP 4.0 and MySQL 4.0 are now supported.

Spring-RCPs mission is to provide an elegant way to build highly-configurable, GUI-standards-following rich-client applications faster by leveraging the Spring Framework, and a rich library of UI factories and support classes.
The Spring Rich Client Project (RCP) is a sub-project of The Spring Framework. Spring-RCPs mission is to provide an elegant way to build highly-configurable, GUI-standards-following rich-client applications faster by leveraging the Spring Framework, and a rich library of UI factories and support classes. Initial focus is on providing support for Swing applications but a goal of Spring-RCP is to be view agnostic as much as possible.
Spring Rich Client Projects goal is to provide a viable option for developers that need a platform and a best-practices guide for constructing Swing applications quickly.
Specifically, spring-richclient seeks to:
Provide a way to build structured, highly-configurable, GUI-standards-following Swing applications faster by leveraging the Spring Framework.
Foster integration with existing rich-client-related projects where it make sense. For example, jgoodies-forms and TableLayout are two good layout managers. We dont need to develop another one.
Adhere to the principles set forth by the Spring Framework--programming to interfaces; the importance of sound OO design, documentation, and testing.
Main features:
- A command framework that provides centralized configuration of Swing actions and appropriate handler registration based on the current active view. Command configuration, as well as action bar contribution policies (to menus or toolbars), can be defined centrally and externalized in Spring bean defintiions.
- A forms data binding and validation framework, for connecting edits made in your UI controls with your domain model automatically--with as you type feedback.
- Support for multiple window management, page configuration, and view management. The concepts here are inspired by Eclipses perspective/view constructs. Views can be defined in the Spring container, associated with one or more pages, and a default page can be configured to be loaded at startup.
- Common support classes addressing various rich client requirements including: well formed dialogs, wizards, input validation (typing hints and validation results reporting), button bars,internationalization, image/icon caching, progress monitoring, UI threading (classes cleanly promoting responsive UIs), treetable/property sheet, table sorting/high-volume table updates, GUI standards builders/helpers, help/about, etc.
Spring-rich adds value for people needing to develop Swing applications and do so in a way that promotes consistent, well-designed, configurable Swing applications. The spring-rich developers strongly feel the old days of Swing apps not looking native and not being performant or web-accessible are gone with JDK1.4.2 and 1.5 and webstart.
It is our belief the only problem with Swing is that there are a limited number of higher-level abstractions available that assist in making the toolkit simpler and easier to use, and a limited number of design best practices. The goal of spring-richclient is to provide that.
Enhancements:
- [RCP-400] - jgoodies forms not included as spring-rich dependencies
- Regression bug: icons on MessageAreaPane didnt show up

Mail::Summary::Tools are tools for mailing list summarization.



SYNOPSIS

# create a summary from anything Mail::Box can open.
# you may also programatically create summary objects and serialize
# them if you dont have the threads in a standard mail format.

% mailsum create --dates --posters --clean -i foo.mbox -o summary.yaml


# edit the text in your editor, if you dont like YAML files

% mailsum edit --skip --dates --posters --links --archive gmane summary.yaml


# create pretty outputs

% mailsum totext --shorten -a google summary.yaml > summary.txt
% mailsum tohtml --archive google summary.yaml > summary.html

This distribution contains numerous classes useful for creating summaries, and an App::Cmd based frontend to those classes.
The main usage is illustrated in the "SYNOPSIS" section.

Wizard Site Framework project has been used in production sites for three years, serving countless thousands of page views.
It is modular , coming out of the factory with a basic structure, allowing the webmaster to spend more time on design and less on the plumbing.
Included is a user authentication system, scripts for registering, changing passwords, contact forms, confirmation emails, listing users, editing their profiles, privacy statements (etc.etc.), fully integrated into the site skeleton and under the rule of common CSS stylesheets.
Very cool is the menu and sitemap systems which are generated from the database automatically when a page is added or altered during authoring. The menu systems use the famed Suckerfish CSS-driven Javascript code harnessed to a MySQL database with PHP scripting.
You can, for example, have either horizontal or vertical menus, and they can be set at whatever depth you think is reasonable. You can hide pages from the menu or sitemap or restrict their view to only site members with the appropriate credentials.
Other features include such utilities as visitors statistics tied to the user management system so that you can see what specific pages on your site your registered members are viewing.
This is the third generation of the Wizard framework. While the structure of the site continues to be managed through an admin panel, and stored in a MySQL database, what is rather unique about the latest iteration is that the page content, indeed the entire page, is stored on the server as an HTML - PHP file.
While previous versions stored HTML content in the database, the Version 3.0 makes the page completely accessible to such online programs as Macromedia Contribute or other authoring tools.
Unlike previous versions, or content management systems (CMS) that store the HTML content in a database table, you have the ability to include whatever server-side or client-side code in site pages, removing a major disadvantage of most content management systems.
This makes Wizard Site Framework totally customizable and flexible. And because it is lightweight and very efficient it is easily scalable to large sites.
Enhancements:
- Many major and minor bugs were fixed.
- The front and back ends are now W3C compliant.
- A Poll and Blog script was added.
- Preliminary support for the PostgreSQL database was added.

DBD::Informix::Summary is an updated version of the information about DBD::Informix in the DBI book.
Main features:
- Transactions Yes, if enabled when database was created
- Locking Yes, implicit and explicit
- Table joins Yes, inner and outer
- LONG/LOB data types Yes, upto 2GB
- Statement handle attributes available After prepare()
- Placeholders Yes, "?" (native)
- Stored procedures Yes
- Bind output values Yes
- Table name letter case Configurable
- Field name letter case Configurable
- Quoting of otherwise invalid names Yes, via double quotes
- Case insensitive "LIKE" operator No
- Server table ROW ID pseudocolumn Yes, "ROWID"
- Positioned update/delete Yes
- Concurrent use of multiple handles Unrestricted