Tool bar icon having embedded link for worldwide web document and internat enable type graphical user interface with integrated web browser

Description: TECHNICAL FIELD [Detailed description of the invention]

【0001】

[Industrial application field]

The present invention relates generally to graphical user interfaces, in particular to designing graphical user interfaces in which toolbar icons are linked to corresponding web documents that are loaded and executed when those linked icons are selected. Regarding.

【0002】

[Conventional technology]

Graphical user interfaces (often referred to as GUIs) are well-known mechanisms by which users can interact with computer programs and files. A typical GUI supplies a set of selectable icons, each associated with a file that can be accessed by a particular operation or controlling program supplied by the program that controls the GUI. To do. A user who wants to launch an operation from the GUI does so by selecting the appropriate icon (eg with the mouse). For example, a word processor user can activate spell checking on an active document by selecting the spell checking icon from the word processor toolbar. Similarly, the user selects the file icon, drags the selected icon to another icon representing the destination directory, and then drops (deselects) the icon from one directory to another. You can move files. This type of GUI design is also suitable for launching a standalone program (for example, by double-clicking on an icon that represents an executable program).

【0003】

In each of these cases, the immediate operation triggered by icon selection must be local to the network or computer hosting the operating system or application program displaying the selected icon. It doesn't become. This means, for example, that the icon cannot be directly associated with an executable program located on a remote system. Instead, in the prior art, the execution of a remote program is performed by rinsing the icon for the remote program to a locally executable program that establishes communication with the remote system, and then downloading and executing the remote program to the local system. It can only be done indirectly. Of course, this scheme only works when the remote program is precompiled so that the local program and the remote system can support compatible communication modes and (it) run on the local system.

【0004】

Therefore, a graphical user who links an icon to a remote object, such as a program or file, so that the remote object can be downloaded and / or executed using the services of the operating system or the application displaying the icon. -There is a need for an interface. There is also a need for a GUI such that local services that handle icon selection events and remote objects can be associated with a host system that ensures that the remote system stored on it can communicate. Moreover, it is desirable that all executable, remote file subsets be executable on any system that is guaranteed to be able to communicate with the remote system. These features link the World Wide Web (WWW), which links many of the servers that make up the Internet, each storing documents identified by its own general-purpose resource locators (URLs). It is carried out in "). Documents stored on a web server are placed in a standard document description language called HTML (Hypertext Markup Language). Using HTML, web document designers associate hypertext links or annotations with specific words or phrases in a document (these hypertext links provide information about a word or phrase to others. (Identifies the URLs of a web document or other parts of the same document) and can identify visual aspects and content of web pages.

【0005】

A document stored on the WWW using a web browser (a computer program designed to display HTML documents and communicate with a web server) running on a web client connected to the Internet. To access. Generally, this is done by a user who has selected a hypertext link in a document that is viewed in a web browser (commonly displayed by the web browser as a highlighted word or phrase). .. The web browser then issues an HTTP (Hypertext Transfer Protocol) request for the requested document to the web server identified by the URL of the requested document. In response, the specified web server also uses HTTP to return the requested document to the web browser.

【0006】

The standard HTML syntax of web pages and the standard outpatient protocol (HTTP) supported by the WWW ensure that any web browser can communicate with any web server. However, until the invention of the Java programming language and Java applets, there was no way to supply platform-independent application programs across the Internet and WWW.

【0007】

An important feature of the Java programming language is the architecture of programs written in the Java language-independence, and Java, which means that they can be run on any computer platform that has a Java interpreter. Includes verifiability of the integrity of such programs, which means that the integrity of the programs can be verified prior to their execution. The Java program verifier ensures that the program cannot overflow or underflow the operand stack of the computer on which the verified program is running, and that all program instructions only display data of known data types. Determine if it complies with certain stacking and data usage restrictions that ensure utilization. As a result, Java language programs cannot generate object pointers and, in general, cannot access system resources other than those resources that explicitly grant permission for use by the user. As a result, when one or more code fragments are downloaded to the client along with the associated form or image file, the Java-compatible browser running on the client displays the image or fills out the form. You can validate and execute downloaded code fragments that you need.

【0008】

[Problems to be Solved by the Invention]

Therefore, Java-compatible web browsers can download Java applets that are guaranteed to run on local systems from any WWW server. However, existing web browsers only download web documents depending on the user selecting the hyperlink on the web page currently displayed by the browser, or the user entering the URL in the browser. It is configured as follows. Web browsers provide services for these webs depending on the user selecting the icon associated with the remote object, executable program (standalone program or applet) or other file from the GUI. Not configured as. Therefore, there is a need for a GUI that provides icons that can be associated with local or remote files and programs. Then, when the icon associated with the remote file or program is selected, this GUI should call the local web browser service on the remote filter or program's URL and, if possible, download it to the local machine. The result is a file or program that is executed and executed, and all other objects referenced in such file or program.

【0009】

An object of the present invention is to provide a system and method capable of supplying icons that can be associated with local or remote files and programs in view of the problems in the prior art.

【0010】

[Means for solving problems]

