|
You are here |
tomasvotruba.com | ||
| | | | |
richardmiller.co.uk
|
|
| | | | | Background I am recreating Lime Thinking's current website [http://www.limethinking.co.uk] using Symfony2 [http://symfony.com/], much of the site is made up of what are effectively static pages. The main content of the page is stored as an XML file which then has the overall XSL template | |
| | | | |
www.beberlei.de
|
|
| | | | | ||
| | | | |
matthiasnoback.nl
|
|
| | | | | As you may have read on the Symfony blog: as of Symfony 2.4 you can register console commands using the service tag console.command. What is the big deal, you would say. Well, let's discover it now. This is how the documentation tells you to write your console commands: namespace Matthias\ConsoleBundle\Command; use Symfony\Bundle\FrameworkBundle\Command\ContainerAwareCommand; use Symfony\Component\Console\Input\InputInterface; use Symfony\Component\Console\Output\OutputInterface; class MyCommand extends ContainerAwareCommand { protected function configure() { $this->setName('my:action'); } protected function execute(InputInterface $input, OutputInterface $output) { // do something } } How to make sure your command will be noticed? Until Symfony 2.4 there wer... | |
| | | | |
conradakunga.com
|
|
| | | This is Part 3 of a series on Dependency Injection | ||