Seagull PHP Framework

This article may not meet the general notability guideline. Please help to establish notability by adding reliable, secondary sources about the topic. If notability cannot be established, the article is likely to be merged, redirected, or deleted. (February 2010)

This article includes a list of references, related reading or external links, but its sources remain unclear because it lacks inline citations. Please improve this article by introducing more precise citations where appropriate. (August 2008)

Seagull PHP Framework
Stable release	0.6.7 / February 23, 2010; 17 day(s) ago (2010-02-23)
Operating system	Cross-platform
Type	Content Management Framework
License	BSD
Website	seagullproject.org

Seagull PHP Framework (Seagull) is an OOP PHP software framework for building web, command line and GUI applications. Seagull uses Model-view-controller design pattern. Many popular PHP applications are integrated within the project, as are various templating engines, PEAR libs, testing tools and managed library code.

1 Features
2 Modularity
3 Security
- 3.1 Data Validation
- 3.2 Authentication and Authorisation
4 Consistency
5 See also
6 External links

Features

Seagull offers the following key features:

PHP 4/5 compatible
compact core framework with complete modules in package
Model-view-controller pattern
performance conscious design^{[citation needed]}
multiple input and output formats
integrated object-relational mapper for rapid application development
loosely coupled components, use template engine of your choice, output to multiple devices or CLI
caching
localization. Translated into more than 21 world languages.
integrated PEAR libraries

Modularity

Seagull is an OOP application with an emphasis on modularity. The framework itself consists of a set of base classes organised according to the MVC design pattern that take care of permissions, authentication, sessions, i/o and database abstraction layer. Each generalised area of functionality comes in the form of a module.

Most task-specific functionality comes from libraries, quite often from PEAR, that can be independently updated when upgrades/improvements are available

Each object in the application (Member, Group, Property, Document, Article, etc) is represented as an entity, developers are provided with tools to quickly prototype entities so that skeleton classes are created and updated automatically

Security

Data Validation

All input data to the application is filtered and validated before any processing takes place. Filters appropriate to the input mechanism are invoked before subsequent validation tests are run. In the case of HTTP input, all request data is first stripped of javascript and leading/trailing whitespace.

Authentication and Authorisation

Seagull uses standard PHP sessions which propagate persistence of user data using cookies by default. Both database and file-based persistence are supported. The PHP engine automatically detects whether the client returns session cookies, if not the session is propagated in the URL. Anti session-hijacking measures are in place to ensure the user session can not be compromised. Seagull works identically whether or not end users have cookies enabled in their browsers. Any module in the application can be set to require authentication by setting the 'requiresAuth' flag to true on a per-screen basis. Once users are authenticated, fine grained permissions can be controlled by testing for role membership.

Consistency

Quality Control

All contributor features and bugfixes are submitted as patches which are subject to peer review and if deemed valid, applied by the project maintainer. A large part of the codebase is covered by unit and web tests.

Coding Standards

All the code in Seagull follows the consistent style set out in the coding standards document included in the root of each distribution. The standard follows PEAR coding standards very closely which is essentially a reiteration of the K & R guidelines from the original C Programming Language (1978)