An object of the present invention is that in a first computer having a display and memory, the first computer is networked with a set of remote computers, the components of which are constrained to exist only on the computer. A system for invoking the loading and execution of non-composite documents from the graphical user interface displayed on the first computer: It has a set of selectable icons, each icon of which is relevant. A viewable toolbar associated with one or more operations launched through icon selection; a set of references to the components or files each required to perform one or more of the associated operations. A set of complex documents, each of which has a file type selected from an applet or data file and a subset of files that have a locally or remotely selected location; each set of documents with one of the icons. A set of links; and icons associated with one or more of the links, each selected from a local link when the document is stored on the computer or from a network link when the document is stored on a remote computer. When one of the loaded files is selected, the computer is loaded with the file referenced in the document associated with the selected icon via a set of links and one of the loaded files is executable. Achieved by a system equipped with a computer that is configured to perform, thereby invoking the operation associated with the icon.

【0011】

In the systems of the invention, applets may be written in a platform-independent computer language that is interpreted and executed in a virtual machine implemented by a browser. In the system of the present invention, the platform-independent computer language may be configured to be Java. In the system of the invention, the compound document is an HTML document, and each of the references is a URL from the filename when the location of the referenced file is local, or when the location of the referenced file is remote. It may be configured to be selected from. In the system of the present invention, when an icon linked to an HTML document is selected, the browser loads and runs the applet, thereby performing all operations and user and system interactions associated with the selected icon. To coordinate and control; the HTML document may be configured to contain a single reference to the applet that coordinates all of the operations associated with the icon.

【0012】

The system of the present invention further comprises an icon specification file associated with one applet, which indicates a set of input files on which the associated applet should be manipulated. May be configured to be unconstrained to be positioned only on the first computer.

【0013】

In the system of the present invention, each of the input files remotely stored in the first computer is referenced by the URL of the applet specification file, and each of the input files stored in the first computer is a local route and a file. It may be configured to be referenced by name. It is also an object of the present invention to load a composite document that is not constrained to have that component only on a first computer that is networked with a set of remote computers that can host a subset of the component. And how to launch the run from the graphical user interface displayed on the first computer: display a toolbar with a set of selectable icons, each icon selecting that icon. Associated with one or more operations launched through and linked to one or more composite documents, each with a set of references to the components or files needed to perform one or more of the related operations. Each of the subsets of files, including, has a file type selected from an applet or data file; one or more composites linked to the selected icon by selecting one of the icons. Loading the document; by loading one or more compound sentences, the file referenced in the compound document is loaded, and the file is not constrained to exist only on the first computer; and is loaded. When the file has a type selected from an applet or a stand-alone application, it is achieved by a method that includes a step to execute the loaded file.

【0014】

In the method of the invention, the applet may be written in a platform-independent computer language that is interpreted and executed in a virtual machine implemented by a browser. In the method of the invention, the steps of loading one or more compound documents are: Local routes and files supplied to the linked compound document when the compound document to be loaded is stored on the first computer. Search for compound documents by name; and when the compound document to be loaded is stored on one of the remote computers, using the network node and file name supplied for the linked compound document. A stage may be provided for issuing a document request message for a compound document over a network.

【0015】

In the method of the invention, the step of loading the file is: When the referenced file is stored on the first computer, it is referenced using the local route and file name provided for the referenced file of the reference. Searches for referenced files; and when the referenced file is stored on one of the remote computers, references across the network using the network node and file name supplied for the referenced file for reference. It may be provided with a step of issuing a document request message for the file. In the method of the invention, the compound document is an HTML document, and each of the references is selected from local references when the referenced file is stored on the first computer, or a set of referenced files. It may be selected from the general-purpose resource locator (URL) when it is stored in one of the remote computers.

【0016】

In the methods of the invention, the HTML document comprises a single reference to the applet that coordinates all of the operations associated with the icon; and the loading and executing phase comprises loading and executing the applet. All operations and user and system interactions associated with the icon selected by may be coordinated and controlled.

【0017】

[Action]

The present invention has been demonstrated by directing a computer networked with a set of remote computers to display a set of components of a graphical user interface and by selecting one or more of the displayed sets of components. A computer configured to initiate an operation-a readable memory. This computer memory includes browser software and a toolbar specification that defines the features associated with a set of components. More specifically, the toolbar specification defines a set of visual attributes for each component in a set of components and a set of links to related files.

【0018】

A set of visual attributes defines the appearance (outline) of a component when viewed by a computer. Each link in a set of links associates a component with a document that contains a reference to a file that needs to implement the operation associated with the component. The referenced file can have a type selected from an applet or data file and can be located on one of the computers or remote computers. As a result, the link can be selected from a local link to a file stored on the computer or a network link to a file stored on a remote computer. Given these data structures, when one of the components is selected, the browser can load and execute the file referenced in the document associated with the selected component via a set of links. Instruct the computer to execute one of the loaded files.

【0019】

Further objects and features of the present invention will be more easily apparent from the following detailed description and claims with reference to the accompanying drawings.

【0020】

[Example]

