About "VCL is dead and rad is dead"

I attended the Erlang conference in Shanghai these two days. I have no time to write the fifth section. Please reply to some comments first. Among them, the most important part is a group of comments from Nanyu. There are about three or four comments, which write a lot of things. The following is an example.

 

For comments, see:

Http://blog.csdn.net/aimingoo/archive/2008/12/17/3540112.aspx

 

 

If I do not understand it correctly, what you say is that rad is dead and replaced by web UI.

-------

This is the most basic misunderstanding. Rad has many sayings, but none of them are directly related to "UI development", so it will not die, there is no need to replace the Web UI. Similar concepts have emerged in many discussions on this topic.

 

In section 4, I write the following text or reply to this question:

So let's review the entire process ,...... Can this indicate that rad is dead? Not all, it can indicate that "the interface-Based Visual rad productization technology is dead ". I must emphasize this in this section to show that there is no necessary, direct, and strong association between the death of VCL and the death of rad. In my opinion on the death of rad, VCL is just an introduction, not a credential.

 

To put it down, Rad is almost regarded as a synonym for Delphi or ms vb in Borland products.

-------

This is also a major conceptual error. The problem is the same as the problem above. Rad actually refers to "Rapid software development" (the process or method), and is similar to the UI method of Delphi/VB, and IDE are just a specific tool for the above process or method. This tool is a part of the entire process or method, not all of it.

 

In fact, I was also troubled by this incorrect concept. However, when the reader biekvn discussed it with me in the insite message, he found that rad was often misunderstood. So I asked a question: if the IDE of Delphi's drag interface is rad, Eclipse IDE does not use the drag interface, but some modules have automatic tools such as syntax check errors, isn't it rad? The answer is of course computing. Eclipse certainly improves our development efficiency and is also a feasible tool for implementing the rad process. However, note that eclipse does not have a so-called drag interface (for the time being, a third party does not care about it). To put it simply, the operation method of the drag interface, as well as the componentized interface and skin interface brought about by it, it is just a method or tool for rad implementation, but it is not all or synonymous with rad.

 

After clarifying this concept, I must emphasize more:In the article "VCL dead and rad dead", I have discussed two issues: the former is the problem of UI development and design methods, and the latter is the problem of software engineering methods. For the idea of rad's death, VCL is just an introduction, not a credential.

 

 

Q: Why are more BS programs and fewer CS programs?

-------

There are many answers to this question. Of course, the "BS easy to deploy" you mentioned is one of them, which is also critical. However, there are other potential factors, such as the BS magnitude and network conditions. I often mention BS short connections, which are an effective supplement to CS persistent connections. This is the internal motivation for them to shift and increase in different environments.

 

Web UI is not a concept with the BS program you mentioned. I basically don't discuss whether Web UI must access a remote web server in a browser. In fact, the technical solution I made public at the sd2c conference is to use the Web UI for the client interface of C/S. We only need to discuss the question of "What is a Web UI mode in essence. My answer is: block + layer + link-based, descriptive, and migratable. These three points are exactly what the technical UI does not possess Based on MFC, wimp, and (generally) MVC pattern.

 

We will discuss B/S and C/S, discuss web UI and wimp UI, and discuss rad and RUP ...... And so on. We should not confuse the cause and effect of multiple concepts or fields. Most of the time we will discuss them separately. We may mention the influence of each other, but even so, we need to clarify and then confuse them.

 

"Similarly," link "is the essence of user UI interaction and also the essence of WWW"
Comment :...... There is a large amount of text content that needs to be linked. This is the essence of WWW, rather than "Link.

-------

This problem is divided into two parts: the essence of UI interaction and the essence of WWW. In the concept of UI interaction, "Link" represents "click", that is, behavior. If "block + layer" is "UI description", "Link" is "UI interaction", which is the element that makes UI activities. I said that he is the essence of UI interaction. As for the question of "is the essence of WWW?", you should check the source text of www. You will understand that the source of web is structured, it can be connected to each other. "There is a very close relationship. To put it simply, if it is not a link, the Web will only become pages instead of web site and web world.

 

As for Mac, the question of making the mouse have only one key is explained later. Or you can look at the design documents of the MAC system. Of course, it's even more interesting to add a scroll wheel to the Mac mouse. People who study the UI have a lot of ideas-I mean philosophical, aesthetic, or design ideas or opinions.

 

 

"So, in fact, the success of web is more humane than the traditional wimp UI, and more direct to designers (such as PS experts.
Comment: Again: (UI) designers and PS experts are two different things.

-------

En... This is also the most important point in your comment. In fact, this is also my point of view, which is also mentioned in the text, but the reader does not pay attention to it. In my opinion:When the interface is separated, the E2 + C2 problem occurs naturally. E2 refers to effect and experience. The effects are guaranteed by art design, while the experience is guaranteed by front-end development.

 

So here I am talking about art design. The subject refers to people who use "PS-like tools" to design and implement interfaces. Of course, you can say that the UI Designer does not necessarily use ps. It doesn't matter. PS is just an example here. I am not sure that the Xbox UI Designer uses ps or that the mac ui Designer uses PS for work. I just gave a brief reference.

 

I don't know that the "UI Designer" package you mentioned does not include UED. For me, UED is a team rather than an individual. From this perspective, the UI Designer is a person, while the "uidesign" is a field. "Uidesign" may include effects, experiences, and their implementations. As long as the UI is separated, all the people working in this separated UI field, including programmers, can be called "UI designers ". In fact, according to the above explanation, "uidesign" is equivalent to "UED (user experience design )", because the experience also includes visual experience-color, shape, location, comparison, and so on. Therefore, it is not easy for us to distinguish these terms.

 

So I said, "more oriented to designers (such as PS experts )......" In this sentence, the designer has to be confined to the scope of "UED designers who use tools such as Ps. In this case, I will use examples to illustrate that my "limitation" is just a writing habit, if I had to use ten or twenty terms to define different angles in an article, I could certainly do the same, but that would be even harder to read.

 

Okay. What should I explain in such a paragraph? I mean, the PS-class flat plotting tool is mainly composed of blocks and layers, and the Web UI has similar characteristics, therefore, the conversion between them is natural and smooth. You (as a programmer) do not need to explain to a PS engineer what is "icon" and how big or how many colors it should have. Because there is no icon in the Web UI system.

 

Whether or not a uidesigner should draw a square on the interface and fill in some pixels to indicate that "this is an indicator (the main path of the icon)" is the choice of the designer, it is not a limitation of "Windows OS", "VCL Component System", or "Win32 API. In this way, the uidesign will be free, and the UI you see will be free and human-of course, a specific uidesign and developer (we assume the entire UED Team) whether a "human nature" interface can be made is beyond my scope of discussion.

 

 

 

Others (other replies may be added)

-------

To fengjssoft,
As far as you know, there are only a few web systems that are comparable to your CS programs, so we cannot discuss anything. In the Buddhist family, there are many people with insights. When the accumulation of what you know reaches a certain level, it becomes an obstacle for new insights. This is a stage that will inevitably go through.

 

To mobeing,
I wrote this group of articles because I spoke on sd2c and said "VCL is dead and rad is dead", but I don't have enough time to clear my point of view. Even though I still haven't been able to fully understand it before writing it, I have been thinking deeply about it in the process of writing it, so I wrote it down and wrote it down very carefully.

As for my understanding of VCL you mentioned, I don't explain it, because it seems that you know me well. I would like to thank you for your concern and suggestions, so that you can cherish each other and be careful.