Download the PHP package cammanderson/phruts without Composer
On this page you can find all versions of the php package cammanderson/phruts. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download cammanderson/phruts
More information about cammanderson/phruts
Files in cammanderson/phruts
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package phruts
phruts
PHP implementation of Struts in current framework interoperability group standards.
- Run through Silex (e.g. get Dependency Injection, dispatcher, security, cache, esi, etc and support building up of other services)
- Uses Symfony HTTPFoundation/HTTPKernel
- Implements PSR's (Naming Conventions, Logging, Autoloading)
- Use Twig or your other preference dependencies
What is Phruts?
Phruts is based on Apache Struts, a Java MVC framework. Your controllers are configured through an XML file, which then also controls application flow and forwarding. Some parts are OK, some parts are much better done by other frameworks.
Install
Add to your composer and do a
Add to your Silex application
Configure your MVC config
Create your app/config/web-config.xml. This configuration is digested using the Phigester which will read in the XML configuration and reflect them onto the application configuration. Configuration is then frozen and cached.
Extra things:
- Create your folder (this is a config option)
- Create a twig template
Feature support:
- Error handlers
- Global forwards
- Request Processor based on roles defined by Symfony Security
- Action forwards (internal action chaining)
- Wildcard path matching
- Action switching and multiple module support
- Multiple module config merging (e.g. multi config.xml)
- Struts 1.2 API
Current Development Status
- COMPLETE: Code Coverage 35%+
- COMPLETE: Code Coverage 75%+
- COMPLETE: Finalise ActionKernel for mounting on Silex\Application
- UNDERWAY: Confirm Struts 1.2 code coverage for framework features
- UNDERWAY: Write the standard Struts style Twig extensions for accessing form+messages
- Next: Documentation on working with Silex
- Consider Struts Validation framework (we never used it, so might not make it forward)
- Struts 1.3 framework features (for convenience techniques only)
Why would I do this? Best way to learn techniques in web development is through studying Request->Response web frameworks. I have a soft-spot for the old Struts application, and we have legacy PHPMVC code which we would like to easily move forward. This project makes it easy for us to port that legacy code and modernise it fast by implementing PSR's, giving that code base a future supported life.
All versions of phruts with dependencies
cammanderson/phigester Version ~1.0
symfony/http-foundation Version *
silex/silex Version ~1.2
psr/log Version *