What to read before you write your framework in php?

Good day! Please, advise me some materials (websites, books, etc.) to establish a framework in php. Syntax and basic concepts are familiar. You need to understand the basic patterns, more widely to explore the functionality of php. Don't know where to start and which direction to move.

October 3rd 19 at 01:46
7 answers
October 3rd 19 at 01:48

For understanding the architectural flexibility I would advise you to read a series of articles from Fabien Potencier, author of Symfony.

Good article on the case. Thank you! - alberta.Jaco commented on October 3rd 19 at 01:51
October 3rd 19 at 01:50
There's a wonderful book PHP. Objects, patterns, and programming techniques. How to write a framework not teach, but covers the basic patterns and gives a deeper understanding of the PLO, not in the academic style that is private method access to it is not from the outside, and more explains how to think when designing
October 3rd 19 at 01:52

Books and websites will not help here, see the source code of existing frameworks, study how others write. Heed how they work is that learn a lot from you, otherwise you write "bicycles", etc.

October 3rd 19 at 01:54
All the puff-frameworks - shit. To better understand how to be a web framework, you need to look for frameworks in other languages, for example, in RoR (although he's not perfect, of course). The people there are very different thought and wasn't constrained puff paradigm. Django is also good, captures the essence of the framework response to the request.

To write a framework you need to understand what problem it solves, and therefore these tasks should be in your employment to occur quite relevant, and not all at once, but individually. To make you understand what a templating engine is better and why, which model for working with data is better and why, what event handler is better and why, etc.

You should start with processing the command line. Your framework must be able to work with data tables, network, be able to handle the error (e.g., database dumps) from the command line. Then when you build up internal API, we can perform routing, and view function.

Well, we should not forget that the first option will still go to /dev/null
October 3rd 19 at 01:56
Yii for a start - it's horror in the darkness.
Easier to start with microframeworks.
October 3rd 19 at 01:58
October 3rd 19 at 02:00
This is not advertising, asking the same question, did a lot of looking, came across the video. People adequate and without - then you can think, explains the working Varick. Link to lessons YouTube

Find more questions by tags FrameworksIT educationPHP