PRADO is a component-based and event-driven programming framework for developing Web applications in PHP. PRADO stands for PHP Rapid Application Development Object-oriented. PRADO is best suitable for creating Web applications that are highly user-interactive. It can be used to develop systems as simple as a blog system to those as complex as a content management system (CMS) or a complete e-commerce solution. Because PRADO promotes object-oriented programming (OOP) through its component-based methodology, it fits extremely well for team work and enterprise development. Its event-driven programming pattern helps developers gain better focus on business logic rather than distracted by various tedious and repetitive low-level coding handling. PRADO comes with many features that can cut down development time significantly. In particular, it provides a rich set of pluggable Web controls, complete database support including both active record and complex object mapper, seamless AJAX support, theme and skin, internationalization and localization, various caching solutions, security measures, object extensions with behaviors, composer integration with plugins, cron task manager, industry standard RBAC permissions, command line application interface, and many other features. The best way to install PRADO is through composer. If you don't use composer yet, first install it: The built-in PHP Test Web Server can be used to immediately start developing and testing a web application. The web server is started with command (assuming the above application in the directory "app"): The asset-packagist repository is used to install javascript dependencies. Assuming you already installed composer, run the command: PRADO 4.x supports Composer extensions to plug in new functionality directly into a PRADO application; such as new web controls, API integration, authorization, new services, analytics, custom behaviors, and CLI commands. 3rd party extensions can be found at Packagist - Prado4-Extensions. The community is encouraged to write and submit 3rd party PRADO 4 extensions for others to find and use. PRADO provides a rich set of features for runtime extension of an application with composer extensions. Behaviors modify existing functionality and add new properties and methods to instanced run-time objects. Class-wide behaviors add default behaviors to classes, interfaces, and traits when instancing new objects and to "listen"ing instances. "Global Events" enable extensions to communicate with other extensions without knowledge of application configuration. "Dynamic Events" enable objects to communicate with their attached behaviors with direct function calls. The example PRADO Composer extension has its own manifest, Module, web page, and error messages. It can be included in an application with the following command: Once downloaded and installed in composer, an extension is activated by adding the Composer Extension Name as a new module ID in the application configuration file application.xml or application.php. To include the example extension "pradosoft/prado-composer-extension", the PRADO configuration would include this module xml: Several different example PRADO applications are provided in the repository. You can see these applications running here: . 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 PRADO uses phpunit for unit testing, PHPStan for static analysis, and Playwright for functional testing. The Playwright suite starts a PHP built-in server automatically on port 8037 before any test runs and stops it afterwards — no manual server setup is needed. Local Playwright test servers automatically terminate when the parent unit test process exits. If a stale Playwright server is left over from a previously killed run, stop it first:
Excerpt from the source-code README · 9,531 chars · not written by Vinony
via Wikidata · CC0
Discovered by embedding cosine similarity (sentence-transformers MiniLM, 384-dim).