Automatic conversion between sets of text urls and cohesive scenes of visual urls

AUTOMATIC CONVERSION BETWEEN SETS OF TEXT URLS AND COHESIVE SCENES

OF VISUAL URLS

0003This application claims the benefit of U.S. Provisional Application Nos. 60/151,672 filed August 31, 1999, and 60/152,141 filed August 31, 1999. This application is also related to U.S. Patent Application Serial No. 09/540,860, filed March 31, 2000 and U.S. Patent Application Serial No. 09/540,433, filed March 31, 2000.

FIELD OF THE INVENTION

0005The present invention relates generally to the field of data representation and more specifically to the representation of URLs and other file references.

COPYRIGHT NOTICE /PERMISSION

0007A portion of the disclosure of this patent document may contain material which is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure as it appears in the Patent and Trademark Office patent file or records, but otherwise reserves all copyright rights whatsoever.

0008BACKGROUND OF THE INVENTION With the increasing popularity of computing and the use of the Internet, in many fields, communication with computers and similar devices in a simple and convenient manner becomes extremely important. Graphical user interfaces (GUIs) take advantage of the computer's graphics capability to simplify the interaction between users and devices. For instance, such features of GUIs as icons provide the users with a convenient way of executing a command or opening a window by merely clicking on an icon. The icons represent visual file references which are created by converting corresponding textual file references. The area on the display screen where icons are grouped is referred to as the desktop because the icons are intended to represent real objects on a real desktop. The icons are usually presented as visually unrelated to each other. Each icon sits in its own screen space with no relevance to the adjacent icons. Similarly, the conversion of textual references to files and directories into visual references is typically purely functional, with no consideration for visual cues and context.

0009Web browsers, in contrast, do take into account visual effects when presenting file references such as URLs to the users. Currently, images can be used to represent hyperlinks to URLs. However, existing tools offer no capability for automatically associating URLs and other file references with meaningful visual objects and for integrating the resulting visual objects into a contextually relevant cohesive scene.

SUMMARY OF THE INVENTION

0011Methods and systems for automatic conversion between textual file references and visual file references are described. In one embodiment, textual file references are automatically converted into visual file references by providing a conversion interface enabling a user to identify a set of textual file references, creating a set of visually-linked objects corresponding to the set of textual file references identified by the user, and integrating the set of visually- linked objects into a cohesive scene.

0012In another embodiment, visually-linked objects are converted into textual file references by receiving a request to convert a cohesive scene of visually-linked objects into a set of textual file references and creating a set of textual file references corresponding to visually-linked objects within the cohesive scene.

0013In yet another embodiment, a conversion between cohesive scenes of visually-linked objects is performed by providing a conversion interface enabling a user to identify a set of visually-linked objects within a first cohesive scene, extracting the identified set of visually-linked objects from the first cohesive scene, and converting the extracted set of visually-linked objects into a set of visually-linked objects of a second cohesive scene.

BRIEF DESCRIPTION OF THE DRAWINGS

0015The objects, features and advantages of the present invention will be apparent to one skilled in the art in light of the following detailed description in which:

0016Figure 1 is a block diagram of one embodiment of a system in which automatic conversion between textual file references and visual file references can be performed;

0017Figure 2 is a block diagram of one embodiment for an architecture of a computer system;

0018Figure 3 is a block diagram of one embodiment for a data manipulation and display architecture;

0019Figure 4 is a block diagram of one embodiment for the data representation of a cohesive scene or a repertoire;

0020Figure 5 is a flow diagram of one embodiment of a process for automatically converting a set of textual file references into a cohesive scene of visually-linked objects; Figures 6A and 6B show an exemplary conversion interface, according to one embodiment of the present invention;

0021Figures 7A-7D are display windows of exemplary cohesive scenes of visually linked objects in which hierarchical structures of initial sets of textual file references are maintained, according to some embodiments of the present invention;

0022Figure 8A-8E show exemplary user interfaces illustrating a process of adding visually-linked objects to a cohesive scene, according to one embodiment of the present invention;

0023Figure 9 is a flow diagram of one embodiment of a process for automatically converting a set of visually-linked objects into a set of textual file references; and

0024Figure 10 is a flow diagram of one embodiment of a process for automatically converting a set of visually-linked objects of a first cohesive scene into a set of visually-linked objects of a second cohesive scene.

DETAILED DESCRIPTION

