Patent Grant
7409644
This application is related to U.S. applications attorney docket Nos. MSFT-1-20362, MSFT-1-20460, MSFT-1-20699, MSFT-1-20700, and MSFT-1-20790, and U.S. application Ser. Nos. 10/395,533 and 10/395,560, each of which is hereby incorporated by reference in its entirety.
The present invention relates to file systems, and more particularly, to a file system shell.
Present computer file systems have a number of undesirable limitations. One limitation is that users are generally unable to control the structure that they are shown. In other words, when folders are organized, a user must choose a structure, and that structure is then difficult to change. As a specific example, for a “music” folder, a user may choose to organize the music files in an artist/album format, wherein all of the album folders for each artist are grouped into that particular artist's folder, and all of the songs on a particular album are grouped into that album's folder. The artist/album format is not conducive to playing a type of music (e.g., playing two jazz songs from two different artists), or for playing a selection of albums from different artists.
As another issue, a user may have a large number of files which are difficult to organize. Some users implement a rigid sense of placement for the files, and thus create strict hierarchies for them. The management of such files become increasingly complex and difficult as the number of available documents grows, making search and retrieval also difficult. This problem is further exacerbated when additional files are utilized from other locations, such as shared files, etc.
Users also have to deal with files being in different locations, such as on different devices, on other PCs, or online. For example, users can select to listen to their music on the computer (as may be accessible to a music program) or can go online and listen to music from Web sites, however there is a strict division between these two sources. Music coming from different locations is organized differently, and not kept in the same fashion or place. As another example, files stored on a corporate network may inherently be separated from files a user has on a current machine.
Users also have to keep track not only of what file data is stored, but where it is stored. For example, for music files, users are forced to keep copies on various systems and to try to track which music files are located where. This can make files difficult to locate, even when they are locally stored.
It is also sometimes difficult to find and return to files that a user has. A user may find it difficult to recall where and how they stored certain files. Given a set of folders and even a group of similar files, users often find it difficult to quickly find the one that they are looking for. For files stored in a difficult place to find, it is that much more complex to locate. In addition, once users have enough files in a folder, it becomes more difficult to parse the folder quickly, especially if the contents are similar.
It is also sometimes difficult for users to find or return to files on a network. Sharing and publishing files is often hard to do, and it may often be even more difficult to retrieve such a file from someone who makes it available. Users typically have to memorize or map the various sites and names that they need for finding files on a network.
Name spaces may vary, which can cause confusion to the user as to what is “correct.” This is particularly true on a network where there are different naming conventions, limitations, and so on. For example, certain operating systems may require short names with no spaces in order for them to be visible.
Programs also often save files to their own directory or other name spaces, which can make it difficult for users to find their way back to the files. Programs often have default directories and places they save documents. A user often has to search through their hard disk and make guesses about where a file is stored.
Related items are also often stored in separate places. Related files that a user has may be stored on different parts of the hard disk, etc. This problem becomes more common with the developments of digital media services that have multiple content types (e.g., pictures, music, video).
Another issue with file systems is related to the address bar. As users navigate within a file system on a computer, a conventional graphical interface control, referred to as an address bar, shows the users where they are in the file system hierarchy. The conventional address bar shows the current location in terms of the file system's hierarchical structure of folders, subfolders, and files. Altering the user's location displayed in the conventional address bar is typically performed in one of two manners. The first is to manually edit the address in the address bar. Manually editing the address in the address bar permits a user to relocate to any number of locations in the file system hierarchy, but requires the user to have specific information regarding the organization of the file system on the computer, i.e., a specific file system location. The second method involves using external navigation tools which, when manipulated, update the address bar to reflect the new address or location. While bypassing the manual edit of the address in the address bar, manipulating external navigation tools still requires the user to have specific information concerning the organization of the file system and traverse the hierarchical structure. However, conventional address bars cannot reference files or data stored among multiple file system locations, such as folders or drives, due to a one-to-one relationship between the address in the address bar and a specific location in the file system hierarchy.
The prior art lacks an address bar that allows users to specify addresses that display files stored among multiple file system locations. The prior art further lacks an address bar that also permits users to easily modify the address of the address bar without manually editing the address, or requiring specific knowledge concerning the organization of the underlying file system. Also lacking in the prior art is an address bar that presents alternative selections of files to the user from which the user may select to navigate to those selections of files. Such an address bar could also selectively present a conventional address bar interface to the user enabling the user to interact with the address bar according to previous experience according to user preferences.
Another issue with file systems is related to the identification of items stored on a computer. The need to readily identify items stored in a computing environment such as a personal computer (PC) is dramatically increasing as more individuals utilize computers in their daily routines and as the type of stored information varies between pictures, music, documents, etc. Documents and media are typically stored on computers in a hierarchical fashion and are organized with files of information or media stored within folders. File system browsers enable users to navigate through the file system and locate and open files and folders. For example, Microsoft Corporation's WINDOWS® EXPLORER™ is an operating system utility which enables users to browse the file system.
Many users find it difficult to correctly identify a file based on the information currently available in conventional file system browsers. Of course the contents of a file can be verified by opening it with an application program, but this method of browsing files is extremely inefficient. The ability to view metadata about a file within a file system browser can greatly assist a user in identifying a particular file without having to open it. In Microsoft Corporation's WINDOWS® 9X operating systems, for example, a user can view object metadata by accessing the property sheet for a particular object. A property sheet presents the user with a list of the attributes or settings of an object in the form of a tabbed, index-card-like selection of property pages, each of which features standard dialog-style controls for customizing parameters. However, using the property sheet to locate an item can be slow and cumbersome, and some users find it difficult to locate the relevant metadata in a property sheet. Similarly, the use of infotips to locate an item can be slow and cumbersome because a user must hover the mouse over each file in order to view the limited metadata displayed in an infotip.
Conventional file system browsers do not allow users to enter and edit metadata relating to files and folders, which would significantly enhance a user's ability to later locate a file. To date, the ability of users to enter and edit metadata has been limited to special purpose software programs. For example, media players for electronic music files present users with the ability to edit metadata associated with music albums and artists. Another example of such programs includes application programs for electronic picture files. However, the utility of media players and other such programs is limited to the particular type of file supported by the program, as opposed to a general purpose file system browser which supports multiple file types.
Microsoft Corporation's WINDOWS® XP operating system includes an image browser for use in the My Pictures folder. The My Pictures folder is endowed with special features which enable users to view pictures as photos, not just as document icons. My Picture's image browsing features include the ability to view thumbnail-size and large versions of photos, rotate photos that are sideways, and create a slide show. A user can also view a photo's details, such as its dimensions, the date and time it was taken, and the name of the camera that took it. The preview control area in the My Picture's folder contains an enlarged preview image of a user-selected image, iterator buttons to assist a user in iterating through a series of pictures and controls for rotating pictures in a clockwise or counterclockwise direction. While the image browsing features in WINDOWS® XP have advanced the state of the art by alleviating the need to invoke an application program to view and manipulate pictures, users still cannot enter and edit metadata associated with the pictures.
Accordingly, there is a need for an improved user experience within a shell or file system browser which enables users to readily locate an item based on the metadata associated with that item. There is also a need for a system and method which allow users to enter and edit metadata associated with items of various types within a shell browser without the need to invoke an application program. There is also a need for a file system or shell browser which offers users improved file content recognition features so that users can readily locate their files. A need also exists for an improved graphical user interface for a shell browser which allows for the selection of a previewer for a particular file type from a plurality of available previewers. There is also a need for an extensible shell browser which would allow software developers to provide additional information and functionality to users on a file type basis. There is also a need to provide a similar UI experience across different collections of items.
In accordance with one aspect of the invention, a system and method utilizing virtual folders is provided. The virtual folders expose regular files and folders (also known as directories) to users in different views based on their metadata instead of the actual physical underlying file system structure on the disk. Thus, the system is able to take a property that is stored in the database and represent it as a container that is like a folder. Since users are already familiar with working with folders, by presenting the virtual folders in a similar manner, users can adapt to the new system more quickly.
In accordance with another aspect of the invention, the virtual folders are provided according to a method that is utilized in a computer system having a display and a memory for storing the items. In accordance with the method, a metadata property is selected. The system then searches for items that have the selected metadata property, and a virtual folder display object is provided that represents the collection of items that have the metadata property.
In accordance with another aspect of the invention, the system includes a folder processor that obtains queries from a user and a relational database for storing information about the items. The folder processor first obtains a query from a user and passes the query to the relational database. The relational database provides results back to the folder processor, and based on the results from the relational database, the folder processor provides the results to the user as virtual folders. In one embodiment, the results that are provided back to the folder processor include database rows and columns. The database rows and columns are converted by the folder processor into an enumerator structure, which is then used to populate the display with the resulting virtual folders.
In accordance with another aspect of the invention, users are able to work with the virtual folders through direct manipulation. In other words, the mechanisms that are provided for manipulating the virtual folders are similar to those that are currently used for manipulating conventional physical folders (e.g., clicking and dragging, copying, pasting, etc.).
In accordance with another aspect of the invention, the method for performing the direct manipulation of the virtual folders is provided in a computer system having a display and a memory for storing the items. In accordance with the method, groups of items are represented as virtual folders. Defined actions are provided that can be performed for direct manipulation of the virtual folders, wherein when a defined action is performed, the virtual folder is manipulated as directed by the defined action. An example of a defined action would be clicking and dragging a virtual folder. In one embodiment, the action of clicking and dragging a first virtual folder to a second virtual folder performs the function of copying the items from the first virtual folder to the second virtual folder. The copying of items to a virtual folder may involve adding or otherwise altering selected metadata properties that are associated with the items.
In accordance with another aspect of the invention, filters are provided for manipulating the virtual folders. The filters are essentially tools for narrowing down a set of items. In one embodiment, the filters are dynamically generated based on the properties of the separate items. For example, for a set of items, the filter mechanism may review the properties, and if the items generally have “authors” as a property, the filter can provide a list of the authors. Then by clicking on a particular author, the items that don't have the author disappear. This allows the user to narrow the contents.
In accordance with another aspect of the invention, a method for filtering items is provided in a computer system having a display and a memory for storing items with metadata properties. Display objects are provided on the display that each represent one or more items. The metadata properties of the items that are represented by the display objects are evaluated. A filter term is provided on the display that corresponds to a metadata property that is shared by a plurality of the items, wherein the selection of the filter term causes the items that are represented on the display to be reduced to those items that share the specified metadata property.
In accordance with another aspect of the invention, a plurality of items are represented on the display, and a filter term is dynamically generated based on the metadata properties of the items. When the filter term is selected, it reduces the items that are represented on the display to those that have the metadata property that corresponds to the filter term.
In accordance with another aspect of the invention, a plurality of items are represented on the display, and a filter area is provided in which a user can enter a filter term. When a filter term is entered by the user, the items that are represented on the display are reduced to those that contain the filter term. As the user types the filter term, additional items may be filtered as each new character is added to the filter term.
In accordance with another aspect of the invention, a back button is provided which may be used to back through a filtering process. For example, after a user has entered a filter term, the user may wish to return to the set of items that were represented on the display before the filter term was applied. The back button allows the user to back up to the desired point in the filter navigation.
In accordance with another aspect of the invention, quick links are provided. In one embodiment, quick links are a set of predefined links (e.g., located on the left side of the display) that can be clicked on to generate useful views of the sets of items. These can be predefined by the program, or set by a user. For example, clicking on “all authors” could return a view stacked by authors. “All documents” may return a flat view of all the documents across all of the storage areas. Users can also create their own quick links. For example, a user might filter down to all of the documents that they modified in January 2003, and then could save that as a quick link.
In accordance with another aspect of the invention, a method for providing quick links is implemented in a computer system having a display and a memory for storing items. In accordance with the method, a user first navigates to a view of a desired collection of items. A quick link that corresponds to the desired collection of items is saved and is provided with a name. The name of the quick link is presented on the display such that by clicking on the quick link a user can return to the view of the desired collection of items.
In accordance with another aspect of the invention, libraries are provided. Libraries consist of large groups of usable types of files that can be associated together. For example, photos may be one library, music may be another, and documents may be another. The libraries provide tools and activities that are related to the particular types of items. For example, in the photo library, there are tools and filters that relate to manipulating photos, such as for creating slide shows or sharing pictures.
In accordance with another aspect of the invention, a method for creating libraries is provided in a computer system with a display and a memory for storing items. The method begins by creating a library to contain items with one or more specified metadata properties. Then, items with the one or more specified metadata properties are automatically grouped into the library. Tools are also provided for manipulating the items of the library.
In accordance with another aspect of the invention, a wide scope of files or items may be available. In other words, the system is able to represent files/items from multiple physical locations (e.g., different hard drives, different computers, different network locations, etc.) so that to a user all the items appear to be from one location. For example, a user can be presented with all of their music files on a single screen, and manipulate the files all from one view, even though the files may be physically stored on different hard drives, different computers, or different network locations.
In accordance with another aspect of the invention, a scope is utilized in a method for displaying items in a computer system having a display. The method involves defining a scope of the physical memory locations from which items are to be drawn, the scope comprising the present computer memory and at least one other physical location. Once a query is received, in response to the query items are drawn from the physical locations as defined in the scope, and the items that are drawn from the query are then presented in a view on the display. In one embodiment, the at least one other physical location may be another computer, a location on a network, or an external storage device. In one embodiment, the view on the display can be switched to a physical folder view which indicates the physical locations where the items are physically stored.
In accordance with another aspect of the invention, non-file items may be represented in the virtual folders. In other words, files that are stored in memory are located in a physical store. The virtual folders can be made to include items that are not currently represented in the physical store. Examples of non-file items are e-mails, and contacts.
In accordance with another aspect of the invention, a method for presenting non-file items is implemented in a computer system with a display and a memory for storing items. The method includes providing a database that allows both non-file items and file items to be searched by a query. Once a query is received, both non-file items and file items that match the query are drawn, and the items that match the query are then presented on the display. In one embodiment, a relational database is provided that includes selected information about file items, and which may hold certain non-file items in their entireties.
In accordance with another aspect of the invention, a virtual address bar for selecting content stored on a computer file system is provided. A virtual address bar comprises a plurality of segments. Each segment corresponds to a filter for selecting content stored on the computer file system. Collectively, the corresponding filters of each segment in the virtual address bar represent a virtual address for selecting content stored on a computer file system.
Each segment is an interactive segment that can respond to user interactions to modify the virtual address of the virtual address bar. Selecting a segment in the virtual address bar causes those segments subsequent to the selected segment to be removed from the virtual address bar. Alternatively selecting a segment in the virtual address bar causes a list of selectable peer filters to be displayed to the user. The peer filters are peers to the alternatively selected segment's corresponding filter. Selecting one of the peer filters causes the alternatively selected segment to replace its corresponding filter with the selected peer filter. Additionally, those segments subsequent to the alternatively selected filter segment are removed from the virtual address bar.
Segments may be added to the virtual address bar according to external user actions. Segments are added at the end of the segments in the virtual address bar. Any segments that conflict with an added segment are removed. An existing segment in the virtual address bar conflicts with the added segment when the existing segment is mutually exclusive to the added segment. An existing segment in the virtual address bar also conflicts with the added segment when the existing segment is broader or narrower in scope than the added segment.
In accordance with another aspect of the invention, a shell browser is provided which includes a window and an edit control. The window displays a group of items and also displays metadata values associated with one or more of the displayed items. The edit control permits user modification of at least a portion of the metadata values displayed in the window.
In accordance with another aspect of the invention, a graphical user interface is embodied on a computer-readable medium and is executable on a computer. The graphical user interface includes a first screen area which displays a set of items in a shell browser and a second screen area which displays metadata associated with one or more of the displayed items. The graphical user interface also presents the user with means within the shell browser for modifying the displayed metadata.
In accordance with a further aspect of the invention, computer-implemented methods are provided for enabling a user to modify metadata within a shell browser. One such method includes displaying a plurality of items, receiving a first input from the user representing a selection of at least one displayed item, displaying metadata associated with the selected item(s) and providing an edit control for user modification of the displayed metadata. Another such method includes displaying a welcome pane and metadata associated with the welcome pane and providing an edit control for user modification of the displayed metadata.
In accordance with another aspect of the invention, a data structure containing metadata associated with one or more items is displayed in a shell browser. The data structure, which is stored on one or more computer-readable media, includes a field containing user modifiable metadata associated with the one or more displayed items, and the user modifiable metadata contained in the data structure is also displayed in the shell browser.
In accordance with another aspect of the invention, a shell browser is provided which includes a default previewer and an extensibility mechanism. The default previewer provides a standard level of functionality for multiple item types. The extensibility mechanism enables functionality beyond the standard level provided by the default previewer for one or more of the item types.
In accordance with another aspect of the invention, a shell browser is provided which includes a first previewer and a second previewer. The first previewer provides a standard level of functionality for multiple item types, and the second previewer provides an alternative or extended level of functionality for one or more of the multiple item types. The shell browser is configured to selectively deploy either the first previewer or the second previewer for the one or more item types.
In accordance with another aspect of the present invention, a graphical user interface for a shell browser which supports multiple item types is provided. The graphical user interface includes a first screen area for displaying a set of items in the shell browser and means for selecting a previewer for the displayed items from a plurality of available previewers.
In accordance with another aspect of the invention, a computer-implemented method is provided for selecting a previewer in a shell browser which supports multiple item types. The method includes providing a plurality of previewers in the shell browser for a particular item type and selecting one of the previewers for the particular item type. The method then associates the selected previewer with the particular item type.
In accordance with another aspect of the invention, a computer-implemented method is provided for enabling the use of third party previewers in a shell browser which supports multiple item types. The method includes providing a shell browser having a default previewer for the multiple item types and providing an extensibility mechanism which enables a third party to develop an alternative previewer for at least one of the multiple item types.
In accordance with another aspect of the invention, a data structure is provided which contains information indicative of a plurality of previewers in a shell browser. The data structure, which is stored on one or more computer-readable media, includes a first field containing information indicative of a default previewer which supports multiple item types. A second field contains information indicative of an alternative previewer for a first item type, and a third field contains information indicative of whether to invoke the default previewer or the alternative previewer when items of the first item type are displayed in the shell browser.
In accordance with another aspect of the invention, different types of items are grouped into libraries for which a similar set of basic UI features are provided. In other words, a similar set of basic UI features is provided for different types of libraries, such as a document library, a photo library, and a music library. This set of basic UI features may include features such as filtering, creating new categories, editing the metadata of the items, altering the pivots, etc. The similar set of basic UI features for the libraries allows a user to process and organize different types of items using attributes and features they are already familiar with.
The foregoing aspects and many of the attendant advantages of this invention will become more readily appreciated as the same become better understood by reference to the following detailed description, when taken in conjunction with the accompanying drawings, wherein:
The present invention is directed to a file system shell which incorporates a number of desirable features. In essence, the shell provides users with the ability to view and manipulate files and other items that are stored on a computer. The following description first provides a summary of the features that are shown in the
In summary,
As noted above,
The virtual folder modeling is also able to be used for traditionally non-file entities. An application of this is to have a set of user interfaces similar to files and folders (that is, objects and containers) to show traditionally non-file entities. One example of such non-file entities would be e-mails, while another would be contact information from a contact database. In this manner, virtual folders provide for a location-independent, metadata-based view system that works regardless of whether the data being shown is from files or non-file entities. In general, these aspects allow more flexibility in terms of letting users manipulate their files and data, using both common user interface techniques (drag and drop, double-click, etc.) as well as leveraging the rich integration of various data types.
Although not required, the invention will be described in the general context of computer-executable instructions, such as program modules, being executed by a personal computer.
Generally, program modules include routines, programs, characters, components, data structures, etc., that perform particular tasks or implement particular abstract data types. As those skilled in the art will appreciate, the invention may be practiced with other computer system configurations, including hand-held devices, multiprocessor systems, microprocessor-based or programmable consumer electronics, network PCs, minicomputers, mainframe computers, and the like. The invention may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote memory storage devices.
With reference to
A number of program modules may be stored on the hard disk 39, magnetic disk 29, optical disk 31, ROM 24 or RAM 25, including an operating system 35, one or more application programs 36, other program modules 37 and program data 38. A user may enter commands and information into the personal computer 20 through input devices such as a keyboard 40 and pointing device 42. Other input devices (not shown) may include a microphone, joystick, game pad, satellite dish, scanner, or the like. These and other input devices are often connected to the processing unit 21 through a serial port interface 46 that is coupled to the system bus 23, but may also be connected by other interfaces, such as a parallel port, game port or a universal serial bus (USB). A display in the form of a monitor 47 is also connected to the system bus 23 via an interface, such as a video card or adapter 48. One or more speakers 57 may also be connected to the system bus 23 via an interface, such as an audio adapter 56. In addition to the display and speakers, personal computers typically include other peripheral output devices (not shown), such as printers.
The personal computer 20 may operate in a networked environment using logical connections to one or more personal computers, such as a remote computer 49. The remote computer 49 may be another personal computer, a server, a router, a network PC, a peer device or other common network node, and typically includes many or all of the elements described above relative to the personal computer 20. The logical connections depicted in
When used in a LAN networking environment, the personal computer 20 is connected to the local area network 51 through a network interface or adapter 53. When used in a WAN networking environment, the personal computer 20 typically includes a modem 54 or other means for establishing communications over the wide area network 52, such as the Internet. The modem 54, which may be internal or external, is connected to the system bus 23 via the serial port interface 46. In a networked environment, program modules depicted relative to the personal computer 20 or portions thereof may be stored in the remote memory storage device. It will be appreciated that the network connections shown are exemplary, and other means of establishing a communications link between the computers may be used.
As implemented on a system of the type illustrated in
As illustrated in
The relational database 230 stores properties about all files in the system. It also stores some items, like contacts (i.e., non-file items), entirely. In general, it stores metadata about the types of files and items that it contains. The relational database 230 receives SQL queries from the query builder 220. The relational database 230 also sends SQL rowsets to the rowset parser component 218, with one row per item column, columns being the item properties.
The virtual folder descriptions database 232 includes the virtual folder descriptions. The virtual folder descriptions database 232 sends data to the query builder component 220, including a list of types to display in the folder, the initial filter, and the physical locations to show results from (the scopes).
With regard to the other shell folders component 234, the folder processor 210 delegates to existing shell folders from many types of items, including all files, for handlers or properties. The other shell folders component 234 sends properties from other folders to the property factory 224. The other shell folders component also sends handlers to the handler factory 214.
The folder handlers component 236 provides code behavior for the items that exist only in the database, like contacts. This is what allows non-file items to behave akin to files. The folder handlers component 236 sends handlers to the handler factory 214.
For the native handling code component 212, the folder processor 210 directly implements certain handlers based on the properties of the items. The native handling code component 212 sends handlers to the handler factory 214. For the native handling code component 212 and the folder handlers component 236, like all namespaces, virtual folders have to provide a set of handlers (context menu, icon, thumbnail, infotip, . . . ) for their items. For most of these (infotip, data object, drag-drop handler, background context menu . . . ) the virtual folder provides a common (native) handler for all the types it holds. However there are others which the author of the type has to provide (context menu on the item itself, writable property store, . . . ). The default handler can also be overridden. Virtual folders reuse this for files and allow non-file items do the same.
The handler factory 214 takes ID lists and produces code behaviors that provide context menus, icons, etc. In general, the folder processor 210 may use native handlers, external handlers, or delegate to other shell folders to get handlers, as described above with respect to the native handling code component 212, the other shell folders component 234, and the folder handlers component 236. The handler factory component 214 sends handlers to the shell browser in view 240, as requested by the view. The handler factory component 214 sends a property handler to the property writer 216.
The property writer 216 converts user intentions such as cut, copy, and paste into property rights to the file or item. A shell browser and view component 240 sends data to the property writer 216, including direct manipulation (cut/copy/paste) or editing of metadata. In general, since virtual folders present an organization based on the properties of an item, operations such as move and copy (drag-drop) become an edit on those properties. For example, moving a document, in a view stacked by author, from Author 1 to Author 2, means changing the author. The property writer component 216 implements this function.
The rowset parser 218 takes database rowsets and stores all item properties into a shell ID list structure. A rowset takes the piecewise definition of the virtual folder and builds a SQL string which can then be issued to the database. The rowset parser component 218 sends ID lists to the enumerator component 222. As described above, the rowset parser component 218 also receives data from the relational database 230, including SQL rowsets, with one row per item, the columns being item properties.
The query builder component 220 builds SQL queries. The query builder component 220 receives data from the enumerator component 222, including new filters from the navigation. The query builder component 220 also receives data from the virtual folder descriptions database 232, including a list of the types to display in the folder, the initial filter, and the physical location to show results from (the scopes). The query builder component 220 sends the SQL queries to the relational database 230.
In general, the query builder component 220 includes a set of rows (in other words a table). This is what running the query yields. The rowset parser component 218 takes each row and using the column names transforms the row into an ID list. An ID list is a well-known shell structure which is used to reference items in a namespace. Doing this allows virtual folders to be just like any other namespace to the rest of the shell. Also caching this data helps keep database access, which can be costly, to a minimum.
The enumerator component 222 operates in response to a navigation to a virtual folder. As described above, the enumerator component 222 receives ID lists from the rowset parser component 218, and sends new filters from the navigation to the query builder component 220. The enumerator 222 also sends data to the shell browser and view component 240, including ID lists that are returned to be inserted into the view after a navigation.
The property factory component 224 takes ID lists and property identifiers and returns values for those properties. The property factory component 224 receives data from the handler factory component 214 including the property handler. As described above, the property factory component 224 also receives data from the other shell folders component 234, including properties from other folders. The property factory component 224 also sends data to the shell browser and view component 240, including item properties, as requested by the view.
The shell browser and view component 240 displays the contents of a folder in a window, and handles all the user interaction with the displayed files or items, such as clicking, dragging, and navigating. Thus, the shell browser and view component 240 receives the user actions. The shell browser and view component 240 also gets the data regarding the code behaviors that it needs from the folder, in this case the folder processor 210.
As described above, the virtual folders expose regular files and folders (also known as directories) to users in different views based on their metadata instead of the actual physical underlying file system structure on the disk. Thus, the system is able to take a property that is stored in the database and represent it as a container that is like a folder. Since users are already familiar with working with folders, by presenting the virtual folders in a similar manner, users can adapt to the new system more quickly.
At a block 328, the folder processor takes these results and converts them from the rows and columns of data into an enumerator structure, which is used by the folder view to populate the screen with the resulting virtual folders and items for the user to interact upon. At a decision block 330, a user decides whether to change the view (by issuing a different query or “pivot”). For example, a user could issue a “show all artists” pivot. If the user does want to change the view, then the routine returns to block 324 where the folder processor passes this new query to the relational database, and receives back new rows and columns of results, and constructs a new enumerator structure. The process then continues as described above, as the folder view clears and updates, using the enumerator to draw the “artist” objects to the screen.
In one example, album objects are provided that represent containers that users can navigate into. For example, double-clicking the “Beatles” albums will navigate the view to see all of the Beatles' songs. The folder processor issues the “show all Beatles' songs” query to the relational database, which hands back the rows and columns of data for those songs. The folder processor creates an enumerator of all these songs, which then get drawn to the screen.
The user can also choose the view at any point while browsing virtual folders. From the above example, after narrowing down to just show Beatles songs, a user can change the view to only show the songs as albums. The process of changing the view of items into another representation is called “stacking”. This is because the items are conceptually arranged into “stacks” based on that representation. In this case, the songs are rearranged into stacks for each of the various albums. Users can then navigate into one of these stacks, only seeing the songs from that particular album. Again, the user can rearrange the view of these remaining songs into stacks based on a property (e.g., a rating, for example). If the rating property were selected, the songs from that Beatles album would be shown in stacks for a one-, two-, or a three-star rating.
The results of each query depend on which physical locations are included in the scope. For example, the scope may be made to include only the folders in the user's “my documents” folder. Alternatively, the scope could include all folders on the computer, or even all folders on multiple network connected computers. The user is able to view and change the scope through a scope property sheet. In one example, the scope property sheet could be exposed by right-clicking on the virtual folder and choosing “properties.” The user could add new folders to the scope, or remove folders that were previously added.
One group of users for which virtual folders will provide particular utility is knowledge workers. Virtual folders allow knowledge workers to easily switch between viewing documents by file type, project, case number, author, etc. Since knowledge workers each tend to have a different method for organizing documents, virtual folders can be used to accommodate these different preferences.
As illustrated in
It will be appreciated that a number of obstacles are presented to a user who wishes to navigate a physical folder file structure such as that illustrated in
The quick link elements include an “all categories” quick link 610, on “all authors” quick link 611, a “January work” quick link 612, and a selection for displaying additional quick links 613. As will be described in more detail below, quick links can be selected by a user to perform desired navigations of the virtual folders. Quick links may be provided by the system, and some quick links may be created and saved by a user.
The filter elements include a “filter by” indicator 620, an entry blank 621, a “by date” indicator 622, a “year” selector 623, a “pick an author” selector 624, a “pick a category” selector 625, and a “more filters” selector 626. The “filter by” indicator 620 directs a user to the fact that the items below can be used to filter the virtual folders or items. The entry blank 621 provides an area in which a user can type a desired new filter term. The “by date” indicator 622 directs a user to the fact that by selecting a date from the “year” selector 623, the virtual folders or items can be filtered by the selected year. The “pick an author” selector 624 allows a user to filter according to a specific author. The “pick a category” selector 625 allows a user to filter according to a selected category. The “more filters” selector 626 allows a user to pull up additional filters on the display.
The activity selectors include a “create a new category” selector 630, “activity” selectors 631 and 632, and a “more activities” selector 633. As will be described in more detail below, the activities that are presented may be for generally desirable functions, or may more specifically be directed to activities useful for the type of virtual folders that are currently being displayed. For example, the “create a new category” selector 630 can be selected by the user to create a new category which will be represented by a new stack.
As noted above, the activity selectors 631 and 632 may be more specifically directed to the type of folders or items that are being displayed. For example, the present display is of a document library, for which the “activity” selectors 631 and 632 may be directed to activities specifically tailored for documents, such as editing or creating attachments. If the present library had been a photo library, the “activity” selector 631 and 632 could be for activities specifically directed to photos, such as forming photo albums or sharing photos with other users.
The information and control elements include information lines 640 and 641, a control line 642, a backspace control 643, and information lines 644 and 645. The information lines 640 and 641 provide information as to the current navigation of the virtual folders or items. In the present example, the information line 640 indicates that the current navigation is to a document library, while the information line 641 indicates the more complete navigation, showing that the document library is within the storage area. The control line 642 provides a number of standard controls, and the backspace button 643 allows a user to back up through a navigation. The information line 644 provides numerical information about the contents of the present navigation. In the present example, the information line 644 indicates that there are 41 items which take up 100 MB in the stacks of the document library. The information line 645 is available to provide additional information, such as additional information about a file that is selected.
The stacks of the document library include an “ABC Corp.” stack 651, a “backups stack” 652, a “business plans” stack 653, an “XYZ Corp.” stack 654, and a “marketing reports” stack 655. The numbers on top of each of the stacks indicate how many items are in each stack. For example, the “ABC Corp.” stack 651 is shown to include 8 items. The total number of items of the stacks adds up to the number of items indicated in the information line 644, which as described above is 41 in the present example. A selection box SB is provided which can be utilized by a user to select a desired item. The selection of the “ABC Corp.” stack 651 yields a view of the items of that stack, as will be described below with respect to
As shown in
Another example of direct manipulation is right clicking an item and selecting delete. In one embodiment, when a deleting function is selected by a user, the user is queried whether the item should be deleted all together, or simply removed from the present virtual folder. If the item is just to be removed from a present virtual folder category stack as noted above, this can be accomplished by removing the desired category from the metadata for the item. In other words, if one of the items that had been copied from the ABC Corp. stack 651 to the West Coast stack 656 was then to be removed from the West Coast stack 656, this could be accomplished by modifying the category data for the particular file to no longer include the “West Coast” category.
The back button 643 may be utilized by a user to back through the filtering process. As described above with respect to
In one embodiment, in addition to the back button, an additional means is provided for a user to back up in or otherwise modify the filtering navigation. This additional means involves allowing the user to directly access and modify the information line 641, which correspondingly changes the filter navigation. In other words, by directly accessing and modifying the information line 641, the user can remove one or more of the applied filters, or modify the values for any of the applied filters. This feature is described in greater detail in U.S. patent application Ser. No. 10/420,040, filed Apr. 17, 2003, which is commonly assigned and hereby incorporated by reference in its entirety.
A timer may also be utilized in conjunction with a user typing in filter terms such as those shown in
In one embodiment, after a user has typed a filter term in the filter area 621, and then chooses another filter or navigation, the navigation state is updated, and the filter term in the filter area 621 is made to be empty again. In addition, as will be described in more detail below with reference to
As described above with respect to
In general, the filters may be configured to apply to different properties of the files or items. In one embodiment, the filters may be classified according to different types, such as: alphabet index; discrete values; dates; and numerical ranges. Example properties for the alphabet index may include file name, author, artist, contact friendly name, owner, document author, document title, document subject, and description. Example properties for the discrete values may include location, file type (application name), genre, track, decade (for music), rating (for music), bit rate, protected, document category, document page count, document comments, camera model, dimensions, product name, product version, image X, image Y, and document created time. Example properties for the dates may include last accessed, last modified, created on, taken on (for pictures). An example property for the numerical range may be file size.
It will be appreciated that the filters described above with respect to
As shown in
As shown in
The exemplary networked computing environment 1200 may also include one or more remote servers, such as server 1204, that stores files accessible to the computing device 1202, and connected to the computing device via a communications network, such as the Internet 1206, as shown in
An address in the conventional address bar 1302 corresponds to a specific location in a file system. As previously described, in order to edit the address displayed in the conventional address bar 1302, a user must modify the address according to specific knowledge of the file system. Alternatively, a user may select an entry in a tree view 1304 to navigate to an alternative location. Those skilled in the art will recognize that other controls external to the address bar 1302 may also be available that are not shown in the exemplary file view 1300. While the address displayed in the conventional address bar 1302 corresponds to a specific location in a file system, related files distributed among multiple folders in the file system cannot be displayed in conjunction with the conventional address bar 1302.
Similar to a conventional address, such as address 1304 of
The first segment in a virtual address bar, such as segment 1502, is referred to as a root segment, or root filter. The root segment represents the broadest category of content available for selection by the virtual address bar 1402. For example, segment 1502 “Files” would likely represent a filter that references all files accessible the computer file system. Alternatively, a root segment may represent a filter that references all system services available to the user on the computer system, or a filter that references all hardware devices installed in the computer system. Those skilled in the art will recognize that numerous other alternative root filters may be utilized by the present invention. Thus, the above described examples are given for illustrative purposes, and should not be construed as limiting upon the present invention. Additionally, the labels displayed for each segment, such as “Files” on the root segment 1502, are illustrative and should not be construed as limiting upon the present invention. According to one embodiment, a label displayed on a segment is user configurable.
Each additional segment in a virtual address bar 1402, such as segments 1504, 1506, and 1508, represent additional filters to be applied when selecting and displaying files or content in a file viewer 1400. For example, root segment 1502 “Files” references all files available to the computer system. Segment 1504 “Document Library” filters the files selected by the root segment 1502, by selecting those files that were generated as documents by the user, such as through a word processor, spreadsheet, or some other document generating application. Segment 1506 “Word Documents” filters the files selected by segment 1504 according to those documents that were generated using a word processor, such as Microsoft Corporation's Word application. Finally, segment 1508 “Author A” filters the word processing documents selected by segment 1506 according to whether they were authored by “Author A.” Thus, content selected according to the virtual address represented in the virtual address bar 1402 must satisfy the filters corresponding to all of the segments in the virtual address bar.
Segments in the virtual address bar 1402 are generally ordered from those filters that are most inclusive, to those filters that are least inclusive. For example, as previously discussed, segment 1502 “Files” is the broadest and most inclusive. Segments 1506 “Word Documents” and segment 1508 “Author A” are less inclusive. The virtual address bar 1402 illustrates the ordering of segments from left to right, and, for purposes of the present discussion, segments 1504, 1506, and 1508 are subsequent to the root segment 1502. However, it should be understood that other orientations are possible, such as a top-down arrangement, without departing from the scope of the invention. Thus, the orientation from left to right should be viewed as illustrative, and not construed as limiting on the present invention.
As previously mentioned, segments in a virtual address bar 1402, such as segments 1502, 1504, 1506, and 1508, do not necessarily correspond to specific locations in a computer file system, such as folders, drives, and directories. Thus, segment 1504 “Document Library” may reference files or content distributed on multiple servers, drives, or folders/directories. However, certain segments in a virtual address bar 1402 may reference specific locations with a computer file system hierarchy. A further discussion of virtual address segments referencing specific file system locations is given below in regard to
In contrast to a conventional address bar, each segment in a virtual address bar 1402 represents an actionable, interactive user interface element. For example, a segment in a virtual address bar 1402 is responsive to user selection, monitors whether a cursor is located over the segment for a specific period of time, and may be removed from the virtual address bar by a dragging user interaction. Hence, as shown in
In addition to selecting segments in a virtual address bar to navigate to a less restrictive segment, a user may also wish to navigate to, or select, peer filters of current segments in a virtual address. A peer filter is an alternative filter that may be selected and applied to a given segment in the virtual address bar. For example, with reference to
To illustrate alternatively selecting a segment, with reference to
In order to select an alternative peer filter, as shown in
Segments may be added to a virtual address in a virtual address bar through various user interactions at the end of the existing segments. To add a filter to a virtual address in a virtual address bar, a user may manipulate an actionable control associated with a particular filter found on a window, or file viewer with the virtual address bar. For example, with reference to the file viewer 1400 of
When a filter is added to a virtual address in a virtual address bar, a process is undertaken to ensure that the newly added filter does not conflict with any filters currently existing as part of the virtual address. If the newly added filter conflicts with an existing filter, the existing filter is removed. A newly added filter conflicts with an existing filter in a virtual address if the newly added filter varies from the breadth of the existing filter, being either more or less broad than the existing filter. Additionally, a newly added filter conflicts with an existing filter if the newly added filter is mutually exclusive to the existing filter. However, a newly added filter that is equivalent to an existing filter is not added because it has no effect. It should be understood that the above description of conflicts is given for illustration purposes, and should not be construed as limiting upon the present invention. Those skilled in the art will recognize that other conflicts between filters may exist that are contemplated as falling within the scope of the present invention.
As shown in
When a virtual address bar, such as virtual address bar 1800 (
As shown in
In order to reconfigure a virtual address bar 1900, functioning as a conventional address bar, to function normally as a virtual address bar, the user must so indicate in a manner other than clicking on the empty area of the bar. When configured to function as a conventional address bar, a virtual address bar must permit the user to click in the empty area for address editing purposes. Clicking in the empty area of a conventional address bar places an editing cursor at the end of the address/path for editing purposes. Accordingly, to reconfigure the virtual address to again function in its normal manner as described above, a user must press a predefined key or key sequence, such as the Esc or Tab key, or by place the focus on another area of a window or view by clicking on another area of the window or view. Those skilled in the art will recognize that other user actions may also be utilized to reconfigure the virtual address bar 1900 to again function in its normal mode as described above, all of which are contemplated as falling within the scope of the present invention.
At block 2104, a determination is made whether the new filter conflicts with an existing filter already in the virtual address. As previously discussed in regard to
Turning to
For purposes of the present invention, the terms “metadata” and “user modifiable metadata” exclude the shell item name. The term “shell item name” refers to the property which is used for purposes of sorting and displaying the item within the shell browser. As mentioned above, one unique aspect of the present invention is the ability of a user to edit metadata within a shell browser.
Those skilled in the art will appreciate that the present invention contemplates the presence of optional features within the window 2200. For example, the preview control 2206 and the task control 2210 are not essential features for purposes of the present invention. Moreover, other non-essential features which are not shown in
The view area 2204 provides a listview of one or more items 2212, such as file system files or folders. The term “listview” refers to an enumeration or list of items within a container. The terms “item” and “shell item” are used interchangeably herein to refer to files, folders and other such containers, and other non-file objects which can be represented in a listview. Examples of non-file objects may include, but would not be limited to, contacts, favorites and email messages. The terms “shell browser” and “file system browser” are used interchangeably herein to refer to a browser which allows a user to navigate through various namespaces including files and other non-file items.
Those skilled in the art will appreciate that the present invention contemplates many possible designs and layouts for the window 2200. For example, the preview pane 2202 is shown above the view area 2204 in
Referring next to
Those skilled in the art will appreciate that the present invention contemplates means other than context menus for enabling user modifications to displayed metadata within a shell browser. Another such means for is for the user to click on the metadata to enter an editing mode. By contrast, a user could enter an editing mode by hovering over the relevant text or object in the preview pane. Numerous alternative means are available and within the scope of the present invention.
In the event a user selects multiple items at 2704, the displayed metadata may include intersecting properties of the selected items, a union of properties, or perhaps a new property relevant to the selected items. Alternatively, the displayed metadata may include a rotating sample of metadata from each of the selected items (e.g., cycling from one selected item's metadata to the next selected item's metadata every 30 seconds). It is possible for the display of metadata which would result from a selection of all of the items to be identical to the display of metadata which would result from a null select.
The present invention enables a number of scenarios which were not possible with conventional shell browsers. As a first example, a student can manage her projects using the preview pane. When she obtains new documents as part of a project she is working on, she can select those documents in her document library and enter the name of the document author and the name of the project into keyword fields using the edit control. Now the new documents will show up in her favorite view: “Documents Grouped by Keyword and Listed by Author.” A second example of a new scenario enabled by the present invention involves an employee looking for materials for an upcoming ad campaign. As he browses through his employer's stock collection of photos using the shell browser, he selects a couple of pictures and, from the preview pane, adds a new keyword “Summer 2003 Campaign.” Having updated the metadata for a multiple selection, the employee then pivots by keyword and can view all of the “Summer 2003 Campaign” files grouped together. Many other scenarios which take advantage of the present invention would be apparent to those skilled in the art.
A user can select any one of the thumbnail images, which will cause a larger preview image of the user thumbnail selection image to be displayed within the preview control area. In addition, user selection of a thumbnail image will also allow the user to select and perform any one of the tasks listed in the task option area 3206, with respect to the selected image. A first control button allows a user to quickly and successively preview an enlarged image of each of the thumbnail images within a given folder, by iterating in one direction. In other words, a user would not have to specifically “click” on each and every successive thumbnail image in order to preview the picture. Instead the user will merely click on the first control button repeatedly to move through the folder. A second control button performs a similar iteration function but only in the opposite direction.
Turning to
Those skilled in the art will appreciate that the present invention contemplates the presence of optional features within the window 3300. For example, the metadata control 3208 and the task control 3210 are not essential features for purposes of the present invention. Moreover, other non-essential features which are not shown in
The view area 3304 provides a listview of one or more items 3312, such as file system files or folders. The term “listview” refers to an enumeration or list of items within a container. The terms “item” and “shell item” are used interchangeably herein to refer to files, folders and other such containers, and other non-file objects which can be represented in a listview. Similarly, “shell item” refers to an item in a shell library. Examples of non-file objects may include, but would not be limited to, contacts, favorites and email messages. The terms “shell browser” and “file system browser” are used interchangeably herein to refer to a browser which allows a user to navigate through various namespaces including files and other non-file items.
Those skilled in the art will appreciate that the present invention contemplates many possible designs and layouts for the window 3300. For example, the preview pane 3302 is shown above the view area 3304 in
Referring next to
The extended controls 3614 represent a level of functionality beyond what is typically available from a shell browser. For example, a default preview pane or preview control, such as those shown in
Extended controls 3614 can be made available to the user as part of an alternative previewer in a shell browser. The term “previewer” can refer to a preview control or to the a preview pane which includes a preview control. The present invention contemplates a shell browser which provides the user with a default previewer offering a standard level of functionality for multiple item types and one or more alternative previewers offering a different level of functionality for particular item types to enhance the user experience. Opening up the development of alternative previewers to independent software vendors (ISVs) and other third party developers adds value to the file browsing experience by showing relevant aspects of the file in an easily recognizable way. The present invention contemplates custom previewers for numerous file types and non-file item types including, but not limited to, image files, video files, contacts, games, scanners, video cameras, document files, spreadsheet files, slide presentation files, drawing files and tablet ink files.
The present invention enables a number of scenarios which were not possible with conventional shell browsers, some of which have been described above. Third parties are allowed to describe and demonstrate their file types by providing code that can look inside the file type and provide a meaningful image that a user will understand. For example, Apple could implement a QuickTime™ preview control, which would be displayed when the user selects a QuickTime™ file in the shell browser. This preview control could provide an alternative or extended level of functionality beyond the default previewer in the shell of an operating system, including functionality such as showing the first five seconds of a QuickTime™ movie and/or offering buttons and controls for the user to launch the QuickTime™ player. An alternative previewer for a music file could provide similar extended functionality. As those skilled in the art will appreciate, the possibilities for extended functionality in an alternative previewer are unlimited.
The context menu 3714 in
Those skilled in the art will appreciate that the present invention contemplates means other than context menus for selecting a previewer for the displayed items from a plurality of available previewers within a shell browser. Another such means is for the user to click on the preview control to enter a selection mode. Similarly, the user may be prompted to select a previewer by right-clicking within the preview pane. By contrast, a user could enter a selection mode by hovering over relevant text or over a relevant object in the preview pane. Numerous alternative means are available and within the scope of the present invention.
At 3814, the system (as opposed to the user) automatically and transparently selects a default previewer from two or more available previewers for a particular item type. The system may select a previewer in response to an event such as display of a new item type or the presence of an alternative previewer. The system is configured to select a default previewer based on logical rules. Under exceptional circumstances, the system may decide at 3816 to override the rules and select a previewer that would not have been selected under the applicable rules. For example, if the rule is to select a newly available previewer over the current default previewer, an installed application may generally have the authority to change the default previewer to the previewer now available from the installed application. However, the shell browser, for example, may reserve the right to override the change proposed by the newly installed application. For instance, an override may be appropriate when the newly installed application cannot be authenticated as a proper owner of the item type in question.
In any event, the method 3810 then associates the selected previewer with the particular item type at 3818. The selected previewer will remain in use until a different one is selected. However, if the selected previewer is an installed application, uninstalling the application will also terminate the use of the selected previewer.
Referring next to
There are many possible approaches for the extensibility mechanism referenced above in 3904. One such approach involves exposing a set of application program interfaces (APIs) so that independent software vendors (ISVs) and other third party developers may develop alternative previewers. With the API approach, a registration mechanism exists which allows an ISV to associate their preview control with an item type owned by the ISV. When an item or file of that type is selected in the shell browser, the ISV's preview control is instantiated via this registration mechanism and the extensibility API. The API provides data to the preview control: data representing the selected item(s) in the view and data representing the parent container of the items in the view. The preview control operates on this data and provides a user interface through the API which is presented in the shell browser. The user may provide input with keystrokes and mouse events which are passed by the shell browser to the preview control which can operate on those user input events.
Those skilled in the art will appreciate that many approaches are possible in the context of the extensibility mechanism of the present invention. In addition to the API approach, similar functionality may be achieved via user configuration, a pointer to HTML or hosting a flash. Moreover, the extensibility model may require that only one application that owns the item type selected may provide only one alternative previewer. In other words, the number of available previewers may be limited to a default previewer and one alternative previewer to avoid a poor user experience in which multiple registered, extended previewers are in competition with one another. However, another model would be to allow any application that can handle the selected item type to provide one additional previewer. An alternative model would allow any running code to provide one additional previewer for any item type. It may also be desirable under certain circumstances to allow replacement or removal of the default previewer. Many other models are possible and are contemplated by the present invention.
While the preferred embodiment of the invention has been illustrated and described, it will be appreciated that various changes can be made therein without departing from the spirit and scope of the invention. For example, it will be appreciated that the locations of the various UI features that are shown herein are illustrative and may be altered, and that different placements of the various UI features will still fall within the spirit and scope of the invention. Furthermore, the different aspects of the invention described herein may be formed in various combinations, also without departing from the spirit and scope of the invention.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5241671 | Reed et al. | Aug 1993 | A |
| 5333315 | Saether et al. | Jul 1994 | A |
| 5388196 | Pajak et al. | Feb 1995 | A |
| 5461710 | Bloomfield et al. | Oct 1995 | A |
| 5499364 | Klein et al. | Mar 1996 | A |
| 5504852 | Thompson-Rohrlich | Apr 1996 | A |
| 5513306 | Mills et al. | Apr 1996 | A |
| 5559948 | Bloomfield et al. | Sep 1996 | A |
| 5598524 | Johnston, Jr. et al. | Jan 1997 | A |
| 5630042 | McIntosh et al. | May 1997 | A |
| 5680563 | Edelman | Oct 1997 | A |
| 5696486 | Poliquin et al. | Dec 1997 | A |
| 5757925 | Faybishenko | May 1998 | A |
| 5790121 | Sklar et al. | Aug 1998 | A |
| 5802516 | Shwarts et al. | Sep 1998 | A |
| 5831606 | Nakajima et al. | Nov 1998 | A |
| 5835094 | Ermel et al. | Nov 1998 | A |
| 5838317 | Bolnick et al. | Nov 1998 | A |
| 5838322 | Nakajima et al. | Nov 1998 | A |
| 5867163 | Kurtenbach | Feb 1999 | A |
| 5875446 | Brown et al. | Feb 1999 | A |
| 5878410 | Zbikowski et al. | Mar 1999 | A |
| 5899995 | Millier et al. | May 1999 | A |
| 5923328 | Griesmer | Jul 1999 | A |
| 5929854 | Ross | Jul 1999 | A |
| 5933139 | Feigner et al. | Aug 1999 | A |
| 5935210 | Stark | Aug 1999 | A |
| 5987454 | Hobbs | Nov 1999 | A |
| 5987506 | Carter et al. | Nov 1999 | A |
| 6003040 | Mital et al. | Dec 1999 | A |
| 6008806 | Nakajima et al. | Dec 1999 | A |
| 6014137 | Burns | Jan 2000 | A |
| 6021262 | Cote et al. | Feb 2000 | A |
| 6023708 | Mendez et al. | Feb 2000 | A |
| 6025843 | Sklar | Feb 2000 | A |
| 6037944 | Hugh | Mar 2000 | A |
| 6061692 | Thomas et al. | May 2000 | A |
| 6061695 | Slivka et al. | May 2000 | A |
| 6078924 | Ainsbury et al. | Jun 2000 | A |
| 6097389 | Morris et al. | Aug 2000 | A |
| 6144968 | Zellweger | Nov 2000 | A |
| 6147601 | Sandelman et al. | Nov 2000 | A |
| 6181342 | Niblack | Jan 2001 | B1 |
| 6202061 | Khosla et al. | Mar 2001 | B1 |
| 6237011 | Ferguson et al. | May 2001 | B1 |
| 6240421 | Stolarz | May 2001 | B1 |
| 6243094 | Sklar | Jun 2001 | B1 |
| 6243724 | Mander et al. | Jun 2001 | B1 |
| 6246411 | Strauss | Jun 2001 | B1 |
| 6256031 | Meijer et al. | Jul 2001 | B1 |
| 6275829 | Angiulo et al. | Aug 2001 | B1 |
| 6308173 | Glasser et al. | Oct 2001 | B1 |
| 6317142 | Decoste et al. | Nov 2001 | B1 |
| 6324551 | Lamping et al. | Nov 2001 | B1 |
| 6339767 | Rivette et al. | Jan 2002 | B1 |
| 6341280 | Glass et al. | Jan 2002 | B1 |
| 6363377 | Kravets et al. | Mar 2002 | B1 |
| 6363400 | Chtchetkine et al. | Mar 2002 | B1 |
| 6401097 | McCotter et al. | Jun 2002 | B1 |
| 6411311 | Rich et al. | Jun 2002 | B1 |
| 6430575 | Dourish et al. | Aug 2002 | B1 |
| 6437807 | Berquist et al. | Aug 2002 | B1 |
| 6448985 | McNally | Sep 2002 | B1 |
| 6453311 | Powers, III | Sep 2002 | B1 |
| 6453319 | Mattis et al. | Sep 2002 | B1 |
| 6466238 | Berry et al. | Oct 2002 | B1 |
| 6466932 | Dennis et al. | Oct 2002 | B1 |
| 6480835 | Light | Nov 2002 | B1 |
| 6505233 | Hanson et al. | Jan 2003 | B1 |
| 6513038 | Hasegawa et al. | Jan 2003 | B1 |
| 6526399 | Coulson et al. | Feb 2003 | B1 |
| 6535229 | Kraft | Mar 2003 | B1 |
| 6535230 | Celik | Mar 2003 | B1 |
| 6539399 | Hazama et al. | Mar 2003 | B1 |
| 6549217 | De Greef et al. | Apr 2003 | B1 |
| 6549916 | Sedlar | Apr 2003 | B1 |
| 6563514 | Samar | May 2003 | B1 |
| 6573906 | Harding et al. | Jun 2003 | B1 |
| 6573907 | Madrane | Jun 2003 | B1 |
| 6583799 | Manolis et al. | Jun 2003 | B1 |
| 6590585 | Suzuki et al. | Jul 2003 | B1 |
| 6606105 | Quartetti | Aug 2003 | B1 |
| 6613101 | Salomon et al. | Sep 2003 | B2 |
| 6628309 | Dodson et al. | Sep 2003 | B1 |
| 6636238 | Amir et al. | Oct 2003 | B1 |
| 6636250 | Gasser | Oct 2003 | B1 |
| 6662198 | Satyanarayanan et al. | Dec 2003 | B2 |
| 6684222 | Cornelius et al. | Jan 2004 | B1 |
| 6735623 | Prust | May 2004 | B1 |
| 6738770 | Gorman | May 2004 | B2 |
| 6745206 | Mandler et al. | Jun 2004 | B2 |
| 6754829 | Butt et al. | Jun 2004 | B1 |
| 6762776 | Huapaya | Jul 2004 | B2 |
| 6762777 | Carroll | Jul 2004 | B2 |
| 6763458 | Watanabe et al. | Jul 2004 | B1 |
| 6768999 | Prager et al. | Jul 2004 | B2 |
| 6784900 | Dobronsky et al. | Aug 2004 | B1 |
| 6795094 | Watanabe et al. | Sep 2004 | B1 |
| 6801919 | Hunt et al. | Oct 2004 | B2 |
| 6803926 | Lamb et al. | Oct 2004 | B1 |
| 6816863 | Bates et al. | Nov 2004 | B2 |
| 6823344 | Isensee et al. | Nov 2004 | B1 |
| 6847959 | Arrouye et al. | Jan 2005 | B1 |
| 6853391 | Bates et al. | Feb 2005 | B2 |
| 6865568 | Chau | Mar 2005 | B2 |
| 6871348 | Cooper | Mar 2005 | B1 |
| 6876996 | Czajkowski et al. | Apr 2005 | B2 |
| 6880132 | Uemura | Apr 2005 | B2 |
| 6883009 | Yoo | Apr 2005 | B2 |
| 6883146 | Prabhu et al. | Apr 2005 | B2 |
| 6906722 | Hrebejk et al. | Jun 2005 | B2 |
| 6922709 | Goodman | Jul 2005 | B2 |
| 6938207 | Haynes | Aug 2005 | B1 |
| 6944647 | Shah et al. | Sep 2005 | B2 |
| 6947959 | Gill | Sep 2005 | B1 |
| 6950818 | Dennis et al. | Sep 2005 | B2 |
| 6952724 | Prust | Oct 2005 | B2 |
| 6980993 | Horvitz et al. | Dec 2005 | B2 |
| 7010755 | Anderson et al. | Mar 2006 | B2 |
| 7051291 | Sciammarella et al. | May 2006 | B2 |
| 7068291 | Roberts et al. | Jun 2006 | B1 |
| 7139811 | Lev Ran et al. | Nov 2006 | B2 |
| 7203948 | Mukundan et al. | Apr 2007 | B2 |
| 7240292 | Hally et al. | Jul 2007 | B2 |
| 20010034771 | Hutsch et al. | Oct 2001 | A1 |
| 20010047368 | Oshinsky et al. | Nov 2001 | A1 |
| 20010049675 | Mandler et al. | Dec 2001 | A1 |
| 20010053996 | Atkinson | Dec 2001 | A1 |
| 20010056434 | Kaplan et al. | Dec 2001 | A1 |
| 20010056508 | Arneson et al. | Dec 2001 | A1 |
| 20020019935 | Andrew et al. | Feb 2002 | A1 |
| 20020033844 | Levy et al. | Mar 2002 | A1 |
| 20020046232 | Adams et al. | Apr 2002 | A1 |
| 20020046299 | Lefeber et al. | Apr 2002 | A1 |
| 20020049717 | Routtenberg et al. | Apr 2002 | A1 |
| 20020052885 | Levy | May 2002 | A1 |
| 20020054167 | Hugh | May 2002 | A1 |
| 20020059199 | Harvey | May 2002 | A1 |
| 20020062310 | Marmor et al. | May 2002 | A1 |
| 20020075310 | Prabhu et al. | Jun 2002 | A1 |
| 20020075312 | Amadio et al. | Jun 2002 | A1 |
| 20020075330 | Rosenzweig et al. | Jun 2002 | A1 |
| 20020087740 | Castanho et al. | Jul 2002 | A1 |
| 20020087969 | Brunheroto et al. | Jul 2002 | A1 |
| 20020089540 | Geier et al. | Jul 2002 | A1 |
| 20020091679 | Wright | Jul 2002 | A1 |
| 20020091697 | Huang et al. | Jul 2002 | A1 |
| 20020091739 | Ferlitsch et al. | Jul 2002 | A1 |
| 20020095416 | Schwols | Jul 2002 | A1 |
| 20020097278 | Mandler et al. | Jul 2002 | A1 |
| 20020103998 | DeBruine | Aug 2002 | A1 |
| 20020104069 | Gouge et al. | Aug 2002 | A1 |
| 20020107973 | Lennon et al. | Aug 2002 | A1 |
| 20020111942 | Campbell et al. | Aug 2002 | A1 |
| 20020113821 | Hrebejk et al. | Aug 2002 | A1 |
| 20020120505 | Henkin et al. | Aug 2002 | A1 |
| 20020120757 | Sutherland et al. | Aug 2002 | A1 |
| 20020129033 | Hoxie et al. | Sep 2002 | A1 |
| 20020138552 | DeBruine et al. | Sep 2002 | A1 |
| 20020138582 | Chandra et al. | Sep 2002 | A1 |
| 20020138744 | Schleicher et al. | Sep 2002 | A1 |
| 20020152262 | Arkin et al. | Oct 2002 | A1 |
| 20020152267 | Lennon | Oct 2002 | A1 |
| 20020156895 | Brown | Oct 2002 | A1 |
| 20020161800 | Eld et al. | Oct 2002 | A1 |
| 20020163572 | Center et al. | Nov 2002 | A1 |
| 20020169678 | Chao et al. | Nov 2002 | A1 |
| 20020184357 | Traversat et al. | Dec 2002 | A1 |
| 20020188605 | Adya et al. | Dec 2002 | A1 |
| 20020188735 | Needham et al. | Dec 2002 | A1 |
| 20020194252 | Powers, III | Dec 2002 | A1 |
| 20020196276 | Corl et al. | Dec 2002 | A1 |
| 20020199061 | Friedman et al. | Dec 2002 | A1 |
| 20030009484 | Hamanaka et al. | Jan 2003 | A1 |
| 20030014415 | Weiss et al. | Jan 2003 | A1 |
| 20030018657 | Monday | Jan 2003 | A1 |
| 20030018712 | Harrow et al. | Jan 2003 | A1 |
| 20030028610 | Pearson | Feb 2003 | A1 |
| 20030041178 | Brouk et al. | Feb 2003 | A1 |
| 20030046260 | Satyanarayanan et al. | Mar 2003 | A1 |
| 20030069893 | Kanai et al. | Apr 2003 | A1 |
| 20030069908 | Anthony et al. | Apr 2003 | A1 |
| 20030074356 | Kaier et al. | Apr 2003 | A1 |
| 20030078918 | Souvignier et al. | Apr 2003 | A1 |
| 20030093321 | Bodmer et al. | May 2003 | A1 |
| 20030093531 | Yeung et al. | May 2003 | A1 |
| 20030093580 | Thomas et al. | May 2003 | A1 |
| 20030101200 | Koyama et al. | May 2003 | A1 |
| 20030105745 | Davidson et al. | Jun 2003 | A1 |
| 20030110188 | Howard et al. | Jun 2003 | A1 |
| 20030115218 | Bobbitt et al. | Jun 2003 | A1 |
| 20030117403 | Park et al. | Jun 2003 | A1 |
| 20030117422 | Hiyama et al. | Jun 2003 | A1 |
| 20030120928 | Cato et al. | Jun 2003 | A1 |
| 20030120952 | Tarbotton et al. | Jun 2003 | A1 |
| 20030122873 | Dieberger et al. | Jul 2003 | A1 |
| 20030126136 | Omoigui | Jul 2003 | A1 |
| 20030126212 | Morris et al. | Jul 2003 | A1 |
| 20030135495 | Vagnozzi | Jul 2003 | A1 |
| 20030135517 | Kauffman | Jul 2003 | A1 |
| 20030135659 | Bellotti et al. | Jul 2003 | A1 |
| 20030140115 | Mehra | Jul 2003 | A1 |
| 20030154185 | Suzuki et al. | Aug 2003 | A1 |
| 20030158855 | Farnham et al. | Aug 2003 | A1 |
| 20030177422 | Taraoukhine et al. | Sep 2003 | A1 |
| 20030184587 | Ording et al. | Oct 2003 | A1 |
| 20030210281 | Ellis et al. | Nov 2003 | A1 |
| 20030212680 | Bates et al. | Nov 2003 | A1 |
| 20030212710 | Guy | Nov 2003 | A1 |
| 20030222915 | Marion et al. | Dec 2003 | A1 |
| 20030225796 | Matsubara | Dec 2003 | A1 |
| 20030227487 | Hugh | Dec 2003 | A1 |
| 20030233419 | Beringer | Dec 2003 | A1 |
| 20040001106 | Deutscher et al. | Jan 2004 | A1 |
| 20040002993 | Toussaint et al. | Jan 2004 | A1 |
| 20040003247 | Fraser et al. | Jan 2004 | A1 |
| 20040008226 | Manolis et al. | Jan 2004 | A1 |
| 20040019584 | Greening et al. | Jan 2004 | A1 |
| 20040019655 | Uemura et al. | Jan 2004 | A1 |
| 20040030731 | Iftode et al. | Feb 2004 | A1 |
| 20040044696 | Frost | Mar 2004 | A1 |
| 20040044776 | Larkin | Mar 2004 | A1 |
| 20040054674 | Carpenter et al. | Mar 2004 | A1 |
| 20040056896 | Doblmayr et al. | Mar 2004 | A1 |
| 20040068525 | Aboulhosn et al. | Apr 2004 | A1 |
| 20040070612 | Sinclair et al. | Apr 2004 | A1 |
| 20040083433 | Takeya | Apr 2004 | A1 |
| 20040085581 | Tonkin | May 2004 | A1 |
| 20040088374 | Webb et al. | May 2004 | A1 |
| 20040091175 | Beyrouti | May 2004 | A1 |
| 20040098370 | Garland et al. | May 2004 | A1 |
| 20040098379 | Huang | May 2004 | A1 |
| 20040098742 | Hsieh et al. | May 2004 | A1 |
| 20040103280 | Balfanz et al. | May 2004 | A1 |
| 20040117358 | Von Kaenel et al. | Jun 2004 | A1 |
| 20040133572 | Bailey et al. | Jul 2004 | A1 |
| 20040133588 | Kiessig et al. | Jul 2004 | A1 |
| 20040148434 | Matsubara et al. | Jul 2004 | A1 |
| 20040153451 | Phillips et al. | Aug 2004 | A1 |
| 20040153968 | Ching et al. | Aug 2004 | A1 |
| 20040167942 | Oshinsky et al. | Aug 2004 | A1 |
| 20040177116 | McConn et al. | Sep 2004 | A1 |
| 20040177148 | Tsimelzon, Jr. | Sep 2004 | A1 |
| 20040177319 | Horn | Sep 2004 | A1 |
| 20040183824 | Benson et al. | Sep 2004 | A1 |
| 20040189704 | Walsh et al. | Sep 2004 | A1 |
| 20040189707 | Moore et al. | Sep 2004 | A1 |
| 20040193594 | Moore et al. | Sep 2004 | A1 |
| 20040193600 | Kaasten et al. | Sep 2004 | A1 |
| 20040193621 | Moore et al. | Sep 2004 | A1 |
| 20040193672 | Samji et al. | Sep 2004 | A1 |
| 20040193673 | Samji et al. | Sep 2004 | A1 |
| 20040199507 | Tawa | Oct 2004 | A1 |
| 20040205168 | Asher | Oct 2004 | A1 |
| 20040205625 | Banatwala et al. | Oct 2004 | A1 |
| 20040205633 | Martinez et al. | Oct 2004 | A1 |
| 20040205698 | Schliesmann et al. | Oct 2004 | A1 |
| 20040215600 | Aridor et al. | Oct 2004 | A1 |
| 20040220899 | Barney et al. | Nov 2004 | A1 |
| 20040223057 | Oura et al. | Nov 2004 | A1 |
| 20040225650 | Cooper et al. | Nov 2004 | A1 |
| 20040230572 | Omoigui | Nov 2004 | A1 |
| 20040230599 | Moore et al. | Nov 2004 | A1 |
| 20040230917 | Bales et al. | Nov 2004 | A1 |
| 20040249902 | Tadayon et al. | Dec 2004 | A1 |
| 20050004928 | Hamer et al. | Jan 2005 | A1 |
| 20050010860 | Weiss et al. | Jan 2005 | A1 |
| 20050015405 | Plastina et al. | Jan 2005 | A1 |
| 20050027757 | Kiessig et al. | Feb 2005 | A1 |
| 20050050470 | Hudson et al. | Mar 2005 | A1 |
| 20050055306 | Miller et al. | Mar 2005 | A1 |
| 20050080807 | Beilinson et al. | Apr 2005 | A1 |
| 20050097477 | Camara et al. | May 2005 | A1 |
| 20050114672 | Duncan et al. | May 2005 | A1 |
| 20050120242 | Mayer et al. | Jun 2005 | A1 |
| 20050131903 | Margolus et al. | Jun 2005 | A1 |
| 20050149481 | Hesselink et al. | Jul 2005 | A1 |
| 20050166159 | Mondry et al. | Jul 2005 | A1 |
| 20050171947 | Gautestad | Aug 2005 | A1 |
| 20050192953 | Neale et al. | Sep 2005 | A1 |
| 20050192966 | Hilbert et al. | Sep 2005 | A1 |
| 20050243993 | McKinzie et al. | Nov 2005 | A1 |
| 20050246331 | De Vorchik et al. | Nov 2005 | A1 |
| 20050246643 | Gusmorino et al. | Nov 2005 | A1 |
| 20050246664 | Michelman et al. | Nov 2005 | A1 |
| 20050256909 | Aboulhosn et al. | Nov 2005 | A1 |
| 20050257169 | Tu | Nov 2005 | A1 |
| 20050283476 | Kaasten et al. | Dec 2005 | A1 |
| 20060004692 | Kaasten et al. | Jan 2006 | A1 |
| 20060020586 | Prompt et al. | Jan 2006 | A1 |
| 20060036568 | Moore et al. | Feb 2006 | A1 |
| 20060080308 | Carpentier et al. | Apr 2006 | A1 |
| 20060129627 | Phillips et al. | Jun 2006 | A1 |
| 20060173873 | Prompt et al. | Aug 2006 | A1 |
| 20060200466 | Kaasten et al. | Sep 2006 | A1 |
| 20060200832 | Dutton | Sep 2006 | A1 |
| 20060218122 | Poston et al. | Sep 2006 | A1 |
| 20070168885 | Muller et al. | Jul 2007 | A1 |
| 20070186183 | Hudson | Aug 2007 | A1 |
| Number | Date | Country |
|---|---|---|
| 1421800 | Nov 2001 | CN |
| 2329492 | Mar 1999 | GB |
| 9938092 | Jul 1999 | WO |
| 0163919 | Aug 2001 | WO |
| WO 0225420 | Mar 2002 | WO |
| WO 2004107151 | Sep 2004 | WO |
| Number | Date | Country | |
|---|---|---|---|
| 20040230599 A1 | Nov 2004 | US |
