TWI582625B - Method for operating tool in working environment and machine using such method - Google Patents

Description

Method of operating a tool in a work environment and a machine to which the method is applied

The present invention relates to a method of operating a drive tool relating to a method of enabling a tool that is incompatible with a work environment to be executed in a work environment and a machine to which the method is applied.

In the modern convenience of life, people are accustomed to using electronic devices with computing power to perform various applications such as work, paperwork, entertainment, social communication, etc., and with the gradual development of science and technology, information spreads more quickly and in various ways. Web platforms, operating systems and software tools have been developed for people to use, to bring people a more efficient life; especially in the "post-computer era", in addition to traditional desktop computers, tablets, mobile phones and other mobile devices The emergence of people can access homepages around the world through their browsers and the Internet anytime, anywhere.

With the rapid development of the Internet, many web development technologies have been proposed for public use, although more diversification does bring many incompatibility issues; for example, based on any framework (such as Angular The tools written by JS) are difficult to adapt to operating environments based on other frameworks (such as Famous JS) without modification, and thus make it difficult to integrate operations effectively. Further, written by different frameworks Tools or work environments are difficult to integrate with each other due to factors such as different architectures, different naming rules, and even overlapping names.

Furthermore, although the tools and work environments written in the same framework are compatible with each other to enable the tool to operate in the work environment, it is possible for people to use the tools to perform unscrupulous behaviors, such as stealing web pages or making The web page jumps to other websites, so there are doubts about information security.

Based on the above description, there is an urgent need for a method in which any tool written in any framework can operate in any operating environment and does not constitute a security threat.

The main object of the present invention is to provide a method for operating a tool in a work environment, in particular, a tool that is incompatible with a work environment can be executed in a work environment by generating an inline frame (iframe) in a work environment. The method is to enable a variety of tools to be integrated in the operating environment and to take into account the information security of the operating environment.

In a preferred embodiment, the present invention provides a method for operating a tool in a work environment, comprising: providing a work environment in a browser in a browser that can run a unified tool; A software development kit (SDK) provided by the operating environment is used as a unified internal inline frame (iframe) generated in the working environment and in the working environment. At least one standard interface of at least one data and/or at least one instruction, and the software development package is compatible between the work environment and the unified built-in framework; and running the unified tool in the work environment; The operation of the unified tool is completed by generating a built-in frame in the working environment and loading an Adapter, and the converter is an original tool that is incompatible with the working environment and the Forming at least one standard interface to form a software module, and the operating environment is driven by the at least one standard interface to drive the unified tool In the primitive tools of the built-in frame.

In a preferred embodiment, the at least one profile and/or the at least one command is passed between the job environment and the built-in framework through a PostMessage function defined by an HTML5 Web Messaging specification.

In a preferred embodiment, the at least one standard interface is a driving interface used by the operating environment to drive the unified tool.

In a preferred embodiment, the original tool is integrated with the at least one standard interface by using and/or implementing a software function call provided and/or defined by the at least one standard interface.

In a preferred embodiment, the unified built-in framework is the unified tool.

In a preferred embodiment, the driving method includes: transmitting an initial instruction to the built-in framework to start the original tool in the built-in framework; and/or transmitting a close command to the built-in frame To close the original tool in the built-in frame.

In a preferred embodiment, a basic attribute of the unified tool includes a type and a link indicating where the original tool is located.

In a preferred embodiment, the type is used to define a component type, and the component type and the link are used to obtain a physical component necessary for the plug-in, management, or execution of the unified tool.

In a preferred embodiment, the original tool is a utility, an interface tool, an agent, an application, a service, or any Taken from an associated machine or an executable component of a server.

In a preferred embodiment, the working environment is a working environment of a working space, and the working space is constructed by a projectable space instance.

In a preferred embodiment, the projectable spatial real system is an object, an extensible markup language (XML) file, or a structured language or a structured protocol (structured) Protocol) An instance of an instance.

In a preferred embodiment, the present invention also provides a machine comprising: a browser for being in the form of a website and capable of running a unified tool A work environment is loaded therein; wherein a software development kit (SDK) provided by the work environment is used as a unified built-in frame for the work environment and the work environment. Passing at least one standard interface between at least one data and/or at least one instruction between (inline frame, iframe), and the software development package is compatible between the working environment and the unified built-in frame; and an execution a unit for generating the built-in frame in the working environment and loading an Adapter to form the unified tool that the working environment can run; wherein the converter is incompatible with the working environment A software module is formed by integrating an original tool with the at least one standard interface, and the working environment executes the original tool in the built-in frame through the at least one standard interface to drive a driving manner of the unified tool.

