Free framework software for linux

SMS Framework is an Objective C framework for decoding SMS messages in PDU format to objects.
It is easily usable in Cocoa and GNUstep environments, and it reduces developer responsibility for decoding messages to extracting the raw messages from the phone.
The XCode project file contains three targets: one system wide framework, one framework to include in applications, and a small application for testing the framework.
Enhancements:
- Fixes two small bugs in decoding that seem to affect international users.
- The bugs became apparent after OS X 10.4.5 appeared.

SA Web Framework project is a complete PHP application framework, based on the Front Controller Pattern.
SA stands for SkyApp? and is the framework which we developed and which we are using here at Skyweb.
SA is open source and released under LGPL license which means you can use it for free.
SA relies heavily on PEAR which gives us access to some nice features like mime mail handling, independent database abstraction layer, destructors, database session storing and many more.
SA was developed and tested using PHP 4.4.0.
Enhancements:
- The whole application stack has been rewritten in order to take advantage of the PHP5 object model.
- Some new classes and interfaces were introduced and the existing ones were completely rewritten.
- A new Page handling concept was implemented.
- The default page class now extends Smarty.

ROMA wants to change the way to do Java Applications. Its a Meta-Framework designed to build cross frameworks applications in very short time.
ROMA wants to glue the best of Java tools and frameworks together. ROMA doesnt want to reinvent the wheel or another brand new Web Framework, but just use the existent products with very low effort for the developer.
Main features:
- Roma its totally based on POJO (Plain Old Java Objects)
- True Object Oriented vision in all aspects: from the model to the view and to the repository/database
- Encourage the use of the Domain Driven Model (DDD) approach: lets think to the Domain: the other things are secondary Aspects
- It works with Conventions? ala Ruby On Rails: much less code to write and maintain and more uniformity in projects
- Applications are fully portable across frameworks since the application is developed using POJOs. For example you can switch between JDO and EJB3 PersistenceAspect without changing code unless you use directly the aspect implementation (see below)
- Allow to makes things dirty: you can use directly the target framework taking the full advantage of the implementation power
- You can use the already developed Modules (CRUD, User&Profiles, etc.) and extend their if you need
- The skill requested to build application can be lower than required for modern Java Web Applications: minor cost of development
- Roma is based on Spring Framework as IoC container, but you can use another one if you want.

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.

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.

Locale::Framework is a Perl module for internationalization.

SYNOPSIS

use Locale::Framework;
use Locale::Framework::SQL;

Locale::Framework::init(new Locale::Framework::SQL(
DSN => "dbi:Pg:dbname=zclass;host=localhost",
DBUSER => "test",
DBPASS => "testpass",
[TABLE => "testtrans"]));

print _T("This is a test");

Locale::Framework::language("nl_NL");

print _T("This is a test");
Alternative interface (using wxLocale backend as an example), which does exactly the same. There is no local object scope, theres only a global class (or program that is) scope. OO interface is only for conveniance.
use Locale::Framework;
use Locale::Framework::wxLocale;

my $LOC=new Locale::Framework;

$LOC->init(new Locale::Framework::wxLocale("./locale","test"));

print _T("This is a test");
$LOC->language("nl_NL");
print _T("This is a test");

ABSTRACT

This module provides simple string based internationalization support. It exports a _T function that can be used for all text that need displayed. It can work with different backends, e.g. SQL or file based backends. The backend defaults to Locale::Framework::Dumb, which doesnt translate at all.

