|
XML(Extensible Markup Language) is a well known self-describe markup language. We can use it to describe the data object, and it allows more data structure constructions than other explicit markup languages such as HTML. The XML data structure description organism is the best solution for information sharing on the Internet. The standard of data structure, without communicate in advance, and the feature of self-description make data exchange much easier than others. It is becoming the first choice for enterprise data interchange. XPointer(XML Pointer Language) is a new allocating organism for XML. It improves the HTML's restriction that only HTML Pointer can point to document. Using the Fragment Identifier, we can easily refer the XML's document to any resources. This paper discuss about the planning and implementation of XML editor based on standard XML organism. From planning to implementation, steps by steps show the system structure and editor coding. The features of the editor include the browsing, editing, allocating and searching. The planning of editor is divided to three parts: the Graphic User Interface planning, the Powerful Locating Capability planning and Normalized Editing planning. The Graphic User Interface planning including several concepts: tree windows, document window, attribute window, partially display and selected display. The Powerful Locating Capability planning shows the Location Undo and Redo designing concept and implement the newest XPointer organism. TkXE has two pointing method, one is Basic Moving Function which support the user rapidly travel among nodes. The other is Searching Function which support the users allocate the specific segment on the XML documents. The function is like searching a function and attribute from a subtree, or the looking for a character among the paragraph. The Normalized Editing planing are based on Subtree Editing, Markup Function and Modification Undo and Redo designing concept. During the implementation that based on the planning concepts, the relationship between the XPointer and XML are discussed. Furthermore, the problems are identified and the solutions are found during the planning and implementation.
|