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:
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.
As with any Open-Source project, contributing
code or documentation is the most common way to help, but we also have a wide range of
sponsoring opportunities.
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.
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!
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.
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.
(For example, BrowserKit uses Symfony\Component\DomCrawler.)