prior
Sponsored Links
Sponsored Links
Secleted [ 0 ] software to compare
Results 1 - 15 of about 122
cvs2svn 2.0.0
cvs2svn is a Python script that converts a CVS repository to a Subversion repository. more>>
cvs2svn is a Python script that converts a CVS repository to a Subversion repository. The project is designed for one-time conversions, not for repeated synchronizations between CVS and Subversion.
Enhancements:
- The conversion is now driven explicitly by the CVS dependency graph, giving a more robust conversion and fixing a few subtle bugs that existed in prior releases.
- A new --use-internal-co option has been added.
- It accelerates conversions significantly by avoiding having to use CVS or RCS to extract revision contents.
- Numerous other improvements to the quality of conversion, new conversion options, and bugfixes have been implemented.
<<lessEnhancements:
- The conversion is now driven explicitly by the CVS dependency graph, giving a more robust conversion and fixing a few subtle bugs that existed in prior releases.
- A new --use-internal-co option has been added.
- It accelerates conversions significantly by avoiding having to use CVS or RCS to extract revision contents.
- Numerous other improvements to the quality of conversion, new conversion options, and bugfixes have been implemented.
Download (0.33MB)
Added: 2007-08-22 License: GPL (GNU General Public License) Price:
514 downloads
Text::Indent 0.1
Text::Indent is a simple indentation of text shared among modules. more>>
Text::Indent is a simple indentation of text shared among modules.
SYNOPSIS
In your main program:
use Text::Indent;
my $indent = Text::Indent->new;
$indent->spaces(2);
In a module to produce indented output:
use Text::Indent;
my $indent = Text::Indent->instance;
$indent->increase;
print $indent->indent("this will be indented two spaces");
$indent->increase(2);
print $indent->indent("this will be indented six spaces");
$indent->decrease(3);
Text::Indent is designed for use in programs which need to produce output with multiple levels of indent when the source of the output comes from different modules that know nothing about each other.
For example take module A, whose output includes the indented output of module B. Module B can also produce output directly, so it falls to module B to know whether it should indent its output or not depending on its calling context.
Text::Indent allows programs and modules to cooperate to choose an appropriate indent level that is shared within the program context. In the above example, module A would increase the indent level prior to calling the output routines of module B. Module B would simply use the Text::Indent instance confident that if it were being called directly no indent would be applied but if module A was calling it then its output would be indented one level.
<<lessSYNOPSIS
In your main program:
use Text::Indent;
my $indent = Text::Indent->new;
$indent->spaces(2);
In a module to produce indented output:
use Text::Indent;
my $indent = Text::Indent->instance;
$indent->increase;
print $indent->indent("this will be indented two spaces");
$indent->increase(2);
print $indent->indent("this will be indented six spaces");
$indent->decrease(3);
Text::Indent is designed for use in programs which need to produce output with multiple levels of indent when the source of the output comes from different modules that know nothing about each other.
For example take module A, whose output includes the indented output of module B. Module B can also produce output directly, so it falls to module B to know whether it should indent its output or not depending on its calling context.
Text::Indent allows programs and modules to cooperate to choose an appropriate indent level that is shared within the program context. In the above example, module A would increase the indent level prior to calling the output routines of module B. Module B would simply use the Text::Indent instance confident that if it were being called directly no indent would be applied but if module A was calling it then its output would be indented one level.
Download (0.005MB)
Added: 2007-08-08 License: Perl Artistic License Price:
807 downloads
Java Parallel Processing Framework 1.0 Beta 1
Java Parallel Processing Framework is a set of tools and APIs to facilitate the parallelization of CPU intensive applications. more>>
Java Parallel Processing Framework is a set of tools and APIs to facilitate the parallelization of CPU intensive applications, and distribute their execution over a network of heterogenous nodes.
Java Parallel Processing Framework is intended to run in clusters and grids.
Main features:
- an API to delegate the processing of parallelized tasks to local and remote execution services
- a set of APIs and user interface tools to administrate and monitor execution services
- real-time adaptive load balancing capabilities
- scalability up to an arbitrary number of processing nodes
- support for failover and recovery
- limited intrusiveness for existing or legacy code
- a dynamic deployment mechanism, that enables the execution of new, or updated, code without having to deploy onto the grid
- fully documented APIs, administration guide and developer guide
- runs on any platform supporting Java 2 Platform Standard Edition 5.0 (J2SE 1.5)
Enhancements:
- JPPF is now licensed under the terms of the Apache License, Version 2.0. Starting from JPPF 1.0 beta1, all releases will be licensed under these terms.
- Prior versions will remain under the terms of the LGPL.
- For the first time, JPPF integrates seamlessly with J2EE. The JPPF Resource Adapter provides J2EE application servers with an access to native grid services.
- Numerous bug fixes, especially with regards to the distributed class loading mechanism.
<<lessJava Parallel Processing Framework is intended to run in clusters and grids.
Main features:
- an API to delegate the processing of parallelized tasks to local and remote execution services
- a set of APIs and user interface tools to administrate and monitor execution services
- real-time adaptive load balancing capabilities
- scalability up to an arbitrary number of processing nodes
- support for failover and recovery
- limited intrusiveness for existing or legacy code
- a dynamic deployment mechanism, that enables the execution of new, or updated, code without having to deploy onto the grid
- fully documented APIs, administration guide and developer guide
- runs on any platform supporting Java 2 Platform Standard Edition 5.0 (J2SE 1.5)
Enhancements:
- JPPF is now licensed under the terms of the Apache License, Version 2.0. Starting from JPPF 1.0 beta1, all releases will be licensed under these terms.
- Prior versions will remain under the terms of the LGPL.
- For the first time, JPPF integrates seamlessly with J2EE. The JPPF Resource Adapter provides J2EE application servers with an access to native grid services.
- Numerous bug fixes, especially with regards to the distributed class loading mechanism.
Download (7.8MB)
Added: 2007-07-31 License: The Apache License 2.0 Price:
816 downloads
Candidate Management for SugarCRM 0.7.1 Beta
Candidate Management for SugarCRM is a candidate management module created by HR (Human Resources) people for other HR people. more>>
Candidate Management for SugarCRM is a candidate management module created by HR (Human Resources) people for other HR people. This product is based on actual, day-to-day recruitment needs and captures information that is important for pooling and searching.
Novares full Candidate Management Module is a human resource recruitment solution for SugarCRM. Use it to prepare Job Requisitions, enter candidates, schedule interviews, attach resumes, track candidate history.
View the readme file for special installation instructions. You need to have SugarCRM already installed prior to installing this module.
<<lessNovares full Candidate Management Module is a human resource recruitment solution for SugarCRM. Use it to prepare Job Requisitions, enter candidates, schedule interviews, attach resumes, track candidate history.
View the readme file for special installation instructions. You need to have SugarCRM already installed prior to installing this module.
Download (0.74MB)
Added: 2007-07-27 License: Other/Proprietary License Price:
822 downloads
Pylon Application Platform 20070716
Pylon Application Platform is a free and open source platform for embedded applications. more>>
Pylon Application Platform is a free and open source platform for embedded applications.
Our mission:
- Our goal is to dominate the world.
- We consider Microsoft as our main competitor. The second our competitor is UAZ (Ulyanovsky Automobilny Zavod) which produces UAZ vehicles. That vehicle is just another way for user to be perfect.
- Pylon is designed by programmers and for programmers only.
- Pylons authors hate Java, Java applications, and Java programmers.
- Pylons authors like Apples creatures just a little bit.
- Pylons authors love Kubuntu.
- We decline any responsibility for any results of using Pylon.
- We do not recomend to use Pylon prior to version 0.2.0-alpha1 as a platform for Nuclear Power Plant control software.
- We do not recomend to use Pylon prior to version 0.5.0 as a platform for Automatic Washing Machine firmware.
- Pylon is a way to be perfect. Nothing more
Main features:
- Pylon is absolutely free either for commercial or for any other purpose.
- It is written in pure C and C++.
- It is for Linux only.
- It is a scriptable platform. That means that Pylon-based application will be scriptable. Pylon uses Forth as a scripting language.
- Pylon-based application is supposed to be a single thread application.
- Pylon provides a non-preemptive multitasking.
<<lessOur mission:
- Our goal is to dominate the world.
- We consider Microsoft as our main competitor. The second our competitor is UAZ (Ulyanovsky Automobilny Zavod) which produces UAZ vehicles. That vehicle is just another way for user to be perfect.
- Pylon is designed by programmers and for programmers only.
- Pylons authors hate Java, Java applications, and Java programmers.
- Pylons authors like Apples creatures just a little bit.
- Pylons authors love Kubuntu.
- We decline any responsibility for any results of using Pylon.
- We do not recomend to use Pylon prior to version 0.2.0-alpha1 as a platform for Nuclear Power Plant control software.
- We do not recomend to use Pylon prior to version 0.5.0 as a platform for Automatic Washing Machine firmware.
- Pylon is a way to be perfect. Nothing more
Main features:
- Pylon is absolutely free either for commercial or for any other purpose.
- It is written in pure C and C++.
- It is for Linux only.
- It is a scriptable platform. That means that Pylon-based application will be scriptable. Pylon uses Forth as a scripting language.
- Pylon-based application is supposed to be a single thread application.
- Pylon provides a non-preemptive multitasking.
Download (0.47MB)
Added: 2007-07-24 License: Public Domain Price:
827 downloads
Gladius DB 0.7.0
Gladius DB is a fast and efficient PHP flatfile database engine written in pure PHP. more>>
Gladius DB is a fast and efficient PHP flatfile database engine written in pure PHP; its SQL syntax is compatible with a subset of intermediate SQL92.
You will not need any specific extension to have it work, and it is bundled with an adoDB lite driver.
This project is licensed under the GNU General Public License, be sure to have read and understood it before using Gladius in your own software.
SQL Conformance
The formal name of the SQL standard is ISO/IEC 9075 "Database Language SQL". The version this document refers to is ISO/IEC 9075:2003, or simply SQL:2003. The versions prior to that were SQL:1999 and SQL-92. Each version supersedes the previous one, so claims of conformance to earlier versions have no official standing.
Starting with SQL:1999, the SQL standard defines a large set of individual features rather than the three levels (Entry, Intermediate and Full) declared in SQL-92. A large subset of these features represents the "Core" (mandatory) features, SQL implementation must supply in order to claim conformance. The rest of the features are purely optional.
In the following sections, we provide a list of all SQL:2003 features with an indication of whether it is supported by Gladius DB; every feature consists of an unique identifier and a name. Feature identifiers containing a hyphen are subfeatures. If a particular subfeature is not supported, the main feature is listed as partly supported. Comments are provided where necessary.
Version restrictions:
- performance slowdown with a huge number of records
- no storage gain for binary fields (for example, numbers)
- non-validating SQL parser (an SQL query that works with Gladius may not be syntactically correct)
- all strings are considered binary and should always be Unicode safe
- no specific collation or character set support
- cannot SELECT calculated or immediate values
- CHAR VARYING, DOUBLE PRECISION and INTERVAL data types (specified in the SQL92 standard) are not recognized
- no specific date/time functions (as of Gladius DB v0.6.2)
<<lessYou will not need any specific extension to have it work, and it is bundled with an adoDB lite driver.
This project is licensed under the GNU General Public License, be sure to have read and understood it before using Gladius in your own software.
SQL Conformance
The formal name of the SQL standard is ISO/IEC 9075 "Database Language SQL". The version this document refers to is ISO/IEC 9075:2003, or simply SQL:2003. The versions prior to that were SQL:1999 and SQL-92. Each version supersedes the previous one, so claims of conformance to earlier versions have no official standing.
Starting with SQL:1999, the SQL standard defines a large set of individual features rather than the three levels (Entry, Intermediate and Full) declared in SQL-92. A large subset of these features represents the "Core" (mandatory) features, SQL implementation must supply in order to claim conformance. The rest of the features are purely optional.
In the following sections, we provide a list of all SQL:2003 features with an indication of whether it is supported by Gladius DB; every feature consists of an unique identifier and a name. Feature identifiers containing a hyphen are subfeatures. If a particular subfeature is not supported, the main feature is listed as partly supported. Comments are provided where necessary.
Version restrictions:
- performance slowdown with a huge number of records
- no storage gain for binary fields (for example, numbers)
- non-validating SQL parser (an SQL query that works with Gladius may not be syntactically correct)
- all strings are considered binary and should always be Unicode safe
- no specific collation or character set support
- cannot SELECT calculated or immediate values
- CHAR VARYING, DOUBLE PRECISION and INTERVAL data types (specified in the SQL92 standard) are not recognized
- no specific date/time functions (as of Gladius DB v0.6.2)
Download (0.056MB)
Added: 2007-07-16 License: GPL (GNU General Public License) Price:
516 downloads
Cobra 0.97
Cobra HTML Toolkit is an open source library that provides a pure Java HTML parser and a renderer. more>>
Cobra HTML Toolkit is an open source library that provides a pure Java HTML parser and a renderer. Cobra is intended to support HTML 4, Javascript and CSS 2. The parser can be used independently of the Cobra renderer.
The Warrior browser is an application that uses the Cobra toolkit to parse and render HTML.
Test Program:
Cobra comes with a test program that shows how a URL is rendered and its HTML DOM as a tree representation. It can be run as follows:
set CLASSPATH=cobra.jar;js.jar
java -Xbootclasspath/p:dom.jar org.xamjwg.html.test.TestEntry
Note that the -Xbootclasspath parameter is only necessary with JDKs prior to 1.5.
Parser Usage:
The recommended way to use the Cobra parser is via the DocumentBuilderImpl class, as follows:
import org.xamjwg.html.parser.*;
import org.xamjwg.html.test.*;
import org.xamjwg.html.*;
import org.w3c.dom.*;
...
HtmlParserContext context = new SimpleHtmlParserContext();
DocumentBuilderImpl dbi = new DocumentBuilderImpl(context);
Document document = dbi.parse(new InputSourceImpl(inputStream));
Rendering Engine Usage:
A Swing component, HtmlPanel, can render a HTML document, as follows:
import org.xamjwg.html.parser.*;
import org.xamjwg.html.test.*;
import org.xamjwg.html.gui.*;
import org.xamjwg.html.*;
import org.w3c.dom.*;
...
HtmlPanel panel = new HtmlPanel();
// This panel should be added to a JFrame or
// another Swing component.
HtmlParserContext context = new SimpleHtmlParserContext();
HtmlRendererContext rcontext = new SimpleHtmlRendererContext(panel);
// Note that document builder should receive both contexts.
DocumentBuilderImpl dbi = new DocumentBuilderImpl(context, rcontext);
Document document = dbi.parse(new InputSourceImpl(inputStream));
// Now set document in panel.
panel.setDocument(document);
<<lessThe Warrior browser is an application that uses the Cobra toolkit to parse and render HTML.
Test Program:
Cobra comes with a test program that shows how a URL is rendered and its HTML DOM as a tree representation. It can be run as follows:
set CLASSPATH=cobra.jar;js.jar
java -Xbootclasspath/p:dom.jar org.xamjwg.html.test.TestEntry
Note that the -Xbootclasspath parameter is only necessary with JDKs prior to 1.5.
Parser Usage:
The recommended way to use the Cobra parser is via the DocumentBuilderImpl class, as follows:
import org.xamjwg.html.parser.*;
import org.xamjwg.html.test.*;
import org.xamjwg.html.*;
import org.w3c.dom.*;
...
HtmlParserContext context = new SimpleHtmlParserContext();
DocumentBuilderImpl dbi = new DocumentBuilderImpl(context);
Document document = dbi.parse(new InputSourceImpl(inputStream));
Rendering Engine Usage:
A Swing component, HtmlPanel, can render a HTML document, as follows:
import org.xamjwg.html.parser.*;
import org.xamjwg.html.test.*;
import org.xamjwg.html.gui.*;
import org.xamjwg.html.*;
import org.w3c.dom.*;
...
HtmlPanel panel = new HtmlPanel();
// This panel should be added to a JFrame or
// another Swing component.
HtmlParserContext context = new SimpleHtmlParserContext();
HtmlRendererContext rcontext = new SimpleHtmlRendererContext(panel);
// Note that document builder should receive both contexts.
DocumentBuilderImpl dbi = new DocumentBuilderImpl(context, rcontext);
Document document = dbi.parse(new InputSourceImpl(inputStream));
// Now set document in panel.
panel.setDocument(document);
Download (1.8MB)
Added: 2007-07-15 License: LGPL (GNU Lesser General Public License) Price:
833 downloads
libsynaptics 0.14.6c
libsynaptics is a library intended to support all upcoming driver versions of the Xorg Synaptics Touch Pad Driver. more>>
libsynaptics is a library intended to support all upcoming driver versions of the Xorg Synaptics Touch Pad Driver. Programs that want to access the touch pad should make use of this library and will thereby not interfere with each other.
Available parameters can be read and written and the version of the installed driver can be determined. It is still not clear whether libsynaptics will be distributed seperately or within the driver package (which seems to be the better solution to me!).
Enhancements:
A new release of libsynaptics and ksynaptics is now available. This fixes several bugs and breaks backward compatibility with earlier libsynaptics versions. This is why you will have to update both libsynaptics and ksynaptics or keep your current versions.
- new: new mouse button icons (svg based)
- fixed: syndock would run in smart mode even if disabled in ksynaptics
- new: rewrote libsynaptics 0.14.6c, an bug-fixing rewrite
- fixed: the nasty syndock crash on logout should be fixed
IMPORTANT:
- Install libsynaptics 0.14.c first!
- Since the latest libsynaptics breaks backwards compatibility, you cannot use any libsynaptics prior to 0.14.c!
<<lessAvailable parameters can be read and written and the version of the installed driver can be determined. It is still not clear whether libsynaptics will be distributed seperately or within the driver package (which seems to be the better solution to me!).
Enhancements:
A new release of libsynaptics and ksynaptics is now available. This fixes several bugs and breaks backward compatibility with earlier libsynaptics versions. This is why you will have to update both libsynaptics and ksynaptics or keep your current versions.
- new: new mouse button icons (svg based)
- fixed: syndock would run in smart mode even if disabled in ksynaptics
- new: rewrote libsynaptics 0.14.6c, an bug-fixing rewrite
- fixed: the nasty syndock crash on logout should be fixed
IMPORTANT:
- Install libsynaptics 0.14.c first!
- Since the latest libsynaptics breaks backwards compatibility, you cannot use any libsynaptics prior to 0.14.c!
Download (0.30MB)
Added: 2007-07-02 License: GPL (GNU General Public License) Price:
844 downloads
auto-build 1.2.0
auto-build is a Perl module that can run automated, unattended software build processes. more>>
auto-build is a Perl module that can run automated, unattended software build processes.
SYNOPSIS
# auto-build [OPTION]...
Run build using latest code currently in source control
# auto-build --config /etc/auto-build.d/auto-build.conf
Run build using code committed prior to 12:30 on Dec 12th 2004
# auto-build --timestamp 12:30:00 Dec 12th 2004
--config /etc/auto-build.d/auto-build.conf
SUMMARY
auto-build is the command used to execute the Test-AutoBuild software build automation framework. It is intended to execute a single iteration of the build engine and then quit with its exit status providing an indication of the build success / fail status (see the EXIT STATUS section later in this manual page). To perform a continous automated build this command would be launched on a frequent basis from cron. Locking will ensure that two instances do not execute concurrently, so it can safely be triggered every 5 minutes.
OPTIONS
The following command line options are valid:
--config=FILE
Specify an alternative path to the configuration file for the build process. If ommitted, will default to looking for the file $HOME/auto-build.conf. The configuration data is loaded by the Config::Record module, so refer to that modules manual page for details of permitted syntax. The file will also be pre-processed by the Template module allowing dynamic generation of complex configuration files
--log4perl=FILE
Specify an alternative file containing configuration settings for the Log::Log4perl logging system. If ommitted, log4perl settings will be loaded from the master autobuild configuration file.
--timestamp=DATE
Specify the timestamp to use when checking code out of the source control repositories. For repository modules supporting timestamps it is guarenteed that the code checked out will be the latest version not newer than this timestamp. If ommitted, the timestamp will default to the current timestamp. The argument can be either an plain integer specifying number of seconds since the epoch, or any of the text representations handled by the Date::Manip module
today
1st thursday in June 1992
05/10/93
12:30 Dec 12th 1880
8:00pm december tenth
--verbose
Increase the verbosity of warning messages and errors. This will ensure that if the builder unexpectedly crashes, a complete stack trace will be dumped along will full arguments.It will also cause the post-processed configuration file to be dumped.
--help
Display a summary of the command line help options
<<lessSYNOPSIS
# auto-build [OPTION]...
Run build using latest code currently in source control
# auto-build --config /etc/auto-build.d/auto-build.conf
Run build using code committed prior to 12:30 on Dec 12th 2004
# auto-build --timestamp 12:30:00 Dec 12th 2004
--config /etc/auto-build.d/auto-build.conf
SUMMARY
auto-build is the command used to execute the Test-AutoBuild software build automation framework. It is intended to execute a single iteration of the build engine and then quit with its exit status providing an indication of the build success / fail status (see the EXIT STATUS section later in this manual page). To perform a continous automated build this command would be launched on a frequent basis from cron. Locking will ensure that two instances do not execute concurrently, so it can safely be triggered every 5 minutes.
OPTIONS
The following command line options are valid:
--config=FILE
Specify an alternative path to the configuration file for the build process. If ommitted, will default to looking for the file $HOME/auto-build.conf. The configuration data is loaded by the Config::Record module, so refer to that modules manual page for details of permitted syntax. The file will also be pre-processed by the Template module allowing dynamic generation of complex configuration files
--log4perl=FILE
Specify an alternative file containing configuration settings for the Log::Log4perl logging system. If ommitted, log4perl settings will be loaded from the master autobuild configuration file.
--timestamp=DATE
Specify the timestamp to use when checking code out of the source control repositories. For repository modules supporting timestamps it is guarenteed that the code checked out will be the latest version not newer than this timestamp. If ommitted, the timestamp will default to the current timestamp. The argument can be either an plain integer specifying number of seconds since the epoch, or any of the text representations handled by the Date::Manip module
today
1st thursday in June 1992
05/10/93
12:30 Dec 12th 1880
8:00pm december tenth
--verbose
Increase the verbosity of warning messages and errors. This will ensure that if the builder unexpectedly crashes, a complete stack trace will be dumped along will full arguments.It will also cause the post-processed configuration file to be dumped.
--help
Display a summary of the command line help options
Download (0.20MB)
Added: 2007-06-16 License: Perl Artistic License Price:
860 downloads
Log::Log4perl::Layout::XMLLayout 0.03
Log::Log4perl::Layout::XMLLayout is an XML Layout. more>>
Log::Log4perl::Layout::XMLLayout is an XML Layout.
SYNOPSIS
use Log::Log4perl::Layout::XMLLayout;
my $app = Log::Log4perl::Appender->new("Log::Log4perl::Appender::File");
my $logger = Log::Log4perl->get_logger("abc.def.ghi");
$logger->add_appender($app);
# Log with LocationInfo
my $layout = Log::Log4perl::Layout::XMLLayout->new(
{ LocationInfo => { value => TRUE },
Encoding => { value => iso8859-1}});
$app->layout($layout);
$logger->debug("Thats the message");
########################### Log4perl Config File entries for XMLLayout
log4perl.appender.A1.layout = Log::Log4perl::Layout::XMLLayout
log4perl.appender.A1.layout.LocationInfo = TRUE
log4perl.appender.A1.layout.Encoding =iso8859-1
###########################
Creates a XML layout according to http://jakarta.apache.org/log4j/docs/api/org/apache/log4j/xml/XMLLayout.html
Logfiles generated based on XMLLayout can be viewed and filtered within the log4j chainsaw graphical user interface (see example section below). chainsaw is part of the JAVA based log4j package and can be downloaded from http://jakarta.apache.org/
The output of the XMLLayout consists of a series of log4j:event elements as defined in the log4j.dtd. It does not output a complete well-formed XML file. The output is designed to be included as an external entity in a separate file to form a correct XML file.
For example, if abc is the name of the file where the XMLLayout ouput goes, then a well-formed XML file would be:
< ?xml version="1.0" ? >
< !DOCTYPE log4j:eventSet SYSTEM "log4j.dtd" [< !ENTITY data SYSTEM "abc" >] >
< log4j:eventSet version="1.2" xmlns:log4j="http://jakarta.apache.org/log4j/" > &data; < /log4j:eventSet >
This approach enforces the independence of the XMLLayout and the appender where it is embedded.
The version attribute helps components to correctly intrepret output generated by XMLLayout. The value of this attribute should be "1.1" for output generated by log4j versions prior to log4j 1.2 (final release) and "1.2" for relase 1.2 and later.
<<lessSYNOPSIS
use Log::Log4perl::Layout::XMLLayout;
my $app = Log::Log4perl::Appender->new("Log::Log4perl::Appender::File");
my $logger = Log::Log4perl->get_logger("abc.def.ghi");
$logger->add_appender($app);
# Log with LocationInfo
my $layout = Log::Log4perl::Layout::XMLLayout->new(
{ LocationInfo => { value => TRUE },
Encoding => { value => iso8859-1}});
$app->layout($layout);
$logger->debug("Thats the message");
########################### Log4perl Config File entries for XMLLayout
log4perl.appender.A1.layout = Log::Log4perl::Layout::XMLLayout
log4perl.appender.A1.layout.LocationInfo = TRUE
log4perl.appender.A1.layout.Encoding =iso8859-1
###########################
Creates a XML layout according to http://jakarta.apache.org/log4j/docs/api/org/apache/log4j/xml/XMLLayout.html
Logfiles generated based on XMLLayout can be viewed and filtered within the log4j chainsaw graphical user interface (see example section below). chainsaw is part of the JAVA based log4j package and can be downloaded from http://jakarta.apache.org/
The output of the XMLLayout consists of a series of log4j:event elements as defined in the log4j.dtd. It does not output a complete well-formed XML file. The output is designed to be included as an external entity in a separate file to form a correct XML file.
For example, if abc is the name of the file where the XMLLayout ouput goes, then a well-formed XML file would be:
< ?xml version="1.0" ? >
< !DOCTYPE log4j:eventSet SYSTEM "log4j.dtd" [< !ENTITY data SYSTEM "abc" >] >
< log4j:eventSet version="1.2" xmlns:log4j="http://jakarta.apache.org/log4j/" > &data; < /log4j:eventSet >
This approach enforces the independence of the XMLLayout and the appender where it is embedded.
The version attribute helps components to correctly intrepret output generated by XMLLayout. The value of this attribute should be "1.1" for output generated by log4j versions prior to log4j 1.2 (final release) and "1.2" for relase 1.2 and later.
Download (0.006MB)
Added: 2007-06-08 License: Perl Artistic License Price:
869 downloads
IOC::Proxy::Interfaces 0.29
IOC::Proxy::Interfaces is a IOC::Proxy subclasss to proxy objects with a given interface. more>>
IOC::Proxy::Interfaces is a IOC::Proxy subclasss to proxy objects with a given interface.
SYNOPSIS
use IOC::Proxy::Interfaces;
my $proxy_server = IOC::Proxy->new({
interface => AnInterface,
# ... add other config values here
});
$proxy_server->wrap($object);
# our $object is now proxied, but only the
# methods which are part of the interface
# will work, all others will throw exceptions
$object->method_in_interface(); # works as normal
$object->method_not_in_interface(); # will thrown an exception
This is a subclass of IOC::Proxy which allows for the partial proxing of an object. It will only proxy the methods of a given interface, all other methods will throw a IOC::MethodNotFound exception. This could be used to (in a very weird way) emulate the concept of upcasting in Java, it is also somewhat like the idea of using interfaces with Dynamic Proxies in Java as well (see the article link in "SEE ALSO").
This proxy can be useful if you need to have an object strictly conform to a particular interface in a particular situation. The interface class is also pushed onto the proxies @ISA so that it will respond to UNIVERSAL::isa($object, Interface) correctly. Keep in mind that there is no need for the object being proxied to have the interface in its @ISA prior to being proxied. The proxy is dynamic and only requires that the object conform to the interface when it is being wraped but the proxy object.
<<lessSYNOPSIS
use IOC::Proxy::Interfaces;
my $proxy_server = IOC::Proxy->new({
interface => AnInterface,
# ... add other config values here
});
$proxy_server->wrap($object);
# our $object is now proxied, but only the
# methods which are part of the interface
# will work, all others will throw exceptions
$object->method_in_interface(); # works as normal
$object->method_not_in_interface(); # will thrown an exception
This is a subclass of IOC::Proxy which allows for the partial proxing of an object. It will only proxy the methods of a given interface, all other methods will throw a IOC::MethodNotFound exception. This could be used to (in a very weird way) emulate the concept of upcasting in Java, it is also somewhat like the idea of using interfaces with Dynamic Proxies in Java as well (see the article link in "SEE ALSO").
This proxy can be useful if you need to have an object strictly conform to a particular interface in a particular situation. The interface class is also pushed onto the proxies @ISA so that it will respond to UNIVERSAL::isa($object, Interface) correctly. Keep in mind that there is no need for the object being proxied to have the interface in its @ISA prior to being proxied. The proxy is dynamic and only requires that the object conform to the interface when it is being wraped but the proxy object.
Download (0.048MB)
Added: 2007-06-07 License: Perl Artistic License Price:
869 downloads
IOC 0.29
IOC Perl module is a lightweight IOC (Inversion of Control) framework. more>>
IOC Perl module is a lightweight IOC (Inversion of Control) framework.
SYNOPSIS
use IOC;
my $container = IOC::Container->new();
$container->register(IOC::Service::Literal->new(log_file => "logfile.log"));
$container->register(IOC::Service->new(logger => sub {
my $c = shift;
return FileLogger->new($c->get(log_file));
}));
$container->register(IOC::Service->new(application => sub {
my $c = shift;
my $app = Application->new();
$app->logger($c->get(logger));
return $app;
}));
$container->get(application)->run();
This module provide a lightweight IOC or Inversion of Control framework. Inversion of Control, sometimes called Dependency Injection, is a component management style which aims to clean up component configuration and provide a cleaner, more flexible means of configuring a large application.
What is Inversion of Control
My favorite 10 second description of Inversion of Control is, "Inversion of Control is the inverse of Garbage Collection". This comes from Howard Lewis Ship, the creator of the HiveMind IoC Java framework. His point is that the way garbage collection takes care of the destruction of your objects, Inversion of Control takes care of the creation of your objects. However, this does not really explain why IoC is useful, for that you will have to read on.
You may be familiar with a similar style of component management called a Service Locator, in which a global Service Locator object holds instances of components which can be retrieved by key. The common style is to create and configure each component instance and add it into the Service Locator. The main drawback to this approach is the aligning of the dependencies of each component prior to inserting the component into the Service Locator. If your dependency requirements change, then your initialization code must change to accommodate. This can get quite complex when you need to re-arrange initialization ordering and such. The Inversion of Control style alleviates this problem by taking a different approach.
With Inversion of Control, you configure a set of individual Service objects, which know how to initialize their particular components. If these components have dependencies, the will resolve them through the IOC framework itself. This results in a loosely coupled configuration which places no expectation upon initialization order. If your dependency requirements change, you need only adjust your Services initialization routine, the ordering will adapt on its own.
<<lessSYNOPSIS
use IOC;
my $container = IOC::Container->new();
$container->register(IOC::Service::Literal->new(log_file => "logfile.log"));
$container->register(IOC::Service->new(logger => sub {
my $c = shift;
return FileLogger->new($c->get(log_file));
}));
$container->register(IOC::Service->new(application => sub {
my $c = shift;
my $app = Application->new();
$app->logger($c->get(logger));
return $app;
}));
$container->get(application)->run();
This module provide a lightweight IOC or Inversion of Control framework. Inversion of Control, sometimes called Dependency Injection, is a component management style which aims to clean up component configuration and provide a cleaner, more flexible means of configuring a large application.
What is Inversion of Control
My favorite 10 second description of Inversion of Control is, "Inversion of Control is the inverse of Garbage Collection". This comes from Howard Lewis Ship, the creator of the HiveMind IoC Java framework. His point is that the way garbage collection takes care of the destruction of your objects, Inversion of Control takes care of the creation of your objects. However, this does not really explain why IoC is useful, for that you will have to read on.
You may be familiar with a similar style of component management called a Service Locator, in which a global Service Locator object holds instances of components which can be retrieved by key. The common style is to create and configure each component instance and add it into the Service Locator. The main drawback to this approach is the aligning of the dependencies of each component prior to inserting the component into the Service Locator. If your dependency requirements change, then your initialization code must change to accommodate. This can get quite complex when you need to re-arrange initialization ordering and such. The Inversion of Control style alleviates this problem by taking a different approach.
With Inversion of Control, you configure a set of individual Service objects, which know how to initialize their particular components. If these components have dependencies, the will resolve them through the IOC framework itself. This results in a loosely coupled configuration which places no expectation upon initialization order. If your dependency requirements change, you need only adjust your Services initialization routine, the ordering will adapt on its own.
Download (0.048MB)
Added: 2007-06-06 License: Perl Artistic License Price:
871 downloads
PythonCAD DS1-R36
PythonCAD is a CAD package written, surprisingly enough, in Python. more>>
PythonCAD is a CAD package written, surprisingly enough, in Python. PythonCAD project aims to produce a scriptable, open-source, easy to use CAD package for Linux, the various flavors of BSD Unix, commercial Unix, and other platforms to which someone who is interested ports the program. Work began on PythonCAD in July, 2002, and the first public release was on December 21, 2002.
The twenty-fifth release of PythonCAD was made available May 26, 2005. This release fixes several compatibility issues found when running PythonCAD on PyGTK releseses prior than 2.4. Also, numerous changes to the event handling code have been applied to make the code better conform to GTK+/PyGTK conventions. Additionally a number of bug fixes and code improvements appear in this release as well.
Between the sixteenth and seventeenth releases of the program, the code was moved around internally to better cooperate with other Python programs. Unfortunately the Cocoa front-end code has suffered since then due to lack of maintainence and is currently not functional. Releases after the seventeenth release have attempted to improve the situation, but to no avail. A developer or team of developers running Mac OS X is needed to bring the Cocoa code into a usable state.
<<lessThe twenty-fifth release of PythonCAD was made available May 26, 2005. This release fixes several compatibility issues found when running PythonCAD on PyGTK releseses prior than 2.4. Also, numerous changes to the event handling code have been applied to make the code better conform to GTK+/PyGTK conventions. Additionally a number of bug fixes and code improvements appear in this release as well.
Between the sixteenth and seventeenth releases of the program, the code was moved around internally to better cooperate with other Python programs. Unfortunately the Cocoa front-end code has suffered since then due to lack of maintainence and is currently not functional. Releases after the seventeenth release have attempted to improve the situation, but to no avail. A developer or team of developers running Mac OS X is needed to bring the Cocoa code into a usable state.
Download (0.42MB)
Added: 2007-06-05 License: GPL (GNU General Public License) Price:
878 downloads
ObjStore 1.59
ObjStore is a Perl extension for ObjectStore OODBMS. more>>
ObjStore is a Perl extension for ObjectStore OODBMS.
SYNOPSIS
Like perl? Sick of SQL? Ready to try something new? This extension implements something like a relational database management system, except that s/SQL/Perl/ig.
ObjectStore is the market leader in object-oriented databases http://www.odi.com (NASDAQ: ODIS). They use a unique Cache-Forward Architecture to make persistent data available in literally the most efficient manner possible.
Prior to this joining of forces
ObjectStore was too radical a design decision for many applications
Perl5 did not have a simple way of storing complex data persistently
Now there is an easy way to build database applications (especially if you are concerned about preserving your ideals of encapsulation).
<<lessSYNOPSIS
Like perl? Sick of SQL? Ready to try something new? This extension implements something like a relational database management system, except that s/SQL/Perl/ig.
ObjectStore is the market leader in object-oriented databases http://www.odi.com (NASDAQ: ODIS). They use a unique Cache-Forward Architecture to make persistent data available in literally the most efficient manner possible.
Prior to this joining of forces
ObjectStore was too radical a design decision for many applications
Perl5 did not have a simple way of storing complex data persistently
Now there is an easy way to build database applications (especially if you are concerned about preserving your ideals of encapsulation).
Download (0.16MB)
Added: 2007-05-15 License: Perl Artistic License Price:
900 downloads
Zero Touch Linux Server 1.0
Zero Touch Linux Server is the easiest way to setup your back office infrastructure. more>>
Zero Touch Linux Server is the easiest way to setup your back office infrastructure. If you need mail server, file server or domain controller - ZTL is perfect for you. ZTL is now a FREE product that brings together the stability of Linux and the security of Trustix or 100% binary compatibility of CentOS with a simple web-based interface.
ZTL allows you to perform administrative tasks without any special knowledge. If you need to setup a server for your office, and do not have prior experience in doing it - ZTL is for you.
Main features:
- remote administration of servers
- three levels of access
- simple and comfortable web-based interface
- one click server upgrade
- based on powerful and secure operating system: Trustix Secure Linux
- based on free and 100% binary compatible operating system: CentOS Enterprise-class Linux Distribution
- ability to install and configure Web, Mail, DNS, Domain Controler, File Server, Printer Server as well as Database, DHCP, Proxy servers, Firewall servers
Three levels of access:
Admin Level:
- manage server configuration
- install/uninstall and automatically configure appliances
- create and manage websites/domains
- use PHP plugins: SquirrelMail, phpMyAdmin
Domain Level:
- create and manage websites/mailboxes/users
- add/manage shared folders
- manage MySQL/PostgreSQL databases
- add/manage users
- manage DNS records, Apache webserver virtual host settings
- use PHP plugins: SquirrelMail, phpMyAdmin
- remove/get system information
End User (Mail / FTP user) Level:
- webmail interface
- manage your mail settings
- use PHP plugins: SquirrelMail, phpMyAdmin
- change password
- upload download files via web
<<lessZTL allows you to perform administrative tasks without any special knowledge. If you need to setup a server for your office, and do not have prior experience in doing it - ZTL is for you.
Main features:
- remote administration of servers
- three levels of access
- simple and comfortable web-based interface
- one click server upgrade
- based on powerful and secure operating system: Trustix Secure Linux
- based on free and 100% binary compatible operating system: CentOS Enterprise-class Linux Distribution
- ability to install and configure Web, Mail, DNS, Domain Controler, File Server, Printer Server as well as Database, DHCP, Proxy servers, Firewall servers
Three levels of access:
Admin Level:
- manage server configuration
- install/uninstall and automatically configure appliances
- create and manage websites/domains
- use PHP plugins: SquirrelMail, phpMyAdmin
Domain Level:
- create and manage websites/mailboxes/users
- add/manage shared folders
- manage MySQL/PostgreSQL databases
- add/manage users
- manage DNS records, Apache webserver virtual host settings
- use PHP plugins: SquirrelMail, phpMyAdmin
- remove/get system information
End User (Mail / FTP user) Level:
- webmail interface
- manage your mail settings
- use PHP plugins: SquirrelMail, phpMyAdmin
- change password
- upload download files via web
Download (450MB)
Added: 2007-05-03 License: Freeware Price:
915 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 prior 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
