diff options
| author | xue <> | 2006-01-18 03:30:52 +0000 |
|---|---|---|
| committer | xue <> | 2006-01-18 03:30:52 +0000 |
| commit | 9cc191d67ccd6f283f2245e01d47e7a6e3acff4c (patch) | |
| tree | 762911bba7bb4147de1ba65493c3a327c1291732 | |
| parent | c95e5b62084b49ae7b51e5b6848327e82ac15c87 (diff) | |
| -rw-r--r-- | index.html | 128 |
1 files changed, 128 insertions, 0 deletions
@@ -0,0 +1,128 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
+<head>
+<title>PRADO Framework for PHP 5</title>
+<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
+</head>
+
+<body>
+<h1>PRADO Framework for PHP 5 </h1>
+<p>Version 3.0a, January 18, 2006<br>
+Copyright© 2004-2006 by <a href="http://www.pradosoft.com/">PradoSoft</a><br>
+All Rights Reserved.
+
+<p>PRADO is a component-based and event-driven framework for Web application
+ development in PHP 5. </p>
+<p>Components following the PRADO protocol are highly configurable and reusable.
+ Properties defining the basic features of a component can be configured in specifications,
+ templates or code. New components can be developed by either inheriting an existing
+ component class or composing several components together. The work of using
+ a component amounts to placing the component tag on the page template, configuring
+ component properties, and writing handler functions to respond to component
+ events.</p>
+<p>PRADO shares many similarities with ASP.NET and other RAD tools for Windows
+ GUI development, such as Borland Delphi. In particular, it supports event-driven
+ programming, viewstate maintenance, javascript, template, form validations, theme/skin,
+ etc.</p>
+<h2>Requirements</h2>
+<p>The sole requirement for PRADO is PHP 5.0.4 or higher. It has been tested
+with Apache 2.0 on both Windows XP and RedHat Linux.</p>
+<h2>Installation</h2>
+<ul>
+ <li> Unpack the distribution file using "unzip" command on Linux or
+ "winzip" program on Windows.</li>
+ <li> Copy all the files and directories under the unpacked "prado"
+ directory to the DocumentRoot of the Web server (or a subdirectory of that).</li>
+ <li> Browse the URL, http://<Web-server-address>/requirements/index.php, to see
+ if your Web server configuration satisfies the requirement for using PRADO.</li>
+ <li> The directory "framework" contains the core code of PRADO.</li>
+ <li>The directory "docs/manual" contains the PRADO API documentation
+ in HTML format.</li>
+</ul>
+<h2>Included Demos</h2>
+<ul>
+ <li><a href="demos/quickstart/index.php">Prado QuickStart Tutorial</a></li>
+ <li><a href="demos/composer/index.php">Prado Component Writer</a></li>
+</ul>
+<h2>Documentation</h2>
+<p>
+Complete documentation will be added in beta version. Please refer to
+Prado QuickStart Tutorial and the included API documentation for now.
+</p>
+
+<h2>Credits</h2>
+<h3>Prado Developer Team</h3>
+<ul>
+<li><a href="mailto:qiang.xue@gmail.com">Qiang Xue</a> - PRADO founder, author of application controller, core components and controls.</a></li>
+<li><a href="mailto:weizhuo@gmail.com">Xiang Wei Zhuo</a> - author of I18N/L10N support, active controls (AJAX) and PRADO javascript framework, unit and functionality testing.</a></li>
+<li><a href="mailto:jrags@jasrags.net">Jason Ragsdale</a> - the PetShop demo, project site maintenance</li>
+<li><a href="mailto:nyeholt@optushome.com.au">Marcus Nyeholt</a> - component development and unit testing.</a></li>
+<li><a href="mailto:alex@linium.net">Alex Flint</a> - component development and unit testing.</a></li>
+<li><a href="mailto:luftyluft@gmail.com">Brian Luft</a> - documentation and marketing</li>
+<li><a href="mailto:carl@decart.no">Carl Mathisen</a> - art design, PRADO v2 maintenance</li>
+<li><a href="mailto:compte_messagerie@hotmail.com">Alban</a> - component development</li>
+<li><a href="mailto:rodolfo@equinoxe.g-networks.net">Rodolfo Gonzales</a> - PRADO v2 maintenance</li>
+<li><a href="mailto:wkonkel@gmail.com">Warren Konkel</a> - PRADO v2 maintenance</li>
+<li><a href="mailto:jnavratil@houston.rr.com">John Navratil</a> - PRADO v2 maintenance</li>
+</ul>
+
+<h3>Past Team Members</h3>
+<ul>
+<li><a href="mailto:j.todd.patrick@gmail.com">Todd Patrick</a></li>
+<li><a href="mailto:pimvanderzwet@gmail.com">Pim van der Zwet</a></li>
+<li><a href="mailto:tim.evans@gmail.com">Tim Evans</a></li>
+<li><a href="mailto:johnteag@gmail.com">John Teague</a></li>
+</ul>
+
+<h3>Special Credits To</h3>
+<ul>
+<li>All PRADO users - great suggestions, feedback and support</li>
+<li>ASP.NET 2.0 for its great inspiration and reference</li>
+<li>All third-party work used in PRADO (<a href="framework/3rdParty/readme.html">more details</a>)</li>
+</ul>
+
+
+<h2>Terms and Condition</h2>
+<p>PRADO is released under the BSD License.</p>
+<p>Copyright © 2004-2006, PradoSoft (http://www.pradosoft.com)<br/>
+All rights reserved.
+</p>
+<p>
+Redistribution and use in source and binary forms,
+with or without modification, are permitted provided
+that the following conditions are met:
+<ul>
+<li>Redistributions of source code must retain the above
+ copyright notice, this list of conditions and the
+ following disclaimer. </li>
+
+<li>Redistributions in binary form must reproduce
+ the above copyright notice, this list of conditions
+ and the following disclaimer in the documentation
+ and/or other materials provided with the distribution.</li>
+
+<li>Neither the name of the developer nor the names of
+ its contributors may be used to endorse or promote
+ products derived from this software without specific
+ prior written permission. </li>
+</ul>
+</p>
+<p>
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS
+AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED
+WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
+WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
+PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL
+THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY
+DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
+CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
+PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF
+USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER
+IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
+NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF
+THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
+POSSIBILITY OF SUCH DAMAGE.
+</p>
+</body>
+</html>
|