In a preferred embodiment, the at least one profile and/or the at least one command is passed between the job environment and the built-in framework through a PostMessage function defined by an HTML5 Web Messaging specification.

In a preferred embodiment, the at least one standard interface is a driving interface used by the operating environment to drive the unified tool.

In a preferred embodiment, the original tool is integrated with the at least one standard interface by using and/or implementing a software function call provided and/or defined by the at least one standard interface.

In a preferred embodiment, the unified built-in framework is the unified tool.

In a preferred embodiment, the driving method includes: transmitting an initial instruction to the built-in framework to start the original tool in the built-in framework; and/or transmitting a close command to the built-in frame To close the original tool in the built-in frame.

In a preferred embodiment, a basic attribute of the unified tool includes a type and a link indicating where the original tool is located.

In a preferred embodiment, the type is used to define a component type, and the component type and the link are used to obtain the plug-in, management, or execution of the unified tool. A necessary physical component.

In a preferred embodiment, the original tool is a utility, an interface tool, an agent, an application, a service, or any Taken from an associated machine or an executable component of a server.

In a preferred embodiment, the working environment is a working environment of a working space, and the working space is constructed by a projectable space instance.

In a preferred embodiment, the projectable spatial real system is an object, an extensible markup language (XML) file, or a structured language or a structured protocol (structured) Protocol) An instance of an instance.

3‧‧‧projectable space entities

4‧‧‧Working environment

6‧‧‧Projected workspace

7‧‧‧ Built-in frame

8‧‧‧Transformer

11‧‧‧First machine

12‧‧‧ second machine

13‧‧‧Tool cloud

14‧‧‧ Machine

21‧‧‧Software Development Kit

22‧‧‧Standard interface

53‧‧‧Calculator

51‧‧‧Unification tools

111‧‧‧Browser

141‧‧‧ browser

142‧‧‧Execution unit

971‧‧‧First electronic device

972‧‧‧Second electronic device

973‧‧‧projectable space entity

974‧‧‧Projecting means

975‧‧‧Working environment

976‧‧‧Projected workspace

977‧‧‧Microcore

979‧‧‧Dropbox

980‧‧‧ Unified script

981‧‧‧personal work space

982‧‧‧Dropbox

983‧‧‧Cloud Hard Drive

984‧‧‧Server

985‧‧‧ original information

985’ ‧ ‧ Unified Information Unit

986‧‧‧Original tools

986’‧‧‧First unified tool

987‧‧‧ original tools

987’‧‧‧Second unified tool

991‧‧‧ original elements

992‧‧‧Element converter

993‧‧‧Unified data structure

994‧‧‧ unified elements

1111‧‧‧ Path Link Information

9731‧‧‧ Unified script

9761‧‧‧dotted box

9761’‧‧‧Dropbox Input

9762‧‧‧dotted box

9762’‧‧‧ Picture Reader

9791‧‧‧jpg image file

9791’‧‧‧Unified jpg image file

9792‧‧‧jpg image file

9792’‧‧‧Unified jpg image file

9793‧‧‧gif image file

9793’ ‧ ‧ unified gif image file

9881‧‧‧Information input device

9882‧‧‧Information Input

9883‧‧‧Information input device

P1‧‧‧ steps

P2‧‧‧ steps

S1‧‧‧ initialization instructions

S2‧‧‧End order

S3‧‧‧ Calculation instruction set

S4‧‧‧ Results Information

989‧‧‧Transformer

Figure 1: Schematic diagram of the implementation concept of the unified method in one embodiment.

Figure 2: A diagram showing a better concept of a unified script as an intermediate language for implementing a personal workspace.

Figure 3 is a schematic diagram of a preferred configuration of the personal workspace shown in Figure 2.

Figure 4 is a schematic diagram showing the initial state of a method of projecting a workspace in a preferred embodiment.

FIG. 5A is a schematic diagram showing the operation of the method of projecting the workspace shown in FIG. 4. FIG.

FIG. 5B is a schematic diagram showing the operation of the method of projecting the workspace shown in FIG. 4. FIG.

Figure 6 is a schematic diagram showing the relative relationship between the projectable spatial entity shown in Figure 4 and the projected workspace shown in Figure 5B.

Figure 7 is a flow chart of a preferred method of the method of the present invention for operating a tool in a work environment.

Figure 8: In the step P1 shown in Figure 7, the website is provided in the browser form. A preferred schematic of the operating environment in which the unified tool is run.

