My views on PHP event driver title

We can see that someone is discussing the PHP event-driven title and should have replied to a post. However, I think that the reply is insufficient to attract everyone's attention. Therefore, I will open a post to detail my understanding of this title and describe and analyze Yijia. The concept of event-driven is generalized. We can see that someone is discussing the PHP event-driven title and should have replied to a post. However, I think that the reply is insufficient to attract everyone's attention. Therefore, I will open a post to detail my understanding of this title and describe and analyze Yijia.

The concept of event-driven is generalized. It can be on the client or the server.

In terms of WEB utilization, the client's real event is based on JS, plug-ins, JAVAAPPLET, and so on. if it is based on plug-ins or JAVAAPPLET, it is not in the HTML category, there are only a few cases where JavaScript is really necessary, most of which are basic controls such as FORM submission or link clicking. Therefore, it is meaningless to talk about events.

The true significance of event-driven lies not in visual programming, but in its concept, just like OO. Event-driven is an extension of OO. its original prototype is the message mechanism. However, event-driven messages are encapsulated into callable functions, which are similar to callback functions in Apis. you can define the content of these functions. Visual programming separates these functions and defines parameters (most of which are ready-made objects) so that you can write code and apply these parameters (these objects are actually used) to do something.

Therefore, it is possible to have a complete event-driven PHP framework design. To make a visual event driver like VB, you must have a complete integrated development environment, including page design, event encoding, compilation, transcoding, and a series of other functions. Event-driven like dot NET only encapsulates some commonly used WEB elements or controls, such as buttons and text boxes, let you have a visual interface to design it. after it is compiled, it is stillAnd so on, just convert your event code to JS or server-side code. The important reason for PHP is that the IDE is not rich enough and there is no pre-compilation mechanism. Therefore, the final submitted code is the ultimate PHP code, it is not a mixture of resource code and event code of vertex NET (generally an ASP document conforming to XML specifications, including non-standard HTML code ). Therefore, PHP cannot achieve the so-called event-driven programming in the narrow sense, but it can be completely without titles.

If you are interested, go to www.php.net official homepage and check out a set of event-driven PHP framework PRADO written by a Chinese guy Qiang Xue, this is still the best option to win a high vote. we strongly recommend it! Please refer to the http://www.zend.com/php5/contest, you will understand his source code PHP event driver is what's going on. However, in my opinion, because PHP does not have a pre-compilation mechanism and is overly reliant on OO (although it is code written using PHP5), this framework is somewhat ambitious and complex to use, scalability is not very good. However, the concept is very good, and some ideas solve the problem of confusing titles for many days. Let me briefly introduce this framework.

This framework is written in ZDE and PHP5. it has specific documents, clear structures, excellent comments, easy to understand code, and a high degree of coding. The authors clarify that this framework references the concepts of ASP point NET and Borland Delphi.