Just finished Chapter 1 and 2. Some notes.
- Symfony takes advantage of PHP5. Magic methods are used often. I really should push myself to learn PHP5 and OOP. I will suspend reading the book when I encountered PHP language problems. The book says OOP skills are essential before you start to use symfony.
- I could understand what MVC framework is, but didn’t fully understand symfony workflow. Layout/view logic/template is one of them I couldn’t understand. The layout is application-global. I didn’t get what logic view is. I hope reading more will give me a clear picture.
- The structure of a project wasn’t very clear. I have no idea how define applications and modules. This might not be well-explaned yet in this very early chapter. But I got a basic understanding.
- A project tree structure has a lot of config, lib and templates directories specific to each level. I shold be careful not to misplace files in different levels.
- Parameter holders. I have no understanding whatsoever about them.
- Class autloading. You don’t need include statements in spite of many lib directories. Really good news.
My tasks.
- YAML’s syntax is easy to understand. Learn YAML bundle of TextMate.
- Classes and Objectes in PHP 5 is my new friend.
- Read symfony’s coding standards, and be familiar with it.
If you have any advice on me, please don’t hesitate to leave a comment.
Comments
Starting from a
Starting from a suger-syntaxed framework like Symphony, especially without fundamental skills and experience of oop, design patterns and PHP itself of cource, you’re only to lose your way. Such kinda framework is to build up a web application rapidly and for those who can build same thing without using any framework. Neither for study nor for a layman. haste makes waste:)
@an old conductor: I see. If
@an old conductor: I see. If I start to learn PHP, you might say I should start with C. If I start to learn C, you would recommend an assembly language.