The WMF parser takes a WMF file as input, parses it to get and categorize the codes for its element types (e.g. As the former one, the converter also consists of two functional units: a WMF parser and an SVG converter. We have done another project in SVG: a converter which converts WMF file to SVG file. In Figure 8, we give the display of the rendering of the converted SVG file from the HTML file in Internet Explorer web browser, at the same time we give the source of the SVG file in the background of the figure. In Figure 7, we give the display of the rendering of an HTML file in Internet Explorer web browser, at the same time we give the source of the HTML file in the background of the figure. We are not attempting to give much detail about the programming and implementing of the project, but give some results which are enough to indicate the effort. In most cases, it converts the information contained in a pair of HTML tags to the resulting SVG equivalence which is contained in a pair of SVG tags. The SVG converter works on the HTML tags and properties and converts the information to the equivalent SVG representation. The HTML parser takes an HTML file as input, parses it to get and categorize the HTML tags and their associated properties. Basically, the converter consists of two functional units: an HTML parser and an SVG converter. We have done a project in SVG: a converter which converts HTML file to SVG file. Secondly, we describe part of our future work: the transcoding of events from the viewer to the resource, or from the user-facing I/O to the resource-facing I/O. The indication is that, our trial in the SVG projects is the initial effort in the implementation of a General Collaboration Web Service. This effort is in the direction we have described earlier from the resource to the viewer, or from the resource-facing I/O to the user-facing I/O it is motivated by the clue of implication: OpenOffice can save its presentation file (*.sxi) as PowerPoint file (*.ppt), and PowerPoint can save its presentation file (*.ppt) as HTML file, WMF file, and so on. In this section we first describe our initial effort in the implementation of a general Collaboration Web Service: a converter which converts HTML file to SVG file, and a converter which converts files in WMF format to SVG format. Thus, collaboration is achieved through the general Collaboration Web Service. As always, the Master client and the Participant client(s) of each resource type collaborate on event messages via the underlying communication of the NB event broker. More specifically, as described in the scenarios before, the speaker’s WS viewer is bound to the instance of the general Collaboration Web Service that has the Master client of a resource bound to it, and each audience’s WS viewer is bound to the instance of the general Collaboration Web Service that has the Participant client of the corresponding resource bound to it. On one end, a client of a resource (collaborative applications) finds and binds to the general Collaboration Web Service and cooperates with it through its resource-facing I/O on the other end, a WS viewer performs the same procedure to bind to the general Collaboration Web Service and cooperates with it through its user-facing I/O. The users or applications can find this Web Service using Universal Discovery, Deployment and Integration (UDDI), and then bind to it and use it via the internet, as in Figure 6. The information of this Web Service, such as its Universal Resource Identifier (URI) endpoint, its exposed methods, etc., is described in the Web Service Description Language (WSDL) file, and the Web Service is deployed and published to a Service Broker with this file. Suppose that we have developed our general Collaboration Web Service. Web Services enable developers and users to integrate functionality across businesses and organizations.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |