Free application of ferrite flexible cable cores software for linux

SME Web Application Framework provides a Web application framework for small and medium-sized organizations.

SMEWebApp is a framework for constructing Web applications for SMEs (small and medium-sized enterprises, companies, institutions, and organizations). It is built on phpWebApp, and it is higher-level and more specific than phpWebApp.

It has some components that can be reused in any application (perhaps with small modifications), like hierarchical menus, user authentication, and user administration.

The aim of the project is to make Web application construction for SMEs easier than using VB.

Realtime Application Interface project allows applications with strict timing constraints to be run on Linux.
A real time system is able to guarantee the timing requirements of the processes under its control.
RTAI provides an API and the necessary kernel modifications to accommodate such requirements.
Enhancements:
- Improvements were made to netrpc.
- Context switching between hard and soft real-time, handling of TSC errors, and POSIX compatibility have been improved.
- There are numerous minor bugfixes.

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.

LAMP Application Server project is a combination of common open source tools that provides a unified system from which administrators, developers, and other parties can manage a large application cluster. The underlying platform is LAMP based.
Enhancements:
- Fixed vhost config to correctly handle index pages on static directory area
- Fixed a MySQL install bug. Table `domain_dns_config` is now MyISAM like the rest.

Application Standard Components Library (ASCL) comprises a set of reusable Ada packages. The focus is not on light-weight components but larger components such as a configuration manager and a CLI application environment which does all the argument parsing.

It also includes a build environment for Linux which can be updated and maintained independently of the actual source code. It supports the personal software process for Ada programming.

An open Quality of Service Architecture is an open architecture for the provisioning of Quality of Service related functionality into the Linux kernel.
The project features a flexible, portable and lightweight software architecture for supporting QoS related services on the top of a general-purpose operating system as Linux. The architecture is well founded on formal scheduling analysis and control theoretical results.
At the core of the software there is an adaptive Resource Reservation layer that is capable of dynamically adapting the CPU allocation for QoS aware applications based on its run-time requirements.
As it is highlighted by the AQuoSA architecture, the project is mainly composed of two components:
- the QoS Res module, for which you can browse online the kernel, application and internal APIs
- the QoS Mgr module, for which you can browse online the kernel, application and internal APIs
Enhancements:
- Some bug fixed

Adaptive Quality of Service Architecture (AQuoSA) is an open architecture for the provisioning of adaptive Quality of Service functionality into the Linux kernel. The project features a flexible, portable, lightweight and open architecture for supporting soft real-time applications with facilities related to timing guarantees and QoS, on the top of a general-purpose operating system as Linux.
At the core of the architecture there is an adaptive resource reservation layer that is capable of dynamically adapting the CPU allocation for QoS aware applications based on their run-time requirements.
Timing guarantees are provided through an in-kernel reservation based process scheduler, whose services are exposed to applications through a well-designed API.
A supervisor performs admission control, so that admitting into the system new applications with timing guarantees does not affect the timing guarantees of already admitted applications. Also, it takes care of guaranteeing appropriate security policies in the assignment of timing guarantees to users and user groups, as configured by the system administrator.
A feedback-based QoS control layer may be optionally used by applications who want to keep their timing guarantees by using a CPU allocation that is continuously adapted according to their actual needs. This leaverages the programmer, within certain limits, to hard-code any particular reservation amount within the application, because the best allocation is found out automatically at run-time. Also, this enhances the possibilities for the system to host additional QoS controlled applications. The available control algorithms are well founded on formal scheduling models and control theoretical results.
Enhancements:
- This release introduces a couple of flags useful when creating servers. If QOS_F_PERSISTENT is enabled, a server is allowed to exist beyond detach of the last task. If QOS_F_SOFT is enabled, a server tasks are scheduled by the Linux default scheduler/policy, when outside of the server reservation.
- Also, various stability issues in destroying servers have been fixed, also thanks to a new release of the generic scheduler patch for the Linux kernel (gs-2.2).

Prima::Application is root of widget objects hierarchy.

Prima::Application class serves as a hierarchy root for all objects with child-owner relationship. All toolkit objects, existing with non-null owner property, belong by their top-level parental relationship to Prima::Application object. There can be only one instance of Prima::Application class at a time.

SYNOPSIS

use Prima;
use Prima::Application;
or
use Prima qw(Application);

Prima::MainWindow-> create();

run Prima;

USAGE

Prima::Application class, and its only instance are treated specially throughout the toolkit. The object instance is contained in

$::application

scalar, defined in Prima.pm module. The application instance must be created whenever widget and window, or event loop functionality is desired. Usually

use Prima::Application;

code is enough, but $::application can also be assigned explicitly. The use syntax has advantage as more resistant to eventual changes in the toolkit design. It can also be used in conjunction with custom parameters hash, alike the general create() syntax:

use Prima::Application name => Test application, icon => $icon;

In addition to this functionality Prima::Application is also a wrapper to a set of system functions, not directly related to object classes. This functionality is generally explained in "API".