Figure 9 is a preferred schematic diagram of generating a built-in frame and loading the converter in the working environment in step P2 of Figure 7.

Figure 10 is a schematic diagram of a preferred operation of the calculator of Figure 9 performed in a work environment.

Figure 11 is a block diagram of a preferred embodiment of a machine for applying the method of operating a tool to a work environment of Figure 7 in accordance with the present invention.

The invention will be more fully understood from the following description, including the <RTIgt; For the sake of brevity, the publications cited in this specification, including the disclosure of patents, are hereby incorporated by reference.

The following examples of the invention are non-limiting and represent only a variety of aspects and features of the invention. In the most limited technical sense, the term "information source" as used herein refers to a sequence of symbols that can be interpreted as useful information, and such useful information is used to organize and tag data; wherein the source of information may include : Websites (such as Internet services), internal networks, online communities, software, e-books, databases, and other informational media (such as storage media available for non-transitory computers, mobile device storage media). Moreover, the "original information" described herein may include files, web pages, databases, policies, rules, or any data accessible to related machines and servers, and the "original tools" described herein may include utilities. An interface tool set, a smart agent tool, an application, a service tool, or any executable element that can access related machines and servers. However, the source of information, original information and original tools are not limited to the above.

Moreover, "original information" and "original tools" are one embodiment of the "original elements" described herein, and in the implementation of the present invention, multiple "original elements" from the same or different "information sources" Each can be modeled into multiple "unified elements" through a unified method, so that multiple "unified elements" in the same working environment can be compatible with each other to coordinate specific tasks; "Unified tools" and "unified information units" are all examples of "unified elements." Also, the "element converter" described in this article (Matterizer) is a component, device, or code used to unify the "original elements."

In an embodiment, the unified method may be: reconstructing original information obtained from at least one information source of the plurality of information sources according to a unified data structure, thereby modeling the original information into unified information. Unit, and/or reorganizing the original tool obtained from at least one information source of the plurality of information sources according to another unified data structure, thereby modeling the original tool into a unified tool; wherein the unified data structure and the Another unified data structure may be the same or different, and the above unified method may be implemented by an element converter (Matterizer).

Please refer to FIG. 1 , which is a schematic diagram of the implementation concept of the above unified method in an embodiment. 1 illustrates an element converter 992 reforming an attribute and an associated link of the original element 991 in accordance with the unified material structure 993 to model the original element 991 as a unified element 994, such that the basic attributes of the unified element 994 include The type of the original element and the link that indicates where the original element is located.

In this embodiment, the original element 991 includes at least the original information (not shown) or the original tool (not shown), but is not limited thereto. Secondly, in the above unified method, when the attributes obtainable from the original information correspond to the attributes to be unified in the unified information unit, the unified information unit can be directly generated via the element converter 992; When the attributes obtained by the original information cannot correspond to the attributes that are to be unified in the unified information unit, the original information must be redefined by logically reorganizing the attributes and related links of the original information, so that the original information is converted into The new original information corresponding to the attributes that are to be unified in the unified information unit, thereby indirectly generating a unified information unit.

Moreover, the type of unified tool is used to define a component type, and the component type of the unified tool and the link where it is located are used to obtain a physical component necessary for the plug-in, management, or execution of the unified tool. When the original tool is compatible with the working environment of the workspace, the unified tool can be directly generated via the element converter 992; and when the original tool is incompatible with the working environment of the workspace, An adapter (or SDK) and/or a software development kit (SDK) of the original tool drives the original tool to indirectly generate the unified tool; wherein the adapter is used to provide a workspace-compatible interface implementation (interface implementation).

Regarding the "specific implementation method of the unified method" and "system" described in this embodiment The specific method of obtaining the element and the specific mode of operation of the elemental converter can be found in US Patent Application No. 14/324,069, entitled "A METHOD OF UNIFYING INFORMATION AND TOOL FROM A PLURALITY OF INFORMATION SOURCES", and a reference to the claim. U.S. Patent Application Serial No. 14/324,069, the entire disclosure of which is hereby incorporated by reference in its entirety, the entire entire entire entire entire entire entire entire entire entire contents "Device", so it will not be repeated here.

In particular, the above unified method is only one embodiment of the unified method adopted in the present case, and the method for unifying multiple original elements from different information sources is not limited to the above, and those skilled in the art can Make any equal change design based on actual application needs.