0026Methods and systems for automatic conversion between textual file references and visual file references are described. In the following detailed description of the present invention, numerous specific details are set forth in order to provide a thorough understanding of the present invention. However, it will be apparent to one skilled in the art that the present invention may be practiced without these specific details. In some instances, well-known structures and devices are shown in block diagram form, rather than in detail, in order to avoid obscuring the present invention. Some portions of the detailed descriptions that follow are presented in terms of algorithms and symbolic representations of operations on data bits within a computer memory. These algorithmic descriptions and representations are the means used by those skilled in the data processing arts to most effectively convey the substance of their work to others skilled in the art. An algorithm is here, and generally, conceived to be a self-consistent sequence of steps leading to a desired result. The steps are those requiring physical manipulations of physical quantities. Usually, though not necessarily, these quantities take the form of electrical or magnetic signals capable of being stored, transferred, combined, compared, and otherwise manipulated. It has proven convenient at times, principally for reasons of common usage, to refer to these signals as bits, values, elements, symbols, characters, terms, numbers, or the like.

0027It should be borne in mind, however, that all of these and similar terms are to be associated with the appropriate physical quantities and are merely convenient labels applied to these quantities. Unless specifically stated otherwise as apparent from the following discussions, it is appreciated that throughout the present invention, discussions utilizing terms such as "processing" or "computing" or "calculating" or "determining" or "displaying" or the like, refer to the action and processes of a computer system, or similar electronic computing device, that manipulates and transforms data represented as physical (electronic) quantities within the computer system's registers and memories into other data similarly represented as physical quantities within the computer system memories or registers or other such information storage, transmission or display devices. The present invention also relates to apparatus for performing the operations herein. This apparatus may be specially constructed for the required purposes, or it may comprise a general-purpose computer selectively activated or reconfigured by a computer program stored in the computer. The algorithms and displays presented herein are not inherently related to any particular computer or other apparatus. Various general-purpose machines may be used with programs in accordance with the teachings herein, or it may prove convenient to construct more specialized apparatus to perform the required method steps. The required structure for a variety of these machines will appear from the description below. In addition, the present invention is not described with reference to any particular programming language. It will be appreciated that a variety of programming languages may be used to implement the teachings of the invention as described herein.

0028Some portions of the detailed description that follows are presented in terms of algorithms and symbolic representations of operations on data bits within a computer memory in the form of a computer program. Such a computer program may be stored in a computer readable storage medium, such as, but is not limited to, any type of disk including floppy disks, optical disks, CD-ROMs, and magnetic-optical disks, read-only memories (ROMs), random access memories (RAMs), EPROMs, EEPROMs, magnetic or optical cards, or any type of media suitable for storing electronic instructions, and each coupled to a computer system bus.

0029The algorithms and displays presented herein are not inherently related to any particular computer or other apparatus. Various general purpose systems may be used with programs in accordance with the teachings herein, or it may prove convenient to construct more specialized apparatus to perform the required method steps. The required structure for a variety of these systems will appear from the description below. In addition, the present invention is not described with reference to any particular programming language. It will be appreciated that a variety of programming languages may be used to implement the teachings of the invention as described herein.

0030Definitions

0031The term "automatic" refers to a process which is performed without requiring any user assistance to the process.

0032The term "file references" includes references to various files (e.g., text files, data files, program files, directory files, etc.), to various collections of files (e.g., folders, computer applications, streaming content, updated content, etc.), or to other file references. In addition, file references include references to documents and resources on public and private networks (e.g., World Wide Web), including URLs and other similar references.

0033The term "visually-linked objects" (also referred herein as "visual file references") refers to graphic objects (e.g., images, video clips, 3-D graphics, 2- D graphics, etc.) that contain a link to a file reference (e.g., a file address such as a URL). The link may be embedded within the visually-linked object at the time such object is downloaded or may be added to the downloaded object by the automatic conversion system. Activating a visually-linked object may open an application, access or launch a web page, open a file, or perform any other suitable action. For instance, activating a visually-linked object containing a link to a document opens the document, and activating a visually-linked object containing a link to a program executable file executes the program. If the user has not opened a connection to the Internet, activating a visually-linked object containing a link to a URL may automatically initiate the Internet connection and open the web browser, thereby allowing the user to automatically access the content referred to by the URL. Other functionality of the visually-linked objects will become apparent by reference to the drawings and by reading the description that follows.