Expresso Framework provides an architectural framework.
Expresso Framework is an open standards-based J2EE architectural framework that allows the developer to concentrate on application logic.
It is a library of extensible Java Server application framework components for creating database-driven Web applications based on open standards. Expresso integrates with Apache Jakarta Struts, which emphasizes presentation and application configuration, and bringing a powerful tag library to Expresso.
Expresso adds capabilities for security, robust object-relational mapping, background job handling and scheduling, self-tests, logging integration, automated table manipulation, database connection pooling, email connectivity, event notification, error handling, caching, internationalization, XML automation, testing, registration objects, configuration management, workflow, automatic database maintenance, and a JSP tag library.
Enhancements:
- Move password hash to UserInfo interface and its implementers: password hash no longer in User.java facade, but rather in UserInfo.java interface and its implementers. This allows more flexibility in handling external authentication.
Contributed By: Larry Hamel
- Velocity support for view rendering: Velocity can now be used to render the view. See EDG for details.
Contributed By: David Lloyd
- RunSQL Can Display Table Definitions: Enter the table name in the query section of RunSQL and it will now display the current definition of the underlying database table. Experimental
Contributed By: Michael Rimov
- RunSQL Executes Updates: RunSQL can now execute updates methods as well as select. This allows you to issue ALTER TABLE statements straight through the (secured) web interface. Experimental
Contributed By: Michael Rimov
- Initial Maven integration: Currently has been tested with the site:generate target and the corresponding compile, unittest, etc reports. Not yet used for building distributions. Experimental
Contributed By: Michael Rimov
- RequestRegistry automatically sets data context and security parameters: All calls to setDataContext() will no longer be necessary in client code. This info is propagated using ThreadLocal variables and the "Registry" pattern as described by Martin Fowler. Security parameters (i.e., requesting UID) are also propagated to RowSecuredDBObject, but for the sake of backwards compatibility, they are not propagated to SecuredDBObject. CheckLogin does this work. However, this functionality is also available in a servlet filter, RequestRegistryFilter. If you choose to use RequestRegistryFilter, you could do away with CheckLogin calls from the controller. We would use RequestRegistryFilter everywhere, but legacy installations have various URL paths, each of which requires filtering.
Contributed By: Michael Rimov
- Customizable per-instance UserInfo: Theres a new constructor in User that takes a UserInfo parameter. It allows special behavior for certain users.
Contributed By: Michael Rimov
- New Method: DataObject.setFieldsWithDefaults(): Populates all null fields in the object with default values as specified by the data objects metadata. The behavior mirrors that of DefaultAutoElement.
Contributed By: Michael Rimov.
- revise login bean CurrentLogin to be overridable: revise login bean CurrentLogin to be overridable, as a class handler in expresso-config.xml
Contributed By: Larry Hamel
- Added delimiter attribute to IfMemeberOfGroup tag: If a the delimiter is specified, the groupname will be split on the delimiter. The user will be search for any of the named groups (a logical OR is performed).
Contributed By: Mike Traum
- DataField.isChanged() works after update() and add(): Add method so that DBObject.update() and DBObject.add() can indicate when to cache the current field value as the original value for purposes of isChanged() comparison. Previously, isChanged() was working for DBObject.retrieve() only.
Contributed By: Larry Hamel
- AllowedHtmlPlusURLFilter: AllowedHtmlPlusURLFilter offers the recognition of a limited subset of HTML to be used within an input field. the subset has been chosen to offer some basic formatting without risking Cross site scripting (XSS) dangers.
Contributed By: Larry Hamel
- Struts Validator Integration: Expresso can now use Struts Validator for validating input forms. Rules are defined in validation.xml and validator-rules.xml. See Validating user input in EDG for more details
Contributed By: Raul Davidovich
- new class - com.jcorporate.expresso.core.controller.TilesController: Expresso aware implementation of the org.apache.struts.tiles.Controller interface. This allows for manipulation of theControllerResponse for a particular tile before it is displayed, independantly of the State currently being processed. Developers should extend this class and code the execute() method.
Contributed By: Malcolm Wise
- Various JoinedDataObject enhancements/fixes: You can now specify which fields to retrieve from each dataobject in the join. This list can also include expressions such as SUM(). Added custom WHERE clause facility. Aliases can be used in the custom WHERE clause and these will be translated when the WHERE clause is built. Fixed generation of ON clause when joining tables with a compound key. Provided setConnection() method to facilitate transactioning.
Contributed By: Malcolm Wise
- Stored Procedure support: Now DBObjectos have built in support for database stored procedures
Contributed By: Yves Henri Amaizo