See Figure 1, at least three computers: A 102A, B 102B, and C Computer network 100 with 102C is shown. Each computer 102 includes a processor 104, fast, main memory (eg, RAM) or slower, secondary memory (eg, hard disk drive), memory 106, and display 108. Computers 102 operate according to well-known computational principles (ie, each computer 102 is a program in its memory 106 under the control of an operating system (not shown) that provides system services for the program it is running. To execute). In a preferred embodiment, the networked computer of the present invention can communicate using a standard communication protocol (such as HTTP) and a platform independent program can be downloaded and executed over the network from within the browser software. The interconnection 103 between the computers 102 is provided by the Internet, which is applicable to any environment where it is possible. For the purposes of illustrating the operations of the present invention, it is assumed that there is no network operating system that coordinates file exchange operations among the three computers A, B and C.

【0021】

Details of the invention are described herein with respect to the particular implementation shown in FIG. In this implementation, the user interface of the invention is, among other things, executable programs (Java applets and stand-alone executables) and non-executable files (image files) in a collection called a portfolio to the user. And Java class library), it is embedded in an application called Java Workshop (JWS) program 150A. In a major break from the prior art in the area of programs and file managers, JWS Program 150A allows users to generate and work with portfolios that are remote (stored away from the user's machine or local network) or local. It has an integrated (integrated) JWS browser 154A. In addition, JWS Browser 154A assembles the portfolio into a mix of local and remote "projects".

【0022】

The term "project" is defined for the purposes of this document to mean a component of the portfolio.

【0023】

The user interface of the present invention is like a portfolio composed of both local and remote projects by providing a single paradigm for working with all objects regardless of their position. Facilitates user interaction with mixed objects. Of course, there are differences between working with remote objects and working with local objects. For example, running a Java applet stored on a remote computer is a very different task than running a locally stored standalone program. These differences are handled by JWS program 150A. However, the user interface of the present invention causes the user to launch the execution of a remote applet or local program in the same way (eg, by double-clicking an icon representing an applet). How the user interface of the present invention provides this position-transmission flexibility is described herein with reference to FIG.

【0024】

With reference to Figure 1, memory 106A is Java Includes a set of JWS files 110A that collectively define the user interfaces, methods and data files that make up the Workshop (JWS). More specifically, the JWS file 110A contains a set of interface files called the JWS program 150 (hereinafter referred to as "JWS"), the JWS browser 154A, and the JWS toolbar specification 112A. The JWS Toolbar Specification 112A consists of four file subgroups: Icon Specification 114A, Web Document 120A, JWS Applet 140A and other reference files 148A. The components 114A, 120A, 140A, 148A identify the appearance (appearance) and, more importantly, the operation of a set of icons (IAi) 162Ai displayed on the display 108A as components of the JWS Toolbar 160. The JWS Toolbar 160, a key component of the JWS user interface, is displayed by the JWS program 150A on the JWS window 156A. JWS window 156A also includes applet window 164A controlled by JWS applet 140A executed by JWS program 150A during project and / or portfolio management.

【0025】

Each icon IAi defines the icon's visual attribute 116Ai and identifies a link 118Ai to the web document 120Ai that lists the first set of files to be loaded or executed whenever the icon IAi is selected. It has the corresponding icon specification 114A. The link 118Ai can be for a web document 120Ai stored in a local system (eg, computer 102A), in which case the link is a file provided by the local operating system (not shown). -Includes local routes and filenames that can be processed by the service. Link 118Ai can also be for remote web documents (eg, documents stored on computers 102B, 102C) that can be searched on the Internet by a regular web browser. The JWS program 150A incorporates the JWS browser 154A, which provides all the features of a regular web browser, so it doesn't matter where the web document 120Ai linked to a particular icon IAi is stored, and of what type. It doesn't matter if the documents linked to the platform are remembered. Important for the preferred embodiment, the JWS browser 154A communicates with a remote platform hosting the web document 120A1 via one of the standard communication protocols endorsed by the Internet, such as HTTP or FTP. It means that you can do it. If so, the linked web documents 120Ai are automatically downloaded by the JWS browser 154A (triggered by the JWS program 150A) whenever their corresponding icon is selected. This removes much of the complexity that would be required in the prior art to implement a similar feature that links an icon to a remote, executable document.

【0026】

Each web document 120A (which would have been first stored locally or remotely before being loaded into memory 106A) contains two components: Name (Title) 122Ai and a set of references to its components. 124Ai. Web document 120A can also include embedded files (not shown); however, web browsers do not make a functional distinction between embedded files and referenced files, and this No application. Reference 124Ai of web document 120A can be for remote or local files, as in link 118Ai. In each case, they are processed by the JWS browser 154A as described for link 118Ai. One important advantage of the user interface of the present invention is that reference 124Ai is for Java applet 140Ai, which causes its associated web document to handle operations associated with icon IAi that references applet 140Ai. It means that you can do it. In this situation, when the JWS browser 154A searches for the web document 120Ai linked to the selected icon IAi, it automatically pulls in and references the referenced applet 140A (stored in the remote system). Start running. Running on the virtual machine of JWS browser, applet 140Ai then icon without having to worry about network and operating system complexity processed by local operating system and JWS browser 154A respectively. Can implement related operations.

【0027】

In a preferred embodiment, a single JWS applet 140Ai is referenced in each web document 120Ai. This single applet controls or directly implements all the functionality associated with one icon IAi. For example, in a preferred embodiment, the spell checker icon IA1 could be linked to the remote applet 140A1 via the web document 120A1 and once downloaded to computer 102A and executed by JWS browser 154A, the appropriate document. Spell-Check. Alternatively, the web document 120Ai can reference many applets 140Ai. For example, icon IA2 is linked to web document 120A2 that references the spell-checker applet and grammar-checker applet so that both are automatically launched by the JWS browser 154A whenever icon IA2 is selected from toolbar 160. sell. In addition to applets, web documents of the invention can reference other types of component 148A, including data and image files.

【0028】

Refer to Figure 2 for a data flow diagram that illustrates the sequence of steps in which an applet is invoked in response to the selection of a particular icon IA1 from toolbar 160. Each icon selection event is monitored by the JWS browser 154A, which searches for link 118A1 from icon IA1 specification file 114A1 following icon IA1 selection. Through link 118A1, icon IA1 is associated with web document 120A1, which is automatically loaded by JWS browser 154A. The JWS browser 154A then loads all of the referenced files in document 120A1 and also executes the referenced files (ie, applets) that are executable. In this example, it is assumed that there is one referenced executable, applet 140A1. Once it is active, the applet 140A1 can display on it dialog boxes and icons that facilitate user interaction with the applet's features and capabilities, such as part of display 108A (eg, for example). You can control the applet window 164A).

【0029】

Referring to FIG. 3, a data structure diagram showing further details of the data items stored in the memory 106A used by the Java WorkShop Program 150A is shown. These data items include the visual attribute 116Ai for the icon IAi displayed by the JWS150A on the toolbar 160 and the icon specification 114Ai defining the web document link 118Ai. These icons (shown in Figure 2) are the portfolio manager icon IA1, the project manager icon IA2, the text edit project icon IA3, the build / compile icon IA4, the source browse icon IA5, and the debug icon. Includes icon IA6, run icon IA7 and help icon IA8. When selected, icons IA1 through IA8 allow the user to access the following capabilities (and menus) provided by Java WorkShop 150A to work with JWS portfolios and projects, respectively: [0030]

IA1: Providing access to Portfolio Manager applet 140A1 to view projects in the current portfolio; IA2: Provides access to the project manager applet 140A2, which allows users to edit project information; IA3: Provides access to a JWS text editor applet (not shown) that allows users to edit project source code; IA4: Provides access to the JWS project compiler applet (not shown); IA5: Provides access to a JWS browser applet (not shown) that allows the user to browse the JWS source programs contained in other referenced file 148A; IA6: Provides access to a JWS debug applet (not shown) that allows the user to debug the JWS source program contained in other referenced file 148A; IA7: Provides access to JWS project run method 146A2f to run executable projects (ie applets and standalone programs); IA8: Provides access to the JWS Help applet (not shown), which provides context-sensitive help for JWS operations.

【0031】

As illustrated with reference to FIG. 1, in a preferred embodiment, the icon specification 114Ai to a web document 120Ai having a reference 124Ai to a single applet 140Ai that implements the operation associated with the corresponding icon IAi. Includes the link. Therefore, the icon specification 114Ai associated with the portfolio manager icon IAi is linked to a web document (Portfolio.HTM) 120A1 containing a single reference 118A to the portfolio manager applet 140A1. Similarly, the icon specification 114A2 associated with the project manager icon IA2 is linked to a web document (Portfolio.HTM) 120A2 that has a single reference 118A2 to the project manager applet 140A2. These applets 140A1 and 140A2 supply methods 146A1 and 146A2 that can be applied to portfolios and projects, respectively.

【0032】

Method 146Ai is made available to the user as an option for menu 147Ai that is displayed when the icons for those related applets are selected. For example, Portfolio Manager Method 146A1 appears as an option on the Portfolio menu 147A1. In the normal GUI scheme, when one of the methods / options is subsequently selected from its parent menu, the option's submenu, or page, is then displayed by the JWS150A and enabled for user interaction. Many of the submenus 147Aij are supplied by preferred embodiments; for example, Project-> Create, Import, Choose, and Remove submenus 147A1a, 147A1b, 147A1c, 147A1d and Project-> Create, Import, Choose, Remove, The Run and Copy submenus 147A2a, 147A2b, 147A2c, 147A2d, 147A2e, 147A2f provide a list of portfolios and projects to which the submenu related methods can be applied, respectively. For example, reference to Figure 4 shows an example of the Portfolio-> Choose submenu 147A1c listing a set of portfolios (Portfolio1, Portfolio2, Portfolio3) for the Portfolio-> Choose method 146A1c. Figure 4 also shows a portfolio menu 147A1 listing the portfolio manager method 146A1 (Create, Import, Choose, Remove).

【0033】

With reference to FIG. 3 again, the JWS applet 140Ai method 146Ai is described here from the perspective of the user working with their corresponding menu 147Ai submenu 147Aij. Most of this description focuses on the methods of the portfolio and project manager applets 114A1 and 114A2, which are the key components of the JWS150A.

【0034】

Portfolio manager method Portfolio Manager Applet 140A1 allows JWS150A users to tolerate Create 146A1a, Import 146A1b, Choose 146A1c and Remove 146Ad portfolios, respectively. Supply method 146A1. Each of these methods 146A1 accomplishes its corresponding task by interacting with a set of portfolio files 160Ai, each of which can be stored locally or in a remote system and represents a portfolio. As shown in Figure 3, a typical portfolio file 160A contains a collection of references 164A1i to the component project file 170A of that portfolio. In other file references in the present invention, the project reference 162Ai is for a locally stored project, such as when the reference is a local file name (Name), or the reference is a URL. It can be for web documents in such cases.

【0035】

For example, referring to Figure 5, "Applet", "Standalone", all of which are local projects stored in the user's "home" (ie, local) directory of memory 106A. Programs, Java Package, Image A portfolio file 160A1 containing project file references 162A1j for its component projects, including the "(image)" and "Remote" applets, is shown. These projects are in the user's "home" directory. Since everything is stored, they can be read and written by the user and their corresponding project files can be referenced by path and filename, eg to applet project file 170A1. Reference 162A1a is /home/Applet.prj. Portfolio file 160A1 is also a reference to the project file for a read-only project (SemiRemote) stored in Machine A's library directory 162A1f. (/lib/SemiRemote.pri) , And a reference to project file 170B1 for a read-only project (Internet) stored on machine B that can only be accessed on the Internet using the JWS browser 154A 162A1g (/http://B.com/) Internet.pri) Includes references.

【0036】

Referring again to FIG. 3, in a preferred embodiment, each user has a personal portfolio (having a corresponding portfolio file 160Ai) containing only the projects belonging to that user. When the JWS150A is first launched, it brings up a personal portfolio as a current or active portfolio. Using the Portfolio Manager Choose method / option 146A1c, the user can choose another portfolio 160Ai to be the current portfolio. The user can enter the filename (if it is local) or URL (if it is remote) of the desired portfolio, and the Portfolio-> Choose submenu 147A1c (this term) that lists all available portfolios. Is Portfolio This is done by selecting from the Choose option user selection from Menu 147A1 followed by the Choose submenu displayed by JWS150A. The user can then view the projects that consist of the current portfolio by selecting the portfolio manager icon IA1 from the JWS toolbar 160. In this and other situations described herein, the running applet displays its results and menu on applet window 164A.

【0037】

Users of JWS150A can create a new portfolio by selecting the Create option in the portfolio manager and then entering the name of the portfolio to be created. Accordingly, JWS150A will generate the corresponding portfolio file 160A on the local system, display its name on the toolbar 160A and add the name of the portfolio to the Choose and Remove submenus 147A1c, 147A1d, Portfolio-> Create Method 146 Call A1a. The newly generated portfolio does not have a project, but the user can add a project to the Portfolio-> Create submenu 147A2a (described below) or add an existing project to Project-> Import. It can be incorporated into a portfolio with menu item 147A2b (also described below). Once a new portfolio is created, its creator can keep it private or publish it on the internet for access by others.

【0038】

Users can also import existing portfolios that do not currently exist in their Portfolio-> Choose submenu 147A1c. To import such a portfolio, the user first selects the Import option listed in Portfolio menu 147A1. This is an import submenu with a name field where the user enters the file name or URL of the portfolio to be imported, and an import button that the user clicks when they finish typing. Trigger Portfolio-> Import Method 146A1b to send out. Accordingly, the import method 147A1c adds the portfolio name to the Portfolio-> Choose and Portfolio-> Remove submenus 147A1c, 147A1d. JWS150A will also change the current portfolio to an imported portfolio. Once it is Portfolio-> Choose If it is above the submenu 147A1c, the imported portfolio can be treated like any other portfolio.

【0039】

The user can remove a portfolio by selecting the portfolio to be removed from the Portfolio-> Remove submenu. Accordingly, JWS154A calls Portfolio-> Remove method 146A1d, which removes the portfolio selected from the Choose and Remove submenus 147A1c, 147A1d, but does not delete the corresponding portfolio file 160A of the portfolio. Since the portfolio file is not deleted from the user's system, the user can import the portfolio at any time using the Portfolio-> Import option 146A1b. Each project file included in the portfolio has a corresponding project file 170A that describes the project and contains the contents of the project. More specifically, each project file 170A contains the following information: [0040]

(1) Project name 172A; (2) Project type 174A (Java applet (APPLET), stand-alone program (STANDALON), Java class library (PACKAGE), data file (IMAGE), import of a remote project of one of these four types shown above Copy, or remote applet (REMOTE)); (3) Project management information 176A, which includes whether the source code 178A for the project should be distributed to others requesting the project on the Internet and project option 180A; (4) Project content 182A; and, which can contain a set of references to the actual project content and / or other project file 170Ai, and enable multiple levels of embedded projects. (5) Run page URL184A (applicable only to applet projects), which is the URL of the HTML file containing the applet tag for the applet project.

【0041】

This information determines which of the project methods provided by the JWS150A can be adopted by users on a particular project. These project methods 146A2 are described here.

【0042】

Project method The JWS150A provides multiple ways to work with your project. These methods are available to users as options on the Project menu 147A2. When one of these methods / options is selected, the JWS150A will (then) display a corresponding submenu 147A2j where the user can specify further operation details. The project method 146A2 is: Create 146A2a, Import 146A2b, Choose 146A2c, Edit 146A2d, Remove 146A2e, Run 146A2f, Copy 146A2g, and Paste. (Paste) 146A2h.

【0043】

These methods allow the user to work with an existing project (local or remote) or create a new one. In either case, the project is always in the context of the portfolio. When a project is generated, it becomes the current project in the current portfolio. Users can create Java applet projects, stand-alone project projects, Java package projects, image projects or remote projects. To generate one of these projects, the user first selects the Chooses portfolio to which the project should be associated with it and then selects the Create option from the Project menu 147A2. Thus, JWS150A calls Project-> Create Method 146A2a. This method 146A2a, on which the user selects the type of project they want to generate, Project-> Create Display page 147A2a (for example, if the user wants to generate an applet, (they) click on the applet button displayed on the submenu). The user then identifies the name of the package to be generated and the local directory of memory 106A in which the corresponding project file 170Ai of the package should be stored. Once the user has identified the attributes for the project, the Project-> Create method adds a reference 162Aij to the corresponding project file of the project to the portfolio file 170Ai of the current portfolio 160Ai.

【0044】

In certain situations (when the generated project is an applet, standalone, project or Java package), the user may also have access to the source code for the newly generated project. In these situations, the user enters the filename of the corresponding source file on Project-> Create page 147A2a. The JWS150A maintains (maintains) these source file names in memory 106A so that the source files can be accessed by the user. Add to (source) list (for example, for editing and compiling). The user can also use the main file (ie, the file containing the "main" routine) for the program of which the newly generated project is a part. Enter the name of. When the generated project is a Java applet, it is possible that the Java applet is referenced in an HTML page so that the applet is executed when the applet reference is selected. Yes, the JWS150A should be represented via the Run Page URL field on the Project-Create page, where the user optionally enters the name of the HTML page on which to run the applet. Allow for relationships.

【0045】

When the user is creating an image project, after Choosing image from the Project-> Create submenu 147A2a, the user chooses the name of the image project and the URL of the corresponding image file. Enter. The user then: [0046]

(1) Image alignment with respect to surrounding text (for example, choosing bottom alignment) causes the browser displaying the image to align the bottom of the image with the bottom of the text. ); (2) Whether the image is active (meaning that the viewer of the image can click on different areas of the image to produce different behaviors); (3) Cannot display the image You can optionally enter attributes associated with the image, such as an optional text string that can be displayed in place of the image by the browser.