0034The term "repertoire" refers to a grouping of visually-linked objects within a cohesive scene. It should be noted that a repertoire may also recursively contain other repertoires in addition to visually-linked objects.

0035Overview

0036The present invention enables automatic conversion between textual file references and visual file references.

0037In one embodiment, a visually-linked data manipulation and display system provides a conversion interface that enables a user to identify a set of textual file references, creates a set of visually-linked objects that corresponds to the set of textual file references identified by the user, and integrates the set of visually-linked objects into a cohesive scene. In another embodiment, a cohesive scene of visually-linked objects is automatically converted into a set of textual file references upon receiving a conversion request from the user. In yet another embodiment, visually-linked objects of one cohesive scene are automatically converted into visually-linked objects of a different cohesive scene. It should be noted that textual file references include file references in any type of textual form including but not limited to a binary form.

0038An Exemplary System

0039Figure 1 illustrates one embodiment of a system in which automatic conversion between textual file references and visual file references can be performed. Referring to Figure 1, system 100 represents a networked visually- linked data manipulation and display system which consists of clients 106, 108 connected via wide area network (WAN) 112 to server 102. Server 102 is connected to mass storage device 104. Mass storage device 104 may be any suitable storage medium such as, for example, read only memory (ROM), random access memory (RAM), EPROM's, EEPROM's, magnetic optical discs, or any type of medium suitable for storing electronic data. In an alternate embodiment, wide area network (WAN) 112 may be a local area network (LAN).

0040In one embodiment, a user may access and download visually-linked objects from server 102 onto client 106. Additionally, the user may download the visually-linked objects from another client 108. Alternatively, the visually- linked objects may be downloaded onto client 106 in response to the user request to convert a set of textual file references into a cohesive scene of visually-linked objects. Activating a visually-linked object (e.g., by clicking on the visually-linked object) causes programs within the client 106 to be activated to open an application, access or launch a web page, open a file, or any other suitable action. In one embodiment, the basic application to build and modify the visually-linked objects, together with the objects themselves, are maintained and accessed on server 102.

0041In an alternate embodiment, the basic application, together with the objects themselves, may be downloaded to client 106. In this embodiment, the basic application may be downloaded and initiated on client 106 if the user accesses a visually-linked object for the first time, or alternatively, in response to the user request for conversion. After the basic application is initiated, the visually-linked objects will be downloaded to client 106 and displayed upon client 106 display.

0042The visually-linked objects are integrated into a cohesive scene using a visual metaphor. In one embodiment, the visual metaphor is a real world visual metaphor. The repertoires and /or the visually-linked objects included in the cohesive scene may be represented as planets, solar systems, galaxies, universes, cities, buildings, floors, rooms, etc. In this embodiment, other repertoires and visually-linked objects may be used such as, for example, a house containing rooms with the rooms containing visually-linked objects.

0043In another embodiment, system 100 uses a non-real world metaphor to create a cohesive scene of repertoires and visually-linked objects. For instance, any fanciful repertoire may be used for the placement of visually-linked objects which may have geometric shapes (e.g., cubes, sphere, pyramids, etc.) or other non-real world representations.

0044In one embodiment, the visually-linked objects are displayed, together with windows containing a set of graphical tools, on client 106. The graphical tools allow the user to modify the repertoires and visually-linked objects. In the description that follows, the real world metaphor (specifically, a planet theme) will be used. However, any other visual metaphor (real world or non- real world) may be used by the basic application without loss of generality.

0045In one embodiment, a wizard guides the user through the process of converting textual file references (e.g., bookmarks) into visually-linked objects. The visually-linked objects refer to the visual representations of links to sites, files, folders, and the like that may take the form of buildings or cities on the planet. The user's planet may contain visually-linked objects with links to, for example, bookmarks, sponsor (or branded) sites, and objects with links to planets of other users (e.g., a user of client 108). The user may place the visually-linked objects anywhere on the planet. In one embodiment, the user may publish the planet with visually-linked objects on server 102 for access by other users. The access may be available only to a defined group of people (e.g., a group of students doing research for school related projects) or to the public in general.

0046The application graphical tools are part of the basic application that may be downloaded over WAN 112. The basic application enables the manipulation and modification of visually-linked objects and their attributes such as size, position, color, texture, and embedded links. Client 106 does not need to be connected to WAN 112 to build, manipulate, or move the visually- linked objects.

