Free framework 3.5 software for linux

Config::Framework is a Perl module with handy one-stop shopping for (most) of your configuration file needs.

SYNOPSIS

#create a new object, load two configuration files and decrypt the passwords. my $Object = new Config::Framework( Files => [ApplicationCfg.xml,UserCfg.xml], GetSecure => 1 ) || die $Config::Framework::errstr;

#change some data in one of the loaded configs $Object->{UserCfg}->{backgroundColor} = #00CCFF;

#write that change back to the file you loaded it from $Object->WriteConfig(configNamespace => "UserCfg") || die $Object->{errstr};

#Define a new configuration namespace %{ $Object->{newConfig} } = ( configNamespace => "newConfig", protectNamespace => 1, Version => 1, #arbitrary data keys follow backgroundColor => #006699, getRecords => 10, followLinks => 1, someThing => "in a bag" );

#Write your new configuration data out to an encrypted file #under the applications ApplicationFramework directory $Object->WriteConfig( configNamespace => "newConfig", Encrypt => 1, Crypt => "Rijndael", Key => "l33tp4sw3rd" File => "$Object->{FrameworkDir}/newConfig.xml" ) || die $Object->{errstr};

At long last I have decided to re-write the documentation for Config::Framework, in a manner which should be comprehensible by people other than myself. I would like to offer my sincerest appologies to anyone who tried to comprehend the sprawling stream-of-consiousness rant that was the previous documentation. Im sorry, I wasnt trying to make you insane. Now on with the show.

Ok so what is Config::Framework? Its a handy module for dealing with situations where you need your program to be able to load external data from a file that controls how your program operates. Im talking about configuration files here. So what do you do in a situation like that? Well you figure out a format to store your configuration parameters in, then write routines to read that format and put it some sort of meaningful data structure, and to write data from the data structure back out to the file.

Wouldnt it be nice if someone defined a standard config file format so that you wouldnt need to write your own parser? Well in the end, all a config file really is, is an arbitrary data structure expressed in in ascii. A standard way of serializing data structures in ascii you say? That sounds a bit like XML! Well the Data::DumpXML module will serialize perl data structures into XML and restore them for you, and you could certainly dump that to a file easily enough.
Ok getting to the point. The main thing that Config::Framework does for you is to define a standard data structure (or at least some standard guidelines for your data structure) and then front-ends Data::DumpXML so that you can arbitrarily dump and restore these data structures to files.

While were at it, Config::Framework aspires to be your one-stop-shop for config-type-stuff, by helping you stay organized in the way you handle external configuration data.

Salto Framework is a framework based on Ajax, Struts and J2EE technologies. Salto Framework provides graphical components such as datatables, treeviews and listboxes, and allows you to refresh only some parts on the screen. Thanks to the framework you dont have to write any javascript or to know anything about Ajax mechanism.

EmanonPHP Framework is a framework developed in PHP which uses a .NET-like convention for calling classes.

Amanith Framework is a Crossplatform & Opensource C++ Vector Graphic Framework.
Amanith gives to developers a complete and reliable set of classes to work with geometric elements (lines, curves, paths, meshes, and so on); it provides many powerful modelling operators (like cut, join, flatten and so on) and, at the same time, the fastest rendering layer totally built on top of OpenGL.
Some other useful classes included in Amanith complete the framework with: fonts and pixelmaps support, hierarchycal animations, fast and robust tesselation, bitmap to vector tracing, mathematics and calculus functions, matrices, distance and intersection queries.
Main features:
Open Sourced!
- Open source has made Amanith possible, so we wanna Amanith to be open source too.
- This mean that Amanith source code is fully available for everyone.
Cross Platform
- Same source tree can be compiled without modifications under multiple targets.
- Linux, Win32, Mac, FreeBSD, NetBSD, OpenBSD, Solaris, IRIX, AIX are only few of them.
Modular
- All the framework is heavily based on a light plug-in system.
- This make fast and easy to include or esclude everything you want.
Standards adherence
- The Amanith philosophy is to support many open standards as possible.
- Png, Jpeg, Svg, Xml, OpenGl, Ansi c++, and many others.

