New technologies emerge and become popular in the field of scripting technology almost every day. Scripting technology introduces new rules and allows people to change the names of existing things on a whim. Suddenly, you call a technology but others don't understand it, and vice versa, others call it a technology and you know little about it, or even in both cases, you are referring to the same thing.
The purpose of this article is simply to provide an overview of the numerous script-based technical names and acronyms. Some changes were made to the names last year. Likewise, some technologies have become more mature and refined from their initial stages, while others have changed slightly but still use the original names (and thus seem a bit confusing now). But by the time you finish reading this article, everything will be clear. In order, please see below:
Dynamic HTML (DHTML) DHTML Scriptlets XML XML Scriptlets IE 5.0 Behaviors HTML Components (HTC)
The above names are larger in scope, but they are the names of typical scripting technologies available from Microsoft.
Dynamic HTML (Dynamic HTML)
Because Dynamic HTML (Dynamic HTML) first appeared in Internet Explorer 4.0, it is the ancestor of all Microsoft scripting technologies. Dynamic HTML (Dynamic HTML) can also be classified as "A" (for Active), which is a large number of engines, programming tools and technologies in use today.
Each web page is an organic combination of tags, paragraphs, forms, form elements in Windows, frames and tables, etc. When you think of this, you will have a rough understanding of the Document Object Model. The standard description made by the World Wide Web Proxy (W3C) details the hierarchy of content and access paths in web pages.
DHTML is a name that is often used to identify a way that IE4, IE5 and Navigator4 change a certain mode and use it to determine the mode of the current web page. The key is that these patterns support dynamic and script-driven changes to web pages using the code of the page itself. This opens up a new path for Web developers who write dynamic and interactive applications.
Editor's note: When the W3C publishes the DOM rules, it expects version 5 of both major browsers (IE and Nav) to enforce their DHTML according to this rule. In this way, even though Nav5 is suitable for DOM and IE5 is not, it will be easier for web administrators to create web pages that are compatible with both browsers, rather than having to execute DHTML differently in IE4/Nav4 browsers as is currently the case.
Dynamic HTML Scriptlets (DHTML Scriptlets)
DHTML supports organizing various types of content in a web page to achieve many special effects. Using these codes, these contents and functions can be reused in multiple pages. In this process, "cut" and "paste" are usually used, but sometimes there is not much repetitive work required.
For example, paste SPANs & IMGs or TABLEs & anchors to create a completely new object with preset functionality and customizable parameters, or perhaps a TABLE and the Remote Data Service ActiveX control elements that enable the object to be displayed in various ways. item record. It is not a new markup, nor a new binary ActiveX control, but an HTML-based visual component: a DHTML Scriptlet.
A DHTML Scriptlet is an HTML page placed into another HTML homepage. The homepage has a main body and a set of script codes that can operate independently. It can also display some capabilities, methods and content. A DHTML Scriptlet is placed via the OBJECT tag and served from a simple HTML file. If there is a user interface, this kind of object can display some special functions. But it can also be a simple, unremarkable commercial object.
Originally known simply as scripts, components have lost much of their original value and have fallen out of favor, but it is the only way to create composite HTML controls that is possible. If you need a special visual HTML component that is a combination of multiple tags, then DHTML Scriptlets are the only option besides binary ActiveX controls. If the user interface is not a concern, or if you just want to improve the performance of a single element, you should take advantage of other script-based tools.
XML
XML is the abbreviation of eXtensible Markup Language, which provides a new development scope for Web applications. XML is becoming a widely used programming language for exchanging data on the Web. What is commendable is that its structure is similar to HTML but more rigorous. The importance of XML is that it is a programming language designed to create new script classes, which are real COM objects composed of script code.
XML Scriptlets
Today, XML Scriptlets are a confusing subject, and their original name, Server Scriptlets, is even more confusing. There's a big leap from Server to XML, but the original names are easier to understand:
1. They work like servers.
2. Most of them serve as server-auxiliary versions of DHMTL scripts to execute commands on the server.
XML Scriptlets are XML documents that include data and metadata that identify and define a COM object. The XML tag includes a CLSID, an automated control interface and script code. However, unlike a COM object, XML Scriptlets are not binary libraries, so what's the trick?
In fact, they depend on a DLL that distinguishes and demarcates script code in XML documents from so-called COM-aware applications. The application can identify the CLSID of the rule control, work with the DLL, and then place the script code into the XML to run.
Although DHTML and XML have the same names, they have very little in common, and web administrators can choose between them according to different needs. As shown earlier, DHTML Scriptlets function as both HTML-based and script-based components of the user interface. HTML-based components are used to create WEB pages. In the process from the Web page to the Windows Script homepage, script-based components play a role whenever script code is accepted. XML Scriptlets, on the other hand, are minified interfaces for users that serve as a secondary server backup when it comes to reusing some script code in ASP pages.
The next step in the development ofIE5.0 Behaviors
scripts is how they work in IE5.0 Behaviors. IE4.0 or higher supports DHTML and XML Scriptlets. At the same time, Behaviors is a special form of IE5.0. An IE5.0 Behavior is an XML Scriptlet that assigns a special function to an existing HTML tag or a set of tags. For example, linking from one page to another could add the ability to fade the background to achieve a gradient. Write a program that implements this function and briefly describe what will happen when the code is run and its results.
In a way, applying a behavior to a markup is similar to further dividing a Window into Win32. Applying a behavior simply assigns the name of a CSS class to the tag, and the Behavior attribute of this name is the URL of the XML Scriptlet. Behaviors are designed to replace DHTML Scriptlets, but they cannot create new combined HTML controls. They apply to a single tag, not multiple or interacting tags. (They most likely originated from Microsoft's XML Chromeffects project, which was unsuccessful).
HTML Components
Technically speaking, HTML Components (HTC) are XML documents that are slightly different from the original design compared to XML Scriptlets. But they include the same content and have the same browsing capabilities. HTCs code is simpler and more intuitive than XML Scriptlets. In addition, HTCs and XML Scriptlets are designed specifically for writing IE5.0 behaviors. XML Scriptlets are more commonly used to solve the problem of making script code reusable and into templates.
Summary
Over the past year and a half, we have observed and tracked some interesting initiatives involving web scripts. From DHTML Scriptlets to IE 5.0 behaviors and related technologies, XML Scriptlets are also applied in other fields such as Windows Scripting Host. XML is becoming increasingly popular, while HTML seems a bit outdated. But one thing remains constant, and that is the "script code" that must be applied to all technologies!