0047In one embodiment, after the visually-linked objects are created, they may be manipulated in a three dimensional (3-D) manner. For example, the planet may have a motion either around an axis or on a plane. That is, the view of the planet may be altered by rotating the planet on its axis, zooming in or out, expanding the view to include a solar system, contracting the view to a single building, or the like. In one embodiment, a planet automatically rotates on its axis whenever it is in full-planet view. In an alternate embodiment, the planet is rotated and manipulated only at the direction of the user. Similarly, solar systems, galaxies, and universes may rotate around an axis.

0048Figure 2 is a block diagram of one embodiment for a computer system 200 suitable for use with the present invention. Computer system 200 may be used in various capacities with the present invention. For example, computer system 200 may be used as a server 102 or as a client 106, 108. Referring to Figure 2, computer system 200 includes CPU 202 connected via bus 215 to a variety of memory structures and input/output 210. The memory structures may include, for example, read only memory (ROM) 204, random access memory (RAM) 206, and /or non- volatile memory 208. In one embodiment, CPU 202 is also connected via bus 215 to network interface 212. Network interface 212 is used to communicate between computer system 200 (e.g., server 102) and a variety of other computer terminals (including clients 106 and 108). Network interface 212 may be connected to WAN 112 by any of a variety of means such as, for example, a telephone connection via modem, a DSL line, or the like.

0049Figure 3 is a block diagram of one embodiment for a basic application

0050300. Referring to Figure 3, basic application 300 includes graphical tool (GUI)

0051305, undo 315, controller 320, scene renderer 325, resource manager 330, sound manager 335, and preferences 340. Application 300 is connected to network interface 212 and local disk 350. Application 300 may be contained within

0052RAM 206 or non- volatile memory 208. In one embodiment, application 300 may be downloaded to client 106 when a user accesses a visually-linked object or a web site with a selection of visually-linked objects. Alternatively, application 300 may be downloaded to client 106 upon the user request to convert textual file references into visual file references. Controller 320 contains software routines to build and modify visually-linked objects and repertoires. Once application 300 is downloaded and initially launched, controller 320 instructs resource manager 330 to download the visually-linked objects from server 102 or from another client 108. Resource manager 330 first checks local disk 350 to determine if the object is saved locally on client 106. If not, resource manager 330 downloads visually- linked objects via network interface 212 to local disk 350. Resource manager 330 transfers the visually-linked objects via controller 320 to scene renderer 325. Scene renderer 325 integrates the visually-linked objects into a cohesive scene. In one embodiment, a planet (or any other appropriate surface for a cohesive scene) is also downloaded to client 106. The visually-linked objects are placed on the planet. The planet is made the current view and added to a repertoire of planets. Scene renderer 325 uses the planet and visually-linked objects to create the display. In one embodiment, the repertoire of planets is visually represented as a solar system. The repertoire, together with the visually-linked objects, is saved in RAM 206 or non- volatile memory 208 for use when needed. In one embodiment, as a user moves a pointer over a visually-linked object, sound manager 335 produces a sound associated with the object. Undo 315 is used to undo an action by the user and GUI 305 is used to enable the user to identify textual file references to be converted, modify the visually-linked objects and interact with the system (e.g., rotate planet, change view, etc.). Figure 4 is a block diagram of one embodiment for the data representation of a downloaded world 400. The downloaded world 400 may be the entire cohesive scene or a portion of the cohesive scene such as a repertoire. Referring to Figure 4, world 400 includes repertoire 450 and one or more visually-linked objects 460. Repertoire 450 includes world meta data 405 and 3-D model world data 410. World 400 is downloaded by resource manager 330 and saved in local disk 350. In one embodiment, any repertoire 450 may be downloaded. In one embodiment, multiple visually-linked objects 460 may be downloaded. In one embodiment, repertoire 450 and visually-linked objects 460 may be downloaded together. In an alternate embodiment, visually-linked objects 460 may be downloaded separate from repertoire 450. In one embodiment, 3-D model world data 410 and 3-D object data 420 contain the graphical renderings of world meta data 405 and object meta data 415 respectively. World meta data 405 contains the data used by scene renderer 325 to build the planet for display. In one embodiment, world meta data 405 contains the name of world 400, a list of visually-linked objects 460, and a reference to a 3-D model world data 410. The list of visually-linked objects 460 contains a set of pointers in which each pointer points to an individual visually-linked object 460 associated with repertoire 450. In one embodiment, each pointer is an identification to separate visually-linked objects 460. World meta data 405 may point to a number of object meta data 415. In addition, world meta data 405 contains a position for each visually-linked object on a planet. World meta data 405 contains a pointer to the 3-D model world data 410 and each object meta data 415 contains a pointer to 3-D object data 420. The representation within 3-D model world data 410 is the actual graphical data used by scene renderer 325 to display the planet repertoire and each visually-linked object contained within object meta data 420 is the actual graphical data used by scene renderer 325 to display the visually-linked object. For example, each visually-linked object within object meta data 420 may be a JPEG or GIF image.