The following is an example of a unified method different from the above description. The first unified method is applied to the information unification method in Garmin satellite navigation. The Point of Interest (POI) function of Garmin satellite navigation is the original landmark information input through the information unification method (original Information) to achieve a unified program to obtain the corresponding unified landmark information (unified information unit); the second method is a unified tool for Android (Android) system, Android (Android) system is a Linux The basic open source mobile device operating system, but the applications (original tools) in the Android system are mostly written by Java, so the application (original tool) written by Java can be unified through the tool. It is modeled as a unified application (unified tool) that is compatible with Android, and can be executed in Android.

Furthermore, the term "workspace" as used herein refers to a workspace that allows at least one element converter and/or at least one tool and/or at least one piece of information to interact to perform a particular task, and at least one information and/or At least one tool can be input into the workspace by at least one element converter, but the manner in which information and/or tools are input into the workspace is not limited thereto; secondly, the information importer (information importer) described below (the information input devices 9881, 9882, 9883 in FIG. 2, the Dropbox input device 9761' in FIG. 6, and the information input device 52 in FIG. 9, FIG. 12A to FIG. 14B, etc.) are all one of the element converters. Implementation. Furthermore, the "unified script" described in this article refers to the intermediate language that can be used to implement the workspace, and through the "unified script" At least one element converter and/or at least one piece of information and/or at least one tool may be provided (eg, built-in or plug-in) to the workspace.

In one embodiment, the at least one information is at least one unified information unit formed by the at least one original information obtained from the at least one information source, and the at least one tool is from at least one information. At least one original tool obtained by the source is formed by at least one unified tool formed by being unified; wherein the user can select the required unified information unit and/or the unified tool according to different tasks. The information source is added (such as built-in or plug-in) to the personal workspace, so the "workspace" can be a user-oriented "personal workspace."

Further, please refer to FIG. 2 and FIG. 3 . FIG. 2 is a schematic diagram of a better concept of a unified script as an intermediate language for implementing a personal workspace, and FIG. 3 is a schematic diagram of a preferred configuration of the personal workspace shown in FIG. 2 . . 2 and FIG. 3 illustrate the unified information unit 985' corresponding to the original information 985 in the Dropbox 982, corresponding to the compatible original tool 986 in the cloud hard disk 983 according to the requirements of the task. The first unified tool 986' and the second unified tool 987' corresponding to the incompatible original tool 987 in the server 984 are combined into the personal workspace 981; in detail, the user can edit one for the first time. As a unified script 980 for realizing the intermediate language of the personal workspace 981, the information input device 9881 of the Dropbox 982, the information input device 9882 of the cloud hard disk 983, and the information of the server 984 are configured by the unified script 980. The input device 9883; wherein the information input device 9881 can unify the original information 985 in the Dropbox 982 into the unified information unit 985' and input to the personal workspace 981.

Moreover, Figures 2 and 3 also illustrate that the original tool stored in the cloud hard drive 983 is a compatible original tool 986 (i.e., the compatible original tool 986 can be unified with the personal workspace 981). The component is structurally compatible with the tool, and the first unified tool 986' corresponding to the compatible original tool 986 can be directly provided to the individual through the unified script 980 (using the information input device 9882 therein) Work space 981.

Moreover, Figures 2 and 3 also illustrate that the original tool stored in the server 984 is an incompatible original tool 987 (i.e., the incompatible original tool 987 is used in the personal workspace 981 for the unified tool). The component architecture is incompatible) and must be compatible with the incompatible original through the unified script 980 (using the compatible converter 989 and the information importer 9983). A second unification tool 987' of the tool 987 is provided to the personal workspace 981.

In addition, FIG. 3 also illustrates that the user configures the arrangement (eg, grouping or placing) unified information unit 985', the first unified tool 986', and the second unified tool 987 according to actual application requirements. 'In a specific area of the personal workspace 981; finally, the user can save by using the unified tool in response to the unified tool and the operational relationship between the unified information units (such as click actions or drag actions between the two) Take or control the corresponding unified information unit to perform the required tasks.

Regarding the "unified script as a specific implementation of the intermediate language of the personal workspace" described in the embodiment, "the user unifies the required unified information unit and/or the required unit according to the actual application requirements. A specific implementation of a tool that can be freely combined into a personal workspace to perform a task. Reference is made to US Patent Application No. 14/325,466 entitled "METHOD FOR PERFORMING TASK ON UNIFIED INFORMATION UNITS IN A PERSONAL WORKSPACE" And the Chinese Patent Application No. 201410796528.4, which is entitled to the United States Patent Application No. 14/324,069, the entire disclosure of The computer program product and system of the method" will not be repeated here.

