Free application data software for linux

Curses::Application provides the Curses Application Framework.

Curses::Application attempts to relieve the programmer of having to deal directly with Curses at all. Based upon Curses::Widgets and Curses::Forms, all one should have to do is define the application forms and contents in the DATA block of a script. Curses::Application will take care of the rest.

This module follows many of the conventions established by the Curses::Widgets and Curses::Forms modules, being built upon that framework. One area of special note, however, is the declaration of forms used within the application.

Curses::Application differentiates between forms and form definitions. A form is an instance of any particular form definition. Keeping that line of separation simplifies the development of MDI (Multiple Document Interface) applications.
Form definitions can be provided in two ways: as a list of definitions in the main::DATA block, or individually by using the addFormDef method. The former would normally be the simplest way to do so.

At the end of your script, declare a DATA block using Perls __DATA__ token. In that DATA block place a hash declaration (%forms) which contains a key/value pair for each form definition. The key being the name of the definition, and the value being a hash reference to the form declarations (see the Curses::Forms pod for directives available to that module). The only extra key that should be in each forms hash reference should be a TYPE directive, which would point to a module name relative to the base Curses::Forms class. If you omit this key, then it will be assumed that the form is a Curses::Forms object, or some custom derivative as specified in ALTPATH.

The Horde Application Framework is written in PHP, and provides the common tools a Web application requires: classes for dealing with preferences, compression, browser detection, connection tracking, MIME, and more.
The Horde Framework does not provide any significant end user functionality and it provides a base for other applications and tools for developers. You will probably want to install some of the available Horde applications, such as IMP (a webmail client), or Kronolith (a calendar).
Enhancements:
- The Oracle session handler has been rewritten. vTimezone support for iCalendar data and ORG support for vCard data have been added.
- The Samba and Cyrus SQL authentication drivers have been improved.
- Automatic Web root detection and signature dimming have been improved.
- Compatibility of generated ZIP files has been improved.
- Validation of some email distribution lists has been fixed.
- Many small fixes and improvements have been made.
- Brazilian Portuguese, Catalan, Dutch, French, German, Portuguese, and Traditional Chinese translations have been updated.

Bundle::Application::Magic is a a bundle to install CGI::Application::Magic plus all related prerequisites.

SYNOPSIS

perl -MCPAN -e install Bundle::Application::Magic

CONTENTS

HTML::Tagset - used by HTML::Parser
HTML::Parser - used by HTML::FillInForm and HTML::TableTiler
HTML::TableTiler - used by HTML::MagicTemplate
HTML::FillInForm - used by HTML::MagicTemplate
Class::constr - used by Template::Magic::Zone
Class::props - used by Template::Magic::Zone
Object::props - used by Template::Magic::Zone
Object::groups - used by CGI::Application::Magic
Template::Magic - the Template::Magic distribution
Data::FormValidator - used by CGI::Application::CheckRM
CGI::Application::Plus - used by CGI::Applicatio::Magic

This bundle gathers together the CGI::Application::Magic and all the related prerequisites.
Note: A Bundle is a module that simply defines a collection of other modules. It is used by the CPAN module to automate the fetching, building and installing of modules from the CPAN ftp archive sites.

php.MVC implements the Model-View-Controller design pattern, and encourages application design based on the Model 2 paradigm. This design model allows the Web page or other contents (View) to be mostly separated from the internal application code (Controller/Model), making it easier for designers and programmers to focus on their respective areas of expertise.
The framework provides a single entry point Controller. The Controller is responsible for allocating HTTP requests to the appropriate Action handler (Model) based on configuration mappings.
The Model contains the business logic for the application. The Controller then forwards the request to the appropriate View component, which is usually implemented using a combination of HTML with PHP tags in the form of templates. The resulting contents are returned to the client browser, or via another protocol such as SMTP.
php.MVC is a PHP port of Jakarta Struts. It currently supports many features of Struts, including declarative application configuration via the XML digester. For example, mappings from the various Action business logic components to appropriate results pages can be specified declaratively in the XML configuration file.
Main features:
- Free OpenSource software: This gives users full control of the software, and the able to modify the source code to suit specific needs.
- Security: php.MVC applications have only one entry point (per application). This makes it easy to protect sensitive application code and data.
- Flexible Installation: Individual php.MVC applications can be installed outside of the main php.MVC library directory tree.
- Multi-applications: There is no limit to the number of applications per php.MVC installation.
- Object Oriented design (OOD). The php.MVC framework is based on OOD principles, making it more extendable and maintainable.
- Database integration: The php.MVC framework ships with the Pear::DB Database Abstraction Layer, and a driver for the MySQL relational database manager (RDBM) is provided.
- Action Chaining: php.MVC allows for passing control to other Actions. This makes it easy to process a sequence of Actions (business logic classes) and static resources (pages).
- XML configuration: php.MVC uses declarative application configurations using Extensible Markup Language (XML) files. Each application has its own XML configuration file.
- MVC Model 2 design: php.MVC implements the Model-View-Controller (MVC) Model 2 design pattern. The Model 2 paradigm allows the separation of the application presentation from the business logic, making it easier for designers and programmers to focus on their respective areas of expertise.
- Form button mapping: php.MVC implements the LookupDispatchAction class to enable HTML form buttons to be mapped to particular business logic methods. For example, a form submit button called "Add to Cart" could be mapped to an Action class method called MyCartAction->addToCart(...).
- Message Resources: php.MVC provides a PropertyMessageResources class that handles messages in text string properties files with parametric replacement. This can provide Locale-sensitive messages for internationalized applications.
- The php.MVC framework is based on Jakarta Struts application framework design. Struts has proven to be reliable, extendable and well supported.
Enhancements:
- This development release adds bugfixes and enhancements to the framework, a compressed performance version for use in more demanding hosting environments, and an example application to demonstrate the use of both versions.