0053In one embodiment, scene renderer 325 uses the data representation of world 400, together with information contained within preferences 340 to create graphical representations for a particular display. In one embodiment, 3-D model world data 410 and 3-D object data 420 may be three-dimensional representations. In an alternate embodiment, either or both may be two- dimensional representations.

0054In one embodiment, graphics (410 and 420) cannot be changed by the user. In an alternate embodiment, graphics may be changed by the user.

0055Conversion of Textual File References

0056Figure 5 is a flow diagram of one embodiment of a process for automatically converting a set of textual file references into a cohesive scene of visually-linked objects. The process is performed by processing logic, which may comprise hardware, software, or a combination of both. Processing logic may be either in the computer system of client 106 or server 102, or partially or entirely in a separate device and /or system(s).

0057Referring to Figure 5, the process begins with providing a conversion interface which enables a user to identify a set of textual file references to be converted (processing block 504). In one embodiment, the conversion interface allows the user to enter file references manually. For instance, the user may input a list of textual URLs that the user wants to convert into visual URLs.

0058In an alternate embodiment, the conversion interface enables the user to specify a file containing textual file references. For example, the user may want to convert the URLs contained in the Bookmark file stored by the Netscape Navigator or Netscape Communicator web browser, or the URLs contained in the Favorites file stored by the Microsoft Internet Explorer web browser. In another example, the user may want to convert the URLs of web pages referred to in a particular web site. In this example, the user may specify the URL of this web site (i.e., the URL of its home web page). The home web page is then searched for references to other web pages to create an initial set of file references. Subsequently, each web page referred to in the initial set is searched for references to other web pages, thereby creating subsets of file references that are associated with each file reference in the initial web site. The search may continue until no more references are found or until the number of file references exceeds the limit specified by the user or defined programmatically. In yet another embodiment, the conversion interface may enable the user to select a subset of the textual file references contained in the file that is specified by the user. It should be noted that any other user interface techniques known in the art may be used to enable the user to identify file references to be converted.

0059In one embodiment, basic application 300 identifies hierarchies in the set of textual file references specified by the user using any conversion interface and stores the identified hierarchical structure for the subsequent use. Figures 6A and 6B illustrate exemplary conversion interfaces that enable the user to identify a set of textual file references to be converted into a cohesive scene of visually-linked objects. Referring to Figure 6A, the conversion interface allows the user to enter URLs into text boxes 602 that are set up in a list format. Referring to Figure 6B, a set of textual URLs is already entered into text boxes 602, either manually or loaded from a file (e.g., the Bookmark file or the Favorites file), and the user can select a subset of URLs to be converted by clicking in corresponding check boxes 654.

0060Returning to Figure 5, at processing block 506, processing logic receives a user request to convert the set of textual file references into a cohesive scene of visually-linked objects. In one embodiment, the user request includes a particular theme (e.g., a planet theme) to be used for the cohesive scene. The theme may be selected from a list of graphical representations of various themes presented to the user. In alternate embodiments, basic application 300 uses a default theme when performing the user request or assigns a certain theme to the user request according to the personal information provided by the user, e.g., user age, area of interest, geographic location, etc.

0061In one embodiment, the user request identifies visually-linked objects to be used to convert the textual file references. The user may specify a particular set of visually-linked objects from a list of visually-linked object sets displayed to the user, or the user may select (from a list of individual visually-linked objects or a list of visually-linked object sets) a visually-linked object for each textual file reference to be converted.

0062At processing block 508, processing logic creates a set of visually-linked objects corresponding to the set of textual file references. In one embodiment, basic application 300 uses the objects specified in the client request. In an alternate embodiment, a default set of visually-linked objects may be used. If the user specifies a particular theme (e.g., a planet theme) to be used for the cohesive scene, a default set of visually-linked objects for this particular cohesive scene is used. In yet another embodiment, basic application 300 intelligently assigns visually-linked objects to the set of textual file references. The visually-linked objects may be assigned based on the user personal information, or based on visual association with the content referred to by file references or with the text of file references themselves (e.g., if the textual URL is www.flowers.com, a visually-linked object represented as a rose is selected).

0063As discussed above, the set of textual file references may contain hierarchical groups. For instance, the Microsoft Internet Explorer web browser allows users to group their Favorites URLs into folders of URLs and folders of folders of URLs. In another example, in which textual file references to web pages associated with a particular web site are converted into visual file references to these web pages, a group may be formed by a subset of web pages that are referred to in a higher-level web page. In one embodiment, the hierarchical structure contained in the textual file references is preserved and incorporated into the created visually-linked objects as illustrated below by Figures 7A - 7D. In one embodiment, textual file references may be associated with importance indicators reflecting the degree of importance of the references to the user. These indicators are utilized when creating and/or placing the visually-linked objects. For example, the size of a visually-linked object may be determined based on the above indicator. It should be noted that any other characteristics contained in the set of textual references may be preserved and incorporated into the created set of visually-linked objects.

0064At processing block 510, the created set of visually-linked objects is integrated into a cohesive scene. The resulting cohesive scene may be two- dimensional or three-dimensional. In one embodiment, a real world visual metaphor is used to integrate visually-linked objects and repertoire (s) into a cohesive scene. The repertoire and the visually-linked objects may be represented as planets, solar systems, galaxies, clusters, universes, cities, buildings, floors, rooms, etc. In alternate embodiments, any non-real world visual metaphor may be used as discussed in more detail above.

0065In one embodiment, graphical tools may be used to modify the visually- linked objects. For instance, visual characteristics of the objects may be modified to reflect the importance of each object to the user. In one embodiment, the created cohesive scene of visually-linked objects can be emailed to a different user or saved on server 102 for access by other users.

0066In one embodiment, the hierarchies contained in the set of textual file references are maintained in the resulting cohesive scene of visually-linked objects. In one embodiment, visually-linked objects and repertoires are represented as naturally occurring hierarchies using the hierarchical structure contained in the set of textual references. For instance, the hierarchies may be represented as land masses, cities, buildings, floors and rooms, or as clusters of people and individual persons.

0067Figures 7A - 7D illustrate display windows of exemplary cohesive scenes of visually-linked objects in which hierarchical structures of initial sets of textual file references are maintained. Referring to Figure 7 A, an integrated cohesive scene produced by the conversion process is shown, in which visually-linked objects are represented as buildings and repertoires of buildings are represented as cities. Referring to Figure 7B, an integrated cohesive scene produced by the conversion process includes visually-linked objects that are represented as buildings, repertoires of buildings that are represented as cities, and repertoires of cities that are represented as planets. Referring to Figure 7C, in one embodiment, the next hierarchical level is represented as solar systems. Each solar system contains a set of planets, with each planet including a set of cities, and each city including a set of buildings which are each visually-linked objects. In an alternate embodiment, some of the shown planets are visually-linked objects rather than repertoires. Referring to Figure 7D, a different example of an integrated cohesive scene produced by the conversion process is shown. In this exemplary cohesive scene, visually- linked objects are represented as people and repertoires of people are represented as clusters of peoples.

0068Cohesive scenes of visually-linked objects may be two-dimensional or three-dimensional and may be realistic or fanciful. Each cohesive scene produced by the conversion process provides meaningful graphical representation of the information frequently used by the user.

0069In some embodiments, drag and drop graphical tools are utilized to add other visually-linked objects to the cohesive scene produced by the conversion process or to a new cohesive scene. In one embodiment, a visually-linked object is selected from a template of visually-linked objects by the user. The graphical tools allow the user to drag the visually-linked object to the existing cohesive scene or to the image of the cohesive scene being created (or to an icon representing the cohesive scene being created) and to drop the visually-linked object into the cohesive scene. These actions result in the automatic integration of the visually-linked object into the cohesive scene. In an alternate embodiment, the graphical tools enable the user to select a textual file reference (e.g., a URL), drag it to a desired object and drop it into the object, thereby converting the textual file reference into a visually-linked object. In yet another embodiment, the graphical tools are used to drag a visually-linked object which is already included in the cohesive scene to a textual file reference, thereby relinking the visually-linked object to a different file address. It should be noted that various other drag and drop techniques to add, modify and delete visually-linked objects and repertoires can be used with the present invention without loss of generality.

0070Figures 8A - 8E are exemplary user interfaces illustrating a process of adding a visually-linked object to a cohesive scene using drag and drop graphical tools, according to one embodiment of the present invention. Referring to Figure 8A, cohesive scene 800 that is being created and template 802 that includes a list of objects are shown. Cohesive scene 800 includes visually-linked objects that are represented as fruits and repertoires of fruits that are represented as bowls of fruits. Referring to Figure 8B, the user selects desired object 804 by clicking on it. Referring to Figures 8C and 8D, the user drags object 804 to cohesive scene 800 and further to bowl 806. Referring to Figure 8E, the user drops object 804 into bowl 806, thereby adding a visually- linked object to cohesive scene 800. Conversion of Visually-Linked Objects

0071In one embodiment, a set of visually-linked objects may be automatically converted into a set of textual file references. Figure 9 is a flow diagram of one embodiment of a process for automatically converting a set of visually-linked objects into a set of textual file references. The process is performed by processing logic, which may comprise hardware, software, or a combination of both. Processing logic may be either in the computer system of client 106 or server 102, or partially or entirely in a separate device and /or system(s).

0072Referring to Figure 9, the process begins with providing a conversion interface that enables a user to identify a set of visually-linked objects to be converted (processing block 904). In some embodiments, the entire cohesive scene of visually-linked objects is converted. In these embodiments, the conversion interface may allow the user to specify the name of the cohesive scene being converted or to point to the cohesive scene being converted. In alternate embodiments, sets of visually-linked objects within one or more cohesive scenes may be converted. In these embodiments, the conversion interface may allow the user to specify the objects individually. It should be noted that any user interface techniques known in the art may be used to enable the user to identify visually-linked objects to be converted.

0073At processing block 906, processing logic receives a user request to convert the set of visually-linked objects into a set of textual file references. In one embodiment, the user request specifies a desired format for the converted set of textual references. Some examples of formats may include plain text lists of references, Bookmark files, Favorites files, etc. In alternate embodiments, a default format may be used for conversion or basic application 300 may select the format based on relevant user information (e.g., the type of the user's web browser).

0074At processing block 908, processing logic creates a set of textual file references corresponding to the set of visually-linked objects. In one embodiment, the set of visually-linked objects contains hierarchical groups. In this embodiment, the hierarchical structure contained in the set of visually- linked objects is preserved and incorporated into the created set of textual file references. In addition, other characteristics of the visually-linked objects (e.g., their degree of importance to the user) may be preserved and incorporated into the created set of textual file references.

0075In an alternate embodiment, automatic conversion between cohesive scenes of visually-linked objects is provided. Figure 10 is a flow diagram of one embodiment of a process for automatically converting a set of visually- linked objects of a first cohesive scene into a set of visually-linked objects of a second cohesive scene. The process is performed by processing logic, which may comprise hardware, software, or a combination of both. Processing logic may be either in the computer system of client 106 or server 102, or partially or entirely in a separate device and /or system(s).

0076Referring to Figure 10, the process begins with providing a conversion interface which enables a user to identify a set of visually-linked objects to be converted (processing block 1004). In some embodiments, all visually-linked objects of the first cohesive scene are converted. In these embodiments, the conversion interface may allow the user to specify the name of the cohesive scene being converted or to point to the cohesive scene being converted. In alternate embodiments, only a portion of the visually-linked objects of the first cohesive scene may be converted. In these embodiments, the conversion interface may allow the user to specify the objects individually. It should be noted that any user interface techniques known in the art may be used to enable the user to identify visually-linked objects to be converted.

0077Further, processing logic extracts the set of visually-linked objects specified by the user from the first cohesive scene (processing block 1006) and converts this set into a set of visually-linked objects of a second cohesive scene (processing block 1008). Each of the two cohesive scenes may be two- dimensional or three-dimensional and may be realistic or fanciful, real- world or non-real world. In some embodiments, graphical representations and other attributes pertaining to the visually-linked objects are changed during the conversion process. In one embodiment, the set of visually-linked objects of the first cohesive scene contains hierarchical groups. In this embodiment, the hierarchical structure contained in the set being converted is preserved and incorporated into the created set of visually-linked objects of the second cohesive scene.

0078The specific arrangements and methods herein are merely illustrative of the principles of this invention. Numerous modifications in form and detail may be made by those skilled in the art without departing from the true spirit and scope of the invention.