"Delphi master breaks" has been published for nearly one year, and there are many readers to send email. I have not done a lot of readers, I can only say sorry here. However, many readers come to Email to ask about the technical details of the system they are building, and also have the reader's source code request help. I hope that these readers can consider it for me, I will work in work, and I have to build the system of the boss. I have a lot of questions that I have written. I also want to find someone to help me see my code. .
Today, I want to talk about the instance of the text editor about the last chapter of the book. Oh, readers think that the design is too complicated, in fact, I think so. However, I don't deny the instance of such a "complex design" in the last chapter.
First of all, this is a book. The content of the book requires coherent, which is consistent. The content of this book is actually around a theme, which is "how to build a good design code". The first six chapters are basically the theoretical description and very abstract examples, such as: Coke tube put gasoline, huh. There is no real instance, the reader is still in the fog, I understand it, I don't understand it, I don't understand it. With an example, the reader has some "implementation" feelings for those theories.
Second, maybe for practical applications, the code design of this instance is too complicated. To achieve a text editor, don't have to be so trouble, huh, huh. This application, the size of the code is generally around 1,000 to two thousand rows, really have to change the editor component, and rewrite one or not. However, the problem is, this example is still in the book, that is, as a teaching aid, its role is not only a demonstration, but also to let readers will leave "design" impression. Therefore, the traces of "design" are very heavy, and the corrosion must be excessive. In addition, I think that the professional programmer's growth will be divided into three phases: 1, primary, feature: high-rated realization, to achieve functionality, with this sense of accommodation 2, intermediate, characteristics: As the code The accumulation of the quantity, I want to reuse the previous written things, began to pay attention to the design, worship design, and use a very dazzling design skill in my own procedure. 3, advanced, feature: from "worship" design to return, can be easily constructed Good design code, but not to go into the magic, design the name "Delphi master" name for the design, although the "master breakthrough", but it is not written to the above-mentioned senior or intermediate programmer (book name is the publishing house designated) , I can't, but you can also break the "master breakthrough" to understand "the breakthrough point"). It is written to those primary programmers who are still focused on implementation, at least, I want to point out an improved direction.
Finally, the book is limited, it is impossible to make a very large application as an example, at least in this book is not suitable. Chinese programmers are still poor, write thick, buy less :). I wrote the original intention of this book, but I also hope that I can give some help like I have been confused, evoke a sense of consciousness, I really want to study, study, a book is absolutely enough. If you have such awareness, you can buy a big one.
I haven't written the article for a long time, busy, people are tired is the reason, and I am sorry again for readers who have not received my reply.
2003-8-1 Zhuhai