In particular, the above personal workspace is only an embodiment of the workspace, and the workspace applied to the present case is not limited to the above; for example, a unified script that implements the intermediate language of the workspace can be edited in advance. Make the workspace a workspace with built-in preset element converters and/or preset information and/or preset tools. Such workspaces are not limited to individual operations, but can also be used for multiple applications. The user operates simultaneously or separately.

Furthermore, the "workspace" described herein can be projected to any computing-capable electronic device (such as a cell phone, tablet, notebook, desktop computer, etc.) via a "projection workspace method". However, not limited to the above, any user can operate the "projected workspace" on any computing device.

In an embodiment, the method for projecting a workspace includes: first, obtaining a projectable space instance that is instantiated by a unified script via a path link information (URI); wherein, unified Script is defined to configure element conversion At least one of a device, information, and tools to build a workspace (as previously described), and a projectable spatial entity is used to create a projected workspace corresponding to the workspace to provide for operation element conversion At least one of a device, an information, and a tool to perform a task interface; then, using a projector to interpret the projectable spatial entity and establishing at least one of an element converter, information, and a tool to be configured The work environment in the projectable spatial entity to thereby execute the projected workspace, whereby at least one user interacts with the projected workspace.

The projection means can be obtained from a remote data station, a projectable space entity or a preloaded application, and loaded into an engine for providing a compatible environment to perform projection means, and the engine can be Including the Javascript engine, the Windows application, or the Linux application, but not limited to the above; in addition, the unified script can be defined by a file type (DTD), an extensibility markup language schema (XML schema), a structured language or a structured protocol, etc., but not limited to the above; and the space entity that can be projected can be an object, an extensibility indicator A language (XML) file, or an instance generated by a structured language or a structured protocol, etc., but not limited to the above.

Further, please refer to FIG. 4, FIG. 5A to FIG. 5B and FIG. 6. FIG. 4 is a schematic diagram of an initial state of the method for projecting the workspace in a preferred embodiment, and FIG. 5A and FIG. Schematic diagram of the operational concept of the spatial method. FIG. 6 is a schematic diagram showing the relative relationship between the projectable spatial entity shown in FIG. 4 and the projected workspace shown in FIG. 5B. In the initial state shown in FIG. 4, there are a first electronic device 971 and a second electronic device 972 that are connectable to each other (eg, connected through a network), and the first electronic device 971 stores a space that can be projected. Entity 973, and a projection means 974 is built in the second electronic device 972.

Moreover, the unified script 9731 is declared by a file type definition (DTD), and is defined to configure at least one information input device (which is an implementation aspect of the element converter) and/or at least one Unifying the information unit and/or at least one unified tool to model a workspace, and the projectable spatial entity 973 is an entity generated by an Extensible Markup Language (XML), as shown in FIG. Shown, is used to build a projected workspace 976 corresponding to the workspace, and is allowed to import information and/or unify information units and/or unification tools. In or remove from it.

Moreover, the projection means 974 of the second electronic device 972 establishes a working environment 975 for the projected workspace 976 on the second electronic device 972 and provides a micro core 977 (see FIG. 6) to the operating environment 975. Equiring at least one information input device and/or at least one unified information unit and/or at least one unified tool to be added to the projected workspace 976; wherein, when the second electronic device 972 is connected through a path When the information captures the projectable spatial entity 973 in the first electronic device 971, the projection means 974 in the second electronic device 972 begins to interpret the projectable spatial entity 973, as shown in FIG. 5A; After the projectable spatial entity 973 is interpreted by the projection means 974, the projected workspace 976 is created on the work environment 975 in accordance with the content interpreted by the projectable spatial entity 973, as shown in Figure 5B. The user at the end of the second electronic device 972 can interact with the projected workspace 976 via the second electronic device 972 to perform related tasks.

The relationship between the above-described unified script 9731, the projectable spatial entity 973, and the projected workspace 976 will be further described below using the usage scenarios shown in FIG. 6. The usage scenario shown in FIG. 6 is: creating a workspace that can be projected and can read the jpg image files and gif image files stored in the specified network space for the user to view, and in the context of the use, unified The script 9731 is declared with a file type definition (DTD), and the projectable space entity 973 is generated in an extensibility markup language (XML).

Moreover, a data input device and a unified tool are added to the projectable space entity 973, and the information input device is configured to input at least one unified information unit corresponding to the at least one original information to the projected work. In the space 976, in the context of use, the information input device is a Dropbox input device (ie, the dashed box 9761 is shown), and the original information is the jpg image file 9791, 9792 and the gif image file 9793 in the Dropbox 979 information source. The unified information unit is a unified jpg picture file 9791', 9792' and a unified gif picture file 9793', which will be described later, and the unified tool is a picture reader (ie, the dotted line box 9762). Used to read the image file input into the projected workspace 976.

