Download the PHP package peytz/wizard without Composer
On this page you can find all versions of the php package peytz/wizard. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
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 wizard
Wizard Component for Symfony2
This is a simple component mainly developed for usage with the Symfony2 framework. And because of that there is some references to that. Which easily can be changed.
License
See LICENSE for licensing terms.
Contributing
Everybody is welcome to send Pull Requests. But we reserve the right to reject any that is not in line with our goals for this component.
See https://github.com/Peytz/Wizard/contributors for a list of contributors
Installing
There is 3 ways to install this component. You can use Composer, Phar or just include the code directly in your application.
Using phar
Theres is a ready to use phar achive in build/peytz-wizard.phar which includes its own small autoloader that automatically
registers with php when included.
Using Composer
You can also install it via composer by using something like the following require.
Running tests
Usage
The api is very simple. You create a Report which properly should be an Doctrine Entity. The Report
holds your data and must implement ReportInterface
A Report is required as a contructor argument for a Wizard. A Wizard should be subclassed to add
custom steps or use a DependencyInjection framework to inject them into a Wizard object.
A Wizard holds a n number of Steps that implements the StepInterface. There is a basic Step
implementation of StepInterface availible.
Controller action implementation using Symfony Validator component for validation. Validation Groups are extremely useful for this.
Sample Symfony2 DIC definition
I you want to use DependencyInjection with Symfony2 this is another way of having a Wizard and its steps associated.
The power of using a DIC is that each StepInterface implementation can have optional dependencies. Like building forms
programmatically instead of having a FormType.
