minimalist
Sponsored Links
Sponsored Links
Secleted [ 0 ] software to compare
Results 1 - 15 of about 39
Minimalist Admin 0.4
Minimalist Admin is a very simple Web interface for the Minimalist mailing lists manager. more>>
Minimalist Admin is a very simple Web interface for the Minimalist mailing lists manager.
Installation:
1. Unarchive Minimalist Manager
Make sure that you are in your WWW directory and then unarchive the Minimalist Manager archive (whatever the filename is):
$ tar -zxvf minimalist-manager-0.3.tgz
2. Configure
Check the config.inc file. There you can specify settings that are relevant to your setup.
3. Create list configuration
The list information is taken from the lists.lst file from Minimalist.
In the directory /lists you find 2 files. One .css file in which you can modify the appearance of the subscribe/unsubscribe window. And one config file, in which relevant information which describes the mailinlist.
You have to create at least the config file per list. If there is no css file it will use the toplevel stylesheet located in the root of Minimalist Manager.
4. Done
This is all that is needed. Fire up your browser and go to the site that you specified to host Minimalist Manager.
<<lessInstallation:
1. Unarchive Minimalist Manager
Make sure that you are in your WWW directory and then unarchive the Minimalist Manager archive (whatever the filename is):
$ tar -zxvf minimalist-manager-0.3.tgz
2. Configure
Check the config.inc file. There you can specify settings that are relevant to your setup.
3. Create list configuration
The list information is taken from the lists.lst file from Minimalist.
In the directory /lists you find 2 files. One .css file in which you can modify the appearance of the subscribe/unsubscribe window. And one config file, in which relevant information which describes the mailinlist.
You have to create at least the config file per list. If there is no css file it will use the toplevel stylesheet located in the root of Minimalist Manager.
4. Done
This is all that is needed. Fire up your browser and go to the site that you specified to host Minimalist Manager.
Download (0.010MB)
Added: 2005-10-22 License: GPL (GNU General Public License) Price:
1463 downloads
Email::Store 0.24
Email::Store is a framework for database-backed email storage. more>>
Email::Store is a framework for database-backed email storage.
SYNOPSIS
use Email::Store dbi:mysql:mailstore;
Email::Store->setup; # Do this once
Email::Store::Mail->store( $rfc822 );
Email::Store::Mail->retrieve( $msgid );
...
Email::Store is the ideal basis for any application which needs to deal with databases of email: archiving, searching, or even storing mail for implementing IMAP or POP3 servers.
Email::Store itself is a very lightweight framework, meaning it does not provide very much functionality itself; in effect, it is merely a Class::DBI interface to a database schema which is designed for storing email. Incidentally, if you dont know much about Class::DBI, youre going to need to in order to get much out of this.
Despite its minimalist nature, Email::Store is incredibly powerful. Its power comes from its extensibility, through plugin modules and hooks which allow you to add new database tables and concepts to the system, and so access the mail store from a "different direction". In a sense, Email::Store is a blank canvas, onto which you can pick and choose (or even write!) the plugins which you want for your application.
For instance, the core Email::Store::Entity plugin module addresses the idea of "people" in the email universe, allowing you to search for mails to or from particular people; (despite their changing names or email addresses) Email::Store::Thread interfaces Email::Store to Mail::Thread allowing you to navigate mails by their position in a mail thread; the planned non-core Email::Store::Plucene module plugs into the indexing process and stores information about emails in a Plucene search index for quick retrieval later, and so on.
<<lessSYNOPSIS
use Email::Store dbi:mysql:mailstore;
Email::Store->setup; # Do this once
Email::Store::Mail->store( $rfc822 );
Email::Store::Mail->retrieve( $msgid );
...
Email::Store is the ideal basis for any application which needs to deal with databases of email: archiving, searching, or even storing mail for implementing IMAP or POP3 servers.
Email::Store itself is a very lightweight framework, meaning it does not provide very much functionality itself; in effect, it is merely a Class::DBI interface to a database schema which is designed for storing email. Incidentally, if you dont know much about Class::DBI, youre going to need to in order to get much out of this.
Despite its minimalist nature, Email::Store is incredibly powerful. Its power comes from its extensibility, through plugin modules and hooks which allow you to add new database tables and concepts to the system, and so access the mail store from a "different direction". In a sense, Email::Store is a blank canvas, onto which you can pick and choose (or even write!) the plugins which you want for your application.
For instance, the core Email::Store::Entity plugin module addresses the idea of "people" in the email universe, allowing you to search for mails to or from particular people; (despite their changing names or email addresses) Email::Store::Thread interfaces Email::Store to Mail::Thread allowing you to navigate mails by their position in a mail thread; the planned non-core Email::Store::Plucene module plugs into the indexing process and stores information about emails in a Plucene search index for quick retrieval later, and so on.
Download (0.027MB)
Added: 2006-06-28 License: Perl Artistic License Price:
1215 downloads
TinyMake 0.06
TinyMake is a minimalist build language, similar in purpose to make and ant. more>>
TinyMake is a minimalist build language, similar in purpose to make and ant.
SYNOPSIS
use TinyMake :all;
# a file statement without a rule is like a symbolic target
file all => ["codeGen", "compile", "dataLoad", "test"];
file codeGen => ["database.spec"], sub {
# generate code here
sh "touch $target";
} ;
file compile => ["codeGen"], sub {
# compile code here
sh "touch $target";
} ;
file dataLoad => ["codeGen"], sub {
# load data here
sh "touch $target"
} ;
file test => ["compile", "dataLoad"], sub {
# test code here
sh "touch $target";
} ;
# a file statement without prerequisites will be executed
# if the target doesnt exist.
file clean => sub {
# perform cleanup here
sh "rm compile codeGen dataLoad test"
} ;
make @ARGV
This Perl Module allows you to define file-based dependencies similar to how make works.Rather than placing the build rules in a separate Makefile or build.xml, the build rules are declared using standard Perl syntax. TinyMake is effectively an inline domain-specific language. Using make you might write a makefile that looks like this...
test: compile dataLoad
# test
touch test
codeGen: database.spec
# generate code
touch codeGen
compile: codeGen
# compile code
touch compile
dataLoad: codeGen
# load data
touch dataLoad
database.spec: # source file
The equivalent perl code using TinyMake would look like this...
use TinyMake :all;
# some perl code
.
.
.
file test => ["compile","dataLoad"], sub { # test
`touch test`;
} ;
file codeGen => "database.spec", sub { # generate code
`touch codeGen`;
} ;
# some more perl code
.
.
.
file compile => "codeGen", sub { # compile code
`touch compile`;
} ;
file dataload => "codeGen", sub { # load data
`touch dataLoad`;
} ;
make @ARGV;
<<lessSYNOPSIS
use TinyMake :all;
# a file statement without a rule is like a symbolic target
file all => ["codeGen", "compile", "dataLoad", "test"];
file codeGen => ["database.spec"], sub {
# generate code here
sh "touch $target";
} ;
file compile => ["codeGen"], sub {
# compile code here
sh "touch $target";
} ;
file dataLoad => ["codeGen"], sub {
# load data here
sh "touch $target"
} ;
file test => ["compile", "dataLoad"], sub {
# test code here
sh "touch $target";
} ;
# a file statement without prerequisites will be executed
# if the target doesnt exist.
file clean => sub {
# perform cleanup here
sh "rm compile codeGen dataLoad test"
} ;
make @ARGV
This Perl Module allows you to define file-based dependencies similar to how make works.Rather than placing the build rules in a separate Makefile or build.xml, the build rules are declared using standard Perl syntax. TinyMake is effectively an inline domain-specific language. Using make you might write a makefile that looks like this...
test: compile dataLoad
# test
touch test
codeGen: database.spec
# generate code
touch codeGen
compile: codeGen
# compile code
touch compile
dataLoad: codeGen
# load data
touch dataLoad
database.spec: # source file
The equivalent perl code using TinyMake would look like this...
use TinyMake :all;
# some perl code
.
.
.
file test => ["compile","dataLoad"], sub { # test
`touch test`;
} ;
file codeGen => "database.spec", sub { # generate code
`touch codeGen`;
} ;
# some more perl code
.
.
.
file compile => "codeGen", sub { # compile code
`touch compile`;
} ;
file dataload => "codeGen", sub { # load data
`touch dataLoad`;
} ;
make @ARGV;
Download (0.010MB)
Added: 2007-06-06 License: Perl Artistic License Price:
873 downloads
Devel::Modlist 0.71
Devel::Modlist is a Perl extension to collect module use information. more>>
Devel::Modlist is a Perl extension to collect module use information.
SYNOPSIS
perl -d:Modlist script.pl
The Devel::Modlist utility is provided as a means by which to get a quick run-down on which libraries and modules are being utilized by a given script.
Just as compiler systems like gcc provide dependancy information via switches such as -M, Devel::Modlist is intended to assist script authors in preparing dependancy information for potential users of their scripts.
USAGE
Usage of Devel::Modlist is simple. The primary method of invocation is to use the -d option of Perl:
perl -d:Modlist script.pl
Alternately, one could use the -M option:
perl -MDevel::Modlist script.pl
In the case of this module, the two are identical save for the amount of typing (and option passing, see below). It is not recommended that this module be loaded directly by a script via the use keyword, as that would cause the dependancy reporting after every invocation until it was removed from the code.
OPTIONS
The following options may be specified to the package. These are specified either by:
perl -MDevel::Modlist=option1[,option2,...]
or
perl -d:Modlist=option1[,option2,...]
Options may also be given in an environment variable, which gets read at any invocation in which there are no options explicitly provided. If any options are given in the invocation, then the environment variable is ignored. Two different names are recognized:
Devel::Modlist
Devel__Modlist
The latter is to accomodate shells that do not like the presence of :: in an environment variable name.
The options:
cpan
Reduce the resulting list of modules by using the data maintained in the local CPAN configuration area. The CPAN module (see CPAN) maintains a very thorough representation of the contents of the archive, on a per-module basis. Using this option means that if there are two or more modules that are parts of the same distribution, only one will be reported (the one with the shortest name). This is useful for generating a minimalist dependancy set that can in turn be fed to the CPAN install command to ensure that all needed modules are in fact present.
cpandist
This is identical to the option above, with the exception that it causes the reported output to be the CPAN filename rather than the module name in the standard Perl syntax. This can also be fed to the CPAN shell, but it can also be used by other front-ends as a path component in fetching the requisite file from an archive site. Since the name contains the version number, this behaves as though noversion (see below) was also set. If both cpan and cpandist are set, this option (cpandist) takes precedence. If path is also specified, this option again takes precedence.
nocore
Suppress the display of those modules that are a part of the Perl core. This is dependant on the Perl private library area not being an exact substring of the site-dependant library. The build process checks this for you prior to install.
noversion
Suppress the inclusion of version information with the module names. If a module has defined its version by means of the accepted standard of declaring a variable $VERSION in the package namespace, Devel::Modlist finds this and includes it in the report by default. Use this option to override that default.
path
Display the path and filename of each module instead of the module name. Useful for producing lists for later input to tools such as rpm.
stop
Exit before the first actual program line is executed. This provides for fetching the dependancy list without actually running the full program. This has a drawback: if the program uses any of require, eval or other such mechanisms to load libraries after the compilation phase, these will not be reported.
<<lessSYNOPSIS
perl -d:Modlist script.pl
The Devel::Modlist utility is provided as a means by which to get a quick run-down on which libraries and modules are being utilized by a given script.
Just as compiler systems like gcc provide dependancy information via switches such as -M, Devel::Modlist is intended to assist script authors in preparing dependancy information for potential users of their scripts.
USAGE
Usage of Devel::Modlist is simple. The primary method of invocation is to use the -d option of Perl:
perl -d:Modlist script.pl
Alternately, one could use the -M option:
perl -MDevel::Modlist script.pl
In the case of this module, the two are identical save for the amount of typing (and option passing, see below). It is not recommended that this module be loaded directly by a script via the use keyword, as that would cause the dependancy reporting after every invocation until it was removed from the code.
OPTIONS
The following options may be specified to the package. These are specified either by:
perl -MDevel::Modlist=option1[,option2,...]
or
perl -d:Modlist=option1[,option2,...]
Options may also be given in an environment variable, which gets read at any invocation in which there are no options explicitly provided. If any options are given in the invocation, then the environment variable is ignored. Two different names are recognized:
Devel::Modlist
Devel__Modlist
The latter is to accomodate shells that do not like the presence of :: in an environment variable name.
The options:
cpan
Reduce the resulting list of modules by using the data maintained in the local CPAN configuration area. The CPAN module (see CPAN) maintains a very thorough representation of the contents of the archive, on a per-module basis. Using this option means that if there are two or more modules that are parts of the same distribution, only one will be reported (the one with the shortest name). This is useful for generating a minimalist dependancy set that can in turn be fed to the CPAN install command to ensure that all needed modules are in fact present.
cpandist
This is identical to the option above, with the exception that it causes the reported output to be the CPAN filename rather than the module name in the standard Perl syntax. This can also be fed to the CPAN shell, but it can also be used by other front-ends as a path component in fetching the requisite file from an archive site. Since the name contains the version number, this behaves as though noversion (see below) was also set. If both cpan and cpandist are set, this option (cpandist) takes precedence. If path is also specified, this option again takes precedence.
nocore
Suppress the display of those modules that are a part of the Perl core. This is dependant on the Perl private library area not being an exact substring of the site-dependant library. The build process checks this for you prior to install.
noversion
Suppress the inclusion of version information with the module names. If a module has defined its version by means of the accepted standard of declaring a variable $VERSION in the package namespace, Devel::Modlist finds this and includes it in the report by default. Use this option to override that default.
path
Display the path and filename of each module instead of the module name. Useful for producing lists for later input to tools such as rpm.
stop
Exit before the first actual program line is executed. This provides for fetching the dependancy list without actually running the full program. This has a drawback: if the program uses any of require, eval or other such mechanisms to load libraries after the compilation phase, these will not be reported.
Download (0.008MB)
Added: 2007-05-08 License: Perl Artistic License Price:
899 downloads
mod_xmlns 0.97
mod_xmlns Apache module adds XML namespace support to publishing with Apache. more>>
mod_xmlns Apache module adds XML namespace support to publishing with Apache.
mod_xmlns adds XML Namespace support to Apache, and may form the basis of XML-driven publishing systems. It runs as an output filter, so it works automatically with any content generator.
From Version 0.9 (May 1st 2004) it has moved from experimental prototype to provisionally stable (i.e. theres nothing that is known to need changing before it can be declared stable). This hasnt entirely held, as the API has had to be updated. Now the API is shared with mod_publisher, and is being documented.
The basic API for Namespace implementations is:
- Create event handlers for your namespace.
- Declare your handlers in a struct xmlns.
- Make it available to mod_xmlns using ap_register_provider with provider_group=xmlns, provider_name=your_namespace and your choice of version string (see the XMLNSUseNamespace directive).
Directives implemented by mod_xmlns
XMLNSUseNamespace
Syntax: XMLNSUseNamespace URI [on|off] [version]
Activates or deactivates processing for namespace URI, using the processor defined in the version paramater.
XMLNSDefaultNamespace
Syntax: XMLNSDefaultNamespace URI
Sets a URI to use as default namespace (for un-namespaced elements).
XMLNSCommentHandlers
Syntax: XMLNSCommentHandlers on|off
Turns on or off comment handlers defined in namespace implementations. Default is On.
XMLNSCommentRemove
Syntax: XMLNSCommentRemove on|off
Determines whether to strip comments that are not processed by any namespace handler. Default is to pass comments through intact.
Version restrictions:
- mod_xmlns is a minimalist SAX parser, and has no support for DTDs and external entities, nor does it offer much scope for sanity checks on markup being processed. A compatible but richer companion module mod_publisher is in development.
<<lessmod_xmlns adds XML Namespace support to Apache, and may form the basis of XML-driven publishing systems. It runs as an output filter, so it works automatically with any content generator.
From Version 0.9 (May 1st 2004) it has moved from experimental prototype to provisionally stable (i.e. theres nothing that is known to need changing before it can be declared stable). This hasnt entirely held, as the API has had to be updated. Now the API is shared with mod_publisher, and is being documented.
The basic API for Namespace implementations is:
- Create event handlers for your namespace.
- Declare your handlers in a struct xmlns.
- Make it available to mod_xmlns using ap_register_provider with provider_group=xmlns, provider_name=your_namespace and your choice of version string (see the XMLNSUseNamespace directive).
Directives implemented by mod_xmlns
XMLNSUseNamespace
Syntax: XMLNSUseNamespace URI [on|off] [version]
Activates or deactivates processing for namespace URI, using the processor defined in the version paramater.
XMLNSDefaultNamespace
Syntax: XMLNSDefaultNamespace URI
Sets a URI to use as default namespace (for un-namespaced elements).
XMLNSCommentHandlers
Syntax: XMLNSCommentHandlers on|off
Turns on or off comment handlers defined in namespace implementations. Default is On.
XMLNSCommentRemove
Syntax: XMLNSCommentRemove on|off
Determines whether to strip comments that are not processed by any namespace handler. Default is to pass comments through intact.
Version restrictions:
- mod_xmlns is a minimalist SAX parser, and has no support for DTDs and external entities, nor does it offer much scope for sanity checks on markup being processed. A compatible but richer companion module mod_publisher is in development.
Download (0.026MB)
Added: 2006-04-05 License: GPL (GNU General Public License) Price:
1298 downloads
Module::Install 0.64
Module::Install is a standalone, extensible Perl module installer. more>>
Module::Install is a standalone, extensible Perl module installer.
SYNOPSIS
In your Makefile.PL: (Recommended Usage)
# Load the Module::Install bundled in ./inc/
use inc::Module::Install;
# Define metadata
name Your-Module;
all_from lib/Your/Module.pm;
# Specific dependencies
requires Carp => 0;
requires File::Spec => 0.80;
build_requires Test::More => 0.42;
recommends Your::OtherModule => 0.01;
no_index directory => demos;
install_script bin/myscript;
auto_install;
WriteAll;
Quickly upgrade a legacy ExtUtil::MakeMaker installer:
# Drop-in replacement to ExtUtils::MakeMaker
use inc::Module::Install;
WriteMakefile( ... );
A dummy Build.PL so we can work with Module::Build as well:
# Dear Distribution Packager. This use of require is intentional.
# Module::Install detects Build.PL usage and acts accordingly.
require Makefile.PL;
Module::Install is a package for writing installers for CPAN (or CPAN-like) distributions that are clean, simple, minimalist, act in a strictly correct manner with both the ExtUtils::MakeMaker and Module::Build build systems, and will run on any Perl installation version 5.004 or newer.
The intent is to make it as easy as possible for CPAN authors (and especially for first-time CPAN authors) to have installers that follow all the best practices for distribution installation, but involve as much DWIM (Do What I Mean) as possible when writing them.
<<lessSYNOPSIS
In your Makefile.PL: (Recommended Usage)
# Load the Module::Install bundled in ./inc/
use inc::Module::Install;
# Define metadata
name Your-Module;
all_from lib/Your/Module.pm;
# Specific dependencies
requires Carp => 0;
requires File::Spec => 0.80;
build_requires Test::More => 0.42;
recommends Your::OtherModule => 0.01;
no_index directory => demos;
install_script bin/myscript;
auto_install;
WriteAll;
Quickly upgrade a legacy ExtUtil::MakeMaker installer:
# Drop-in replacement to ExtUtils::MakeMaker
use inc::Module::Install;
WriteMakefile( ... );
A dummy Build.PL so we can work with Module::Build as well:
# Dear Distribution Packager. This use of require is intentional.
# Module::Install detects Build.PL usage and acts accordingly.
require Makefile.PL;
Module::Install is a package for writing installers for CPAN (or CPAN-like) distributions that are clean, simple, minimalist, act in a strictly correct manner with both the ExtUtils::MakeMaker and Module::Build build systems, and will run on any Perl installation version 5.004 or newer.
The intent is to make it as easy as possible for CPAN authors (and especially for first-time CPAN authors) to have installers that follow all the best practices for distribution installation, but involve as much DWIM (Do What I Mean) as possible when writing them.
Download (0.078MB)
Added: 2006-09-27 License: Perl Artistic License Price:
1126 downloads
Email::Store::DBI 0.254
Email::Store::DBI is a Perl module for database backend to Email::Store. more>>
Email::Store::DBI is a Perl module for database backend to Email::Store.
SYNOPSIS
use Email::Store dbi:...;
This class is a subclass of Class::DBI and contains means for Email::Store-based programs to register what DSN they wish to use. It also provides for building database tables from schemas embedded in the DATA section of plug-in modules, using Class::DBI::DATA::Schema.
"Email::Store" is the ideal basis for any application which needs to deal with databases of email: archiving, searching, or even storing mail for implementing IMAP or POP3 servers.
"Email::Store" itself is a very lightweight framework, meaning it does not provide very much functionality itself; in effect, it is merely a Class::DBI interface to a database schema which is designed for storing email. Incidentally, if you dont know much about "Class::DBI", youre going to need to in order to get much out of this.
Despite its minimalist nature, "Email::Store" is incredibly powerful. Its power comes from its extensibility, through plugin modules and hooks which allow you to add new database tables and concepts to the system, and so access the mail store from a "different direction". In a sense, "Email::Store" is a blank canvas, onto which you can pick and choose (or even write!) the plugins which you want for your application.
For instance, the core "Email::Store::Entity" plugin module addresses the idea of "people" in the email universe, allowing you to search for mails to or from particular people; (despite their changing names or email addresses) "Email::Store::Thread" interfaces "Email::Store" to "Mail::Thread" allowing you to navigate mails by their position in a mail thread; the planned non-core "Email::Store::Plucene" module plugs into the indexing process and stores information about emails in a Plucene search index for quick retrieval later, and so on.
<<lessSYNOPSIS
use Email::Store dbi:...;
This class is a subclass of Class::DBI and contains means for Email::Store-based programs to register what DSN they wish to use. It also provides for building database tables from schemas embedded in the DATA section of plug-in modules, using Class::DBI::DATA::Schema.
"Email::Store" is the ideal basis for any application which needs to deal with databases of email: archiving, searching, or even storing mail for implementing IMAP or POP3 servers.
"Email::Store" itself is a very lightweight framework, meaning it does not provide very much functionality itself; in effect, it is merely a Class::DBI interface to a database schema which is designed for storing email. Incidentally, if you dont know much about "Class::DBI", youre going to need to in order to get much out of this.
Despite its minimalist nature, "Email::Store" is incredibly powerful. Its power comes from its extensibility, through plugin modules and hooks which allow you to add new database tables and concepts to the system, and so access the mail store from a "different direction". In a sense, "Email::Store" is a blank canvas, onto which you can pick and choose (or even write!) the plugins which you want for your application.
For instance, the core "Email::Store::Entity" plugin module addresses the idea of "people" in the email universe, allowing you to search for mails to or from particular people; (despite their changing names or email addresses) "Email::Store::Thread" interfaces "Email::Store" to "Mail::Thread" allowing you to navigate mails by their position in a mail thread; the planned non-core "Email::Store::Plucene" module plugs into the indexing process and stores information about emails in a Plucene search index for quick retrieval later, and so on.
Download (0.028MB)
Added: 2006-10-03 License: Perl Artistic License Price:
1117 downloads
zeMail 1.0
zeMail is a minimalist webmail package written in Mason. more>>
zeMail is a minimalist webmail package written in Mason. It implements the basic features one would expect from an IMAP mail client, displaying folder and message contents, handling attachments and allowing you to move, mark and purge your messages.
zeMail package is written in plain HTML, and uses JavaScript only to reduce the click count, it will work perfectly with scripting disabled. Compared to the modern AJAX trend, this web mail package is designed to work everywhere.
Installation:
Download and unpack the tarball. Copy the directory lib/Zentus into your Perl inc. path (/usr/local/lib/perl/5.8.4 on Debian).
Copy the contents of mason/ into the desired subdirectory of your Apache htdocs directory or virtual host. Then add the following to your httpd.conf:
PerlModule Zentus::Mail::Connection
PerlModule Zentus::Mail::AttachmentHandler
PerlModule HTML::Mason::ApacheHandler
PerlModule Apache::Session::File
PerlModule Text::Autoformat
< Location / >
SetHandler perl-script
PerlHandler HTML::Mason::ApacheHandler
DirectoryIndex folder
< /Location >
< Location /attachment >
SetHandler perl-script
PerlHandler Zentus::Mail::AttachmentHandler
< /Location >
< LocationMatch "(/icons|/images|.ico|.html|.txt)" >
SetHandler default-handler
< /Location >
< LocationMatch "(autohandler|dhandler|.inc)" >
SetHandler None
< /Location >
This code segment can be added as-is if you intend to devote a VirtualHost to zeMail, otherwise prefix a directory name in the < Location > and < LocationMatch > tags.
Now install the necessary Perl modules from CPAN:
cpan -i HTML::Mason # or deb: libhtml-mason-perl
cpan -i Apache::Session # or deb: libapache-session-perl
cpan -i DB_File::Lock # or deb: libdb-file-lock-perl
cpan -i Text::Autoformat # or deb: libtext-autoformat-perl
cpan -i HTML::FormatText # or deb: libhtml-format-perl
cpan -i Net::IMAP::Simple # (needed really in name only,
# to be removed in next release)
You may have to create the temporary directory manually:
mkdir /tmp/zemail
chown www /tmp/zemail
Now restart your Apache and your are good to go.
Enhancements:
- Supports all basic forms of email, strips out MIME, displays attached images inline, and lets you download the rest.
<<lesszeMail package is written in plain HTML, and uses JavaScript only to reduce the click count, it will work perfectly with scripting disabled. Compared to the modern AJAX trend, this web mail package is designed to work everywhere.
Installation:
Download and unpack the tarball. Copy the directory lib/Zentus into your Perl inc. path (/usr/local/lib/perl/5.8.4 on Debian).
Copy the contents of mason/ into the desired subdirectory of your Apache htdocs directory or virtual host. Then add the following to your httpd.conf:
PerlModule Zentus::Mail::Connection
PerlModule Zentus::Mail::AttachmentHandler
PerlModule HTML::Mason::ApacheHandler
PerlModule Apache::Session::File
PerlModule Text::Autoformat
< Location / >
SetHandler perl-script
PerlHandler HTML::Mason::ApacheHandler
DirectoryIndex folder
< /Location >
< Location /attachment >
SetHandler perl-script
PerlHandler Zentus::Mail::AttachmentHandler
< /Location >
< LocationMatch "(/icons|/images|.ico|.html|.txt)" >
SetHandler default-handler
< /Location >
< LocationMatch "(autohandler|dhandler|.inc)" >
SetHandler None
< /Location >
This code segment can be added as-is if you intend to devote a VirtualHost to zeMail, otherwise prefix a directory name in the < Location > and < LocationMatch > tags.
Now install the necessary Perl modules from CPAN:
cpan -i HTML::Mason # or deb: libhtml-mason-perl
cpan -i Apache::Session # or deb: libapache-session-perl
cpan -i DB_File::Lock # or deb: libdb-file-lock-perl
cpan -i Text::Autoformat # or deb: libtext-autoformat-perl
cpan -i HTML::FormatText # or deb: libhtml-format-perl
cpan -i Net::IMAP::Simple # (needed really in name only,
# to be removed in next release)
You may have to create the temporary directory manually:
mkdir /tmp/zemail
chown www /tmp/zemail
Now restart your Apache and your are good to go.
Enhancements:
- Supports all basic forms of email, strips out MIME, displays attached images inline, and lets you download the rest.
Download (0.079MB)
Added: 2006-01-26 License: BSD License Price:
1366 downloads
Ofnibot 1.0
Ofnibot is a reincarnation of Kevin Lenzos Infobot in minimalist form. more>>
Ofnibot is a reincarnation of Kevin Lenzos Infobot in minimalist form. Kevin Lenzos Infobot program (http://www.infobot.org/) is an awesome IRC bot that is used on many IRC channels around the world.
Unfortunately, Infobot has become somewhat large in its old age. Since I maintain a number of IRC channels that require an information bot, my goal was to create an Infobot-compatible bot from the ground up. This bot is fast, secure, and modern.
The core function of the Infobot is to store a knowledge base of "factoids" or facts about things. The knowledge base can then be accessed and updated using common English phrases.
Ofnibot (Ofni = Info spelled backwards) is meant to provide that same core functionality without the bloat of the Infobot code. Ofnibot uses the modern POE::Component::IRC module to interface with IRC and, more importantly, it uses commands and files that are fully compatible with the original Infobot. The entire program comes in at just over 300 lines of Perl.
Because Ofnibot was programmed from the ground up and does not use any of the Infobot code, I cannot guarantee it behaves exactly the same when responding to users. It does, however, provide an exact subset of Infobot commands and can use the exact same database files as the Infobot. It can easily work as a drop-in replacement.
<<lessUnfortunately, Infobot has become somewhat large in its old age. Since I maintain a number of IRC channels that require an information bot, my goal was to create an Infobot-compatible bot from the ground up. This bot is fast, secure, and modern.
The core function of the Infobot is to store a knowledge base of "factoids" or facts about things. The knowledge base can then be accessed and updated using common English phrases.
Ofnibot (Ofni = Info spelled backwards) is meant to provide that same core functionality without the bloat of the Infobot code. Ofnibot uses the modern POE::Component::IRC module to interface with IRC and, more importantly, it uses commands and files that are fully compatible with the original Infobot. The entire program comes in at just over 300 lines of Perl.
Because Ofnibot was programmed from the ground up and does not use any of the Infobot code, I cannot guarantee it behaves exactly the same when responding to users. It does, however, provide an exact subset of Infobot commands and can use the exact same database files as the Infobot. It can easily work as a drop-in replacement.
Download (0.011MB)
Added: 2006-06-17 License: GPL (GNU General Public License) Price:
1225 downloads
Donzilla 0.9
Donzilla is a customized version of Mozilla App-Suite, created by HardwareHacks 2000. more>>
Donzilla is intended for a user that is looking for everything he or she could possibly need in one convenient package.
Donzilla project is definitely not reccomended to a minimalist user. For minimalist users, there is SillyDog701s Netscape Streamline Series.
Main features:
- ChatZilla
- Mozilla Calendar
- Adblock 0.5d2 Nightly, Build 39
- Googlebar for Mozilla
- CopyImage
- Checky 2.5
- Wmlbrowser 0.4.9
- BBCode 0.4
<<lessDonzilla project is definitely not reccomended to a minimalist user. For minimalist users, there is SillyDog701s Netscape Streamline Series.
Main features:
- ChatZilla
- Mozilla Calendar
- Adblock 0.5d2 Nightly, Build 39
- Googlebar for Mozilla
- CopyImage
- Checky 2.5
- Wmlbrowser 0.4.9
- BBCode 0.4
Download (12.6MB)
Added: 2005-12-20 License: GPL (GNU General Public License) Price:
1471 downloads
AntiCMS Content Management System 0.2.1
AntiCMS is a minimalist content management system for small and simple websites. more>>
AntiCMS is a minimalist content management system for small and simple websites. The main purpose of this system is to separate content, structure and layout.
Layout is defined using templates; content and structure are stored in XML file - database is not required. System is written in Python and released under the GPL.
Its still in early stage of development, so errors and unpredicted behaviour may occour. Currently a content editor is being developed, which will run on users computer and allow easy managent of content and structure of websites.
Enhancements:
- This release adds site configuration (it is now possible to change encodings, paths, and some other properties) and a new variable in the template engine.
<<lessLayout is defined using templates; content and structure are stored in XML file - database is not required. System is written in Python and released under the GPL.
Its still in early stage of development, so errors and unpredicted behaviour may occour. Currently a content editor is being developed, which will run on users computer and allow easy managent of content and structure of websites.
Enhancements:
- This release adds site configuration (it is now possible to change encodings, paths, and some other properties) and a new variable in the template engine.
Download (0.034MB)
Added: 2005-11-07 License: GPL (GNU General Public License) Price:
1446 downloads
AreaEdit 0.4.5
AreaEdit is a formVista compatible fork of the rapidly developing Xinha project. more>>
AreaEdit is a formVista compatible fork of the rapidly developing Xinha project. AreaEdit project is the code that is generated by the formVista FVML < htmleditor > tag during rendering.
Xinha itself is a fork of the original HTMLArea component created by Mihai Bazon and sponsored by Interactivetools. AreaEdit maintains the original HTMLArea (modified BSD) license and is free to use.
While it is designed to work within formVista without modification, AreaEdit does not requre formVista. It is a fully functional editor component supporting a number of plugins and can as easily be used as a standalone editor component for any PHP web application.
The primary difference between AreaEdit and Xinha is one of focus. The Xinha project aims to be a rapidly developing feature-filled editor with many plugins.
By contrast, AreaEdit takes a slower minimalists approach. It aims first and foremost to be functional and maintainable. The feature set we are focusing on is targeted squarely at the serious non-technical business user. Business users dont care about the nuances of HTML
and
<<lessXinha itself is a fork of the original HTMLArea component created by Mihai Bazon and sponsored by Interactivetools. AreaEdit maintains the original HTMLArea (modified BSD) license and is free to use.
While it is designed to work within formVista without modification, AreaEdit does not requre formVista. It is a fully functional editor component supporting a number of plugins and can as easily be used as a standalone editor component for any PHP web application.
The primary difference between AreaEdit and Xinha is one of focus. The Xinha project aims to be a rapidly developing feature-filled editor with many plugins.
By contrast, AreaEdit takes a slower minimalists approach. It aims first and foremost to be functional and maintainable. The feature set we are focusing on is targeted squarely at the serious non-technical business user. Business users dont care about the nuances of HTML
and
tags, they just want the editor to work as they would expect.
If your audience is primarly composed to developers or those familar with HTML, you should take a look at Xinha.
AreaEdit is known to work with MSIE 5.5 or later and any modern Gecko based browsers. (FireFox, Mozilla).
Enhancements:
- This release finally works around the intermittent MSIE "Operation Aborted" error that were seen in some installs.
- The documentation and examples have been updated.
Download (0.79MB)
Added: 2006-01-01 License: BSD License Price:
1391 downloads
Sparklines for Java 1.2
Sparklines are intense, simple, wordlike graphics. more>>
Sparklines are intense, simple, wordlike graphics.
Theres a PHP library for producing sparklines, and even a sparkline web service, but I wanted something I could use to generate sparklines in both Java and JSTL (and I thought it would be a fun project). (Its also worth checking out Whys minimalist python sparklines, which encode the image data directly in the HTML as a data: URI [this library allows you to encode the images as using either data: format or javascript: format (supported by IE) in JSTL])
JSTL examples
< %@ taglib uri="http://java.sun.com/jsp/jstl/core" prefix="c" % >
< %@ taglib prefix="spark" uri="http://www.representqueens.com/taglibs/spark" % >
< c:set var="test" value="5, 35, 22, 19, 16, 10, 4, 33, 9, 12, 27, 36, 22" / >
< img src="< spark:bar name="test" color="red" / >" / >
will produce:
(I think the default size might be a little large).
The "name" attribute specifies the key to find the data (Uses JspContext.findAttribute). It expects the value to be either a List , a Number[], or a String of comma separated int values. Its the only manditory attribute.
The other attributes are width, height, spacing, color, highColor, lastColor, output. You can replace "bar" with "line" to get a linegraph (note: highColor and lastColor are currently not supported for line graphs).
The color attributes can either be a color name (a field name from java.awt.Color), or a HTML hex color (e.g. #ff0000 for red).
Enhancements:
- This release properly URL encodes parameters for server generated sparklines.
- This fixes an issue when using hex specified image colors.
- The tag parameter "background" has been added as a workaround for IE6 PNG transparency.
<<lessTheres a PHP library for producing sparklines, and even a sparkline web service, but I wanted something I could use to generate sparklines in both Java and JSTL (and I thought it would be a fun project). (Its also worth checking out Whys minimalist python sparklines, which encode the image data directly in the HTML as a data: URI [this library allows you to encode the images as using either data: format or javascript: format (supported by IE) in JSTL])
JSTL examples
< %@ taglib uri="http://java.sun.com/jsp/jstl/core" prefix="c" % >
< %@ taglib prefix="spark" uri="http://www.representqueens.com/taglibs/spark" % >
< c:set var="test" value="5, 35, 22, 19, 16, 10, 4, 33, 9, 12, 27, 36, 22" / >
< img src="< spark:bar name="test" color="red" / >" / >
will produce:
(I think the default size might be a little large).
The "name" attribute specifies the key to find the data (Uses JspContext.findAttribute). It expects the value to be either a List , a Number[], or a String of comma separated int values. Its the only manditory attribute.
The other attributes are width, height, spacing, color, highColor, lastColor, output. You can replace "bar" with "line" to get a linegraph (note: highColor and lastColor are currently not supported for line graphs).
The color attributes can either be a color name (a field name from java.awt.Color), or a HTML hex color (e.g. #ff0000 for red).
Enhancements:
- This release properly URL encodes parameters for server generated sparklines.
- This fixes an issue when using hex specified image colors.
- The tag parameter "background" has been added as a workaround for IE6 PNG transparency.
Download (0.030MB)
Added: 2007-03-14 License: The Apache License 2.0 Price:
956 downloads
News Spotter 0.83
News Spotter is a desktop utility which fosters an addiction to current events. more>>
News Spotter is a desktop utility which fosters an addiction to current events. Is a rss reader which automatically monitors news feeds. .Most of the time, News Spotter sits quietly on the left or right side of your screen. But when a new headline is identified from one of its monitored web sites, News Spotter graphically displays the headline as a hyperlink. When you click on the headline, News Spotter opens the corresponding URL in your default browser.
Main features:
- minimalist user interface
- is very simple to use it and very functional
<<lessMain features:
- minimalist user interface
- is very simple to use it and very functional
Download (2.7MB)
Added: 2006-06-06 License: Freely Distributable Price:
1236 downloads
wmWeatherApp 0.0.3
wmWeatherApp is nothing more than a very simplistic weather dock app. more>>
wmWeatherApp is nothing more than a very simplistic weather dock app. There are several quite nice dockapps for this purpose, however they were all far too bloated for my needs therefore I created a very minimalist one.
This application simply grabs the image of the current weather (using your zipcode which you supply as a parameter to wmWeatherApp) and displays it as the background image of the dockapp.
You can left click on the dockapp and have it launch a web browser (which you can configure by setting the environment variable BROWSER) and show you the weather.
Quick usage instructions:
./configure && make && make install
wmWeatherApp -zip 61832 -delay 300
-zip specifies your zipcode
-delay specifies the update interval in seconds. 300 seconds is what I currently use.
The weather image is pulled from www.wunderground.com (which is the most reliable weather provider I have found). License is GPL.
<<lessThis application simply grabs the image of the current weather (using your zipcode which you supply as a parameter to wmWeatherApp) and displays it as the background image of the dockapp.
You can left click on the dockapp and have it launch a web browser (which you can configure by setting the environment variable BROWSER) and show you the weather.
Quick usage instructions:
./configure && make && make install
wmWeatherApp -zip 61832 -delay 300
-zip specifies your zipcode
-delay specifies the update interval in seconds. 300 seconds is what I currently use.
The weather image is pulled from www.wunderground.com (which is the most reliable weather provider I have found). License is GPL.
Download (0.31MB)
Added: 2006-10-26 License: GPL (GNU General Public License) Price:
1094 downloads
Secleted [ 0 ] software to compare
Copyright Notice:
Software piracy is theft, Using crack, password, serial numbers, registration codes, key generators is illegal and prevent future software development. The above minimalist search only lists software in full, demo and trial versions for free download. Download links are directly from our mirror sites or publisher sites, torrent files or links from rapidshare.com, yousendit.com or megaupload.com are not allowed