Seagull is an OO PHP framework with the core modules licensed under BSD, and has the following design goals:
- independence of data, logic & presentation layers
- extensible component architecture
- reduction of repetitive programming tasks
- simplifying data access
- comprehensive error handling
- action request workflow
- simplified form handling
- component reuse
- authentication management
- integration with PEAR libraries
- PHP coding standards
- platform/PHP version/browser independence
- self-generating documentation
- quality end user docs
There are some default modules that come with the framework, these handle tasks related to:
- user/group management
- content management
- document management
- category management
- messaging
- navigation

Sdictionary is a cross-platform dictionary project uses own Sdict dictionary format. Sdictionary includes Sdict, the main program and two simple applications: Jotter and Data.
Unlike ptkdic or gtkdic no MySQL needed, so you can work with dictionary files directly. Currently it is known to work under Unix, Win32 and Symbian OS.
Main features:
- Open Source, .dct format is also open and described in documentation
- Unicode, all words and articles are stored in utf8
- Two index levels: short and full
- Using compression
- Tools to convert from text file to .dct and vice versa
- Simple Web dictionary included into package
- C library framework
- Perl API (Sdict.pm module)
- Simple Jotter and Data applications

SOAP::Data is a Perl class that provides the means by which to explicitly manipulate and control all aspects of the way in which Perl data gets expressed as SOAP data entities.

The SOAP::Data class provides the means by which to explicitly manipulate and control all aspects of the way in which Perl data gets expressed as SOAP data entities. Most of the methods are accessors, which like those in SOAP::Lite are designed to return the current value if no new one is passed, while returning the object reference otherwise (allowing for chained method calls). Note that most accessors (except value) accept a new value for the data object as a second argument.

METHODS

new(optional key/value pairs)
$obj = SOAP::Data->new(name => idx, value => 5);

This is the class constructor. Almost all of the attributes related to the class may be passed to the constructor as key/value pairs. This method isnt often used directly because SOAP::Data objects are generally created for temporary use. It is available for those situations that require it.

name(new name, optional value)
$obj->name(index);

Gets or sets the current value of the name, as the object regards it. The name is what the serializer will use for the tag when generating the XML for this object. It is what will become the accessor for the data element. Optionally, the objects value may be updated if passed as a second argument.

type(new type, optional value)
$obj->type(int);

Gets or sets the type associated with the current value in the object. This is useful for those cases where the SOAP::Data object is used to explicitly specify the type of data that would otherwise be interpreted as a different type completely (such as perceiving the string 123 as an integer, instead). Allows the setting of the objects value, if passed as a second argument to the method.

uri(new uri, optional value)
$obj->uri(http://www.perl.com/SOAP);

Gets or sets the URI that will be used as the namespace for the resulting XML entity, if one is desired. This doesnt set the label for the namespace. If one isnt provided by means of the prefix method, one is generated automatically when needed. Also allows the setting of the objects value, if passed as a second argument to the method.

prefix(new prefix, optional value)
$obj->prefix(perl);

Provides the prefix, or label, for use when associating the data object with a specific namespace. Also allows the setting of the objects value, if passed as a second argument to the method.

attr(hash reference of attributes, optional value)
$obj->attr({ attr1 => value });

Allows for the setting of arbitrary attributes on the data object. Keep in mind the requirement that any attributes not natively known to SOAP must be namespace-qualified. Also allows the setting of the objects value, if passed as a second argument to the method.

value(new value)
$obj->value(10);

Fetches the current value encapsulated by the object, or explicitly sets it.
The last four methods are convenience shortcuts for the attributes that SOAP itself supports. Each also permits inclusion of a new value, as an optional second argument.

actor(new actor, optional value)
$obj->actor($new_actor_name);

Gets or sets the value of the actor attribute; useful only when the object generates an entity for the message header.

mustUnderstand(boolean, optional value)
$obj->mustUnderstand(0);

Manipulates the mustUnderstand attribute, which tells the SOAP processor whether it is required to understand the entity in question.

encodingStyle(new encoding URN, optional value)
$obj->encodingStyle($soap_11_encoding);

This method is most likely to be used in places outside the header creation. Sets encodingStyle, which specifies an encoding that differs from the one that would otherwise be defaulted to.

root(boolean, optional value)
$obj->root(1);

When the application must explicitly specify which data element is to be regarded as the root element for the sake of generating the object model, this method provides the access to the root attribute.

SnapLogic project is an Open Source solution that transforms data into services using the standard technologies of the Web.

The problem of getting data from one place to another is universal. The Internet has solved that problem for documents, but integrating the underlying data remains a serious challenge.

SnapLogic builds integration and transformation services into the server infrastructure so that data contained in databases and applications can be integrated just like Web servers are added to the Internet.

SnapLogic takes the idea of an Enterprise data service and extends it to the Web.