Warning: this is development version of the upcoming Prado 4.

Prado PHP Framework

PRADO is a component-based and event-driven programming framework for developing Web applications in PHP 5. PRADO stands for PHP Rapid Application Development Object-oriented.


API Documentation

The complete API documentation can be found at http://pradosoft.github.io/docs/manual/

Prado uses ApiGen (http://www.apigen.org) to generate its API documentation. An ApiGen configuration file is providen, to generate the documentation just execute ./vendor/bin/apigen generate --config=.apigen.yaml The documentation will be generated in the build/docs/ directory.

Install

The best way to install Prado is through composer.

Just create a composer.json file for your project:

{
    "require": {
        "pradosoft/prado": "~4.0"
    }
}

Then you can run these two commands to install it:

$ curl -s http://getcomposer.org/installer | php
$ php composer.phar install

or simply run composer install if you have have already installed the composer globally.

Then you can include the autoloader, and you will have access to the library classes:

<?php
require 'vendor/autoload.php';

Demo Apps

Several different example prado applications are provided in the https://github.com/pradosoft/prado4-demos repository. You can see these applications running here: http://www.pradoframework.net/site/demos/ . When you create your own prado application you do NOT need these folders.

Testing

Prado uses phpunit (https://phpunit.de/) for unit testing and Selenium (http://www.seleniumhq.org/) for functional testing. A phpunit configuration file is providen, to run the tests just execute ./vendor/bin/phpunit --testsuite unit to run unit tests and ./vendor/bin/phpunit --testsuite functional to run functional tests.

Test results will be saved in in the build/tests/ directory.

Contributing

In the spirit of free software, everyone is encouraged to help improve this project.

Here are some ways you can contribute:

• by using prerelease versions
• by reporting bugs
• by writing specifications
• by writing code (no patch is too small: fix typos, add comments, clean up inconsistent whitespace)
• by refactoring code
• by resolving issues
• by reviewing patches

Starting point:

• Fork the repo
• Clone your repo
• Make your changes
• Write tests for your changes to ensure that later changes to prado won't break your code.
• Submit your pull request