Not applicable.
Not applicable.
Many computer-related applications allow the ability to perform keyword searches for information. Applications such as email programs, word-processing programs, and Internet browsers offer various search capabilities. In relation to browsers, with the wealth of information that may be found on the Internet, various search engines are utilized for keyword searching of the Internet for content specific to the keywords which are inputted into the search engine. A typical search engine generates a set of search results based on the occurrence of the keywords in web pages or meta-tags within web pages.
File Open Dialogs currently contain both browsing capability and search capability. However, both current methods have drawbacks. Current browse capability in a file open dialog is time consuming and difficult for the user. Typical browsing within a file open dialog uses a “browse” metaphor to locate a file to open. A “browse” metaphor scans a hard drive, a database, a list of files, etc. for an item of interest. Several problems exist with the “browse” metaphor. Specifically, the user must understand the hierarchical organization of the data contained on the hard drive. Further, the user must also remember the specific file name associated with the file they wish to retrieve.
A faster way to locate a file to open is through the use of a “search” metaphor. A “search” metaphor allows the user to input a set of keywords that can be matched against all files contained on the hard drive. An example of this type of “search” metaphor is contained in the software ASK JEEVES Desktop Search (“ASK JEEVES”). ASK JEEVES allows a user to search for files and emails on a computer using a keyword or phrase. ASK JEEVES accomplishes this by adding additional windows to a common file open dialog. Essentially, when ASK JEEVES is indexed, an additional window is pasted on top of the common file open dialog. The window includes a “Desktop Search” field and a “Search My Computer” button. A user then types a keyword into the search field. Once a user hits enter or the “Search My Computer” button, ASK JEEVES opens its search application and a second window is displayed along with the results of the search. The results of the search are displayed as files along with their specific full path and file names. From the second window a user is allowed to select a file. Once a file is selected, ASK JEEVES enters the full path name corresponding with the file name into the common file open dialog to open the file.
While ASK JEEVES provides a search function for searching a computer hard drive, it accomplishes the search using multiple windows pasted on the common file open dialog. It further uses the full path name of the file along with the common file open dialog to obtain the file. The multiple windows create a visually confusing search while the need for the common file open dialog causes a limited and slow searching function.
A method for modifying a file open dialog is provided to allow for search capability. The method uses computer hardware and software to provide search capability in a file open dialog. Specifically, a namespace extension is used to create a custom view that provides search capability in a file open dialog. The custom view may include but is not limited to a search field, a search icon, a search toolbar, a results field, a show toolbar, and a preview pane.
A namespace extension is created that provides a custom view along with searching capability. Creation of the namespace extension is accomplished using an existing Shell. The Shell generally organizes objects into a hierarchical namespace, and provides users and applications with a consistent and efficient way to access and manage objects. The Shell interacts with a Shell namespace to organize the file system and the virtual objects managed by the Shell into a single tree-structured hierarchy. The Shell namespace presents the namespace extension as a folder. When a user browses into this folder, the storable medium is presented as a tree-structured hierarchy of folders and files, much like the rest of the Shell namespace.
A namespace extension consists of 2 basic components: a data manager and an interface between the data manager and a browser. Every folder that the browser displays is represented by a Component Object Model (COM) object called a folder object and each time the user interacts with the folder or its contents, the Shell also communicates with the associated folder object. The folder object then responds to the user's action, and the Shell updates the browser's display.
To build the custom view, a COM interface is implemented. The interface is used to build and manage a custom Shell folder. Specifically, the interface displays or performs an operation on the contents of the Shell's namespace and provides communication between the Shell and the files. The namespace extension allows the data stored in the file to be pulled into the Shell.
Next, a series of interfaces are implemented to present the custom view in the file open dialog. As stated above, the custom view file open dialog includes but is not limited to a search field, a search icon, a search toolbar, a results field, a show toolbar, and a preview pane. The series of interfaces provide a channel of communication between a view object and the file open dialog and allow the file open dialog to communicate with the custom view. The interfaces further allow the Shell view to handle a standard shell extension in a common dialog to communicate with the custom view file open dialog.
The present invention is described in detail below with reference to the attached drawing figures, wherein:
The present invention will be better understood from the detailed description provided below and from the accompanying drawings of various embodiments of the invention, which describe, for example, methods and systems for modifying a file open dialog to allow for search capability. The detailed description and drawings, however, should not be read to limit the invention to the specific embodiments. Rather, these specifics are provided for explanatory purposes that help the invention to be better understood.
Having briefly described an overview of the present invention in the Summary section above, an exemplary operating environment is described below.
Exemplary Operating Environment
Referring to the drawings in general and initially to
The invention is operational with numerous other general purpose or special purpose computing system environments or configurations. Examples of well known computing systems, environments, and/or configurations that may be suitable for use with the invention include, but are not limited to, personal computers, server computers, hand-held or laptop devices, multiprocessor systems, microprocessor-based systems, set top boxes, programmable consumer electronics, network PCs, minicomputers, mainframe computers, distributed computing environments that include any of the above systems or devices, and the like.
The invention may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc., that perform particular tasks or implement particular abstract data types. 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 computer storage media including memory storage devices.
With reference to
Computer 110 typically includes a variety of computer-readable media. Computer-readable media can be any available media that can be accessed by computer 110 and includes both volatile and nonvolatile media, removable and non-removable media. By way of example, and not limitation, computer readable media may comprise computer storage media and communication media. Computer storage media includes both volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer-readable instructions, data structures, program modules or other data. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by computer 110. Communication media typically embodies computer-readable instructions, data structures, or program modules. By way of example, and not limitation, communication media includes wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media. Combinations of any of the above should also be included within the scope of computer-readable media.
The system memory 130 includes computer storage media in the form of volatile and/or nonvolatile memory such as read only memory (ROM) 131 and random access memory (RAM) 132. A basic input/output system (BIOS) 133, containing the basic routines that help to transfer information between elements within computer 110, such as during start-up, is typically stored in ROM 131. RAM 132 typically contains data and/or program modules that are immediately accessible to and/or presently being operated on by processing unit 120. By way of example, and not limitation,
The computer 110 may also include other removable/non-removable, volatile/nonvolatile computer storage media. By way of example only,
The drives and their associated computer storage media discussed above and illustrated in
The computer 110 may operate in a networked environment using logical connections to one or more remote computers, such as a remote computer 180. The remote computer 180 may be a 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 computer 110, although only a memory storage device 181 has been illustrated in
When used in a LAN networking environment, the computer 110 is connected to the LAN 171 through a network interface or adapter 170. When used in a WAN networking environment, the computer 110 typically includes a modem 172 or other means for establishing communications over the WAN 173, such as the Internet. The modem 172, which may be internal or external, may be connected to the system bus 121 via the network interface 170, or other appropriate mechanism. In a networked environment, program modules depicted relative to the computer 110, or portions thereof, may be stored in a remote memory storage device. By way of example, and not limitation,
Although many other internal components of the computer 110 are not shown, those of ordinary skill in the art will appreciate that such components and the interconnection are well known. Accordingly, additional details concerning the internal construction of the computer 110 need not be disclosed in connection with the present invention.
When the computer 110 is turned on or reset, the BIOS 133, which is stored in the ROM 131, instructs the processing unit 120 to load the operating system, or necessary portion thereof, from the hard disk drive 141 into the RAM 132. Once the copied portion of the operating system, designated as operating system 144, is loaded in RAM 132, the processing unit 120 executes the operating system code and causes the visual elements associated with the user interface of the operating system 134 to be displayed on the monitor 191. Typically, when an application program 145 is opened by a user, the program code and relevant data are read from the hard disk drive 141 and the necessary portions are copied into RAM 132, the copied portion represented herein by reference numeral 135.
The subject matter of the present invention is described with specificity herein to meet statutory requirements. However, the description itself is not intended to limit the scope of this patent. Rather, the inventors have contemplated that the claimed subject matter might also be embodied in other ways, to include different steps or combinations of steps similar to the ones described in this document, in conjunction with other present or future technologies. Moreover, although the terms “step” and/or “block” may be used herein to connote different elements of methods employed, the terms should not be interpreted as implying any particular order among or between the various steps herein disclosed unless and except when the order of individual steps is explicitly described.
File Open Dialog Searching Using a Namespace Extension
The described method may be implemented using a file open dialog. A namespace extension can be created to modify the file open dialog to provide search capability. Examples of file open dialogs may be found in MICROSOFT WINDOWS or OFFICE applications.
The namespace extensions are used in conjunction with a Shell and a Shell namespace to create a custom view of the file open dialog. The namespace extensions are created to extend the Shell to allow for searching of file hierarchies on a hard drive. Namespace extensions can be created for both physical data and virtual data. Thus, the namespace extensions located on the Shell can provide a single hierarchical representation of both physical data and virtual data.
The namespace extension once created also allows custom Shell views of the data or files in the hierarchies exposed by the Shell. As such, the creation of the namespace extensions provides search capabilities into the Shell.
A “show” toolbar 260 is shown that contains buttons such as Everything, Documents, Email, Music, Pictures and Videos. These buttons allow the user to select which type of files to view from the file list 240. These buttons are shown as typical examples and are not intended to be limiting. It should be appreciated by one of ordinary skill in the art that any combination of buttons contemplated for viewable files may be used. As shown in
Turning now to
The search field 325 allows the user to input a search term or keyword to be searched. The search toolbar 330 provides various buttons such as Web, News, Images, Desktop, Files, Outlook, and Outlook Express. These buttons are shown as a typical example and are not intended to be limiting. It should be appreciated by one of ordinary skill in the art that any combination of buttons contemplated for searchable areas on hard drives may be used. These buttons allow the user to select the specific types of locations to search. For example, if a user chooses a “Desktop” button 345, only the desktop will be searched. Once a location is selected and a search term has been entered a file list 350 appears in the results field 335.
The “show” toolbar 340 is shown that contains buttons such as Everything, Documents, Email, Music, and Pictures and Videos. These buttons are shown as a typical example and are not intended to be limiting. It should be appreciated by one of ordinary skill in the art that any combination of buttons contemplated for viewable files may be used. These buttons allow the user to select which type of files to view from the search. As shown in
Thus, while ASK JEEVES provides a search function for searching a users hard drive, it accomplishes the search using multiple windows pasted on the common file open dialog. It further uses the full path name of the file along with common file open dialog to obtain the file. The multiple windows create a visually confusing search while the need for the common file open dialog causes a limited and slow searching function.
Returning now to the present invention a discussion of the namespace extension along with the custom file open dialog will be discussed. Creation of the namespace extension is accomplished using an existing Shell. The Shell generally organizes objects into a hierarchical namespace, and provides users and applications with a consistent and efficient way to access and manage objects. Specifically the Shell manages and provides access to the objects that make up a file system. Some examples of these objects are folders and files that reside on a computer hard drive. However, the Shell also manages a number of non-file systems, or virtual objects, as well. Users and applications are able to interact with this virtual folder in much the same way as with any other namespace object.
The shell interacts with a Shell namespace to organize the file system and the virtual objects managed by the Shell into a single tree-structured hierarchy. The Shell namespace presents the namespace extension as a virtual folder. When a user browses into this folder, the storable medium is presented as a tree-structured hierarchy of folders and files, much like the rest of the Shell namespace.
Turning now to
The namespace extension is created by first building a Component Object Model (COM) Dynamic-Link Library (dll). A COM is used to add functionality to the namespace extension. The COM.dll allows executable routines to be stored separately as a file with a dll extension that is loaded only when necessary. Every folder that the browser displays is represented by a COM object called a folder object. Each time the user interacts with the folder or its contents, the Shell communicates with the associated folder object through one of a number of standard interfaces. The folder object then responds to the user's action, and the Shell updates the Shell browser's display.
Next, as shown at 504 a custom view is built. An example of a custom view of a file open dialog 300 is shown in
Next, a second interface is implemented to present the custom view in the file open dialog. As shown in
Next, a third interface is implemented to allow the file open dialog to communicate with the custom view. The third interface allows the Shell view to handle a standard shell extension in a common dialog to communicate with the custom view file open dialog. An example of this type of interface is Microsoft's IcommDlgBrowser. Next, a fourth interface is implemented to extend the capabilities of the third interface. The fourth interface is used by the file open dialog when it hosts a Shell browser. An example of this type of interface is Microsoft's IcoImDlgBrowser2.
Next, as shown in 506 a user's search input is received and at 508 the file open dialog searches for the file. Referring again to
From the foregoing it will be appreciated that, although specific embodiments of the invention have been described herein for purposes of illustration, various modifications may be made without deviating from the spirit and scope of the invention. Accordingly, the invention is not limited except as by the appended claims.
Number | Name | Date | Kind |
---|---|---|---|
5600778 | Swanson et al. | Feb 1997 | A |
5675520 | Pitt et al. | Oct 1997 | A |
6212512 | Barney et al. | Apr 2001 | B1 |
6360280 | Jones | Mar 2002 | B1 |
7277912 | Corboy et al. | Oct 2007 | B2 |
7386535 | Kalucha et al. | Jun 2008 | B1 |
20020007407 | Klein | Jan 2002 | A1 |
20030163455 | Dettinger et al. | Aug 2003 | A1 |
20030182304 | Summerlin et al. | Sep 2003 | A1 |
20040001106 | Deutscher | Jan 2004 | A1 |
20050027757 | Kiessig et al. | Feb 2005 | A1 |
Number | Date | Country | |
---|---|---|---|
20070043700 A1 | Feb 2007 | US |