One of the strengths of Symfony2 lies in its components; they define the building blocks of the framework and they can be used as standalone libraries:
- BrowserKit
- ClassLoader
- Config
- Console
- CssSelector
- DependencyInjection
- DomCrawler
- EventDispatcher
- Finder
- Form
- HttpFoundation
- HttpKernel
- Locale
- Process
- Routing
- Security
- Serializer
- Templating
- Translation
- Validator
- Yaml
For instance, Silex, a micro-framework for PHP 5.3, is based on the Symfony2 components; Sismo, a simple continuous testing server, has been built using many components as well.
The Symfony2 components have been available on Git for quite some time now, and as of today, I'm really excited to announce that they are also installable via the brand new Symfony2 PEAR channel, powered by Pirum of course.
Published in
#Releases
This is great news for PHP developers that prefer to use à la carte components for their applications instead of an entire framework.
Is there any way we could get the package.xml files validating against the PEAR package xml schema, so they're installable with Pyrus?
Thanks!
Great! S1 lack of this flexibiliy and that handicap was a major concern on Symfony1 vs
framework's name of people behind php.I have also tried Silex; it is very small but powerfull. The very best for small app. I'm also willing to teach some students 'how a framework works and how to implement it (mvc, routing, clousures, custom error pages)' with it and then jump to S2.
Great! S1 lack of this flexibiliy and that handicap was a major concern on Symfony1 vs
framework's name of people behind php.I have also tried Silex; it is very small but powerfull. The very best for small app. I'm also willing to teach some students 'how a framework works and how to implement it (mvc, routing, clousures, custom error pages)' with it and then jump to S2.
The Symfony PEAR channel package.xml now validates the XSD.
Great! But, these package aren't define dependencies? (For example, BrowserKit uses Symfony\Component\DomCrawler.)