US 7,149,729 B2Grant
System and method for filtering and organizing items based on common elements
Issue Date:2006-12-12
•20 Claims
•41 Drawing Sheets
Abstract
A system and method for filtering and organizing items from computer memories based on common elements. In accordance with one aspect of the invention, filters are provided for manipulating the items. 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. The system utilizes virtual folders. The virtual folders expose regular files and folders to users in different views based on their metadata instead of the actual physical underlying file system structure on the disk. 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. In accordance with another aspect of the invention, libraries are provided. Libraries consist of large groups of usable types of items that can be associated together.
Metadata
Assignee
- Microsoft Corporation
Inventors
- Shaun A. Kaasten
- Jason F. Moore
- Kenneth M. Tubbs
- Relja Ivanovic
- David G. De Vorchik
- Richard M. Banks
- Patrice L. Miner
Application Information
Application Number:US 11/213,840
Filing Date:2005-08-30
Priority Date:2003-03-27
Art Unit:2162
Classifications
IPC:
G06F17/30
Patent Drawings (41 sheets)
Description
Cross-Reference(s) to Related Application(s)
[0001] This application is a divisional application of prior U.S. patent application Ser. No. 10/440,035, filed May 16, 2003, which is a continuation-in-part of U.S. patent application Ser. No. 10/403,341, filed Mar. 27, 2003, priority from the filing date of which is hereby claimed under 35 U.S.C. § 120. The entire contents of the prior applications are incorporated herein by reference.
Field of the Invention
[0002] The present invention relates to systems and methods for viewing items that are stored in a computer memory, and more particularly, to a system and method for filtering and organizing items based on common elements.
Background of the Invention
[0003] 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.
[0004] 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.
[0005] 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.
[0006] 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.
[0007] 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.
[0008] 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.
[0009] 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.
[0010] 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.
[0011] 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).
[0012] The present invention is directed to providing a system and method that overcome the foregoing and other disadvantages. More specifically, the present invention is directed to a system and method for filtering and organizing items based on common elements.
Summary of the Invention
[0013] A system and method for filtering and organizing items from computer memories based on common elements is provided. In accordance with one aspect of the invention, filters are provided for manipulating the items. 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.
[0014] 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.
[0015] 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.
[0016] 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.
[0017] 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.
[0018] 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.
[0019] 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.
[0020] In accordance with another aspect of the invention, libraries are provided. Libraries consist of large groups of usable types of items 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.
[0021] 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.
[0022] In accordance with another aspect of the invention, the items are presented to a user in virtual folders. The virtual folders expose items 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.
[0023] 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.).
[0024] In accordance with another aspect of the invention, a wide scope of items may be available. In other words, the system is able to represent 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.
[0025] 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.
Brief Description of the Drawings
[0026] 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:
[0027] FIG. 1 is a block diagram of a general purpose computer system suitable for implementing the present invention;
[0028] FIG. 2 is a block diagram of a virtual folder system in accordance with the present invention;
[0029] FIG. 3 is a flow diagram illustrative of a routine by which a user provides a query that draws back selected files and folders;
[0030] FIG. 4 is a flow diagram illustrative of a routine by which virtual folders are constructed and displayed on the screen in accordance with either a default query or a query from the user;
[0031] FIG. 5 is a tree diagram of a folder structure in accordance with a physical folder arrangement on a hard drive;
[0032] FIG. 6 is a tree diagram of a virtual folder structure;
[0033] FIG. 7 is a tree diagram of the virtual folder structure of FIG. 6 , wherein the clients stack is further filtered by contracts and year;
[0034] FIG. 8 is a tree diagram of the virtual folder structure of FIG. 7 , wherein the contracts of the clients stack are further filtered by year;
[0035] FIG. 9 is a tree diagram of the virtual folder structure of FIG. 6 , wherein the contracts stack is further filtered by clients and year, of which the clients are still further filtered by year;
[0036] FIG. 10 is a diagram illustrative of a screen display showing the stacks of a document library;
[0037] FIG. 11 is a diagram illustrative of a screen display showing the documents in the ABC Corp. stack of FIG. 10 ;
[0038] FIG. 12 is a diagram illustrative of a screen display in which a stacking function is selected for the documents of FIG. 11 ;
[0039] FIG. 13 is a diagram illustrative of a screen display in which a “stack by author” parameter is selected for the stacking function of FIG. 12 ;
[0040] FIG. 14 is a diagram illustrative of a screen display in which the files of FIG. 13 have been stacked by author;
[0041] FIG. 15 is a diagram illustrative of a screen display in which a stacking function is selected and a “stack by category” option is further selected for restacking the files of FIG. 14 ;
[0042] FIG. 16 is a diagram illustrative of a screen display in which the files of FIG. 14 have been restacked by category;
[0043] FIG. 17 is a diagram illustrative of a screen display in which a quick link for showing physical folders is selected;
[0044] FIG. 18 is a diagram illustrative of a screen display in which the physical folders are shown which contain the files of the virtual folder stacks of FIG. 17 ;
[0045] FIG. 19 is a flow diagram illustrative of a routine by which a user can directly manipulate virtual folders;
[0046] FIG. 20 is a diagram illustrative of a screen display in which a new “West Coast” stack has been added to the stacks of FIG. 10 ;
[0047] FIG. 21 is a diagram illustrative of a screen display in which direct manipulation is used for copying the files from the “ABC Corp.” stack to the “West Coast” stack of FIG. 20 ;
[0048] FIG. 22 is a flow diagram illustrative of a routine for the system dynamically generating new filter terms;
[0049] FIG. 23 is a flow diagram illustrative of a routine for the system filtering items based on the selection of a filter term;
[0050] FIG. 24 is a diagram illustrative of a screen display in which the stacks of FIG. 10 have been filtered by the term “AB”;
[0051] FIG. 25 is a diagram illustrative of a screen display in which the stacks of FIG. 10 have been filtered by the term “ABC”;
[0052] FIG. 26 is a diagram illustrative of a screen display in which the filter term “year 2002” is selected for the stacks of FIG. 10 ;
[0053] FIG. 27 is a diagram illustrative of a screen display in which the stacks of FIG. 10 have been filtered by the “year 2002” and the further selection of the filter term “month”;
[0054] FIG. 28 is a diagram illustrative of a screen display in which a list is presented for selecting a month for filtering;
[0055] FIG. 29 is a diagram illustrative of a screen display wherein the stacks of FIG. 10 have been further filtered by the month of January, and further showing a filter term of “day”;
[0056] FIG. 30 is a flow diagram illustrative of a routine for creating a new quick link;
[0057] FIG. 31 is a diagram illustrative of a screen display for creating a new quick link called “January Work” based on the filtering of FIG. 29 ;
[0058] FIG. 32 is a diagram illustrative of a screen display in which a quick link of “All Authors” is selected;
[0059] FIG. 33 is a diagram illustrative of a screen display in which a list of all of the authors of FIG. 32 is presented;
[0060] FIG. 34 is a diagram illustrative of a screen display in which “Author 1” has been selected from the list of FIG. 33 and all of the Author 1's documents are shown;
[0061] FIG. 35 is a flow diagram illustrative of a routine for creating a new library;
[0062] FIG. 36 is a diagram illustrative of a screen display in which a collection of various available libraries are shown;
[0063] FIG. 37 is a flow diagram illustrative of a routine for defining the scope of a virtual folder collection;
[0064] FIG. 38 is a block diagram illustrative of the various sources which may form the scope of a virtual folder collection;
[0065] FIG. 39 is a flow diagram illustrative of a routine for including non-file items in a virtual folder collection; and
[0066] FIG. 40 is a diagram illustrative of a screen display showing various non-file items included in a virtual folder.
Detailed Description of the Preferred Embodiment
[0067] The present invention is directed to virtual folders. Virtual folders utilize the same or similar user interfaces that are currently used for file systems. 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. Location-independent views are created which allow users to manipulate their files and folders utilizing similar controls as those presently used for managing file systems. In general, this means that users can organize and rearrange their files based on inherent properties in the files themselves, instead of the managing and organization being done as a separate part of the system. The virtual folders may represent files or items from different physical locations, such as from multiple disk drives within the same computer, between multiple computers, or different network locations, such that one view of files or items can expose files or items sitting at different physical locations. In one embodiment, the different items or files need only be connected via an IP network in order to be included.
[0068] 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.
[0069] FIG. 1 and the following discussion are intended to provide a brief, general description of a suitable computing environment in which the present invention may be implemented. 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.
[0070] With reference to FIG. 1 , an exemplary system for implementing the invention includes a general purpose computing device in the form of a conventional personal computer 20, including a processing unit 21, system memory 22, and a system bus 23 that couples various system components including the system memory 22 to the processing unit 21. The system bus 23 may be any of several types of bus structures including a memory bus or memory controller, a peripheral bus, and a local bus using any of a variety of bus architectures. The system memory includes read-only memory (ROM) 24 and random access memory (RAM) 25. A basic input/output system (BIOS) 26, containing the basic routines that helps to transfer information between elements within the personal computer 20, such as during start-up, is stored in ROM 24. The personal computer 20 further includes a hard disk drive 27 for reading from or writing to a hard disk 39, a magnetic disk drive 28 for reading from or writing to a removable magnetic disk 29, and an optical disk drive 30 for reading from or writing to a removable optical disk 31, such as a CD-ROM or other optical media. The hard disk drive 27, magnetic disk drive 28, and optical disk drive 30 are connected to the system bus 23 by a hard disk drive interface 32, a magnetic disk drive interface 33, and an optical drive interface 34, respectively. The drives and their associated computer-readable media provide non-volatile storage of computer-readable instructions, data structures, program modules, and other data for the personal computer 20. Although the exemplary environment described herein employs a hard disk 39, a removable magnetic disk 29, and a removable optical disk 31, it should be appreciated by those skilled in the art that other types of computer-readable media which can store data that is accessible by a computer, such as magnetic cassettes, flash memory cards, digital video disks, Bernoulli cartridges, random access memories (RAMs), read-only memories (ROMs), and the like, may also be used in the exemplary operating environment.
[0071] 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.
[0072] 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 FIG. 1 include a local area network (LAN) 51 and a wide area network (WAN) 52. Such networking environments are commonplace in offices, enterprise-wide computer networks, intranets, and the Internet.
[0073] 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.
[0074] As implemented on a system of the type illustrated in FIG. 1 , the present invention utilizes virtual folders which make it easier for users to perform basic tasks around file manipulation and folder navigation (browsing) and to provide higher level storage capabilities which can be leveraged in new features. The virtual folders expose files and items to users in different views based on their metadata instead of the actual physical underlying file system structure on the disk.
[0075] FIG. 2 is a block diagram of a virtual folder system 200 in accordance with the present invention. As will be described in more detail below, the virtual folders allow a user to change the “pivot” which controls the way the data is viewed. As an example, a user could view their music as a flat list of all the songs, which can be grouped by album. Alternatively, the user could switch the view to show only the genres or artists or years, etc. The user can tailor the view to see only the objects suited to the task at hand. This allows an improved browsing experience that negates the need for further navigation through folders (both down and back up). The same lessons and capabilities apply to modeling other data-types not stored as files. Contacts, for example, can be exposed to the user in this way, giving them familiar interface capabilities, as well as richer infrastructure for manipulating them than is provided by a flat address book.
[0076] As illustrated in FIG. 2 , the virtual folder system 200 includes a folder processor 210, a relational database 230, a virtual folder descriptions database 232, an other shell folders component 234, a folder handler's component 236, and a shell browser and view component 240. The folder processor 210 includes a native handling code component 212, a handler factory component 214, a property writer component 216, a rowset parser component 218, a query builder component 220, an enumerator component 222, and a property factory component 224.
[0077] 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.
[0078] 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).
[0079] 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.
[0080] 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.
[0081] 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.
[0082] 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.
[0083] 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.
[0084] 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.
[0085] 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.
[0086] 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.
[0087] 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.
[0088] 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.
[0089] 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.
[0090] 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.
[0091] FIG. 3 is a flow diagram illustrative of a routine 300 by which a user provides a query that draws back selected items. At a block 302, the folder processor gets a query from the user. In a block 304, the folder processor passes the query to the relational database. At a block 306, the relational database provides the results back to the folder processor. At block 308, the folder processor provides the results to the user in the form of virtual folders and items.
[0092] FIG. 4 is a flow diagram illustrative of a routine 320 by which virtual folders are constructed and displayed on the screen in accordance with either a default query or a query from the user. At a block 322, when a user first opens the virtual folder, a default query is used. This default query is taken from the registry. For example, the default query for a music library could be to show all the songs grouped by album. At a block 324, the folder processor constructs a query object for this query, and then passes this query to the relational database. At a block 326, the relational database generates the results of the query and passes these back to the folder processor as database rows and columns.
[0093] 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.
[0094] 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.
[0095] 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.
[0096] 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.
[0097] 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.
[0098] FIG. 5 is a tree diagram of a folder structure in accordance with a physical folder arrangement on a hard drive. This physical folder arrangement is based on the traditional implementation of folders, which may be based on NTFS or other existing file systems. Such folders are referred to as physical folders because their structuring is based on the actual physical underlying file system structure on the disk. As will be described in more detail below, this is in contrast to virtual folders, which create location-independent views that allow users to manipulate files and folders in ways that are similar to those currently used for manipulating physical folders.
[0099] As illustrated in FIG. 5 , a folder 400 is a “my documents” folder. At a first level, the folder 400 includes folders 410, 420, and 430, corresponding to Clients 1, 2, and 3, respectively. At a second level, each of the folders 410, 420, and 430 contain a folder 411, 421, and 431, respectively, which each correspond to the contracts for the selected client. At a third level, each of the folders 411, 421, and 431 contains a folder 412, 422, and 432, respectively, each corresponding to the year 2001. At the third level, each of the folders 411, 421, and 431 also contains a folder 413, 423, and 433, respectively, each corresponding to the year 2002.
[0100] 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 FIG. 5 . For example, if the user wishes to work with all of the contracts that the user has produced, the user will first need to navigate to the folder 411 to work with the contracts for Client 1, and then will have to renavigate to the folder 421 to reach the contracts for Client 2, and will again have to renavigate to the folder 431 for the contracts for Client 3. This arrangement makes it difficult for the user to access all of the contracts, and in general prevents simultaneous viewing and manipulation of all of the contracts. Similarly, if the user wishes to view all of the contracts produced in the year 2001, the user will have to navigate and renavigate to the folders 412, 422, and 432, respectively. As will be described in more detail below, the virtual folders of the present invention provide an improved file system structure.
[0101] FIG. 6 is a tree diagram of a virtual folder structure. As will be described in more detail below, virtual folders create location-independent views that allow users to manipulate their files and folders in convenient ways. As shown in FIG. 6 , the virtual folders are represented as stacks. A virtual folder 500 is an “all items” folder. At a first level, the virtual folder 500 contains virtual folders 510, 520, and 530, corresponding to clients, contracts, and year, respectively. As will be described in more detail below, this structure allows a user to access files according to a desired parameter.
[0102] FIG. 7 is a tree diagram of the virtual folder structure of FIG. 6 , wherein at a second level, the virtual folder 510 further includes virtual folders 511 and 512, which correspond to contracts and year, respectively. In other words, the clients stack of virtual folder 510 is further filtered by contracts and year. The process for determining which files and items are contained in each of the virtual folders will be described in more detail below.
[0103] FIG. 8 is a tree diagram of the virtual folder structure of FIG. 7 , wherein at a third level, the virtual folder 511 contains a virtual folder 513, which corresponds to a year. In other words, the contracts stack of virtual folder 511 is further filtered by year. While the virtual folder structure for the virtual folders 510, 511, and 513 have been structured according to clients, contracts, and year, it will be appreciated that the virtual folders allow for other structuring sequences to occur, as will be described in more detail below with reference to FIG. 9 .
[0104] FIG. 9 is a tree diagram of the virtual folder structure of FIG. 6 , wherein at a second level, the virtual folder 520 has been further filtered into virtual folders 521 and 522, corresponding to clients and year. At a third level, the virtual folder 521 has further been filtered to a virtual folder 523, corresponding to a year. The contrast between the organizational structures of FIGS. 8 and 9 helps illustrate the flexibility of the virtual folder system. In other words, in a virtual folder system, a user is able to navigate the virtual folders according to desired parameters, as opposed to being dependent on the location-dependent views of a physical file structure such as that illustrated in FIG. 5 .
[0105] FIG. 10 is a diagram illustrative of a screen display 600 showing the stacks of a document library. As noted above, stacks can be used to represent a type of virtual folder. As will be described in more detail below, the screen display 600 includes quick link elements 610–613, filter elements 620–626, activity elements 630–633, information and control elements 640–645, and virtual folder stacks 651–655.
[0106] 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.
[0107] 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.
[0108] 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.
[0109] 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.
[0110] 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.
[0111] 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 FIG. 11 .
[0112] FIG. 11 is a diagram illustrative of a screen display showing the items in the “ABC Corp.” stack 651 of FIG. 10 . It should be noted that the information lines 640 and 641 now indicate that the present navigation is showing the “ABC Corp.” stack. The “ABC Corp.” stack 651 is shown to include 8 documents 751–758, corresponding to documents 1–8, respectively. The information line 644 correspondingly indicates that there are 8 items which take up 20 MB of memory. Documents of FIG. 11 may be further arranged into stacks within the ABC Corp. stack. In other words, within the virtual folder represented by the ABC Corp. stack 651, additional virtual folders may be organized to hold the documents, as will be described below with respect to FIGS. 12–16 .
[0113] FIG. 12 is a diagram illustrative of a screen display in which a stacking function is selected for the documents of FIG. 11 . As shown in FIG. 12 , the user is able to pull up a function box 760. The function box 760 includes a “view” selection 761, an “arrange icons by” selection 762, a “stacks” selection 763, a “refresh” selection 764, an “open containing folders” selection 765, a “cut” selection 766, a “copy” selection 767, an “undo” selection 768, a “new” selection 769, and a “properties” selection 770. The selection box SB is shown to be around the “stacks” selection 763.
[0114] FIG. 13 is a diagram illustrative of a screen display in which a “stack by author” parameter is selected for the stacking function of FIG. 12 . As shown in FIG. 13 , a box 780 is displayed which presents various stacking options. The stacking options include an “unstack” option 781, a “stack by category” option 782, a “stack by author” option 783, and a “stack by a user” option 784. The selection box SB is shown to be around the “stack by author” option 783.
[0115] FIG. 14 is a diagram illustrative of a screen display in which the files of FIG. 13 have been stacked by author. As shown in FIG. 14 , stacks 791 and 792 correspond to authors Bob and Lisa, respectively. As indicated by the numbers on top of each of the stacks, the Bob stack 791 includes two items, while the Lisa stack 792 includes five items. The item 758 (corresponding to document 8) did not have an author, and so is not included in an “author” stack. The stacks 791 and 792 illustrate that stacks may be organized at multiple levels, such as within the “ABC Corp.” stack 651. Thus, the virtual folders may be formed at multiple levels, such as the “Lisa” stack 792 being within the “ABC Corp.” stack 651 which is within the document library.
[0116] FIG. 15 is a diagram illustrative of a screen display in which a “stack by category” option is further selected for restacking the files of FIG. 14 . As shown in FIG. 15 , the selection box SB is around the “stack by category” option 782. Since some of the items are already stacked in the stacks 791 and 792, the selection of the “stack by category” option 782 will restack the items, as will be described in more detail below with reference to FIG. 16 .
[0117] FIG. 16 is a diagram illustrative of a screen display in which the files of FIG. 14 are restacked by category. As shown in FIG. 16 , the stacks 793 and 794 correspond to the “XYZ Corp.” and “marketing reports” categories, respectively. The items 751 and 752, corresponding to documents 1 and 2, were not designated for any additional categories, and thus did not fall into any of the other category stacks.
[0118] FIG. 17 is a diagram illustrative of a screen display in which a quick link for physical folders is selected. The selection box SB is shown to be around the “all folders” quick link 616. As will be described in more detail below with respect to FIG. 18 , the “all folders” quick link 616 provides for switching to a view of physical folders.
[0119] FIG. 18 is a diagram illustrative of a screen display showing physical folders. The physical folders that are shown contain the files of the virtual folder stacks of FIG. 17 . In other words, the items contained within the stacks 651–655 of FIG. 17 are also contained in certain physical folders in the system. These are shown in FIG. 18 as a “My Documents” folder 851 that is located on the present computer, a “Desktop” folder 852 that is located on the present computer, a “Foo” folder 853 that is located on the hard drive C:, a “My Files” folder 854 that is located on a server, an “External Drive” folder 855 that is located on an external drive, a “My Documents” folder 856 that is located on another computer, and a “Desktop” folder 857 that is located on another computer.
[0120] As shown in FIG. 18 , a user is able to switch from the virtual files representation of FIG. 17 to the physical file representation of FIG. 18 . This allows a user to toggle between virtual file representations and physical file representations, depending on which is desired for a current task. The different locations of the physical folders 851–857 also illustrate that the scope of the virtual file system may be relatively broad, as will be described in more detail below.
[0121] FIG. 19 is a flow diagram illustrative of a routine 880 by which a user can directly manipulate virtual folders. As will be described in more detail below, the mechanisms that are provided for manipulating the virtual folders are similar to those that are currently used for manipulating regular folders (e.g., clicking and dragging, copying, pasting, etc.). As shown in FIG. 19 , at a block 882, the system provides defined actions that the user can perform for direct manipulation of the virtual folders that are represented as display objects. At a block 884, the user performs a defined action. As noted above, one example of this might be a user clicking and dragging a virtual folder to copy its contents to another virtual folder. At a block 886, the virtual folder and/or contents are manipulated as directed by the action performed by the user.
[0122] FIG. 20 is a diagram illustrative of a screen display in which a new West Coast stack 656 has been added to the stacks of FIG. 10 . The West Coast stack 656 was formed by a user creating a new category of “West Coast.” Upon its initial creation, the new West Coast stack 656 would be empty and have zero items. In the embodiment of FIG. 20 , two items have been added to the West Coast stack 656. One method for adding items to a stack is to select a particular item, and either modify or add additional categories to the category metadata for the item, such as adding the category “West Coast” to two items as was done in the embodiment of FIG. 20 . This process illustrates that the category data is a metadata property for an item that is a type of ad-hoc property. In other words, a property of this type does not have any implicit meaning, and can be assigned an arbitrary value by the user. For example, the category “property” can have any value whereas the “author” property should be the name of a person. As will be described in more detail below with reference to FIG. 21 , items may also be clicked and dragged to be copied from other stacks to the West Coast stack 656 (in which case the categories of the items are automatically updated to include “West Coast”). In this regard, FIG. 20 shows that the selection box SB is around the ABC Corp. stack 651, in preparation for its contents being copied.
[0123] FIG. 21 is a diagram illustrative of a screen display in which direct manipulation is used for copying the files from the ABC Corp. stack 651 to the West Coast stack 656. In other words, as shown in FIG. 20 , the user selected the ABC Corp. stack 651, and then as shown in FIG. 21 the user has clicked and dragged the stack to be copied to the West Coast stack 656. Thus, the West Coast stack 656 which had two items in FIG. 20 , is now shown to include a total of ten items, including the additional eight items from the ABC Corp. stack 651. When the items from the ABC Corp. stack 651 were copied to the West Coast stack 656, this was accomplished by modifying the category descriptions of the eight items to also include the “West Coast” category in addition to including the original “ABC Corp.” category. This illustrates one type of direct manipulation that may be performed.
[0124] 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.
[0125] FIG. 22 is a flow diagram illustrative of a routine 900 for the system dynamically generating new filter terms. Filter terms are utilized for manipulating the virtual folders. The filtering terms are essentially utilized as a set of tools for narrowing down a set of items. In one embodiment, filters consist of metadata categories and their values (presented to the user in the user interface as clickable links or drop-down menus). The user clicks on a filter term in order to filter down the current results set of items on the display.
[0126] FIG. 22 illustrates how filters may be dynamically generated. As shown in FIG. 22 , at a block 902, the properties (from the metadata) of the items in a collection on the present display are reviewed. In a block 904, proposed filter terms are dynamically generated based on common properties of the items. At a block 906, the proposed filter terms are presented to the user for possible selection for filtering items. As an example of this process, the system may review the properties of a set of items, and if the items generally have “Authors” as a property, the filter can provide a list of the authors to filter by. Then, by clicking on a particular Author, the items that don't have that Author are removed from the set on the display. This filtering process provides the user with a mechanism for narrowing the set of items on the display.
[0127] FIG. 23 is a flow diagram illustrative of a routine 920 for the system filtering items based on the selection of a filter term. At a block 922, the user either enters a new filter term or else selects one of the filter terms that have been presented by the system. As noted above, the filter terms may be dynamically generated by the system, or they may be preset. At a block 924, the items from the collection on the display are evaluated with regard to whether their selected properties match the filter term. For example, if the filter term is for items that were authored by “Bob,” then the items are evaluated in accordance with whether their author property includes “Bob”. At block 926, the items for which the selected properties do not match the filter term are removed from the collection on the display.
[0128] FIGS. 24–29 generally illustrate how the filtering process appears on the screen display. As will be described below with reference to FIGS. 24–29 , in one embodiment, the filtering may generally operate according to the following process. After the user clicks on a filter value, the items outside the filter range are animated off the screen. The animation is generally designed to make it obvious that items are being removed and that no new items are being added. The back button 643 may be selected by a user so as to undo the filter operations. In one embodiment, a navigation stack is created which contains the sequential filter actions, which is utilized to undo each of the filter actions when the back button 643 is selected. Each time a filter value is selected, the information areas 640 and 641 are updated to indicate the current filter value. In one embodiment, after a filter value is selected, a user is provided an option for saving a new quick link to the current filter navigation, as will be described in more detail below with respect to FIG. 30 . As filter values are selected, the filter controls may be updated to be appropriate for the items remaining in the view.
[0129] FIG. 24 is a diagram illustrative of a screen display in which the stacks of FIG. 10 have been filtered by the term “AB”. As shown, in the filter area 621, the term “AB” has been typed by a user. The information lines 640 and 641 indicate that the items in the display are now those that have been filtered by the term “AB”. As shown, the ABC Corp. stack 651 still contains eight items, while the Backups stack 652 now contains three items, and the XYZ Corp. stack 654 also contains three items. The information line 644 thus indicates that there are a total of 14 items, taking up a total of 35 MB of memory.
[0130] FIG. 25 is a diagram illustrative of a screen display in which the stacks of FIG. 10 have been filtered by the term “ABC”. With regard to the filter term “AB” of FIG. 24 , the user has simply typed the additional letter “C” to make the total filter term “ABC”. As shown in FIG. 25 , the information lines 640 and 641 now indicate that the items on the display are those that contain the term “ABC”. The ABC Corp. stack 651 is still shown to contain eight items, while the Backups stack 652 now contains only two items. The XYZ Corp. stack 654 has disappeared because none of its contents matched the “ABC” filter. The information line 644 now indicates that there are a total of 10 items in the stacks on the display, which take up a total of 25 MB of memory. FIGS. 24 and 25 thus provide examples of how a user may enter new filter terms, and how those filter terms are then used to filter the items that are shown on the display.
[0131] The back button 643 may be utilized by a user to back through the filtering process. As described above with respect to FIG. 10 , the back button 643 allows a user to back up through a navigation. With regard to the examples of FIGS. 24 and 25 , after filtering by the term “ABC” in FIG. 25 , a user could select the back button 643 so as to back up one step of the filtering process, which would return to the state of FIG. 24 . Alternatively, in another embodiment, the back button 643 may clear out the entire filter term, and may thus return to the state before that filtering occurred. In this case, by pressing the back button 643 in FIG. 25 , a user would return to the state of FIG. 10 .
[0132] 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.
[0133] A timer may also be utilized in conjunction with a user typing in filter terms such as those shown in FIG. 24 and 25 . The timer is used to monitor for a pause in the typing by the user. After a selected interval of no typing, the filter is applied. For example, in the state of FIG. 24 , a user has typed the filter term “AB”, with no significant time lag between the “A” and the “B.” After typing the term “AB”, the user pauses, thus producing the state shown in FIG. 24 , where the filter term “AB” is applied. Sometime later, the user adds the letter “C” to complete the filter term “ABC”, and then pauses again, at which point the filter term “ABC” is applied as illustrated in FIG. 25 .
[0134] 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 FIGS. 26–29 , other filter controls may be updated based on the selection of certain filter terms.
[0135] FIG. 26 is a diagram illustrative of a screen display in which the system provided filter term “year 2002” is selected. As noted above, under the by date indicator 622, the year selections 623 include the years 2000, 2001, or 2002. The selection box SB is shown to be around the year 2002, indicating that the user is selecting that as the desired filter term.
[0136] FIG. 27 is a diagram illustrative of a screen display in which the filter term “2002” has been applied. Also shown is the further selection of the “pick a month” selector 623A. As shown in FIG. 27 , after applying the filter term “2002”, the number of items in the stacks have been reduced. More specifically, the ABC Corp. stack 651 now contains six items, the Backups stack 652 now contains eight items, the Business Plans stack 653 now contains three items, and the XYZ Corp. stack 654 now contains five items. The information line 644 now indicates a total of 22 items, taking up a total of 50 MB of memory. The information lines 640 and 641 now indicate that the items shown on the display are those that have been filtered to contain the filter term “2002”.
[0137] FIG. 28 is a diagram illustrative of a screen display in which a list is presented for selecting a month for filtering. A box 950 is provided which includes the list of the months. The box 950 has been provided on the display due to the user selecting the “pick a month” selector 623A. The selection box SB is shown to be around the month of January.
[0138] FIG. 29 is a diagram illustrative of a screen display wherein the stacks of FIG. 28 have been further filtered by the month of January, and further showing a filter term of “day”. As shown in FIG. 29 , the information lines 640 and 641 now indicate that the items on the display are those that have been filtered by the term “January”. The Backups stack 652 is now shown to contain two items, while the Business Plans stack 653 is also shown to contain two items. The information line 644 indicates that there are a total of four items on the display, which take up a total of 10 MB of memory. A “pick by day” selector 623B is provided, should the user wish to further filter the results to a specific day.
[0139] As described above with respect to FIGS. 24–29 , filter terms may be presented by the system, or typed by a user. Once a filter term is selected, the remaining filter terms that are presented may be updated (e.g., after the year “2002” is selected in FIG. 26 , in FIG. 27 the options for selecting a year are no longer presented and instead a “pick a month” option is provided). As noted above, the back button 643 may be selected by a user to back through the filtering process. For example, after the month of “January” has been selected in FIG. 29 , the user may select the back button 643 to back up the filtering process to the year “2002”, as illustrated in FIG. 27 . The filter menu may also include a “stack by” function, which would work similarly to the stack by function described above with respect to FIGS. 15 and 16 . For example, a “file type” filter could have choices for “Excel”, “PowerPoint”, “Word”, and also “Stack by file type”. Choosing the “stack by” function changes the view to show stacks for the various file types.
[0140] 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.
[0141] It will be appreciated that the filters described above with respect to FIGS. 24–29 allow users to reduce a list of items to find a particular item that is of interest. As a specific example, according to the processes described above, a user could narrow a current list of documents to only show Microsoft Word files, authored by a particular person and edited in the last week. This functionality allows a user to find a particular item in a list of many, and helps the user avoid having to manually scan each item in the list.
[0142] FIG. 30 is a flow diagram illustrative of a routine 940 for creating a new quick link. As will be described in more detail below, quick links are predefined links that can be clicked on by a user to create user selected views of the sets of items. In one embodiment, a quick link may be thought of as a type of pivot. Quick links provide a mechanism for retrieving a virtual folder. Clicking a quick link can take a user to a desired folder (in the same way that clicking a “favorites” may take a user to a Web site. The quick links can be predefined by the system, or can be set by a user. For example, clicking on “all authors” could return a view stacked by authors. Clicking on “all documents” may return a flat view for all of the documents for all of the storage areas. Users can also create their own quick links.
[0143] As shown in FIG. 30 , at a block 942, a user makes a selection on the display to indicate that a new quick link should be formed from the present filter term or navigation. At a block 944, the user provides a new name for the new quick link. At a block 946, the new quick link is saved and the new quick link name is provided in the quick link section on the display.
[0144] FIG. 31 is a diagram illustrative of a screen display for creating a new quick link called “January Work” based on the filtering of FIG. 29 . As described above, in FIG. 29 , the stacks have been filtered by the month of January. In FIG. 31 , the user has indicated that the filtering of FIG. 29 should be saved as a new quick link, and has named the new quick link “January work”. Thus, the new January work quick link 612 is shown in the quick links section of the display. With regard to forming new quick links, the user is generally provided with an option such as “save this collection as a quick link”.
[0145] FIG. 32 is a diagram illustrative of a screen display in which a quick link of “All Authors” is selected. As shown in FIG. 32 , the selection box SB is shown around the All Authors selection 611. Other examples of collections that might be accessible by quick links include “all authors”, “recent documents”, “all documents I've shared”, “all documents I've authored”, “all documents not authored by me”, “desktop”, and “all types”.
[0146] FIG. 33 is a diagram illustrative of a screen display in which a list of all of the authors of the items of FIG. 32 is presented. As shown in FIG. 33 , an information line 950 is provided, which indicates columns for showing the name of an item, the author, the modified date, the type, the size, and the location of an item. A list of Authors 951–954 are shown, corresponding to Authors 1–4, respectively.
[0147] FIG. 34 is a diagram illustrative of a screen display in which “Author 1” has been selected from the list of FIG. 33 . The Author 1's documents include documents 951A and 951B, corresponding to documents 1 and 2, respectively. The document 951A is shown to have been authored by Author 1, was modified on 11 Jul., 2001, is a Microsoft Excel file, takes up 282 Kb of memory, and was obtained from the location \\server1 \folder 2. The document 951B is shown to have been authored by Author 1, was modified on 22 Dec., 2002, is a Microsoft Word file, takes up 206 kilobytes of memory, and is physically stored in the location My Documents\folder1. The locations of the documents 951A and 951B also illustrate that the virtual folders of the present invention may contain items from different physical locations, as will be described in more detail below.
[0148] FIG. 35 is a flow diagram illustrative of a routine 960 for creating a new library. One example of a library is the documents library described above with reference to FIG. 10 . In general, 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. Libraries may provide tools and activities that are related to the particular types of items. For example, in the photo library, there may be tools and filters that relate to manipulating photos, such as for creating slide shows or sharing pictures. As shown in FIG. 35 , at a block 962, a new library is created which is to include items with selected characteristics. At a block 964, the selected items are grouped into the library. At a block 966, the tools and/or activities related to the selected characteristics of the items or to other desired functions are provided.
[0149] FIG. 36 is a diagram illustrative of a screen display in which a collection of available libraries are shown. As shown in FIG. 36 , the libraries include a documents library 971, a photos and video library 972, a music library 973, a messages library 974, a contacts library 975, and a TV and movies library 976, as well as an all items library 977. The all items library 977 is shown to include 275 items, which is the total number of items from all of the other libraries combined. The information line 644 indicates a total of 275 items, which take up a total of 700 MB of memory. It should be noted that the documents library 971 is the library that was described above with respect to FIG. 10 .
[0150] FIG. 37 is a flow diagram illustrative of a routine 990 for defining the scope of a virtual folder collection. As will be described in more detail below, a virtual folder system is able to represent items from multiple physical locations (e.g., different hard drives, different computers, different networks locations, etc.) so that to a user, all of the items are readily accessible. For example, a user can be presented with music files from multiple physical locations on a single display, and manipulate the files all at once.
[0151] As shown in FIG. 37 , at a block 992, a scope is defined for the physical locations from which items are to be drawn. At a block 994, in response to a query, the items are drawn from the physical locations as defined in the scope. At a block 996, all of the items drawn by the query are presented on a single display.
[0152] FIG. 38 is a block diagram illustrative of the various sources which may form the scope of a virtual folder collection. As shown in FIG. 38 , the system 1000 may include a present computer 1010, an additional computer 1020, external and removable storage 1030, and locations on a network 1040. The overall scope 1001 is described as including all of the physical locations from which a user's items are drawn to create collections. The scope may be set and modified by a user. As noted above, other figures have illustrated that items may come from different physical locations, such as FIG. 34 showing different documents coming from a server and a My Documents folder on a present computer, and in FIG. 18 showing physical folders that are physically stored in multiple locations.
[0153] FIG. 39 is a flow diagram illustrative of a routine 1080 for including non-file items in a virtual folder collection. Non-file items are contrasted with file items that are typically located in a physical file storage. Examples of non-file items would be things like e-mails, or contacts. As shown in FIG. 39 , at a block 1082 a database is utilized to include non-file items along with file items that may be searched by a query. At a block 1084, in response to a query, both non-file items and file items are drawn to match the query. At a block 1086, both the non-file items and the file items that matched the query are presented on the display.
[0154] FIG. 40 is a diagram illustrative of a screen display showing various non-file items. As shown in FIG. 40 , the items have been filtered to those that include “John”. The items are shown to include a contact item 1101, an e-mail item 1102, and document items 1103 and 1104. The contact item 1101 and e-mail item 1102 are non-file items. The present system allows such non-file items to be included with regular file items, such that they can be organized and manipulated as desired by a user. As was described above with respect to FIG. 2 , such non-file items may be contained entirely within the relational database 230, which otherwise includes information about the properties of files.
[0155] 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.
Claims
The invention claimed is:
1. In a computer system having a display and a memory for storing items with metadata properties, a method of filtering items comprising:
providing a plurality of display objects on the display that each represent one or more items, wherein one or more of the display objects comprises a virtual folder and each virtual folder includes a numerical representation of the number of items that the virtual folder contains;
evaluating the metadata properties of the items that are represented by the display objects;
dynamically generating a filter term that corresponds to a metadata property that is shared by a plurality of the items based on the evaluation of metadata properties; and
presenting the filter term on the display, wherein the selection of the filter term causes the items that are represented on the display to be reduced to the items that share the metadata property and the numerical representation of each virtual folder to be correspondingly reduced.
2. The method of claim 1, wherein a plurality of filter terms are provided on the display.
3. The method of claim 1, wherein a quick linik is provided on the display, and the selection of the quick link provides a view of a predefined collection of items.
4. The method of claim 3, wherein the quick link corresponds to a category of metadata.
5. The method of claim 3, wherein the quick link corresponds to a specified value within a category of metadata.
6. The method of claim 1, wherein a library is provided that includes a collection of items and a set of tools for manipulating the items of the library, and the filter term is configured to be used for filtering the items of the library.
7. The method of claim 6, wherein the library comprises a shell browser.
8. The method of claim 1, wherein at least some of the items that are represented by the display objects on the display are physically stored in different physical folders.
9. The method of claim 8, wherein the different physical folders are stored at different physical locations comprising a present computer and at least one of a different computer, a location on a network, and an external storage device.
10. The method of claim 1, wherein the items that are represented by the display objects on the display comprise both file items and non-file items.
11. The method of claim 10, wherein the non-file items comprise at least one of contacts or e-mails.
12. The method of claim 1, wherein at least one of the display objects represents more than one item.
13. A system for filtering items, comprising:
a display;
means for providing a plurality of display objects on the display that each represent one or more items, wherein one or more of the display objects comprises a virtual folder and each virtual folder includes a numerical representation of the number of items that the virtual folder contains;
means for evaluating metadata properties of the items that are represented by the display objects;
means for dynamically generating a filter term that corresponds to a metadata property that is shared by a plurality of the items based on the evaluation of metadata properties; and
means for providing the filter term on the display.
14. The system of claim 13, further comprising means for providing a quick link, wherein the selection of the quick link provides a view of a predefined collection of items.
15. The system of claim 14, wherein the quick link corresponds to a category of metadata.
16. The system of claim 14, wherein the quick link corresponds to a specified value within a category of metadata.
17. The system of claim 13, further comprising means for retrieving the items that are represented by the display objects from different physical folders stored at different physical locations.
18. The system of claim 13, wherein at least one of the display objects represents more than one item.
19. A computer-readable storage medium having computer-executable components for implementing a method of filtering items with metadata properties, the items being represented on a display, the method comprising:
providing a plurality of display objects on the display that each represent one or more items, wherein one or more of the display objects comprises a virtual folder and each virtual includes a numerical representation of the number of items that the virtual folder contains;
evaluating the metadata properties of the items that are represented by the display objects;
dynamically generating a filter term that corresponds to a metadata property that is shared by a plurality of the items based on the evaluation of metadata properties;
presenting the filter term on the display, wherein the selection of the filter term causes the items that are represented on the display to be reduced to the item that share the metadata property and the numerical representation of each virtual folder to be correspondingly reduced.
20. The computer readable medium of claim 19, wherein at least one of the display objects represents more than one item.
Patent Citations (184)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US5241671(A) | 1993-08-01 | Reed et al. | Applicant |
| US5333315(A) | 1994-07-01 | Saether et al. | Applicant |
| US5388196(A) | 1995-02-01 | Pajak et al. | Applicant |
| US5499364(A) | 1996-03-01 | Klein et al. | Applicant |
| US5504852(A) | 1996-04-01 | Thompson-Rohrlich | Applicant |
| US5513306(A) | 1996-04-01 | Mills et al. | Applicant |
| US5630042(A) | 1997-05-01 | McIntosh et al. | Applicant |
| US5680563(A) | 1997-10-01 | Edelman | Examiner |
| US5696486(A) | 1997-12-01 | Poliquin et al. | Applicant |
| US5757925(A) | 1998-05-01 | Faybishenko | Applicant |
| US5802516(A) | 1998-09-01 | Shwarts et al. | Applicant |
| US5831606(A) | 1998-11-01 | Nakajima et al. | Applicant |
| US5835094(A) | 1998-11-01 | Ermel et al. | Applicant |
| US5838317(A) | 1998-11-01 | Bolnick et al. | Applicant |
| US5838322(A) | 1998-11-01 | Nakajima et al. | Applicant |
| US5875446(A) | 1999-02-01 | Brown et al. | Applicant |
| US5878410(A) | 1999-03-01 | Zbikowski et al. | Examiner |
| US5899995(A) | 1999-05-01 | Millier et al. | Applicant |
| US5933139(A) | 1999-08-01 | Feigner et al. | Applicant |
| US5987454(A) | 1999-11-01 | Hobbs | Applicant |
| US5987506(A) | 1999-11-01 | Carter et al. | Applicant |
| US6003040(A) | 1999-12-01 | Mital et al. | Applicant |
| US6008806(A) | 1999-12-01 | Nakajima et al. | Applicant |
| US6014137(A) | 2000-01-01 | Burns | Applicant |
| US6021262(A) | 2000-02-01 | Cote et al. | Applicant |
| US6025843(A) | 2000-02-01 | Sklar | Applicant |
| US6037944(A) | 2000-03-01 | Hugh | Applicant |
| US6061692(A) | 2000-05-01 | Thomas et al. | Examiner |
| US6061695(A) | 2000-05-01 | Slivka et al. | Examiner |
| US6078924(A) | 2000-06-01 | Ainsbury et al. | Applicant |
| US6097389(A) | 2000-08-01 | Morris et al. | Applicant |
| US6147601(A) | 2000-11-01 | Sandelman et al. | Applicant |
| US6181342(B1) | 2001-01-01 | Niblack | Applicant |
| US6237011(B1) | 2001-05-01 | Ferguson et al. | Applicant |
| US6240421(B1) | 2001-05-01 | Stolarz | Applicant |
| US6243094(B1) | 2001-06-01 | Sklar | Applicant |
| US6243724(B1) | 2001-06-01 | Mander et al. | Applicant |
| US6256031(B1) | 2001-07-01 | Meijer et al. | Applicant |
| US6275829(B1) | 2001-08-01 | Angiulo et al. | Applicant |
| US6317142(B1) | 2001-11-01 | Decoste et al. | Applicant |
| US6324551(B1) | 2001-11-01 | Lamping et al. | Applicant |
| US6339767(B1) | 2002-01-01 | Rivette et al. | Applicant |
| US6341280(B1) | 2002-01-01 | Glass et al. | Applicant |
| US6363377(B1) | 2002-03-01 | Kravets et al. | Applicant |
| US6401097(B1) | 2002-06-01 | McCotter et al. | Applicant |
| US6411311(B1) | 2002-06-01 | Rich et al. | Applicant |
| US6430575(B1) | 2002-08-01 | Dourish et al. | Applicant |
| US6453311(B1) | 2002-09-01 | Powers, III | Applicant |
| US6466238(B1) | 2002-10-01 | Berry et al. | Applicant |
| US6480835(B1) | 2002-11-01 | Light | Applicant |
| US6505233(B1) | 2003-01-01 | Hanson et al. | Applicant |
| US6513038(B1) | 2003-01-01 | Hasegawa et al. | Applicant |
| US6526399(B1) | 2003-02-01 | Coulson et al. | Applicant |
| US6535229(B1) | 2003-03-01 | Kraft | Applicant |
| US6539399(B1) | 2003-03-01 | Hazama et al. | Applicant |
| US6549916(B1) | 2003-04-01 | Sedlar | Applicant |
| US6573907(B1) | 2003-06-01 | Madrane | Applicant |
| US6583799(B1) | 2003-06-01 | Manolis et al. | Applicant |
| US6590585(B1) | 2003-07-01 | Suzuki et al. | Applicant |
| US6613101(B1) | 2003-09-01 | Mander et al. | Applicant |
| US6636238(B1) | 2003-10-01 | Amir et al. | Applicant |
| US6636250(B1) | 2003-10-01 | Gasser | Applicant |
| US6684222(B1) | 2004-01-01 | Cornelius et al. | Applicant |
| US6738770(B1) | 2004-05-01 | Gorman | Applicant |
| US6745206(B1) | 2004-06-01 | Mandler et al. | Applicant |
| US6754829(B1) | 2004-06-01 | Butt et al. | Applicant |
| US6762776(B1) | 2004-07-01 | Huapaya | Applicant |
| US6768999(B1) | 2004-07-01 | Prager et al. | Applicant |
| US6795094(B1) | 2004-09-01 | Watanabe et al. | Applicant |
| US6801919(B1) | 2004-10-01 | Hunt et al. | Applicant |
| US6803926(B1) | 2004-10-01 | Lamb et al. | Applicant |
| US6823344(B1) | 2004-11-01 | Isensee et al. | Applicant |
| US6847959(B1) | 2005-01-01 | Arrouye et al. | Applicant |
| US6853391(B1) | 2005-02-01 | Bates et al. | Applicant |
| US6865568(B1) | 2005-03-01 | Chau | Applicant |
| US6876996(B1) | 2005-04-01 | Czajkowski et al. | Applicant |
| US6880132(B1) | 2005-04-01 | Uemura | Applicant |
| US6883146(B1) | 2005-04-01 | Prabhu et al. | Applicant |
| US6906722(B1) | 2005-06-01 | Hrebejk et al. | Applicant |
| US6922709(B1) | 2005-07-01 | Goodman | Applicant |
| US6980993(B1) | 2005-12-01 | Horvitz et al. | Applicant |
| US2001/0034771(A1) | 2001-10-01 | Hutsch et al. | Applicant |
| US2001/0047368(A1) | 2001-11-01 | Oshinsky et al. | Applicant |
| US2001/0049675(A1) | 2001-12-01 | Mandler et al. | Applicant |
| US2001/0053996(A1) | 2001-12-01 | Atkinson | Applicant |
| US2001/0056434(A1) | 2001-12-01 | Kaplan et al. | Applicant |
| US2002/0019935(A1) | 2002-02-01 | Andrew et al. | Applicant |
| US2002/0033844(A1) | 2002-03-01 | Levy et al. | Applicant |
| US2002/0049717(A1) | 2002-04-01 | Routtenberg et al. | Applicant |
| US2002/0054167(A1) | 2002-05-01 | Hugh | Applicant |
| US2002/0059199(A1) | 2002-05-01 | Harvey | Applicant |
| US2002/0062310(A1) | 2002-05-01 | Marmor et al. | Applicant |
| US2002/0075310(A1) | 2002-06-01 | Prabhu et al. | Applicant |
| US2002/0075312(A1) | 2002-06-01 | Amadio et al. | Applicant |
| US2002/0075330(A1) | 2002-06-01 | Rosenzweig et al. | Applicant |
| US2002/0087969(A1) | 2002-07-01 | Brunheroto et al. | Applicant |
| US2002/0091679(A1) | 2002-07-01 | Wright | Applicant |
| US2002/0091697(A1) | 2002-07-01 | Huang et al. | Applicant |
| US2002/0091739(A1) | 2002-07-01 | Ferlitsch et al. | Applicant |
| US2002/0095416(A1) | 2002-07-01 | Schwols | Applicant |
| US2002/0097278(A1) | 2002-07-01 | Mandler et al. | Applicant |
| US2002/0104069(A1) | 2002-08-01 | Gouge et al. | Applicant |
| US2002/0111942(A1) | 2002-08-01 | Campbell et al. | Applicant |
| US2002/0113821(A1) | 2002-08-01 | Hrebejk et al. | Applicant |
| US2002/0120505(A1) | 2002-08-01 | Henkin et al. | Applicant |
| US2002/0138582(A1) | 2002-09-01 | Chandra et al. | Applicant |
| US2002/0152262(A1) | 2002-10-01 | Arkin et al. | Applicant |
| US2002/0156895(A1) | 2002-10-01 | Brown | Applicant |
| US2002/0161800(A1) | 2002-10-01 | Eld et al. | Applicant |
| US2002/0163572(A1) | 2002-11-01 | Center et al. | Applicant |
| US2002/0169678(A1) | 2002-11-01 | Chao et al. | Applicant |
| US2002/0196276(A1) | 2002-12-01 | Corl et al. | Applicant |
| US2003/0009484(A1) | 2003-01-01 | Hamanaka et al. | Applicant |
| US2003/0018657(A1) | 2003-01-01 | Monday | Applicant |
| US2003/0069908(A1) | 2003-04-01 | Anthony et al. | Applicant |
| US2003/0074356(A1) | 2003-04-01 | Kaier et al. | Applicant |
| US2003/0093321(A1) | 2003-05-01 | Bodmer et al. | Applicant |
| US2003/0093531(A1) | 2003-05-01 | Yeung et al. | Applicant |
| US2003/0101200(A1) | 2003-05-01 | Koyama et al. | Applicant |
| US2003/0105745(A1) | 2003-06-01 | Davidson et al. | Applicant |
| US2003/0110188(A1) | 2003-06-01 | Howard et al. | Applicant |
| US2003/0115218(A1) | 2003-06-01 | Bobbitt et al. | Applicant |
| US2003/0117422(A1) | 2003-06-01 | Hiyama et al. | Applicant |
| US2003/0126212(A1) | 2003-07-01 | Morris et al. | Applicant |
| US2003/0135495(A1) | 2003-07-01 | Vagnozzi | Applicant |
| US2003/0135517(A1) | 2003-07-01 | Kauffman | Applicant |
| US2003/0140115(A1) | 2003-07-01 | Mehra | Applicant |
| US2003/0154185(A1) | 2003-08-01 | Suzuki et al. | Applicant |
| US2003/0177422(A1) | 2003-09-01 | Tararoukhine et al. | Applicant |
| US2003/0210281(A1) | 2003-11-01 | Ellis et al. | Applicant |
| US2003/0212710(A1) | 2003-11-01 | Guy | Applicant |
| US2003/0225796(A1) | 2003-12-01 | Matsubara | Applicant |
| US2003/0227487(A1) | 2003-12-01 | Hugh | Applicant |
| US2003/0233419(A1) | 2003-12-01 | Beringer | Applicant |
| US2004/0002993(A1) | 2004-01-01 | Toussaint et al. | Applicant |
| US2004/0019655(A1) | 2004-01-01 | Uemura et al. | Applicant |
| US2004/0030731(A1) | 2004-02-01 | Iftode et al. | Applicant |
| US2004/0044696(A1) | 2004-03-01 | Frost | Applicant |
| US2004/0044776(A1) | 2004-03-01 | Larkin | Applicant |
| US2004/0054674(A1) | 2004-03-01 | Carpenter et al. | Applicant |
| US2004/0070612(A1) | 2004-04-01 | Sinclair et al. | Applicant |
| US2004/0083433(A1) | 2004-04-01 | Takeya | Applicant |
| US2004/0085581(A1) | 2004-05-01 | Tonkin | Applicant |
| US2004/0088374(A1) | 2004-05-01 | Webb et al. | Applicant |
| US2004/0091175(A1) | 2004-05-01 | Beyrouti | Applicant |
| US2004/0098370(A1) | 2004-05-01 | Garland et al. | Applicant |
| US2004/0098379(A1) | 2004-05-01 | Huang | Applicant |
| US2004/0098742(A1) | 2004-05-01 | Hsieh et al. | Applicant |
| US2004/0103280(A1) | 2004-05-01 | Balfanz et al. | Applicant |
| US2004/0117358(A1) | 2004-06-01 | Von Kaenel et al. | Applicant |
| US2004/0133572(A1) | 2004-07-01 | Bailey et al. | Applicant |
| US2004/0133588(A1) | 2004-07-01 | Kiessig et al. | Applicant |
| US2004/0148434(A1) | 2004-07-01 | Matsubara et al. | Applicant |
| US2004/0153451(A1) | 2004-08-01 | Phillips et al. | Applicant |
| US2004/0167942(A1) | 2004-08-01 | Oshinsky et al. | Applicant |
| US2001/0193594 | 2004-09-01 | Moore et al. | Applicant |
| US2004/0189704(A1) | 2004-09-01 | Walsh et al. | Applicant |
| US2004/0189707(A1) | 2004-09-01 | Moore et al. | Applicant |
| US2004/0193600(A1) | 2004-09-01 | Kaasten et al. | Applicant |
| US2004/0193621(A1) | 2004-09-01 | Moore et al. | Applicant |
| US2004/0193672(A1) | 2004-09-01 | Samji et al. | Applicant |
| US2004/0199507(A1) | 2004-10-01 | Tawa | Applicant |
| US2004/0205168(A1) | 2004-10-01 | Asher | Applicant |
| US2004/0205625(A1) | 2004-10-01 | Banatwala et al. | Applicant |
| US2004/0205633(A1) | 2004-10-01 | Martinez et al. | Applicant |
| US2004/0215600(A1) | 2004-10-01 | Aridor et al. | Applicant |
| US2001/0230599 | 2004-11-01 | Moore et al. | Applicant |
| US2004/0220899(A1) | 2004-11-01 | Barney et al. | Applicant |
| US2004/0225650(A1) | 2004-11-01 | Cooper et al. | Applicant |
| US2004/0230917(A1) | 2004-11-01 | Bales et al. | Applicant |
| US2004/0249902(A1) | 2004-12-01 | Tadayon et al. | Applicant |
| US2005/0010860(A1) | 2005-01-01 | Weiss et al. | Applicant |
| US2005/0015405(A1) | 2005-01-01 | Plastina et al. | Applicant |
| US2005/0027757(A1) | 2005-02-01 | Kiessig et al. | Applicant |
| US2005/0055306(A1) | 2005-03-01 | Miller et al. | Applicant |
| US2005/0080807(A1) | 2005-04-01 | Beilinson et al. | Applicant |
| US2005/0097477(A1) | 2005-05-01 | Camara et al. | Applicant |
| US2005/0192953(A1) | 2005-09-01 | Neale et al. | Applicant |
| US2006/0020586(A1) | 2006-01-01 | Prompt et al. | Applicant |
| CN1421800 | 2001-11-01 | Applicant | |
| GB2329492(A) | 1999-03-01 | Applicant | |
| WO1/63919(A1) | 2001-08-01 | Applicant | |
| WO225420 | 2002-03-01 | Applicant | |
| WO2004107151 | 2004-09-01 | Applicant |
Non-Patent Literature (128)
- Adobe, Inc., et al., “Adobe Photoshop CS Classroom in a Book,” Dec. 1, 2003, pp. 1-29.Applicant
- Adobe, Inc., et al., “Adobe Photoshop 7.0”, 2001; pp. 1-9.Applicant
- Heinlein, et al., “Integration of Message Passing and Shared Memory in the Stanfod FLASH Multiprocessor, Architectural Support for Programming Languages and Operating Systems,” pp. 38-50, published 1994.Applicant
- Louis, et al., “Context Learning Can Improve User Interaction Information Reuse and Integration,” Proceedings of the 2004 IEEE International Conference on, pp. 115-120, Nov. 8-10, 2004.Applicant
- Cohen, et al., “A Case for Associative Peer to Peer Overlays” -ACM SIGCOMM Computer Communications Review, vol. 33, No. 1, Jan. 2003, pp. 95-100.Applicant
- Lui, et al., “Interoperability of Peer-to-Peer File Sharing Protocols” -ACM SIGecom Exchanges, vol. 3, No. 3, Aug. 2002, pp. 25-33.Applicant
- Microsoft Windows XP Version 2002 (Screen Dumps, Figs. 1-16).Applicant
- Simpson, Alan, Windows 95 Uncut, 1995, IDG Books Worldwide, Inc., pp. 104-107.Applicant
- Feng, et al., “Schemata Transformation of Object-Oriented Conceptual Models to XML”, Computer systems Science & Engineering, vol. 18, No. 1, Jan. 2003.Applicant
- Joseph, M., “The UML for Data Modellers,” Elektron, Apr. 2004, pp. 72-73.Applicant
- Wang, G., et al., “Extending XML Schema with Nonmonotonic Inheritance,” in M.A. Jesufeld and O. Paster (eds.), ER 2003 Workshops, Lecture Notes in Computer Science 2814:402-407, 2003.Applicant
- A.T. McCray, et al., Extending the Role of Metadata in a Digital Library System, May 19, 1999, IEEE, pp. 190-199.Applicant
- Alexa T. McCray, et al., Principles for Digital Library Development, May 2001, ACM, pp. 49-53.Applicant
- Stelovsky, J., and C. Aschwanden, “Software Architecture for Unified Management of Event Notification and Stream I/O and Its Use for Recording and Analysis of User Events,” Proceedings of the 35th Annual Hawaii International Conference on System Sciences, IEEE Computer Society, Big Island, Hawaii, Jan. 7-10, 2002, p. 1862-1867.Applicant
- “About Managing Messages With Rules”, Microsoft® Outlook® 2003 Help file, 3 pp.Applicant
- “Trillian/Trillian Pro IM Clients” Products Description, © 1999-2004 Cerulean Studios, <http://www.ceruleanstudios.com> [retrieved Apr. 30, 2004].Applicant
- International Search Report of WO2004/097638 A1 (McKee, et al.) dated Nov. 11, 2004.Applicant
- Lee, J., “An End-User Perspective on File-Sharing Systems,” Communications of the ACM 46(2):49-53, Feb. 2003.Applicant
- Ohtani, A., et al., “A File Sharing Method For Storing Area Network and Its Performance Verification,” NEC Res. & Develop. 44(1):85-90, Jan. 2003.Applicant
- H. Weinreich, et al., “The Look of the Link—Concepts of the User Interface of Extended Hyperlinks,” Proceedings of the Twelfth ACM Conference on Hypertext and Hypermedia, Hypertext '01, Aarhus, Denmark, Aug. 2001, pp. 19-28.Applicant
- Seltzer, M., et al., “Journaling Versus Soft Updates: Asynchronous Meta-data Protection in File Systems,” Proceedings of the 2000 USENIX Technical Conference, San Diego, CA, Jun. 18-23, 2000, pp. 71-84.Applicant
- R. Rao, et al., “Rich Interaction in the Digital Library,” Communications of the ACM 38(4):29-39. 1995.Applicant
- Piernas, J., et al., “DualIFS: A New Journaling File System Without Meta-Data Duplication,” Conference Proceedings of the 2002 International Conference on SUPERCOMPUTING, New York, Jun. 22-26, 2002, p. 137-146.Applicant
- Manber, U., and S. Wu, “GLIMPSE: A Tool to Search Through Entire File Systems,” Proceedings of USENIX Winter 1994 Conference, San Francisco, Ca, Jan. 17-21, 1994.Applicant
- Coster, R., and D. Svensson, “Inverted File Search Algorithms for Collaborative Filtering,” Proceedings of the 25th Annual International ACM SIGIR Conference on Research and Development in Information Retrieval, Tampere, Finland, Aug. 11-15, 2002.Applicant
- Gifford, D.K., et al., “Semantic File Systems,” Proceedings of the 13th ACM Symposium on Operating Systems Principles, Pacific Grove CA., Sep. 1991, pp. 16-25.Applicant
- Blair, C., and G.E. Monahan, “Optimal Sequential File Search: A Reduced-State Dynamic Programming Approach,” European Journal of Operational Research 86(2):358-365, 1995.Applicant
- Clay, L.M., et al., Posting Protocol for Improved Keyword Search Success in Peer-to-Peer File Sharing Systems, Proceedings of SPIE-Int. Soc. Opt. Eng., Santa Clara, CA, Jan. 23-24, 2003, vol. 5019, pp. 138-149.Applicant
- Na, J., and V. Rajaravivarma, “Multimedia File Sharing in Multimedia Home or Office Business Networks,” Proceedings of the 35th Southeastern Symposium on System Theory, Morgantown, W. Va., Mar. 16-18, 2003, pp. 237-241.Applicant
- Kwon G., and K.D. Ryu, “An Efficient Peer-to-Peer File Sharing Exploiting Hierarchy and Asymmetry,” Proceedings of the 2003 Symposium on Applications and the Internet, Orlando, Fla., Jan. 27-31, 2003, pp. 226-233.Applicant
- Qian, J., et al., “ACLA: A Framework for Access Control List (ACL) Analysis and Optimization,” Fifth Joint Working Conference on Communications and Multimedia Security, Darnstadt, Germany, May 21-22, 2001, pp. 197-211.Applicant
- Rao, J.R., “Some Performance Measures of File Sharing on Multiple Computer Systems,” Proceedings of the Conference on Modeling and Simulation, vol. 6, Part I, Pittsburgh, Penn., Apr. 24-25, 1976, pp. 527-530.Applicant
- Reinauer, R., “UNIX System V.# Remote File Sharing Capabilities and Administration,” Unisphere 8(6):64-68, Sep. 1988.Applicant
- Templin, P.J., Jr., “Providing a Centralized File Sharing Resource at Bucknell University”, Proceedings of the User Services Conference for College and University Computing Services Organization, Bloomington, Ind., Oct. 25-28, 1998, pp. 289-292.Applicant
- Yamai, N. et al., “NFS-Based Secure File Sharing Over Multiple Administrative Domains With Minimal Administration,” Systems and Computers in Japan 33(14):50-58, Dec. 2002.Applicant
- Yong Kyu Lee, et al., Metadata Management of the SANtopia File System, Proceedomgs of the 8th International Conference onParallel and Distributed Systems (ICPADS 2001), Kyoungju City, Korea, Jun. 26-29, 2001, pp. 492-499, IEEE Computer Society, 2001, ISBN 0-7695-1153-8.Applicant
- Horst F. Wedde, et al., A Universal Framework for Managing Metadata in the Distributed Dragon Slayer System, Proceedings of the 26th EUROMICRO Conference (EUROMICRO'00), vol. 2, Maastricht, The Netherlands, Sep. 5-7, 2000, pp. 96-101, IEEE Computer Society, 2000, ISBN 1089-6503.Applicant
- Jolon Faichney, et al., Goldleaf Hierarchical Document Browser, Second Australian User Interface Conference (AUIC'01), Gold Coast, Queensland, Australia, Jan. 29-Feb. 1, 2001, pp. 13-20, IEEE Computer Society, 2001, ISBN 0-7695-0969-X.Applicant
- Dino Esposito, New Graphical Interface: Enhance Your Programs with New Windows XP Shell Features, MSDN Magazine, Nov. 2001, vol. 16, No. 11.Applicant
- Stuart Yeates, et al., Tag Insertion Complexity, Data Compression Conference, (DCC 2001), Snowbird, Utah, USA, Mar. 27-29, 2001,pp. 243-252, IEEE Computer Society2001, ISBN 1068-0314.Applicant
- Bipin C. Desal, et al., Resource Discovery: Modeling Cataloguing and Searching, Seventh International Workshop on Database and Expert Systems Applications (DEXA '96), Zurich, Switzerland, Sep. 9-10, 1996, pp. 70-75, IEEE-CS Press, 1996, ISBN 0-8186-7662-0.Applicant
- Gulrukh Ahanger, et al., Automatic Composition Techniques for Video Production, IEEE Transactions on Knowledge and Data Engineering, Nov./Dec. 1998, pp. 967-987, vol. 10, No. 6, IEEE Computer Society, 1998, ISBN 1041-4347.Applicant
- Jane Hunter, An Overview of the MPEG-7 Description Language (DDL), IEEE Transactions on Circuits and Systems for Video Technology, Jun. 2001, pp. 765-772, vol. 11, No. 6, IEEE Computer Society, 2001, ISBN 1051-8215.Applicant
- Philippe Salembier, et al., MPEG-7 Multimedia Description Schemes, IEEE Transactions on Circuits and Systems for Video Technology, Jun. 2001, pp. 748-759, vol. 11, No. 6, IEEE Computer Society, 2001, ISBN 1051-8215.Applicant
- Thomas Sikora, The MPEG-7 Visual Standard for Content Description—An Overview, IEEE Transactions on Circuits and Systems for Video Technology, Jun. 2001, pp. 696-702, vol. 11, No. 6, IEEE Computer Society, 2001, ISBN 1051-8215.Applicant
- B.S. Manjunath, Et al., Color and Texture Descriptors, IEEE Transactions on Circuits and Systems for Video Technology, Jun. 2001, pp. 703-715, vol. 11, No. 6, IEEE Computer Society, 2001, ISBN 1051-8215.Applicant
- “Predefined Properties” http://help.sap.com|saphelp—ep50sp5/helpdata/en/la/9a4a3b80f2ec40aa7456bc87a94259/content.htm.Applicant
- “Info Vision Infonnation Management System” http://66.1 02. 7.1 04/search?q=cache:m IXV6K6sQOQJ:www.amlib.net|products/infovision.htm+customised+multi+property+file+navigation&h|=en.Applicant
- “Previewing Files in the Common Dialog” http://www.elitevb.com|contentiO 1,0084,0 II.Applicant
- “TdcFolderListView component” http://www.appcontrols.com|manuals|diskcontrols/index.htm1?tdcfolderlistview.htm.Applicant
- “Previewing Files” http://developer.apple.com|documentation/QuickTimeIINMAC/QT/iqMovieToolbox.1a.htm.Applicant
- “Text File Previewer 2.0 Beta” http://www.freedownloadscenter.com|Utilities|Text- Viewers|Text- File]reviewer.html.Applicant
- “Your Next OS: Windows 2006?” http://www.pcworld.com|newsiarticle/O,aid,II3'631,OO.asp.Applicant
- “GetOpenFileName Function,” downloaded from <http://msdn.microsoft.com>; date of first publication prior to Mar. 28, 2005; 2 pages.Applicant
- “GetSaveFileName Function,” downloaded from <http://msdn.microsoft.com>; date of first publication prior to Mar. 28, 2005; 2 pages.Applicant
- “Using Common Dialog Boxes,” downloaded from <http://msdn.microsoft.com>; date of first publication prior to Mar. 28, 2005; 8 pages.Applicant
- “How to Use a Common Dialog File Open Dialog with Win32 API,” downloaded from <http://support.microsoft.com>; date of first publication prior to Mar. 28, 2005; 3 pp.Applicant
- “Creating an Enhanced Metafile,” downloaded from <http://msdn.microsoft.com>; date of first publication prior to Mar. 28, 2005; 2 pages.Applicant
- “Common Dialog Box Library,” downloaded from <http://msdn.microsoft.com>: date of first publication prior to Mar. 28, 2005; 8 pages.Applicant
- “OPENFILENAME Structure,” downloaded from <http://msdn.microsoft.com>; date of first publication prior to Mar. 28, 2005; 7 pages.Applicant
- “Open and Save as Dialog Boxes,” downloaded from <http://msdn.microsoft.com>; date of first publication prior to Mar. 29, 2005; 9 pages.Applicant
- “Customizing common dialog boxes,” downloaded from http://msdn.microsoft.com; date for first publication prior to Apr. 20, 2005, 4 pages.Applicant
- G.D. Venolia, et al., Supporting Email Workflow. Microsoft Research Technical Report MSR-TR-2001-88. Revised Dec. 2001 (Original Sep. 2001). Microsoft Corporation, Redmond, WA.Applicant
- G.D. Venolia and C. Neustaedter. Understanding Sequence and Reply Relationships within Email Converstations: A Mixed-Model Visualization. Microsoft Research Technical Report MSR-TR-2002-102. Sep. 23, 2002 (Revised Jan. 13, 2003).Applicant
- Microsoft Digital Image Suite User's Manual, Version 9.0. pp. 105-118, Available: http://www.microsoft.com/products/imaging/guides/SuiteManual.pdf, Apr. 30, 2004.Applicant
- “Using Tags to Organize Your Photos.”, Adobe Photoshop Album 2.0 Tutorial, Available: http://www.adobe.com/digitalimag/tips/phsaltaggin/pdfs/phsaltaggin.pdf, Apr. 30, 2004.Applicant
- Examples of dialogs user interfaces; date of first publication prior to Mar. 31, 2005; 8 pages.Applicant
- “Visually Theming and Styling Your Applications and Documents” (CLI 308); downloaded from <http://msdn.microsoft.com/longhorn/pdcmaterials/pdctalksavalon/>; date of first publication prior to Mar. 31, 2005; 34 pages.Applicant
- New User Interface Possibilities in Longhorn (CLI 304); downloaded from <http://msdn.microsoft.com/longhorn/pdcmaterials/pdctalksavalon/>; date of first publication prior to Mar. 31, 2005; 45 pages.Applicant
- Windows Forms: Exploiting Windows Longhorn“Features from Within Your Application” (CLI 391); downloaded from http://msdn.microsoft.com/longhorn/pdcmaterials/pdctalksavalon/>; date of first publication prior to Mar. 31, 2005; 27 pages.Applicant
- MessageBox Function; downloaded from <http://msdn.microsoft.com>; date of first publication prior to Mar. 31, 2005; 4 pages.Applicant
- Creating and Installing Theme Files; downloaded from <http://msdn.microsoft.com>; date of first publication prior to Feb. 21, 2005; 4 pages.Applicant
- “MessageBox Function”; downloaded from <http://msdn.microsoft.com>; date of first publication prior to Mar. 31, 2005; 4 pages.Applicant
- “Creating and Installing Theme Files”; downloaded from <http://msdn.microsoft.com>; date of first publication prior to Feb. 21, 2005; 4 pages.Applicant
- “About Dialog Boxes”; downloaded from <http://msdn.microsoft.com>; date of first publication prior to Feb. 21, 2005; 10 pages.Applicant
- “Property Sheets and Inspectors”; downloaded from <http://msdn.microsoft.com>; date of first publication prior to Feb. 21, 2005; 6 pages.Applicant
- “PROPSHEETPAGE”; downloaded from <http://msdn.microsoft.com>; date of first publication prior to Feb. 21, 2005; 3 pages.Applicant
- “DialogProc Function”; downloaded from <http://msdn.microsoft.com>; date of first publication prior to Feb. 21, 2005; 2 pages.Applicant
- “Creating Wizards”; downloaded from <http://msdn.microsoft.com>; date of first publication prior to Mar. 31, 2005; 17 pages.Applicant
- “Property Sheets”; downloaded from <http://msdn.microsoft.com>; date of first publication prior to Mar. 31, 2005; 7 pages.Applicant
- “Property Sheet Reference”; downloaded from <http://msdn.microsoft.com>; date of first publication prior to Mar. 31, 2005; 5 pages.Applicant
- “DRAWITEMSTRUCT Structure”; downloaded from <http://msdn.microsoft.com>; date of first publication prior to Feb. 25, 2005; 3 pages.Applicant
- “Using Buttons”; downloaded from <http://msdn.microsoft.com>; date of first publication prior to Feb. 25, 2005; 5 pages.Applicant
- Button Messages; downloaded from <http://msdn.microsoft.com>; date of first publication prior to Feb. 25, 2005; 4 pages.Applicant
- “Button Styles”; downloaded from <http://msdn.microsoft.com>; date of first publication prior to Feb. 25, 2005; 2 pages.Applicant
- “CreateWindow Function”; downloaded from <http://msdn.microsoft.com>; date of first publication prior to Feb. 25, 2005; 5 pages.Applicant
- “Using Dialog Boxes”; downloaded from <http://msdn.microsoft.com>; date of first publication prior to Mar. 31, 2005; 8 pages.Applicant
- “CreatePropertySheetPage Function”; downloaded from <http://msdn.microsoft.com>; date of first publication prior to Mar. 31, 2005; 1 page.Applicant
- “DestroyPropertySheetPage Function”; downloaded from <http://msdn.microsoft.com>; date of first publication prior to Mar. 31, 2005; 1 page.Applicant
- “PropertySheet Function”; downloaded from <http://msdn.microsoft.com>; date of first publication prior to Mar. 31, 2005; 2 pages.Applicant
- “PropSheetPageProc Function”; downloaded from <http://msdn.microsoft.com>; date of first publication prior to Mar. 31, 2005; 2 pages.Applicant
- “PropSheetProc Function”; downloaded from <http://msdn.microsoft.com>; date of first publication prior to Mar. 31, 2005; 2 pages.Applicant
- “PSN—KILLACTIVE Notification”; downloaded from <http://msdn.microsoft.com>; date of first publication prior to Mar. 31, 2005; 1 page.Applicant
- “PSN—QUERYCANCEL Notification”; downloaded from <http://msdn.microsoft.com>; date of first publication prior to Mar. 31, 2005; 1 page.Applicant
- “PSN—RESET Notification”; downloaded from <http://msdn.microsoft.com>; date of first publication prior to Mar. 31, 2005; 1 page.Applicant
- “PSN—SETACTIVE Notification”; downloaded from <http://msdn.microsoft.com>; date of first publication prior to Mar. 31, 2005; 1 page.Applicant
- “PSN—TRANSLATEACCELERATOR Notification”; downloaded from <http://msdn.microsoft.com>; date of first publication prior to Mar. 31, 2005; 1 page.Applicant
- “PSN—WIZBACK Notification”; downloaded from <http://msdn.microsoft.com>; date of first publication prior to Mar. 31, 2005; 3 pages.Applicant
- “PSN—WIZFINISH Notification”; downloaded from <http://msdn.microsoft.com>; date of first publication prior to Mar. 31, 2005; 1 page.Applicant
- “PSN—WIZNEXT Notification”; downloaded from <http://msdn.microsoft.com>; date of first publication prior to Mar. 31, 2005; 3 pages.Applicant
- “PSM—ADDPAGE Message”; downloaded from <http://msdn.microsoft.com>; date of first publication prior to Mar. 31, 2005; 2 pages.Applicant
- “PSM—IDTOINDEX Message”; downloaded from <http://msdn.microsoft.com>; date of first publication prior to Mar. 31, 2005; 1 page.Applicant
- “PSM—INDEXTOHWND Message”; downloaded from <http://msdn.microsoft.com>; date of first publication prior to Mar. 31, 2005; 1 page.Applicant
- “PSM—INDEXTOID Message”; downloaded from <http://msdn.microsoft.com>; date of first publication prior to Mar. 31, 2005; 1 page.Applicant
- “PSM—INDEXTOPAGE Message”; downloaded from <http://msdn.microsoft.com>; date of first publication prior to Mar. 31, 2005; 1 page.Applicant
- “PSM—PAGETOINDEX Message”; downloaded from <http://msdn.microsoft.com>; date of first publication prior to Mar. 31, 2005; 1 page.Applicant
- “PSM—PRESSBUTTON Message”; downloaded from <http://msdn.microsoft.com>; date of first publication prior to Mar. 31, 2005; 1 page.Applicant
- “PSM—QUERYSIBLINGS Message”; downloaded from <http://msdn.microsoft.com>; date of first publication prior to Mar. 31, 2005; 1 page.Applicant
- “PSM—SETCURSEL Message”; downloaded from <http://msdn.microsoft.com>; date of first publication prior to Mar. 31, 2005; 1 page.Applicant
- “PSM—SETCURSELID Message”; downloaded from <http://msdn.microsoft.com>; date of first publication prior to Mar. 31, 2005; 1 page.Applicant
- “PSM—SETFINISHTEXT Message”; downloaded from <http://msdn.microsoft.com>; date of first publication prior to Mar. 31, 2005; 1 page.Applicant
- “PSM—SETHEADERTITLE Message”; downloaded from <http://msdn.microsoft.com>; date of first publication prior to Mar. 31, 2005; 1 page.Applicant
- “PSM—SETWIZBUTTONS Message”; downloaded from <http://msdn.microsoft.com>; date of first publication prior to Mar. 31, 2005; 2 pages.Applicant
- “PROPSHEETHEADER Structure”; downloaded from <http://msdn.microsoft.com>; date of first publication prior to Mar. 31, 2005; 5 pages.Applicant
- “PROPSHEETPAGE Structure”; downloaded from <http://msdn.microsoft.com>; date of first publication prior to Mar. 31, 2005; 4 pages.Applicant
- “PSHNOTIFY Structure”; downloaded from <http://msdn.microsoft.com>; date of first publication prior to Mar. 31, 2005; 1 page.Applicant
- “BCM—GETIDEALSIZE Message” ; downloaded from <http://msdn.microsoft.com>; date of first publication prior to Mar. 31, 2005; 1 page.Applicant
- “PSM—SETTITLE Message”; downloaded from <http://msdn.microsoft.com>; date of first publication prior to Mar. 31, 2005; 1 page.Applicant
- Wikipedia, File Allocation Table, 2006, <http://en.wikipedia.org/wiki/File—Allocation—Table>.Applicant
- European Search Report for 03007909.9-2211 dated Jun. 30, 2006.Applicant
- D. Esposito, “More Windows 2000 UI Goodies: Extending Explorer Views by Customizing Hypertext Template Files”, MSDN Magazine, <http://msdn.microsoft.com/msdnmag/issues/0600/w2kui2/default.aspx?print=true?, first date of publication unknown but no later than Jun. 2000, 15 pages.Applicant
- Microsoft: “Microsoft Windows 2000 Professional Step by Step—Lesson 3—Managing Files and Folders” <http://www.microsoft.com/mspress/books/sampshap/1589.asp>, Jan. 5, 2000, 12 pages.Applicant
- Australian Search Report for SG 200301764-7 dated Mar. 30, 2006.Applicant
- D. Esposito, Visual C++ Windows Shell Programming, Dec. 1, 1998, Apress, ISBN 1861001843, pp. 463-469.Applicant
- P. DiLascia, “More Fun with MFC:DIBs, Palettes, Subclassing, and a Gamut of Goodies, Part III”, Microsoft Systems Journal, Jun. 1997, 20 pages.Applicant
- Australian Written Opinion for SG 200301764-7 dated Mar. 30, 2006.Applicant
- Windows Commander, <http://web.archive.org/web/20030207145141/www.ghisler.com/featurel.htm> (Feb. 7, 2003) and <http://web.archive.org/web/20021017022627/www.ghisler.com/addons.htm> (Oct. 17, 2002), 7 pages.Applicant
- Directory Opus 6.1—Viewer SDK Plugin SDK 1.0, GP Software, 2001, <http://web.archive.org/web/20030219151121/www.gpsoft.com.au/Developer.html>, first date of publication unknown but, prior to Feb. 19, 2003, 30 pages.Applicant