Longhorn era, the end of the browser?
- About Avalon and XAML
After reading the browser war, I can't calm down, maybe I haven't come out from the scene of the scene, but the peace of human beings, it is indeed a bit of bitterness, in this era of rapid development. We actually be killed for more than 2 years (exactly, it should be that IE5 came out later, so we should be close to 5 years), we need some fresh things to stimulate our gradually numb nerves.
When I heard Longhorn, I didn't know how special features of the guy called "the long-range". It is worthy of the Trinity to pay all the family. I have known as three innovative technologies, and there are some technologies. Quirky code: Avalon, Indigo, Winfs, I don't know if this stuff is not a future WINDOW .NET Server 2005 OR / 2006. We don't have to expect, maybe the date I will use the system name I predicted, maybe it is a code, just hope that the code can be so good, can read it, wait until I see XAML, I finally These codes are tossing, and it should be pronounced "Zammel" finally read "tortured".
Ok, the words come true, the next version of the next version of "Longhorn" is an important milestone. "Longhorn" is the first operating system built with a managed code, and the latest storage subsystem is first adopted ("Winfs"), this storage system is a revolution in the file system concept. It is also the first operating system that supports Natural Search Technology (Natural UI), which automatically solves a large number of polymity issues inherent in the query text. Longhorn contains 3 revolutionary technologies, the first is a graphic and presentation engine code "Avalon", the second is a new communication architecture of "Indigo", and the third is a new file system "Winfs". The graphic display engine code to be Avalon is displayed based on XML, while Longhorn-based applications can be written in addition to traditional VB.NET, C # can be written while introducing a new XAML language.
What is Avalon
Avalon is part of the next version of Windows (Cycord "longhorn"), mainly composed of a set of classes in the new .NET framework. Currently, the most important new namespace for Avalon has multiple names, for example, Msavalon.Windows, Msavalon.Windows.Media (these names will be changed). With AVALON, you can use C #, Visual Basic® .NET or any other language to support .NET Public Language Normative (CLS) to write applications. These programs are similar to the current WINDOWS form applications that are currently writable. That is, the standard part of Avalon.
What is XAML
Avalon will define a new tag language that can be used in Longhorn, which is called "XAML" (Extensible Application Markup). You can use XAML to define the layout of text, images, and controls, which is very similar to using HTML. Most writes Avalon applications may contain both program code and XAML. You will use XAML to define the initial visual interface of the application and write code used to implement other functions. You can embed the program code directly into XAML, or you can keep it in a separate file. All functions that can be implemented with XAML can be implemented by program code. Therefore, there is no need to write programs at all without using any XAML. However, it will not be possible; many tasks can only be completed by the program code, so only the simplest application will only include XAML. With the XAML element, you can control the layout of each page, including the display of text and images, insert buttons, text boxes, and the like interactive components. In summary, XAML is a language used to present a user interface that makes a page that makes an application in a declaration. Of course, in addition to using XAML, you can also use the process code to write longhorn applications. In general, a Longhorn successful application will have XAML pages and managed process code at the same time. You can combine them in your own way, but any combination of both is acceptable.
How does Avalon and XAML work?
Let's take a look at an XAML code, which is the most classic "Hello World" program. The following code is stored into helloworld.xaml.
Background = "blanchedalmond" Fontfamily = "COMIC SANS MS" FONTSIZE = " 36PT " Horizontalalignment = "center"> Hello, World! Because there is no code, you can load the helloWorld.xaml file directly into the LONGHORN version of Microsoft Internet Explorer, and then you will see content similar to a web page. You can also use a program called MSBuild to compile HelloWorld.xaml. Two other short files are required for this compile time (not shown here). One of the extensions that extends Proj or MsProj will provide some information about the program and list all the required source files (XAML, and other files). Another XAML short file is also required to indicate which XAML page appears when executing the program. Run the executable of Hello World, you will see a content similar to the Windows program. Figure 1 shows these two versions. In a sense, XAML and HTML pages are very similar, but because it is based on XML, it has a stricter specification, while the entire operating system of Longhorn has become its container because of the IE because it is executed under Avalon. It has a broader space. 1) layout option You can use Windows traditional dot matrix layout while supporting flow layout of HTML style. FlowPanel, DockPanel, TextPanel, etc. Each element can meet most of your requirements. 2) Event processing WINDOWS-based applications are not just to display web pages, they need to respond to user interface events in a very special manner. In this case, XAML must be supplemented by the actual programming code. You can put this code into a separate file or embed it directly into XAML. 3) Elements and objects If there are multiple elements on the page, you can use a model similar to HTML to process .DHTML identifies multiple event sources, the same processing logic, and the same implementation in XAML via window.event.srcelement. XAML VS HTML, browser disappears? To do this is a bit not meaningful, because this is not a level and conceptual comparison, but familiar with web programming friends should also find that this and html page are so amazing, I don't even think that there is no time when I started. Too many differences, just the scorpion of Microsoft. This time, I am failed, and the wrong outrageous, as for the reason, I will do a profound review in the back of the text, first to see the reason for misleading me. 1. The default HTML layout is Flow Layout, but the follow-up support of CSS can make most of the HTML element set Style = "Left: 50px; TOP: 30PX;" This attribute. 2. Event handling comparison classic ways is 3. Elements and objects can be accessed through DOM (Document Object Model), for a considerable part of the HTML element, can support time bubbling, as for event sources, in DHTML development through Window.Event.Srcelement. This property can be easily Get it, and the bubbling that needs to intercept some events can be transferred to the upper orientation of the above-level container through Window.Event.cancelbubble = TRUE. I thought this is the so-called XAML, I finally know that Microsoft is in the crowd, but I am too ignorant, that Indigo, let me understand the so-called Avalon and the so-called XAML is not imagined so simple. Longhorn's application model is "One Writing, N Deployment", Avalon as graphics drawing of XAML files in XML format, and the core of true underlying work is in Indigo. Indigo is that it will be based on Remote technology of the Public Language Runtime (CLR) provides a unified programming model and protocol stack. INDIGO combines the best features of .NET Remoting, ASMX, System.Messaging, and .Net Enterprise Services, enable developers to freely combine various functions, such as declarative transaction, plug-in listeners And transmission and serialization based on XML architecture. The seamless deployment of an application is done by Indigo, so the XAML code logic is also in Indigo unified management, this is the biggest difference with HTML itself, on the traditional browser, no matter how complex script code, large The part is considered for the UI display, and any system level message communication is limited by the container of the browser. Speaking here, we have to make another problem, is the desktop disappearing or the browser disappeared? At this time, I agree that you can consider the disappearance of the desktop, because all the code can download and compile the LONGHORN version of the browser, then since all the applications can run in the browser, is it to consider exiting the desktop app The historical stage, just when I was very pleased for my genius, I suddenly found that even the browser disappeared together, yes, the concept of browsers has also blurred ... From a sense, we have no desktop The concept of applying and browser application, by writing XAML, I can be able to implement any deployment, this time, the entire longhorn is a browser container, communication, and scheduling through Indigo, and Avalon is used to complete the UI Organization. Thinking after the revolution From the peak of the browser IE5 to the world of IE6, we all consider problems in such thoughts within a whole period, including the application and its architecture itself, we have an endless product, But no matter how it is used to never get rid of C / S, B / S these mainstream application architectures, although there are many Articheture and Pattern to guide and supplement our existing applications. However, it is still unable to get rid of the limitations of the two architectures, so Client is still the hotspot discussion in major communities, one can see that change is the occurrence of .NET's so-called Smart Client, Macromedia's Flash technology is also a source Rich Client àthin ClientàSmart Client Different Evolution Process A very good solution. The design idea of that Avalon and XAML is a bit beyond the scope I understand, which is based on the language of the mark defined. If the graphics engine will change our existing ideas, the browser disappears or forever? Look at today's longhorn, look at "torture", don't know if you can get another answer. Write behind: To be honest, write such an article makes me fight, I am always afraid of what is embarrassed. After XAML, "dust, soil", I like to see the evolution of new technologies, although some changes make us unacceptable However, it is still believed that this change can improve productivity. From the process of development of information technology, the old technologies will always be replaced by new technologies, and the browser, is destined to be replaced, as for some of what we mentioned today Technology (so-called big unified browser), then take time to verify Eric Liu 2004 year 5 month 19 day 5 am in Beijing
