Download the PHP package particle/state without Composer
On this page you can find all versions of the php package particle/state. 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 state
Particle\State
Particle\State is a very small and simple library, implementing a finite state machine. You can use it in your application whenever you need to account for transitions between multiple states (and that's probably more often than you would imagine!).
Why?
With winzou/statemachine and yohang/finite already in Packagist, why would we go for another package implementing the very same concept?
Well, first of all, Particle\State is very small in comparison, doing next to nothing. That means everything it does do is easy to follow, without having to wade through lots of code. Also, by doing only one thing, it's rather easy to learn how to use this library.
On top of that, we wanted to have a library that is not obtrusive: you can implement Particle\State without having to model your objects in a certain way. Indeed, Particle\State does not have any interface you need to implement.
Nevertheless, check them out. Maybe they'll serve you better.
Small usage example
Functional features
- Validate if a transition of state is possible;
- Transition the state to a next state;
- Hook event listeners to state changes as transition callbacks.
Non functional features
- Easy to write (IDE auto-completion for easy development)
- Easy to read (improves peer review)
