What to do when you want to migrate to Symfony2, but can't invest the time into rewriting your whole application at once? I get this questions sometimes, and I've asked myself as well for some time already. Talking to other people, I found I was not the only person struggling with this issue. Wrapping Symfony2 around your old application is one option, and I've found this works well in some situations. To automate this, I wrote a very simple wrapper bundle: IngewikkeldWrapperBundle.
Just a little heads-up for people working with Symfony2/Twig: Today I ran into an issue that I couldn't figure out. "It shouldn't be this hard..." I thought, and indeed, it turned out not to be as hard. It's just easy to overlook: Make sure to close your twig tags correctly
In August of last year, I wrote this excited blogpost about phpBB joining the Symfony2 camp by announcing they were going to use Symfony2 as the basis for their new version. Things like this are exciting, because it will allow several communities to work on the same software: Symfony2 developers would be able to help with the development of phpBB, and the other way around. Now, the same thing is happening with Drupal. Even though they are not adopting the full Symfony2 stack, they have just started implementing some Symfony2 components.
I have been aware of Silex for a while as a nice microframework based on Symfony2, and have looked into it a couple of times to see if it would be useful for a project. So far though, the projects I was working on seemed to need more than just Silex, so I picked Symfony2 instead. This morning, I decided to dig into Silex a bit more with a real-world project I still wanted to develop myself: A URL shortener.
Some time ago, inspired by the #linktuesday initiative Lorna started, I built this relatively simple website which I put on LinkTuesday.com. It fetches tweets from Twitter with the #linktuesday hashtag, groups them together and then displays them in various rankings. Insanely simple idea, insanely simple execution.
In January I announced that I had become a Sensio training partner. So far, I had not scheduled any training sessions though. With Symfony2 nearing completion though, it's time to change that, and I've finally scheduled my first training session on Symfony2.
For some time now I've been working on a partnership, and it is with great pride and happiness that I can now officially announce it: My company Ingewikkeld is now an official Sensio trainingpartner for Benelux and Germany. This means that as of January 1st, I am now able to officially offer all Sensio courses in these countries.
So earlier this week I attended this year's Fall Edition of the International PHP Conference in Mainz. They were celebrating their 10th anniversary (with waffles!) and had an excellent schedule again. I was scheduled for given two talks but took the opportunity to also attend many of the conference's talks. And obviously I also was present in the hallway track for quite a while. Let's see what I learned at the IPC.
Earlier this year at the Symfony Live event in Paris, I spoke with Nils Adermann, the new lead developer of the phpBB software. At the conference it was announced that phpBB was considering moving to a Symfony basis for their upcoming version 4. Since then, an RFC was posted and given the schedule for the Libertyvasion conference organized by phpBB, they're gearing up to dive deep into Symfony. This article reflects the thoughts I've offered at the Libertyvasion Conference on the combining of powers of phpBB and Symfony.
This week there was an interesting discussion on twitter between several people from the PHP community on the use of access modifiers, and why things should be public, protected or private, or why not. The thing that triggered this was the fact that the new Symfony2 Coding Style disallows the usage of private methods. This discussion earlier on triggered Lukas Smith to post his opinion. I commented there but the comment became thus long that I decided to write a blogpost about it myself.
17-02-2012: