Inspire yourself by Symfony2 to create better code
3 likes782 views
Symfony2 is now released and, as the first version of symfony, it's a framework that advocates a lot of best practices. Any developer who works on a Symfony2 application should follow the same rules, in order to keep the project on the right tracks. With the help of Symfony2's code and my personal experience, I will try in this session to bend your mind to some principles like Separation of Concerns and pragmatism, in order to achieve successful projects.
Inspire yourself by Symfony2 to create better code
- 10. • • •
- 15. – – –
- 19. • • •
- 20. • • – – – – – –
- 30. • • •
- 31. • • •
- 32. •
- 33. • • •
- 34. • • •
- 36. • • –
- 38. Interfaces 160 140 137 120 100 80 60 40 20 4 0 symfony 1.4 Symfony2
- 39. • • • •
- 41. • • • • – – –
- 43. • • • –
- 46. • • – –
- 47. • • • •
- 48. • – • •
- 49. // src/Symfony/Component/Yaml/Exception/ExceptionInterface.php namespace SymfonyComponentYamlException; interface ExceptionInterface { } // src/Symfony/Component/Yaml/Exception/DumpException.php namespace SymfonyComponentYamlException; class DumpException extends RuntimeException implements ExceptionInterface { }
- 50. • • •
- 51. • • •
- 53. • – – – –
- 55. • • • • •
- 56. • • •
- 58. • • •
- 60. • • • • •
- 61. • – –
- 63. • •
- 64. • – – – •
- 65. • •
- 66. Consumer (Symfony) OAuth2 Provider Consumer Consumer (ZF) (Silex)
- 67. • • • • – – –
Editor's Notes
- #20: Bridges are independent of the third party library and of the component so that component stays uncoupled. This is also a prevention measure for the component to not become bloated.