Moreover, the projected workspace 976 is created after the projectable spatial entity 973 is interpreted by the projection means 974 in the second electronic device 972 such that the projected workspace 976 is provided with a Dropbox input 9761'. (corresponding to the dashed box 9761 shown) and one The picture reader 9762' (corresponding to the dashed box 9762 shown), the Dropbox input unit 9761' unifies the jpg picture files 9791, 9792 and the gif picture file 9793 in the Dropbox 979 information source and inputs them to the projected image. The workspace 6 is such that unified jpg image files 9791', 9792' and unified gif image files 9793' corresponding to the jpg image files 9791, 9792 and gif image files 9793 are presented on the projected workspace 976; When the user of the second electronic device 972 operates the unified jpg image file 9791', 9792' and the unified gif image file 9793' via a specific operation mode (such as clicking to unify the jpg image file) Any one of 9791', 9792' and unified gif image file 9793', or drag any of the unified jpg image files 9791', 9792' and unified gif image file 9793' to the picture reading The device 9762'), the picture reader 9762' will read the contents of any of the unified jpg picture files 9791', 9792' and the unified gif picture file 9793' for presentation by the user. Further, the above-described Dropbox input device 9761' and picture reader 9762' are equivated by the micro core 977.

Specifically, the path connection information of the projectable space entity 973 may be Hyper File Transfer Protocol (HTTP) path link information or File Transfer Protocol (FTP) path link information, and if the first electronic device 971 and the second electronic device are When the 972 is a common device, the path connection information of the space entity 973 that can be projected may also be linked to the local file, but the type of the path connection information is not limited to the above.

For a specific manner of obtaining a method for projecting a workspace as described in this embodiment, reference is made to US Patent Application No. 14/577,772, entitled "METHOD OF PROJECTING A WORKSPACE AND SYSTEM USING THE SAME", and a US patent can be referred to. Application No. 14/324069, No. 14/325,466, and No. 14/577,772, the entire disclosure of which is hereby incorporated herein by reference in its entire entire entire entire entire entire entire entire entire entire entire entire entire entire entire entire entire entire That is, it will not be repeated.

In particular, the above method of projecting the workspace is only a projection method for projecting the workspace to any computing device, but the projection method of projecting the workspace to any computing device is not To the above, it is well known to those skilled in the art that any equal change design can be made according to actual application requirements.

It then goes on to explain how the original tool is transformed into a unified tool and operates in the operating environment when the original tool is incompatible with the job environment. Please refer to FIG. 7, which is a tool for transporting the present invention. A preferred method flow diagram for a method of working environment. The method for operating the tool in the working environment includes: Step P1, providing a working environment in which a unified tool is run in a browser in a website form; wherein a software development package provided by the working environment is used as a working environment and Passing at least one standard interface of data and/or instructions between the unified inline frames (iframes) generated in the working environment, and the software development package is compatible with the operating environment and the unified Between the built-in frames; and step P2, running the unified tool in the working environment; wherein the running of the unified tool is completed by generating a built-in frame in the working environment and loading a converter, and the converter is not in phase a software module formed by integrating an original tool in the working environment with the at least one standard interface, and the working environment executes the original tool in the built-in frame by driving the unified tool through the at least one standard interface .

The method of operating the tool in the working environment shown in FIG. 7 will be described below with reference to an embodiment. In this embodiment, the working environment is the working environment of the working space, and the original tool that is not compatible with the working environment is a calculator from a tool cloud, but this is only an embodiment, and those skilled in the art can Any equal change design is applied to the application requirements.

Please refer to FIG. 8 , which is a schematic diagram of a working environment for providing a running unified tool in a browser in the form of a website in step P1 of FIG. 7 . Figure 8 illustrates a first machine 11 having a browser 111 that provides a compatible environment to perform the projection means as shown in Figures 5A and 5B, while the second machine 12 is provided with a projector that can be used to create a workspace. The space entity 3; wherein, when the first machine 11 end loads the projectable space entity 3 through the path link information 1111 of the projectable space entity 3, the projection means (not shown in FIG. 8, see FIG. 5A) And FIG. 5B) creates a working environment 4 for operation of the projected workspace 6 in the browser 111 and provides a micro-core corresponding to the projected workspace 6 (not shown in FIG. 8, see FIG. 6). The unified elements that are compiled into the projectable spatial entity 3 are loaded.

