All copyrights shall not be reproduced without the consent of the author. Otherwise, they shall be deemed as infringement and the right to be held accountable shall be reserved.
Guide
Who is this book suitable?When I was thinking about this book, I had been wondering which type of readers it should target, whether it was a developer or a beginner? Although I have repeatedly asked questions, I really cannot fully distinguish these two types of readers, because the knowledge of anyone has limitations and no one can understand anything. So I decided that the readers of this book should be those who want to study computer software technology-those who want to study hard! Yes. I will dedicate this book to those who want to read it with my heart. This will also inspire me to write it with my heart! If you are a beginner, do not be afraid. In this book, I only assume that you understand C language and use it to write at least one program with more than 100 lines. I believe that what I am talking about will help you improve your skills in C language development, so that you can jump into the software world as soon as possible. In addition, this book provides you with chapters to introduce basic knowledge and consolidate your technical foundation. In my opinion, to do everything well, you must have relevant professional knowledge as the foundation. The superstructure without foundation is not solid. If you are a PC programmer and want to learn some embedded platform knowledge, this book is also suitable for you. This book can show you the knowledge of embedded systems. To some extent, an embedded system is a small PC. Or because a smaller system is easier to understand, this book also helps you understand large platforms such as Windows through a deep understanding of the Brew platform. Further, if you are learning about com (Component Object Model), I will show you a C-language com implementation in this book, it will further deepen your understanding of COM. If you are a programmer of an embedded system and want to have a deep understanding of a platform and relevant knowledge, this book is also suitable for you. This book deeply analyzes the implementation methods and composition of the embedded system development platform brew. Through these analyses and the related knowledge (implementation of the Shape system and event-driven mechanism, you will have a deeper understanding of the components of the embedded platform. The Brew system architecture analysis provides a good reference for you to design your own development platform. If you are not only a programmer but also a developer on the Brew platform, I have to say that this book is a must-have for your case! This book provides an in-depth analysis of brew's working mechanism, running principles of brew applications, and implementation methods of brew interfaces. At the same time, the example programs in this book also provide you with a BREW application framework, so that whatever BREW application you develop can be handy. If you still do not know whether you should read this book so far, I suggest you read the contents of this book first. Maybe you can find the content that interests you.
Content ArrangementThe book is divided into three parts, each with a different focus. The first article focuses on understanding the basic knowledge required by brew and embedded systems. This includes hardware, C language, compiler, makefile, and other professional content. Although the main purpose of this article is to lay a solid foundation for beginners, I believe that the content mentioned in this Article will be of reference value to professionals. The second article focuses on the BREW application development process, so that we can familiarize ourselves with the Brew platform when developing brew applications. In this article, we also recommend an application framework based on the brew event-driven mechanism, which is implemented in the form of a state machine. With this framework, we can develop applications more easily. The third article is a glimpse of the true nature. In this section, we have analyzed brew's internal implementation methods. This part is also the focus of this book. From this article, we will learn how brew uses C language to implement the com mechanism and how the brew kernel works, and the structure of the Graphic System in the BREW Platform and some advanced brew interface applications. This article goes deep into brew and analyzes brew to provide reference for our software system development.
Conventions in this bookIt wasn't until I started writing this book that I found out that to describe how difficult an idea is, I had to add some additional languages in addition to the use of the colloquial language. Because these images seem intuitive and may be easier to understand (but note that although these descriptions are difficult to understand, they are usually essentially here ). Although I hope that I can express my thoughts or describe a principle in the simplest language, I have to use a few languages to describe accuracy. This is indeed quite contradictory, but I can only do my best. The embedded system in this book usually refers to a mobile phone system or handheld device, because the system is more universal and the BREW Platform is also developed for mobile phones. Since the content of this book is to compare the personal computer system and embedded system to show their respective characteristics, so when describing their commonalities, I will use the computer system as a general term of the two. Some people may think that the computer system should be a PC system. In fact, this is not accurate, because the embedded system is also a computer system, but it is a little smaller. This book also frequently uses the titles "program" and "code". There is no obvious difference between them, but I may choose different titles based on different contexts. In this book, sometimes brew's application is called applet (a small application), and sometimes it is called an application. In fact, the two are the same and there is no difference. There are two naming conventions: sometimes it comes from a habit of brew development documentation itself.
How to contact the authorI tried my best to make this book accurate, readable, and useful, but I know there is still room for improvement. If you find any errors-technical, linguistic, typos, or anything else-please let me know. I will try to fix it in the new version of this book. If you are the first person to tell me, I will be glad to log on to your thank-you-me letter. If you have any suggestions for improvement, I would also like to welcome you. I am very happy to communicate with all readers of this book and accept your corrections and suggestions for this book and my personal opinions. However, I hope to limit my content to my views on books, knowledge, and incorrect corrections or suggestions about this book. It would be a great pleasure to chat with me simply. Network Era, only the network, my e-mail address is: gemsea@163.com
