Ajax and interface design for streaming

Ajax and interface design for streaming

Inshua@gmail.com reprinted please indicate the source

The rapid development of Ajax swept through web development, and the old man was not familiar with it. He believed that AJAX development was not robust enough and there was no navigation. Compared with old web development, the most important improvement of AJAX is probably to keep a copy of memory data that is not flushed in the browser like CS. Because of Ajax, the traditional interface development mode MVC of CS can be smoothly transferred to the Web.
 
The preceding article proposes the db2js development method based on this.
 
Many people may hear this word when implementing MVC in a browser.
 
M: The data model built by the JavaScript Object. Data is stored in JS objects.
V: HTML page
C: Call the JS object method to manipulate the JS object data. The JS object provides an Asynchronous Method for submission back to the database. In my mind, I call the database stored procedure.
 
The functions and even implementation methods of the JS object of this model are similar to those of. Net dataset + dataadapter. You can even share the same set of stored procedures and front-end systems.
 
With the flexibility of JS language and the rich DHTML expressiveness, you can achieve beautiful and interesting interface effects.
 
XML can act as an intermediary in this framework, but it cannot replace JS objects. Here, XML can be used as relationdb, and its relationship with JS objects is still like the traditional issue of ORM, however, JS is a dynamic language, and this ing is much better than in Java.
 
The above topic is still about db2js.
 
Looking back at the genre of interface development, we can find that the three main branches are joining.
 
One is magazine editing from the traditional printed advertisement design and the old industry. Its main capability is image-text mixing. HTML webpages, Word documents, and PDF documents are representative of them. In principle, if the word document does not take the platform binding path, its rich text expressiveness and rendering speed should have taken the lead in this aspect. Since Word documents are easy to understand, in this article, the representatives of the word family are naturally HTML.
 
An art photography film from film and photo processing in the old industry. Its main capabilities are painting and animation. Flash, GIF and Photoshop, and illustrator are their representatives. Even a small GIF makes the world a wonderful place. Think about the GIF waiting for pictures transmitted via QQ, which gives users a pleasant aesthetic while waiting. If the general UI has the stepless scaling of flash and the rendering capability of Photoshop, the visual effect may only be available in the game.
 
The third is the invention of the IT industry: window. Its main capabilities are inherent controls built with fixed locations and painstaking efforts by engineers. Windows and KDE are their representatives. Thanks to native API support, the speed is fast. In fact, if you think about it, the ancestor of the tribe can go up to the tribe of painting. Two aspects can be proved: 1. the tribe of painting naturally supports absolute positioning. We can easily regard what happens in the window as a role in the film. 2. The painting tribe did develop its own window system, such as the flash control library. The criterion for distinguishing the two is self-painting/API, just as swing is in AWT.
 
We can find a trend, and these three are gradually integrating.
 
At the beginning of the day, the shadow of the character interface covered the entire computer world.
Later, the window was dominated by bright icons and rich UI elements.
The emergence of HTML declares that another branch has entered the UI battlefield. It should be noted that the webpage stage is not a specific computer. html cleverly chooses WWW as the stage. With almost no competitors, the UI sky of the Internet becomes the color of HTML.
Later, HTML added form elements, introduced some simple window functions, and added the meaning of a control to the "Graph" character in the text-and-text mixing.
After a long time, flash entered the interface battlefield, and its initial appeal was similar to that of GIF, with a piece of cake in the "image" on HTML.
At first, the tribe of the window tried to mix ActiveX and HTML with javaapplet, but it was not successful. The plot was intriguing. I think one of the main reasons is that the person serving as the interface is an artist, and it is difficult to get started with window systems that need to understand a lot of APIs.
 
After a failed attempt by the tribe of windows to squeeze into HTML, he continued his dream of a single computer UI and invented new elements such as translucent windows. The browser for text-and-text mixing is also a window, so the tribe of the window thinks that the lifeblood of the graphic tribe is in its own hands, there is no consortium to take the initiative to mix HTML, not to move into the core content of HTML: text mixing. Imagine the button of the window system. If it can be transformed into a text-and-text hybrid arrangement, you can copy the text on the interface, or even paste the entire window elsewhere. For users, this kind of UI is at least much more convenient for online searching for fault causes.
The slowness of the window system and the failure to squeeze the window into HTML may make us realize that the original programmer's UI concept is sometimes incompatible with the general user's UI concept.
For a long time, as programmers, we convert to the tribe of windows. Our first surprise was createwindow. From that day on, we had no <button> </button> in our hearts. If you want to make a slightly complex UI, you have to use a lot of challenging self-painting to complete it. For example, when using Delphi, if the customer needs a grid with odd and even colors, they need to derive their own mesh to implement it. In fact, it is easy to implement these things in HTML. Whether it is object-oriented or the purpose of object-oriented is important, which deserves our consideration.
 
Tiancai developed a script system for HTML, allowing the interface maker to control the elements on the web page. At the same time, HTML has gained a capability: CSS.
The former gives HTML dynamic capabilities, allowing it to simulate the response of the window system. In addition to batch formatting, the latter also unexpectedly gives HTML the ability to layer, allowing it to simulate the window-and the layers of the animated tribe.
With these two capabilities, HTML is renamed DHTML.
Because the website UI developer is mainly an artist, these people bring together the best understanding of the beauty of human beings, it is easy to promote the UI performance of text and text mixing to far beyond the window tribe.
 
After receiving strong support, the tribe of HTML became restless and sought to defeat its own life. It may also be that programmers from the tribe of windows have a unique understanding of the tribe after discovering its potential. HTML introduces XML + XSLT web pages. Looking back at this XML revolution, the idea behind it is the separation of data and performance. In view of this concept and the concept of text-and-text mixing, I am afraid it is difficult to succeed.
 
At the same time, the tribe of animation is also booming. The tribe, with flash and Its ActionScript, fully includes the tribe of windows in its own bag. It is reasonable to say that this tribe has the greatest potential, but since there is no local API support, its rendering speed is always different from that of the tribe of windows. In addition, the commercial pursuit of the website has pushed it to the hateful throne of advertising, and has become the target of all, and has lost its talents.
 
Looking back at what happened in the past and observing the recent industry, the starting point of the future has become vaguely visible:
 
Vertices use Ajax technology to exert greater power on the browser stage, but they do not yet have the ability to draw and vector animations. The future direction may be SVG.
 
In the past, under the guidance of Macromedia, the flash of the painting tribe had already been replaced by GIF alternatives, and even relied on RAI on the server side to attack the city. Adobe, now the leader in Flash management, proposed the grand idea of using flash as the desktop. Since it can already include windows, as long as the graphic and text mixed markup language capabilities are introduced to further improve the rendering speed, this kind of inherent cross-platform UI, even if you do not use flex, relying on the Web server, which is born regardless of the platform, is also a terrible force.
 
The window tribe has also realized that the Vista interface is defined using the HTML-like XAML, and the full picture and text are mixed and arranged. The concept of playback is re-introduced to make the interface behavior have the characteristics of animation. This behavior can also be understood as a mix of text and text to achieve great competition, or a mix of text and text into an API-level mix of text and text. To consider this new UI, you only need to change the CSS to implement the previously coveted skin swap function. You can even modify the XAML, adjust the interface definition, and relay the menus and buttons.
 
In a world of peace and love, there is no national border or smoke. No more pure HTML static pages or square windows. Integration is the trend of the times, and the ultimate benefit is the user.