Please refer to FIG. 9 , which is a preferred schematic diagram of generating a built-in frame and loading the converter in the working environment in step P2 of FIG. 7 . Figure 9 illustrates that the tool cloud 13 is provided with a calculator 53 that is incompatible with the work environment 4, and in order to enable the calculator 53 to be executed in the projected workspace 6, a built-in frame 7 is created in the work environment 4. Loaded by converter 8 corresponding to calculator 53 In particular, the operating environment 4 provides a software development package 21, which is a standard development interface 22 for transferring data and/or instructions between the work environment 4 and the built-in framework 7 for pre-integration by the calculator 53, and a software development kit. 21 is compatible between the working environment 4 and the built-in framework 7; wherein the calculator 53 can use and/or implement a software function call and standard interface provided and/or defined by the standard interface 22. The integration of the 22 phases into a software module is well known to those skilled in the art and will not be described again herein, and the manner in which the calculator 53 is integrated with the standard interface 22 is not limited to the above.

Furthermore, the software module formed by the pre-integrated calculator 53 and the standard interface 22 is the converter 8, and when the calculator 53 of the tool cloud 13 is adapted to the projection means (not shown in FIG. 9, see FIG. 5A and 5B) When the result of interpreting the projectable spatial entity 3 is to be configured in the projected workspace 6, the converter 8 is loaded into the built-in framework 7 to become a unified tool that can be run in the working environment 4. 51. More specifically, at this time, the standard interface 22 is a drive interface used by the work environment 4 to drive the unified tool 51, and the work environment 4 can further perform calculation in the built-in frame 7 by driving the drive tool 51. On the other hand, in the preferred embodiment, the unified built-in frame described in step P1 of FIG. 7 is the unified tool 51.

Please refer to FIG. 10, which is a schematic diagram of a preferred operation of the calculator shown in FIG. 9 in a work environment. In the preferred embodiment, any data and/or instructions passed between the working environment 4 and the built-in framework 7 are performed through a PostMessage function defined by an HTML5 Web Messaging specification, but not When the working environment 4 wants to execute the calculator 53 in the built-in frame 7, an initial instruction S1 may be transmitted to the built-in frame 7 to start the calculator 53 in the built-in frame 7, and at this time, the calculator 53 The initial state is set to zero. Then, if a calculation instruction set S3 (such as 5+2) is transferred from the work environment 4 to the built-in frame 7 and received by the calculator 53, the calculator 53 performs calculations to make a result information. S4 (such as 7) is transmitted back to the working environment 4 by the built-in frame 7; finally, when the working environment 4 wants to close the calculator 53 in the built-in frame 7, a close command S2 can be transmitted to the built-in frame 7 to Then the calculator 53 is turned off.

According to the above description, the method of the present invention can make any tool of the incompatible working environment be executed in the working environment, which will facilitate the integration and application of various tools, and although the above working environments are all in the work space. The environment is exemplified, but it is not limited to this. Any type of work environment is applicable to the method proposed in this case.

In particular, since the tool creates a built-in frame in the work environment and loads a converter integrated with the tool and the standard interface, the tools of the incompatible working environment can be executed in the work environment. Even if there are unscrupulous people who want to perform unscrupulous behavior through tools, such as stealing data or performing web page jumps, only the built-in framework will be destroyed, and the operating environment itself will not be affected. Therefore, the operating environment is free from the threat of information security. .

Please refer to FIG. 11 , which is a block diagram of a preferred embodiment of a machine for applying the method for operating a tool to a working environment shown in FIG. 7 . The machine 14 includes a browser 141 and an execution unit 142. The browser 141 is loaded into a work environment in the form of a website and can run a unified tool, and the execution unit 142 is used to generate a built-in frame in the work environment. And loading an Adapter to form a unified tool for the operating environment to run the driver; wherein the software development package provided by the operating environment is used to transfer at least one between the working environment and the unified built-in frame. At least one standard interface of data and/or at least one instruction, and the software development kit is compatible between the operating environment and the unified built-in framework, and the converter is an original tool that is incompatible with the operating environment. The software module formed by integrating the at least one standard interface, and the working environment executes the original tool in the built-in frame through a driving manner of the at least one standard interface to drive the unified tool. The specific operation mode of the machine is the same as that of the above-mentioned FIG. 7 to FIG. 10, and will not be further described herein.

The above are only the preferred embodiments of the present invention, and are not intended to limit the scope of the present invention. Therefore, any equivalent changes or modifications made without departing from the spirit of the present invention should be included in the present invention. Within the scope of the patent application.

P1‧‧‧ steps

P2‧‧‧ steps

Claims (20)