【0047】

Once the user has filled in this information for the image project they are generating, the user can click on the Apply field on Project-> Create page 147A2a, thereby Project-. > Create Method 146A2a makes the newly generated image project the current project or displays the image in the Applet window 164A. The Create method 146A2a also adds the image project name to the Choose, Edit and Remove submenus 147A2c, 147A2d, 147A2e of the Project menu 147A2 and the corresponding project. Add the name of file 170Ai to the portfolio file 160Ai associated with the current portfolio.

【0048】

Users of JWS150A can import any type of project into one of their personal portfolios. They select the portfolio they want to be the current portfolio, select the Import option from the Project menu 147A2, and are imported onto the Project-> Import page 147A2b displayed by Project-> Import Method 146A2b. Do this by entering the name or URL of the project that should be. After entering the required information, the user clicks the import button displayed on the import page 147A2b, thereby importing the project with the import method 146A2b into the current portfolio and the project. Name / URL Project-> Choose, Edit, Remove, and Run Add to submenus 147A2c, 147A2d, 147A2e and 147A2f. The import method 146A2b also adds the name of the project file 170Ai of the imported project to the current portfolio if it is not already included in it. JWS150A does not make the imported project the current project, but if the user subsequently selects the Portfolio Manager icon IA1 from toolbar 160, JWS150A will display the imported project.

