/explore
|
You are here 
|
gonzalo123.com | ||
| | | | |
fabien.potencier.org
|
|
| | | | | The blog of Fabien Potencier about web technology and the symfony framework | |
| | | | |
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 | |
| | | | |
matthiasnoback.nl
|
|
| | | | | Part I: Don't use the standard controller The general belief is that controllers are the most tightly coupled classes in every application. Most of the time based on the request data, they fetch and/or store persistent data from/in some place, then turn the data into HTML, which serves as the response to the client who initially made the request. So controllers are "all over the place", they glue parts of the application together which normally lie very far from each other. This would make them highly coupled: they depend on many different things, like the Doctrine entity manager, the Twig templating engine, the base controller from the FrameworkBundle, etc. | |
| | | | |
swiftwithmajid.com
|
|
| | | That is WWDC week: everybody is so excited about so many new things like SwiftUI, Dark Mode, updateable Core ML models, etc. I will try to cover all the new stuff during the upcoming weeks. Let's start with SwiftUI. SwiftUI is an entirely new approach to building apps for the Apple ecosystem. | ||