A method for operating a tool in an operating environment, comprising: providing a working environment in a browser in a browser that can run a unified tool and provide a software development kit (SDK); The basic attribute of the unified tool includes a type of an original tool and a link indicating where the original tool is located, and the software development package provided by the working environment is used as a Transmitting at least one standard interface of at least one data and/or at least one instruction between the operating environment and a unified inline frame (iframe) generated in the operating environment, and the software development package phase Between the working environment and the unified built-in framework; and generating a built-in framework in the working environment and loading an Adapter into the built-in framework to generate and run the unified a built-in framework; wherein the unified built-in framework is the unified tool, and the converter is the original tool that is incompatible with the working environment and the After phase less a standard interface integrated software modules is formed by one, and the operating environment of the system to execute the original built-in frame of the tool through the at least one standard interface to drive the tool in a uniform drive. The method of operating a tool in a work environment as described in claim 1, wherein the at least one data and/or the at least one command is transmitted to the program via a PostMessage function defined by an HTML5 Web Messaging specification. Between the operating environment and the built-in framework after the unification. The method for operating a tool in an operating environment as described in claim 1, wherein the at least one standard interface is a driving interface used by the operating environment to drive the unified tool. A method for operating a tool in an operating environment as described in claim 1, wherein the original tool is a software function call provided and/or defined by using and/or implementing the at least one standard interface. ) integrated with the at least one standard interface. The method for operating a tool in an operating environment as described in claim 1 of the patent application, wherein the unified built-in framework is the unified tool. The method of operating a tool in a working environment as described in claim 1, wherein the driving method comprises: transmitting an initial instruction to the built-in framework to start the original tool in the built-in framework; and/ Or send a close command to the built-in frame to close the original tool in the built-in frame. A method for operating a tool in an operating environment as described in claim 1, wherein the type is used to define a component type, and the component type and the link are used to obtain plug-in and management of the unified tool. Or a physical component necessary for execution. The method for operating a tool in a work environment as described in claim 1, wherein the original tool is a utility, an interface tool, an agent, an application. , a service or any executable element accessible to a related machine or a server. The method for operating a tool in a work environment as described in claim 1, wherein the work environment is a work environment of a work space, and the work space is provided by a projectable space instance. Built. A method for operating a tool in an operating environment as described in claim 9 wherein the projectable spatial real system is an object, an extensible markup language (XML) file, or a structured An entity instantiated by a structured language or a structured protocol. A machine for a tool to operate therein, comprising: a browser for operating a unified tool and providing a software development kit (SDK) in a website form. Loading therein; wherein a basic attribute of the unified tool includes a type of an original tool and a link indicating where the original tool is located, and the software development package provided by the working environment And at least one standard interface for transmitting at least one data and/or at least one instruction between the unified inline frame (iframe) generated in the working environment and in the working environment, and The software development kit is compatible between the work environment and the unified built-in framework; and an execution unit for generating a built-in framework and loading an Adapter into the built environment In the framework, the unified built-in framework that can be run in the working environment is generated; wherein the unified built-in framework is the unified tool, and the converter is a software module formed by the original tool compatible with the working environment and the at least one standard interface, and the working environment executes the built-in mode by driving the at least one standard interface to drive the unified tool The original tool in the framework. The machine of claim 11, wherein the at least one data and/or the at least one instruction is transmitted to the operating environment and the unified after being passed through a PostMessage function defined by an HTML5 Web Messaging specification. Between the built-in frames. The machine of claim 11, wherein the at least one standard interface is a driving interface used by the operating environment to drive the unified tool. The machine of claim 11, wherein the original tool is a software function call and/or at least one standard interface provided and/or defined by using and/or implementing the at least one standard interface. Integration. The machine of claim 11, wherein the unified built-in frame is the unified tool. The machine of claim 11, wherein the driving method comprises: transmitting an initial instruction to the built-in framework to start the original tool in the built-in framework; and/or transmitting a close Direct the instruction to the built-in framework to close the original tool in the built-in framework. The machine of claim 11, wherein the type is used to define a component type, and the component type and the link are used to obtain a necessary one for attaching, managing, or executing the unified tool. Physical component. The machine of claim 11, wherein the original tool is a utility, an interface tool, an agent, an application, a service. Or any executable element that can be accessed by an associated machine or a server. The machine of claim 11, wherein the working environment is a working environment of a working space, and the working space is constructed by a projectable space instance. The machine of claim 19, wherein the projectable spatial real system is an object, an extensible markup language (XML) file, or a structured language or a An instance instantiated by a structured protocol.