【0049】

JWS150A lets the user create a remote applet project. The user can Choosing the current portfolio, select the Create option from the Project menu, and remote displayed on the Project-> Create submenu 147A2a. Do this by clicking the "remote applet" button. The user then enters the name of the project and the URL of the HTML page that runs the applet. Once these fields are closed, the user exits the Project-> Create submenu 147A2a by clicking on Apply. Create method The 146A2 then generates a project file 170Ai with empty content 182Ai and a run page URL field 184Ai set in the URL of the HTML page that runs the applet. For example, referring to Figure 5, the remote project file 170A5 is the URL of the web page (RunApplet2.htm) that runs the remote applet Applet2 (http://C.com/RunApplet2.htm). Has run page URL 184A5 set to. Generation method 146A2 also adds the name of project file 170Ai to portfolio file 160Ai of the current portfolio. JWS150A then makes the imported project the current project, loads Portfolio Manager 140A1 and selects the current project to be displayed by Portfolio Manager 140A1. JWS150A then named the imported applet project Project (Project) Add to the Choose, Edit, Remove, Run and Copy submenus of menu 147A2 147A2c, 147A2d, 147A2e, 147A2f.

【0050】

The user then selects its name from the Project-> Run submenu 147A2f or loads the Portfolio Manager, selects a remote project, and presses the Run button IA7 on the toolbar 160. This allows you to run remote applets. Project-> Run Method 146A2f then downloads the referenced web page (http://C.com/RunApplet2.htm) and runs a remote applet (Applet2), Web browser 154A Pass the URL of the web page referenced in the run page URL field (eg, 184A5) of the remote applet project file (170A5). The user runs a run page in the applet project file 170Ai page) If you don't specify URL184Ai, the applet project can still be run using Project-> Run method 146A2f. In this situation, Project-> Run Method 146A2f is a new web page containing applet tags generated with project attributes and parameters entered by the user in the Edit Project 146A2d run folder. Web page) is automatically generated. This automatically generated HTML page is loaded into JWS150A, which uses browser 154A to run the applet project. This feature allows the user to run the applet without having to know the HTML syntax for the referenced applet.

【0051】

Project Manager 140A2 Copy method 146A2g runs an applet in an HTML file that runs the applet without requiring the user of JWS150A to know the HTML syntax for the applet referenced by the user. To copy. The user does this by first selecting the applet project in the current portfolio (single-clicking on it) and then selecting the Copy option from the Project menu 147A2. This set of actions causes the Copy method 146A2g to copy the contents of the selected applet project, 182Ai, to the clipboard (not shown) maintained by the JWS150A. The user then selects the Text Editor Icon IA3 from the toolbar 160A, which causes the JWS150A to execute the Editor method 146A2d. Editor method 146A2d is Paste Sends out a text editor that contains Edit menu 147A2d, including a list of edit options, including "(Paste)". Users can use "Paste" from Edit menu 147A2d. Select the "Paste" option, so that the paste method 142A2h pastes the contents of the clipboard (ie, the applet to be copied) into a new file. The user is then copied to the saved HTML file. You can save the new file as an HTML file that will add the appropriate link to the applet to the JWS150A. Like other new projects, the JWS150A will name the new HTML file 170Ai the portfolio file of the current portfolio. Add to 160Ai. Alternatively, the user can simply drag the image of the applet to be copied onto the image of the HTML file they want to contain the applet. JWS150A then adds the contents of the applet. Copies to the specified HTML file and adds the copied applet to the referenced HTML file tag.

【0052】

Project-> Edit Method 146A2d also lets the user edit a project of all types. The Edit method 146A2d can be called by the JWS150A user in one of two methods. First, the user can click on the Edit Project icon IA3 displayed on the toolbar 160 to call the editing on the current project (ie, editing method 146A2d). Second, the user can select the name of the project to be edited from the Project-> Edit submenu 147A2d. Once selected for a project with editing specified, JWS Edit method 146A2d is an edit page containing 6 folders that allow the user to edit information for the specified project. (edit page) Open 147A2d. For these 6 folders and their related information: [0053]

General Information about the project, including the name, type and source directory Information needed to compile a Build project Debug / Browse Information needed to debug and browse source files Information required to run an applet or standalone program in the Run JWS browser; Information needed to have another user copy your Publish project Portfolio Information required to view a project in Portfolio Manager. including.

【0054】

Project-> Edit Method 146A2d allows the user to edit the fields in these six folders only where appropriate. To assist the user, editing method 146A2d grays out inapplicable fields. Whether a field is applicable depends on the type of project being edited and whether the project is local or remote. For example, editing method 146A2d does not allow the user to edit fields in the Debug / Browse folder for projects that are not source files. General, Build, The information that can be entered by the user in the Debug / Browse and Run folders is mostly customary and therefore will not be discussed in more detail. However, what is unique about the editing information in these folders is that the JWS150A lets the user provide information for the local project along with the remote identified by the filename or URLs. This allows the user to identify, for example, that the source code for a particular project to be debugged or browsed is on a remote node. This is not possible with regular project and file management systems.

【0055】

This example also publishes a project on the Internet, as a preferred embodiment of the JWS150A will force the user to adopt the portfolio and project from a remote source and publish their own portfolio and project for the use of others. Provides a method for project creators to show certain attributes of a project related to. These publication attributes are contained in Public and Portfolio Folders, including the following fields: [0056]

Portfolio Folder Description A brief description of the project displayed by the JWS browser when the mouse hovers over the project image in Portfolio Manager; Portfolio image URL URL for an image file (GIF, JPEG, or something else) that represents the project image in the portfolio (if the image file is characteristic, the default GIF file will be used by the JWS150A); and Features General characteristics of a project, for example, the project is video, graphics or sound.

【0057】

Publish Folder Distribute source copies A toggle field with two values (yes / no) that controls whether the project's source files are copied when the project is copied from one portfolio to another (this field is no). When set to, JWS only causes the corresponding project file 170Ai to copy content 182A with Abcent (none); and Submitter Name, E-Mail and URL The name, email address and web page of the person adding the project to the portfolio.

【0058】

The user can modify the current project (ie, the project running on the JWS150A) in one of two ways. First, the user starts by selecting the Portfolio Manager icon IA1 from the JWS toolbar 160. This causes the JWS150A to open a Portfolio display showing the projects in the current portfolio in the Applet Window 164A. The user then selects a project from the Portfolio display that they want to be the current project. JWS150A makes the selected project the current project and displays the name of the current project on the JWS toolbar 160. Alternatively, the user can change the current project by choosing the project name from the Project-> Choose submenu 147A2c.

【0059】

JWS150A allows users to remove a project from their portfolio in one of the following ways: First, in the portfolio manager display of applet window 164A, the user selects the project they want to remove and the Remove icon supplied by the Portfolio Manager 140A1 (illustrated). You can click (omitted). Alternatively, they can choose the name of the project to be removed from the Project-> Remove submenu 147A2e. In either case, once the user has indicated the project to be removed, Project-> Remove Method 146A2e is a Choose, Edit, of Project Menu 147A2. Remove and Copy Remove a project from the submenus 147A2c, 147A2d, 147A2e, 147A2g. Note that Project-> Remove Method 146A2e does not remove the project file 170Ai of the removed project. This ensures that the user can subsequently import the project later (using Project-> Import method 146A2b) if needed.

【0060】

With reference to FIG. 6, a description of the JWS150A user interface that emphasizes the synthetic advantages of the present invention is provided. The eight icons IA1 to IA8 of JWS150A are shown on the toolbar 160. Two portfolios (Portfolio 1 and (Portfolio) Portfolio 2) is shown on applet screen 164A, under the control of Portfolio Manager 140A1. These portfolios represent two different types of portfolios that can be accommodated in the JWS150A. Portfolio 1 is a local portfolio with portfolio files 160A1 containing three local projects P1a, P1b, P1c with corresponding project files 170A1a, 170A1b, 170A1c. Project P2a'shown in shades in Portfolio 1 is a remote portfolio imported from Portfolio 2 across the Internet by the JWS Browser 154A (Figure 1) under the control of JWS150A. This project P2a'is represented in memory 106A by project file 170A2a'. Even if Portfolio 1 is mixed, all the projects can be operated in the same fashion in JWS150A.

【0061】

Portfolio 2 is a remote portfolio whose components are also remotely stored. The JWS150A uses the JWS browser 154A to access the components of Portfolio 2 over the Internet, but displays Portfolio 2 in the same way as Portfolio 1. Note that local portfolios such as Portfolio 1 also refer only to projects stored remotely (eg, projects stored on Machine B). This feature of the seamless JWS150A, which should organize projects and portfolios that can be distributed across the Internet, is due to the integration of the JWS150A and the JWS Web Browser 154A. The Internet-recognition of the present invention can also allow users to publish their own portfolio so that they can be accessed and used by others on the Internet.

【0062】

The present invention has been described with reference to a few specific examples, but the description is for illustration purposes only and is not intended to limit the invention. Various changes will occur to those skilled in the art without departing from the true spirit and category of the invention as defined by the claims.

【0063】

[Effect of the invention]

In the system of the present invention, in a first computer having a display and memory, the first computer is networked by a set of remote computers, and its components are constrained to exist only on the computer. A system for invoking the loading and execution of complex documents from the graphical user interface displayed on the first computer: It has a set of selectable icons, each icon having that icon. A viewable toolbar associated with one or more operations launched through the selection of; a set of references to the components, or files, each required to perform one or more of the associated operations. A set of complex documents, including; each of a subset of files that have a file type selected from an applet or data file and a location selected locally or remotely; each of the set of documents has one icon. A set of links; and icons that are associated with one or more and each selected from a local link when the document is stored on the computer or from a network link when the document is stored on a remote computer. When one is selected, let the computer load the file referenced in the document associated with the selected icon via a set of links and execute one of the loaded files that is executable. It is equipped with a computer that is configured to allow , thereby invoking operations associated with the icon, so that it can supply icons that can be associated with local or remote files and programs.

【0064】

The methods of the invention load and execute a complex document that is not constrained to exist only on a first computer that is networked with a set of remote computers that can host a subset of the components. A method of launching from a graphical user interface displayed on the first computer: displaying a toolbar with a set of selectable icons, each icon through the selection of that icon. Associated with one or more operations to be invoked and linked to one or more complex documents, each containing a set of references to the components or files needed to perform one or more of the related operations. Each subset of files has a file type selected from an applet or data file; loading one or more composite documents linked to the selected icon by selecting one of the icons. By loading one or more compound sentences, the file referenced in the compound document is loaded, and the file is not constrained to exist only on the first computer; and the loaded file is When having a type selected from an applet or stand-alone application, it has a stage to execute the loaded file, so it can provide icons that can be associated with local or remote files and programs.

[Simple explanation of drawings]

[Figure 1]

FIG. 6 is a block diagram of a computer network showing details of memory and disks associated with one of the networked computers.

[Figure 2]

FIG. 5 is a data flow diagram showing the processing steps performed by the present invention following the selection of an icon from the toolbar.

[Fig. 3]

It is a figure which shows the data structure adopted in the preferable example of Java Workshop.

[Fig. 4]

An example of a portfolio manager menu and a submenu associated with one of the portfolio manager methods is shown.

[Fig. 5]

The structure of the portfolio file adopted in the preferred example of Java Workshop is shown.

[Fig. 6]

FIG. 5 is a diagram of a disk window generated by a portfolio manager of the present invention such that some of the displayed components are local or remote to the computer displaying the portfolio manager window.

[Explanation of symbols]

100 computer networks 102 computer 104 processor 106 memory 108 display 110A JWS file 112A JWS Toolbar Specification 114A icon specifications 116A1, A2 Icon visual attributes 118A1, A2 link 120A web document 122A1, A2 title See 124A1 and A2 140A JWS applet 148A reference file 150A Java Workshop (JWS) program 154A Integrated JWS Browser 156A JWS window 160 JWS Toolbar 162Ai icon 164A applet window