Free framework 3.5 sp1 software for linux

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.

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.

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.

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.

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.

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

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.