Azuki Framework project is a Java application framework designed to resolve various problems in the software development lifecycle. These goals are achieved by splitting the software conception into two main stages: creation of independent components and definition of component dependencies (weaving).

The latter is performed with a graphical tool named "the weaver". By representing component interactions using different perspectives, the weaver provides a straightforward way to analyze an applications architecture, allowing deep and easy customization of its behavior.

Whats New in This Release:

azuki-ant
(ADD) Copy $beanproject/tools into $dist/tools directory when deploying
bean.
(ADD) Additional sources files could be specified into checkbuildXXX
macros.

azuki-common
(FIX) Missing characters into StringUtil.splitQuote().
(ADD) SQL_MAX_ROWS global variable for sql query limitation.
(ADD) SQL utility class.
(ADD) Possibility to enable/disable filters on document and text fields.

azuki-framework
(FIX) New method to retrieve framework version.

azuki-weaver
(FIX) Dont show Definition menu entry in pointcut popup menu.
(FIX) Enable status was not displayed correctly into schemas.
(FIX) Check if bean instance is duplicated before renaming.
(FIX) Automatically set a new label when pasting a bean instance.

dist
(FIX) Do not start azuki shell server by default (kernel.xml).
(FIX) Invalid commons-codec library name in CLASSPATH.
(FIX) Set up JNDI and SOAP implementation in shell script .sh and .bat.
(ADD) Create directory $dist/tools.

bean-apportal
(FIX) Display framework version.
(FIX) Bean indentifier retrieval doesnt take care of root context.

bean-gwt
(DEL) Removed, will be included from future 1.1 branch releases.

bean-injection
(FIX) Add some comments.
(FIX) Include arrays in method parameters conversion.
(FIX) Include primitive types in method parameters conversion.

bean-logger
(FIX) Take care to not close the System.err stream when using the
java.util.logging API.
(FIX) Move SQL sources into tools directory.

bean-requesthandler
(FIX) Use the servlet context path for set up the base URI.
(FIX) Throws exception when trying to bind an already binded URI.

bean-shell
(FIX) Null pointer while searching bean metadata in TCP request processing.
(FIX) Move C program sources into tools directory.

Clover.ETL is a Java based ETL framework which can be used to transform structured data. While using JAVA technology it allows for platform independence.
Clover framework can be used standalone as an application run from command line or can be embedded into Your application. Clover.ETL is released under LGPL License.
Clover.ETL is used by many individual developers and several companies, which embeds it into their solutions.
Enhancements:
- The internal transformation language has been improved.
- All reader and writer components support the same set of parameters (dataPolicy, skipFirstLine, skipRows, numRecords, etc.).
- Several new transformation components have been added.

ProM Import Framework project allows you to extract process enactment event logs from a set of information systems.
These can be exported in the MXML format, which is the standard event log data format for Process Mining analysis techniques.
Process Mining is a family of a-posteriori analysis techniques to extract abstract information from process enactment logs. More in-depth information about the are of process mining is available at processmining.org.
Installation:
- Decompress and extract the provided *.tar.gz archive.
- This will create a folder ProMimport, containing all files necessary.
- Start the application by running the provided shell script start.sh.
- The import filter plugins delivered with your installation package are located in the Plugins folder inside the ProMimport directory.
- Load the plugins (which are packaged in *.jar files) that you want to use from within the running app. For that, use Load filter plugin.. from the Filters menu.
- 3rd party plugins, or plugins developed by you, can be added to the application in exactly the same manner.
- Once imported, filters are automatically added to the applications filter cache, and zre re-loaded on every successive startup. Further, all filter and application configuration data is transparently made persistent by the application.
- Thus, after importing all filter plugins necessary, you can safely delete the Plugins folder.
Enhancements:
- This is the initial release of the ProM framework under the new open source CPL license.
- Installers / disk images are provided for Windows and Mac OS X, while the provided source archive is also executable on all platforms supporting Java 5.0.
- Notice that this release depends on a Java runtime environment of version 1.5 / 5.0 or later.
- Prior JRE releases may yield unexpected errors.