Commits
-------

8de3aca7 load default form_div_layout.html.twig when using form and twig service providers

Discussion
----------

Load default form_div_layout.html.twig from TwigBridge

Load default form_div_layout.html.twig when using form and twig service providers. This means you no longer have to copy form_div_layout.html.twig to your project.

This means you no longer have to copy form_div_layout.html.twig to your project

Commits
-------

a3f570d4 [Doc] Changed ArraySessionStorage to FilesystemSessionStorage for functional testing
be168e3b Added doc about session and test

Discussion
----------

Added doc about session and test

---------------------------------------------------------------------------

by fabpot at 2011/09/26 12:57:33 -0700

As noted in the phpdoc, for functional testing, you must use `FilesystemSessionStorage`.

---------------------------------------------------------------------------

by lyrixx at 2011/09/26 14:27:10 -0700

I updated the doc.

Commits
-------

37952fb0 fix ControllerProvider example

Discussion
----------

fix ControllerProvider example

Commits
-------

384e816d Fixed typo

Discussion
----------

Fixed typo

Fixed issue #175

Commits
-------

2805a0f3 [composer] add suggestions for ServiceProviders
768367b2 [composer] adjust package name and required package versions to latest naming
81bace77 [composer] re-add css-selector, adjust versioning syntax
0f620a20 update composer.json
1c6e4436 [composer] bump PHP requirement to 5.3.2
ca2d515b Add composer.json

Discussion
----------

Add composer.json

---------------------------------------------------------------------------

by igorw at 2011/09/22 11:00:53 -0700

Shall I change the version? Are we going to do a release? Will it be 1.0.0? I will leave it at 1.0.0 without tag for now, aka 1.0.0-dev.

---------------------------------------------------------------------------

by igorw at 2011/09/29 00:32:54 -0700

There are still suggestions missing for following packages (because they have no composer.json yet): doctrine/dbal, swiftmailer.

renamed ExtensionInterface to ServiceProviderInterface and ControllersExtensionInterface to ControllerProviderInterface

The main idea is the move of all controller-related code from Application to
ControllerCollection. Reusable applications are now instances of
ControllerCollection instead of Application instances. That way, there is only
one "true" Application instance, and thus only one Pimple container.

Reusable applications can now be packaged as classes, like Extensions. It
allows to package services and controllers into one extension.

Benefits:

 * less hackish (proper wrapping in a class, no need to add a temporary route, no need for the LazyApplication anymore)
 * less code
 * simple and straightforward code (no magic anymore)
 * less side-effects
 * fix most severe/annoying limitations of the current implementation (from what I've read in the mailing-list and the Github issues)
 * better encapsulation of "reusable" applications
 * better separation of concerns
 * simple usage is exactly the same as before (as Application proxies the ControllerCollection methods for the "default" app)

Upgrading is as simple as replacing Application with ControllerCollection for
reusable apps (note that a reusable app is not "standalone" anymore):

    $mounted = new ControllerCollection();
    $mounted->get('/bar', function() { return 'foo'; });

    $app->mount('/foo', $mounted);

A better way now is to create a class:

    use Silex\ApplicationExtensionInterface;

    class FooApplication implements ApplicationExtensionInterface
    {
        public function connect(Application $app)
        {
            $controllers = new ControllerCollection();
            $controllers->get('/bar', function() { return 'foo'; });

            return $controllers;
        }
    }

    $app->mount('/foo', new FooApplication());

Note that you get the "master" application, so that you have access to the
services defined here.

If you want to register services, you can do so in the same extension:

    use Silex\ApplicationExtensionInterface;
    use Silex\ExtensionInterface;

    class FooApplication implements ApplicationExtensionInterface, ExtensionInterface
    {
        public function register(Application $app)
        {
            $app['some_service'] = ...;
        }

        public function connect(Application $app)
        {
            $controllers = new ControllerCollection();
            $controllers->get('/bar', function(Application $app) {
                $app['some_service']->...;

                return 'foo';
            });

            return $controllers;
        }
    }

    $ext = new FooApplication();
    $app->register($ext);
    $app->mount('/foo', $ext);

Commits
-------

394ea192 [docs] basic documentation for the SymfonyBridgesExtension

Discussion
----------

[docs] basic documentation for the SymfonyBridgesExtension

there are no extensive usage examples, but it's a start.

Commits
-------

d4a96c35 [docs] adjust path yet again, to point to /lib/classes
b482107a [docs] add some missing docs for internal swiftmailer services
c4957ef5 [docs] remove unneeded transport and mailer from swiftmailer docs
f210d1ea Merge branch 'master' into swiftmailer-docs
50fddd1c [docs] remove duplicate 'a'
62a31c0f [docs] rewrite usage POST example to not use Swiftmailer
3c92b812 [docs] documentation for SwiftmailerExtension

Discussion
----------

Swiftmailer docs

Finally got round to finishing this one.

* Adds documentation for the SwiftmailerExtension.
* Changes the `POST` example in usage to use `mail()` instead of Swiftmailer.

---------------------------------------------------------------------------

by igorw at 2011/09/18 07:25:43 -0700

Should be complete now.