Patent Publication Number: US-8117225-B1

Title: Drill-down system, method, and computer program product for focusing a search

Description:
RELATED APPLICATIONS 
     The present application claims priority from U.S. Provisional Application No. 61/022,269, filed Jan. 18, 2008, which is incorporated herein by reference in its entirety for all purposes. 
    
    
     BACKGROUND AND FIELD OF THE INVENTION 
     The present invention relates to software applications, and more particularly to online applications. 
     SUMMARY 
     A system, method, and computer program product are provided for focusing a search. In operation, a first search is performed. Additionally, first search results of the first search are displayed. Further, at least one term of the first search results is identified. Still yet, a second search is performed, based on the at least one term of the first search results. In addition, second search results of the second search are displayed. 
    
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
         FIG. 1  shows a system for accessing one or more online applications, in accordance with one embodiment. 
         FIG. 2  shows a representative environment that may be associated with the servers and/or clients of  FIG. 1 , in accordance with one embodiment. 
         FIG. 3  shows a method for linking a plurality of tags with a document, in accordance with one embodiment. 
         FIG. 4  shows a method for linking a plurality of tags with a document, in accordance with another embodiment. 
         FIG. 5  shows a method for suggesting tags or automatically selecting tags, in accordance with another embodiment. 
         FIG. 6  shows an interface for linking a plurality of tags with a document, in accordance with one embodiment. 
         FIG. 7  shows a method for applying a function of an online application to a file generated by a second online application, in accordance with one embodiment. 
         FIG. 8  shows a system for applying a function of an online application to a file generated by a second online application, in accordance with one embodiment. 
         FIG. 9  shows a method for applying a function of an online application to a file generated by a second online application, in accordance with one embodiment. 
         FIG. 10  shows a network browser for applying a function of an online application to a file generated by a second online application, in accordance with one embodiment. 
         FIG. 11  shows a method for accommodating different online applications, in accordance with one embodiment. 
         FIG. 12  shows a method for accommodating different online applications, in accordance with one embodiment. 
         FIG. 13  shows a network browser plugin for accommodating different online applications, in accordance with one embodiment. 
         FIG. 14  shows a network browser for accommodating different online applications, in accordance with one embodiment. 
         FIG. 15  shows a method for storing attachments of an electronic message in a central location associated with an online application from which the attachment was generated, in accordance with one embodiment. 
         FIG. 16  shows a method for storing attachments of an electronic message in a central location associated with an online application from which the attachment was generated, in accordance with one embodiment. 
         FIG. 17  shows a system for storing attachments of an electronic message in a central location associated with an online application from which the attachment was generated, in accordance with one embodiment. 
         FIG. 18  shows an interface for an electronic message application for identifying a file associated with an electronic message, in accordance with one embodiment. 
         FIG. 19  shows a method for displaying a single interface that includes a plurality of files, in accordance with one embodiment. 
         FIG. 20  shows a method for displaying a single interface that includes a plurality of files, in accordance with another embodiment. 
         FIG. 21  shows a data structure of global login information for a single interface that includes a plurality of files associated with a plurality of different online applications, in accordance with one embodiment. 
         FIG. 22  shows a file structure shown in a single interface that includes a plurality of files associated with a plurality of different online applications, in accordance with one embodiment. 
         FIG. 23  shows a network browser for displaying a single interface that includes a plurality of files, in accordance with one embodiment. 
         FIG. 24  shows a method for utilizing a network browser as a desktop, in accordance with one embodiment. 
         FIG. 25  shows a method for utilizing a network browser as a desktop, in accordance with another embodiment. 
         FIG. 26  shows a network browser for using as a desktop, in accordance with another embodiment. 
         FIG. 27  shows a network browser for using as a desktop, in accordance with another embodiment. 
         FIG. 28  shows a method of advertising in conjunction with online applications, in accordance with one embodiment. 
         FIG. 29  shows a method of advertising in conjunction with online applications, in accordance with one embodiment. 
         FIG. 30  shows a network browser for viewing advertisements in conjunction with files associated with online applications, in accordance with one embodiment. 
         FIG. 31  shows a method for performing a search in conjunction with use of an online application, in accordance with one embodiment. 
         FIG. 32  shows an interface for performing a search in conjunction with use of an online application, in accordance with one embodiment. 
         FIG. 33  shows a method for focusing a search, in accordance with one embodiment. 
         FIG. 34  shows an interface for focusing a search, in accordance with one embodiment. 
         FIG. 35  shows a method for executing an online application on a mobile device, in accordance with one embodiment. 
         FIG. 36  shows an interface for executing an online application on a mobile device, in accordance with one embodiment. 
         FIG. 37  shows a method for intelligent cutting and pasting, in accordance with one embodiment. 
         FIG. 38  shows an interface for intelligent cutting and pasting, in accordance with one embodiment. 
     
    
    
     DETAILED DESCRIPTION 
       FIG. 1  shows a system  100  for accessing one or more online applications, in accordance with one embodiment. As shown, a plurality of networks  102  is provided. In the context of the present network architecture  100 , the networks  102  may each take any form including, but not limited to a local area network (LAN), a wireless network, a wide area network (WAN) such as the Internet, peer-to-peer network, etc. 
     Coupled to the networks  102  are servers  104 , including one or more online software applications, which are capable of communicating over the networks  102 . Also coupled to the networks  102  and the servers  104  is a plurality of clients  106 . Such servers  104  and/or clients  106  may each include a desktop computer, lap-top computer, hand-held computer, mobile phone, personal digital assistant (PDA), peripheral (e.g. printer, etc.), any component of a computer, and/or any other type of logic. In order to facilitate communication among the networks  102 , at least one gateway is optionally coupled therebetween. 
       FIG. 2  shows a representative environment  200  that may be associated with the servers  104  and/or clients  106  of  FIG. 1 , in accordance with one embodiment. As shown, the environment  200  may include software application logic  202 , advertisement logic  204 , and third party developer logic  206 . Furthermore, storage  208  may also be provided such that documents may be stored. In some cases, these documents may include documents associated with online applications. Additionally, other storage may be provided for various other data such as user specific information  210 . 
     Various embodiments set forth herein may be implemented utilizing hardware, software, or any desired combination thereof. For that matter, any type of logic may be utilized which is capable of implementing the various functionality set forth herein. 
       FIG. 3  shows a method  300  for linking a plurality of tags with a document, in accordance with one embodiment. As an option, the present method  300  may be implemented in the context of the functionality and architecture of  FIGS. 1-2 . Of course, however, the method  300  may be carried out in any desired environment. It should also be noted that the aforementioned definitions may apply during the present description. 
     As shown, a document generated utilizing an online document editor is identified. See operation  302 . In the context of the present description, an online document editor refers to any online editor used to generate or modify documents. For example, in various embodiments, the online document editor may include, but is not limited to, WebOffice Document Manager, Zoho Writer, Google Docs, and/or any other document editor that meets the above definition. 
     Further, the document generated may include any document capable of being generated with an editor. For example, in various embodiments, the document may include a may include, but is not limited to, a text document, any word processor document (e.g. a Microsoft Word document, Microsoft Works document, etc.), a spreadsheet document (e.g. a .xls document, etc.), a presentation document (e.g. a .ppt document, etc.), a portable document format (PDF) file, a picture, a drawing, and/or any other document that meets the above definition. 
     Additionally, a plurality of tags are determined. See operation  304 . In the context of the present description, a tag refers to any keyword, term, or phrase associated with or assigned to a piece of information (e.g. a picture, a geographic map, a blog entry, a video clip, or any document, etc.). 
     Furthermore, the tags are linked with the document. See operation  306 . As an option, the tag may be utilized to describe the document and enable keyword-based classification and searches of information associated with such document. 
     More illustrative information will now be set forth regarding various optional architectures and features with which the foregoing framework may or may not be implemented, per the desires of the user. It should be strongly noted that the following information is set forth for illustrative purposes and should not be construed as limiting in any manner. Any of the following features may be optionally incorporated with or without the exclusion of other features described. 
       FIG. 4  shows a method  400  for linking a plurality of tags with a document, in accordance with another embodiment. As an option, the present method  400  may be implemented in the context of the functionality and architecture of  FIGS. 1-3 . Of course, however, the method  400  may be carried out in any desired environment. It should also be noted that the aforementioned definitions may apply during the present description. 
     As shown, it is determined whether online documents have been created. See operation  402 . If one or more documents have been created, an interface is displayed for manually collecting tags. See operation  404 . As an option, the interface may be displayed upon saving the document. As another option, the interface may be displayed by selecting a tag creation icon or option in a menu or a toolbar. 
     Furthermore, the interface may include various functionality for manually collecting the tags. For example, the interface may include text edit boxes for manually inserting tags. The interface may also include a drop-down menu or other list of potential tags. 
     Additionally, the interface may provide suggested tags. For example, the list or drop-down menu may include a list of suggested tags. As another option, upon invocation of the interface, suggested tags may be highlighted in the created document. In this case, the interface may include text from the selected document illustrating the highlighted words or phrases to potentially be used as tags. Further, the document itself may include the highlighted words or phrases. In this case, a user may have the option to select the highlighted words or phrases (e.g. by clicking or scrolling over) utilizing a mouse. 
     In one embodiment, the tags may be manually selected from the document without by selecting any of the text in the document, not necessarily recommended tags. Further, the interface may provide a list of words in the created document with an associated number indicating the frequency of use in the document. These words may be ordered in a list from most to least use, for example. Additionally, the list may only include a certain number of the most used words in the document. 
     As another option, the tags may be recommended based on previously existing tags. For example, if a plurality of existing tags include a specific word or term, but other tags associated with those particular tags are dissimilar, a tag may be recommended that exploits this dissimilarity. As a specific example, if two existing documents have a tag that includes “apple” and another tag that includes “computer,” but the newly created document has multiple occurrences of the term “apple” and few occurrences of the term “computer” in the document, another keyword may be recommended based on the number of times found in the document (e.g. “fruit”) to distinguish the documents. 
     Once the tags have been collected, the tags are correlated with a document/index. See operation  406 . In this way, the tags may be indexed. For example, the tags may then be associated or linked with/to the document and an index location such that the tag may be utilized to access the indexed location of the document. In this case, an index may refer to any location of a data structure. Furthermore, the index may refer to any location in a database. In this way, the tags may be utilized for searching the documents. 
     Once the tags are correlated with a document/index, it is determined whether the document is to be edited. See operation  408 . For example, the document may be selected to be edited by the user. If the document is to be edited, the interface is displayed for manually collecting tags. See operation  410 . As an option, the interface may be displayed when the edited document is to be saved (e.g. when the user selects a save document option or icon, etc.). 
     Once the tags have been collected, the tags are correlated with the document/index. See operation  412 . It should be noted, that suggested tags may again be optionally displayed using the interface. Furthermore, the user may have the option to utilize previously generated tags instead of generating new or additional tags. 
     In addition to manual selection, in another embodiment, the tags may also be automatically selected.  FIG. 5  shows a method  500  for suggesting tags or automatically selecting tags, in accordance with another embodiment. As an option, the present method  500  may be implemented in the context of the functionality and architecture of  FIGS. 1-4 . Of course, however, the method  500  may be carried out in any desired environment. It should also be noted that the aforementioned definitions may apply during the present description. 
     As shown, words in a document are parsed. See operation  502 . In the context of the present description, parsing refers to transforming text into a word or data structure. For example, in various embodiments, parsing may include, but is not limited to, extracting words from text, extracting phrases from text, extracting symbols from text, lexical functional grammar parsing, head-driven phrase structure grammar parsing, shallow parsing, dependency grammar parsing, etc. 
     Once the words in the document have been parsed, repeated words are identified. See operation  504 . In one embodiment, identifying the repeated words may include implementing a statistical analysis on the repeated words to determine a frequency of use and/or a relevance analysis (i.e. the likelihood the word is relevant in the context used). As an option, the identification of repeated words may include only identifying nouns and/or verbs that are repeated. 
     Furthermore, unique nouns and or verbs may also be identified. See operation  506 . In this case, the unique nouns or verbs may be identified from the list of repeated words and/or non-repeated words in the document. In one embodiment, the unique nouns or verbs may refer to any noun or verb that is not statistically likely to appear in a document (e.g. less than 60% likely, 50% likely, 40% likely, etc.). Additionally, the unique nouns or verbs may be determined based on the frequency of use in the document. 
     As shown further, tags may be suggested based on the identification. See operation  508 . In this way, nouns, verbs, and/or repeated words may be determined to be tags. 
     In various embodiments, the tags may be suggested as a list, dialog box, input text box, highlighted text, etc. Furthermore, the tags may be automatically selected and applied. For example, an interface may provide a user an option to have tags automatically selected. In this case, tags that would otherwise be suggested may be utilized as tags automatically. Thus, the tags may be determined automatically by parsing words in the document. 
       FIG. 6  shows an interface  600  for linking a plurality of tags with a document, in accordance with one embodiment. As an option, the interface  600  may be implemented in the context of the details of  FIGS. 1-5 . Of course, however, the interface  600  may be implemented in any desired environment. It should also be noted that the aforementioned definitions may apply during the present description. 
     As shown, the interface  600  may include a navigator bar  602  (e.g. an explorer bar) including back, forward, stop, reload, etc. functionally for navigating online. Further, a toolbar  604  may be provided including various functionality for accessing/managing documents. For example, the toolbar  604  may include a file option to access functionality associated with a document (e.g. save, save as, send, properties, etc.). Furthermore, the toolbar  604  may include options for switching between online applications (e.g. word processors, spread sheet generation tools, PDF generators, etc.). Still yet, the toolbar may include various other functions such as view options, format options, tool options, table options, window options, help options, and various icons associated with various functionality. 
     Additionally, the interface  600  includes a window for viewing documents. In operation, a user may generate a document or a plurality of documents using the interface  600 . Tags may then be determined manually or automatically, correlating to the document. 
     As an option, the tags may be manually entered upon saving the document. For example, upon save the document a user interface  606  may be displayed, allowing a user to manually enter a tag or a plurality or tags into a text box  608 . In one embodiment, the interface  606  may include a folder directory  610 . Furthermore, the interface  606  may include a list of suggested tags  612 . Once the tags have been selected (manually and/or automatically), the tags are indexed. 
     Thus, the tags may be utilized for searching the documents. As an option, the interface  600  may allow the user to search a plurality of documents using the tags. In this way, the user may examine tags relating to information being sought, and the tag may be used to find appropriate documents. 
     It should be noted that the interface  600  may represent any network browser. Thus, by using the interface  600  multiple online applications may be accessed utilizing the tags. Furthermore, in various embodiments, the documents may be created using many different online applications. As an option, these online applications may employ functionality of various other online applications. 
       FIG. 7  shows a method  700  for applying a function of an online application to a file generated by a second online application, in accordance with one embodiment. As an option, the present method  700  may be implemented in the context of the functionality and architecture of  FIGS. 1-6 . Of course, however, the method  700  may be carried out in any desired environment. It should also be noted that the aforementioned definitions may apply during the present description. 
     As shown, a file generated utilizing a first online application is identified. See operation  702 . In the context of the present description, an online application refers to any software application that is utilized over a network. For example, in various embodiments, the online applications may include, but are not limited to, online word processors, online spread sheet generators, online presentation tools and generators, online project management software, online accounting software, and/or any other online applications that meet the above definition. 
     Additionally, a function of a second online application to be applied to the file is identified. See operation  704 . In the context of the present description, a function refers to function associated with an application. For example, in various embodiments, the function may include, but is not limited to, a format conversion, a commenting function, a publishing function, a spell check function, a track changes function, a text formatting function, an object modifying function, a drawing function, a table function, a macro function, and/or any other function that meets the above definition. 
     Further, the function of the second online application is applied to the file. See operation  706 . The function may be applied in a variety of ways. For example, the function of the second online application may be applied to the file utilizing code stored at a server hosting the first online application. As another example, the function of the second online application may be applied to the file utilizing code stored at a server hosting the second online application. In this case, the function may be applied by passing a URL associated with the file to second online application. 
     More illustrative information will now be set forth regarding various optional architectures and features with which the foregoing framework may or may not be implemented, per the desires of the user. It should be strongly noted that the following information is set forth for illustrative purposes and should not be construed as limiting in any manner. Any of the following features may be optionally incorporated with or without the exclusion of other features described. 
       FIG. 8  shows a system  800  for applying a function of an online application to a file generated by a second online application, in accordance with one embodiment. As an option, the system  800  may be implemented in the context of the functionality and architecture of  FIGS. 1-7 . Of course, however, the system  800  may be implemented in any desired environment. It should also be noted that the aforementioned definitions may apply during the present description. 
     As shown, a server including a first online application  802 , a server including a second online application  804 , and a client  806  are provided. In operation, a file  808  generated utilizing the first online application  802  is identified. Additionally, a function of the second online application  804  is identified to be applied to the file  808 . Further, the function of the second online application  806  is applied to the file  808 . 
     In one case, the function of the second online application  806  may be unavailable utilizing the first online application. In this way, functionality of multiple applications may be shared between applications. 
     As shown further, the client  806  has access to both the first and second online applications  802  and  804 . For example, the first online application  802  and the second online application  804  may be accessible via a network browser. In this way, the function of the second online application  804  may be selected utilizing the network browser. 
     For example, the function of the second online application  804  may be selected utilizing a toolbar of the network browser. In this case, the toolbar may include a plugin. In the context of the present description, a plugin refers to any computer program that interacts with a host application (e.g. the network browser, etc.). In one embodiment, the plugin may provide a function using an icon and/or dedicated text. 
     Although not illustrated, in one embodiment, the first the second online application  802  and  804  may be included on one server. In another embodiment, the server including the first online application  802  and the server including the second online application  804  may be in communication. In this way, applying the function of the second application  804  to the file  808  may not necessarily involve communicating data via the client  806 , as shown in  FIG. 8 . 
       FIG. 9  shows a method  900  for applying a function of an online application to a file generated by a second online application, in accordance with one embodiment. As an option, the present method  900  may be implemented in the context of the functionality and architecture of  FIGS. 1-8 . Of course, however, the method  900  may be carried out in any desired environment. It should also be noted that the aforementioned definitions may apply during the present description. 
     As shown, a file is identified using a first online application. See operation  902 . As an option, identifying the file may include selecting the file via a user interface. As another option, the file may be selected from a network browser. In this case, the network browser may include a drop-down list of potential files. In one embodiment, the network browser may include a bookmark to the file. 
     Once the file is selected using the first online application, it is determined whether a function from a second online application function is selected to be applied to the file. See operation  904 . As an option, the function may be selected using a toolbar including functionality of both the first and second application. In one case, this toolbar may be displayed upon accessing two or more applications. For example, upon accessing a first online application, a toolbar including functionality of the first application may be displayed. Then, after accessing a second online application, the toolbar may be updated to include functionality of the second online application. 
     In another embodiment, a toolbar may be displayed including functionality of all available online applications. In this case, the available functionality may include only online application functions available to a user or compatible with the opened file and/or application. 
     If it is determined that a function from the second online application is selected to be applied to the file, the function is applied to the file. See operation  906 . The function may be applied to the file in many ways. For example, in one embodiment, code including the function may be transferred to the server including the first application such that the first application may apply the function to the file. 
     In another embodiment, the file may be transferred to the server including the second online application and the function may be applied to the file. In still another embodiment, the server including the file and the first online application may include a list of various functions and associated code, capable of being applied to the file. In this case, such functionality may or may not be included as part of the first application. As an option, all capable functionality of the first online application and/or the second online application may be available via a network browser. 
       FIG. 10  shows a network browser  1000  for applying a function of an online application to a file generated by a second online application, in accordance with one embodiment. As an option, the network browser  1000  may be implemented in the context of the details of  FIGS. 1-9 . Of course, however, the network browser  1000  may be implemented in any desired environment. It should also be noted that the aforementioned definitions may apply during the present description. 
     As shown, the network browser  1000  may include a navigator bar  1002  (e.g. an explorer bar) including back, forward, stop, reload, etc. functionally for navigating a network. Further, a toolbar  1004  may be provided including various functionality for accessing/managing files and/or applications. For example, the toolbar  1004  may include functions of a plurality of applications. 
     In one embodiment, the toolbar  1004  may only include functions of open applications. In another embodiment, the toolbar  1004  may only include functions that may be applied to an open file or application in use. In still another embodiment, the toolbar may include all functions available to a user. As an option, the functions available to a user may include only functions associated with applications to which the user has usage rights. 
     In addition to various application functions, in other embodiments, the toolbar  1004  may include a file option to access functionality associated with a file (e.g. save, save as, send, properties, etc.). Furthermore, the toolbar  1004  may include options for switching between online applications (e.g. word processors, spread sheet generation tools, PDF generators, etc.). Still yet, the toolbar may include various other functions such as view options, format options, tool options, table options, window options, help options, and various icons associated with various functionality. 
     Additionally, the network browser  1000  or the toolbar  1004  may include a tab bar  1006  for easy toggling between applications and files. As an option, the tab bar  1006  may allow the same file to be viewed in the context of a first online application and a second online application. In this way, a file opened by the first online application under a first tab may be viewed in the context of a second online application under a second tab, allowing a function of the second online application to be applied to the file when viewed tinder the second tab and/or the first tab. 
     Furthermore, results of applying the function may be displayed in a separate window. For example, after applying the function to the file, the results may be displayed under a tab separate from the first and/or second online application, or a separate window  1007  of the network browser  1000  or a separate network browser (not shown). 
     It should be noted that, the toolbar  1004  may display functions of an individual online application, or a plurality of different applications. In some cases, the different online applications may be applications located on separate servers. 
       FIG. 11  shows a method  1100  for accommodating different online applications, in accordance with one embodiment. As an option, the present method  1100  may be implemented in the context of the functionality and architecture of  FIGS. 1-10 . Of course, however, the method  1100  may be carried out in any desired environment. It should also be noted that the aforementioned definitions may apply during the present description. 
     As shown, an online application currently visited by a network browser is identified. See operation  1102 . Additionally, at least one of a plurality of network browser toolbars is automatically selected based on the online application currently visited by the network browser. See operation  1104 . Furthermore, the at least one network browser toolbar is displayed. See operation  1106 . 
     In the context of the present description, a network browser toolbar refers to any row, column, or block of buttons, icons, or linked words that, when clicked, activate certain functions of an application. For example, in various embodiments, the toolbar may include save functions, spell check functions, text formatting functions, file formatting functions, search functions, drawing functions, and/or any other functions associated with an application. 
     More illustrative information will now be set forth regarding various optional architectures and features with which the foregoing framework may or may not be implemented, per the desires of the user. It should be strongly noted that the following information is set forth for illustrative purposes and should not be construed as limiting in any manner. Any of the following features may be optionally incorporated with or without the exclusion of other features described. 
       FIG. 12  shows a method  1200  for accommodating different online applications, in accordance with one embodiment. As an option, the present method  1200  may be implemented in the context of the functionality and architecture of  FIGS. 1-11 . Of course, however, the method  1200  may be carried out in any desired environment. It should also be noted that the aforementioned definitions may apply during the present description. 
     As shown, a URL is identified for a first online application. See operation  1202 . In this case, the URL may be identified upon accessing the first application and/or by opening a file associated with the first application. For example, a user may access the first online application using a network browser. In this way, the online application may be identified by monitoring URLs entered into the network browser. 
     Further, a list of toolbars is examined to find a toolbar associated with the URL or the first application are examined. See operation  1204 . For example, a list including a plurality of toolbars associated with various online applications may be stored in a database. Using the identified URL and/or other information about the first online application, the list of toolbars may be examined to determine whether an appropriate toolbar is present for the first online application. 
     Once the URL has been identified, it is determined whether there is an appropriate toolbar present. See operation  1206 . In one embodiment, the URLs entered in the network browser may be compared against a list of predetermined URLs associated with online applications for which an associated toolbar is stored on a client on which the network browser is installed. 
     If there is appropriate toolbar present, a toolbar is automatically executed and displayed for the first online application. See operation  1208 . Thus, upon a match being identified based on the comparison of the URLs, a corresponding one of the toolbars is executed without user intervention. 
     It is then determined whether a window associated with the first online application is closed or a different tab on the network browser is selected. See operation  1212 . If the window is closed or another network browser tab is selected, the toolbar corresponding to the first application is closed or hidden. See operation  1212 . Thus, the network browser toolbar may be removed from an interface of the network browser upon identification of a window in which an associated online application being closed. 
     In one embodiment, multiple tabs on a network browser may be open simultaneously, where more than one tab corresponds to the first application. In this case, the toolbar may remain displayed for all tabs or windows associated with the first application. Furthermore, in the case that a second application is being utilized in one of the tabs or windows, and the second tab utilizes the same or similar toolbar functionality as the first application, the toolbar may also remain displayed for the second application. 
       FIG. 13  shows a network browser plugin  1300  for accommodating different online applications, in accordance with one embodiment. As an option, the network browser plugin  1300  may be implemented in the context of the details of  FIGS. 1-12 . Of course, however, the network browser plugin  1300  may be implemented in any desired environment. It should also be noted that the aforementioned definitions may apply during the present description. 
     As shown, the network browser plugin  1300  may include various information for accessing a first application. For example, the network browser plugin  1300  may include a user name, user login information, an online application URL, user preferences, etc. In one embodiment, the network browser plugin  1300  may be stored on a client computer from which the URL of online applications are accessed. 
     For example, a user may subscribe or access an online application and be prompted to download the network browser plugin  1300  from the location of the online application to the computer or device of the user. The user may then be prompted to fill out all relevant information. In this way, the network browser plugin  1300  may be utilized to access one or more online applications without the need to enter login information every time the application is accessed. In one embodiment, the network browser plugin  1300  may include information associated with a plurality of online applications. In this case, the URL may be utilized as a look-up for all of the information utilized by the online application to allow the user access. 
       FIG. 14  shows a network browser  1400  for accommodating different online applications, in accordance with one embodiment. As an option, the network browser  1400  may be implemented in the context of the details of  FIGS. 1-13 . Of course, however, the network browser  1400  may be implemented in any desired environment. It should also be noted that the aforementioned definitions may apply during the present description. 
     As shown, the network browser  1400  may include a navigator bar  1402  (e.g. an explorer bar) including back, forward, stop, reload, URL entry, etc. functionally for navigating a network. Further, a toolbar  1404  may be provided including various functionality for accessing/managing files and/or applications. For example, the toolbar  1404  may include functions for a first online application. 
     In addition to various functions of the first application, in other embodiments, the toolbar  1404  may include a file option to access functionality associated with a file (e.g. save, save as, send, properties, etc.). Furthermore, the toolbar  1404  may include options for switching between online applications (e.g. word processors, spread sheet generation tools, PDF generators, etc.). Still yet, the toolbar may include various other functions such as view options, format options, tool options, table options, window options, help options, and various icons associated with various functionality. 
     Additionally, the network browser  1400  or the toolbar  1604  may include a tab bar for easy toggling between applications and files. As an option, the tab bar may allow the same file to be viewed in the context of a first online application and a second online application. In this way, a file opened by the first online application under a first tab may be viewed in the context of a second online application under a second tab, allowing a function of the second online application to be applied to the file when viewed under the second tab and/or the first tab. 
     In operation, an online application currently visited by the network browser  1400  may be identified using the URL. Additionally, at least one of a plurality of network browser toolbars may be selected based on the online application currently visited by the network browser. As an option, the toolbar  1404  may be capable of being manually selected utilizing a menu. In this case, the menu may include a plurality of toolbars associated with various URLs or online applications, where the toolbars may include different functionality. 
     For example, a first one of the toolbars may be adapted for applying a first set of functions to a file generated utilizing a first online application, and a second one of the toolbars is adapted for applying a second set of functions to a file generated utilizing a second online application. Once the toolbar  1404  is selected, the toolbar  1404  may be displayed utilizing the network browser  1400 . 
     As an option, log-in information utilized for the online applications may be stored on a computer on which the network browser  1400  is installed. In this way, the login information may be utilized to log-in to the online application currently visited by the network browser  1400 . Thus, the user may enter the URL of the online application into the network browser  1400  and access the application without entering login information every time. 
     In one embodiment, the user may use bookmarks to access the online applications. In another embodiment, the user may click on a tag to access the online application. In still another embodiment, the user may access the online application by clicking an icon on a desktop. Additionally, the user may access the online application by clicking on an item illustrated in a pictorial diagram of a file structure. 
     It should be noted that the toolbar  1404  may be displayed independently (i.e. only a single network browser toolbar is displayed at a time), or with multiple other toolbars (e.g. other online application toolbars, search engine toolbars, email toolbars, etc.). In one embodiment, the network browser toolbar  1404  may be conditionally displayed based on a number of network browser toolbars already displayed. For example, if two toolbars are already being displayed, the network browser toolbar  1404  may not be displayed. 
     In another embodiment, a position of the network browser toolbar  1404  may depend on a number of network browser toolbars already displayed. As an option, if multiple toolbars are already displayed, the network browser toolbar  1404  may be displayed in a position in the network browser  1400  away from the other toolbars being displayed. For example, if multiple toolbars are being displayed at the top of the network browser  1400  the network browser toolbar  1404  may be displayed at the bottom of the network browser  1400 . 
     In still another embodiment, a size of the network browser toolbar  1404  may depend on a number of network browser toolbars already displayed. For example, if a plurality of toolbars are already displayed, the network browser toolbar  1404  may be reduced in size (e.g. font, area, etc.). As another option, icons or buttons normally displayed on the network browser toolbar  1404  may be omitted in the case that limited space is available due to other toolbars being present. 
     In yet another embodiment, an orientation of the network browser toolbar  1404  may depend on a number of network browser toolbars already displayed. For example, if one or more toolbars are being displayed in a horizontal orientation or row across the top-side of the network browser  1400 , the network browser toolbar  1404  may be displayed in a vertical orientation, as a column along a side of the network browser  1400 . As an option, the network browser toolbar may be oriented vertically if one or more browser toolbars are already displayed. 
     In some cases, the toolbar  1404  or another toolbar displayed on the network browser  1400  may include functions for attaching files associated with the online applications to emails or other messages. In one embodiment, these attachments may be stored in a central location associated with an online application from which the attachment was generated. 
       FIG. 15  shows a method  1500  for storing attachments of an electronic message in a central location associated with an online application from which the attachment was generated, in accordance with one embodiment. As an option, the present method  1500  may be implemented in the context of the functionality and architecture of  FIGS. 1-14 . Of course, however, the method  1500  may be carried out in any desired environment. It should also be noted that the aforementioned definitions may apply during the present description. 
     As shown, a file associated with an electronic message is identified, utilizing an electronic message application. See operation  1502 . In the context of the present description, an electronic message application refers to any application capable of identifying an electronic message. For example, in various embodiments, the electronic message application may include, but is not limited to, an email application (e.g. Microsoft Outlook, a web-based email application, etc.), a text messenger application, an instant messenger application, and/or any other electronic messenger application that meets the above definition. In various embodiments, the electronic message may include an email, a text message, an instant message, and any other electronic message. 
     Additionally as shown, an online application associated with the file is determined. See operation  1504 . In this case, the online application may be an online application that generated the file, an online application that is capable of opening or viewing the file, an online application that is capable of modifying the file, etc. 
     Further, the file is stored in one of a plurality of network locations, based on the determined online application. See operation  1506 . The network location may be any location capable of storing files. For example, in various embodiments, the network locations may include a server or a networked database. In this case, the network locations may be locations allocated to an individual user, a group of users, a company, etc. 
     More illustrative information will now be set forth regarding various optional architectures and features with which the foregoing framework may or may not be implemented, per the desires of the user. It should be strongly noted that the following information is set forth for illustrative purposes and should not be construed as limiting in any manner. Any of the following features may be optionally incorporated with or without the exclusion of other features described. 
       FIG. 16  shows a method  1600  for storing attachments of an electronic message in a central location associated with an online application from which the attachment was generated, in accordance with one embodiment. As an option, the present method  1600  may be implemented in the context of the functionality and architecture of  FIGS. 1-15 . Of course, however, the method  1600  may be carried out in any desired environment. It should also be noted that the aforementioned definitions may apply during the present description. 
     As shown, an email from a first user, including an attachment, is received by a second user. See operation  1602 . In this case, the attachment may include any file generated by any application. In one embodiment, the attachment may be virtual attachment. For example, the attachment may include a link corresponding to a file stored on a server. 
     Once the email is received, it is determined whether the attachment is to be opened, saved, and/or edited. See operation  1604 . For example, the second user may select the attachment (e.g. using a mouse, etc.) and be given the option to open, save, edit, forward, etc. the attachment. This option may be presented in the form of a window, a drop-down menu, etc. 
     If it is determined that the attachment has been selected to be opened, saved, and/or edited, an online application associated with the attachment and corresponding user login information for the second user is identified. See operation  1606 . The online application associated with the attachment may be determine in a variety of ways. 
     In one embodiment, the online application may be determined to be associated with the file, based on a header of the file. For example, a header of the file may indicate an application capable of opening, editing, or saving the file. As another option, the online application may be determined to be associated with the file, based on an extension of the file. For example, if the extension includes a “.txt” extension, it may be determined that an online text editor is associated with the file. In another case, a “.pdf” extension may indicate that a PDF viewer or editor is associated with the file. 
     In this way, the online application associated with the file may be determined automatically. In another embodiment, the online application associated with the file may be determined manually. For example, a user may have the option to select from a list of online applications. 
     In this case, the list may include all online applications capable of opening, editing, or saving the file. As an option, the list may include online applications for which the user has permission to use. As another option, the user may be given the option to have an appropriate application selected automatically. 
     In one embodiment, a network browser may be utilized to select the appropriate application. In this case, the network browser may be displayed upon selecting to open, save, or modify the file. As an option, the network browser may display a plurality of tabs corresponding to each online application capable of opening, editing, or saving the file. 
     In addition to determining an online application associated with the attachment, corresponding user login information is also determined. In one embodiment, the login information may be stored on a device on which the electronic message application is installed. In this case, the device may be any device capable of storing login information. For example, in various embodiments, the device may include a mobile device (e.g. a phone, PDA, laptop, etc.), a computer, or any other device that meets the above definition. 
     As an option, the login information may be included as a network browser plugin. In this case, the login information may be automatically accessed by the online application. In one embodiment, the log-in information may be utilized to login to the online application, in response to determining the online application is associated with the file. Thus, upon automatically or manually selecting the online application, the login information may be automatically obtained and utilized to access the application. 
     Once the online application has been determined and the login information of the second user identified, the file is open, saved, or edited (depending on the command), using space in the online application allocated to the second user. See operation  1608 . For example, the file may be automatically transferred from a space at a network location associated with the first user to a space at a network location associated with the second user, such that the second user may access the file using the online application in a private or secure place, not accessible to the first user. 
     As another option, data included in the attachment may be used to reconstruct the file in a space on the network allocated to the second user. In this way, once the online application is determined, a program or function associated with the online application may use data in the attachment to regenerate the file. This data may be communicated either via a device of the second user or directly from the space allocated to the first user. 
     As still another option, the attachment may be saved directly from the device of the second user to the network space allocated to the second user. In these ways, the file (attachment) may be modified/accessed by the second user on a network location using an online application. In another embodiment, the file may be stored in a common network space such that both the first and the second user may access the file. In this way, a working document may be maintained between a plurality of users. 
     As an option, the network location may be associated with a URL corresponding to the online application. For example, a server may host an online application in addition to providing space for file storage or a workspace. As another option, the network location of the user space for file storage may be separate from a network location of the online application. 
       FIG. 17  shows a system  1700  for storing attachments of an electronic message in a central location associated with an online application from which the attachment was generated, in accordance with one embodiment. As an option, the system  1700  may be implemented in the context of the details of  FIGS. 1-16 . Of course, however, the system  1700  may be implemented in any desired environment. It should also be noted that the aforementioned definitions may apply during the present description. 
     As shown, a plurality of online application are located one or more network locations  1702 . As shown further, a device  1704  of a first user has access to at least one of the network locations  1702 . Additionally, a device  1706  of a second user has access to at least one of the network locations  1702 . 
     In use, the first user and/or the second user may each have access to allocated network space on a database or server at the network location  1702 . The users may access online applications associated with the network locations, given the users have proper permission which may be obtained using appropriate login information. The users may access these online applications to create, modify, manage, and store files located at the network locations. 
     In one embodiment, the first and the second user may each have access to a separate network space such that files of the two users are isolated from other users. In another embodiment, a shared or common space may also be utilized. In still another embodiment, the file may be stored in a location only accessible to a recipient of the electronic message. 
     In one case, the first user may desire to send a file to the second user. As an option, the first user may configure an email and send the file as an attachment. As another option, the first user may send a link to the file in an email. 
     When the second user receives the email with the attachment, the second user may choose to open or save the attached file. When the user selects one of these options, an online application for facilitating such operations is determined. Additionally, the file is stored in one of the network locations  1702 , based on the determined online application. For example, as shown the file generated by the first user using the first online application may be associated with the first online application by the device  1706  of the second user. Thus, the file may be saved in a network location associated with the first online application. 
     In one embodiment, the device  1706  of the second user may be used to determine the appropriate online application and the store the file. In this case, the device  1706  maybe any device capable of performing these functions (e.g. a stationary device, a mobile device, etc.). As an option, the file may be saved by selecting the electronic message and further selecting a save menu option. 
     In one embodiment, a request may be received to open the attached file. In this case, the online application associated with the file may be determined in response to the request. Once the online application is determined and user login information is verified, the file may be opened using the online application. In one embodiment, this may include opening the file utilizing a network browser window. 
       FIG. 18  shows an interface  1800  for an electronic message application for identifying a file associated with an electronic message, in accordance with one embodiment. As an option, the interface  1800  may be implemented in the context of the details of  FIGS. 1-17 . Of course, however, the interface  1800  may be implemented in any desired environment. It should also be noted that the aforementioned definitions may apply during the present description. 
     As shown, a menu  1802  may allow a user to select a plurality of options when a message has been received with an attachment including a file. In this case, the file may or may not have being generated using an online application. For example, the menu may include options to store the file to a network space allocated to the user, edit, remove, or copy the file. In one embodiment, the user may have the option to share the file. 
     Once the user makes a selection, the file may be stored on a network space which includes a plurality of other files. As an option, the user may have the ability to view all of these files using a single interface. This may allow the user to view a file structure or tags associated with all of the user&#39;s files stored on the network location. 
       FIG. 19  shows a method  1900  for displaying a single interface that includes a plurality of files, in accordance with one embodiment. As an option, the present method  1900  may be implemented in the context of the functionality and architecture of  FIGS. 1-18 . Of course, however, the method  1900  may be carried out in any desired environment. It should also be noted that the aforementioned definitions may apply during the present description. 
     As shown, a plurality of files are identified, each associated with diverse file types corresponding to different online applications. See operation  1902 . In various embodiments, the file types may include, but are not limited to, a word processor file type, a text editor file type, a PDF file type, a drawing file type, a spreadsheet file type, a presentation file type, and/or any other file type corresponding to an-online application. 
     Further, a single interface is displayed that includes the files. See operation  1904 . As an option, the interface may be displayed using a network browser. As another option, the interface may be displayed on the device of a user. In this case, the device may include a mobile device (e.g. a phone, PDA, laptop, etc.), a computer, or any other device capable of displaying a network browser. 
     More illustrative information will now be set forth regarding various optional architectures and features with which the foregoing framework may or may not be implemented, per the desires of the user. It should be strongly noted that the following information is set forth for illustrative purposes and should not be construed as limiting in any manner. Any of the following features may be optionally incorporated with or without the exclusion of other features described. 
       FIG. 20  shows a method  2000  for displaying a single interface that includes a plurality of files, in accordance with another embodiment. As an option, the present method  2000  may be implemented in the context of the functionality and architecture of  FIGS. 1-19 . Of course, however, the method  2000  may be carried out in any desired environment. It should also be noted that the aforementioned definitions may apply during the present description. 
     As shown, a global login is received. See operation  2002 . Once the global login is received, a file directory of stored files is displayed. See operation  2004 . This file directory may be displayed in a variety of ways using a single interface. 
     For example, the interface may be displayed utilizing a network browser and or a network browser plug-in. In this case, identifiers associated with the files may be stored on a device on which the network browser is installed. In one embodiment, the file identifies may include tags, as described above. 
     In another embodiment, the identifiers associated with the files may be stored on a server. In this case, the server may be a server associated with the single interface. This server may also be associated with one or more online applications. The identifiers associated may be displayed in various ways. For example, the identifiers associated with the files may be displayed utilizing HTML. In another embodiment, the identifiers associated with the files may be displayed utilizing a JAVA script, icons, etc. 
     As an option, a network browser plugin may include the global login information. In this way, the global login information may be automatically obtained when accessing the single interface through a network browser associated with the network plugin. In this case, the network browser, plugin, and login information may be stored on a device of a user. 
     As an option, the log-in information may be capable of being entered when registering an associated one of the online applications in association with the network browser. For example, a user may access an online application for a first time using a network browser and enter registration information. As part of the registration process the user may enter login information which may saved on a device of the user. Thus, this information may be utilized each time the user accesses the interface online. As an option, the user may choose to enter login information each time the user accesses the single interface online (e.g. for security purposes, etc.) 
     Using the single interface, a user may view a plurality of files generated using various applications, with some of the applications being online applications. In some cases, each of the online applications may have different log-in information associated therewith. In these cases, the log-in information may be stored in and associated with a network browser or a network browser plugin. Furthermore, the log-in information may be utilized to access the interface, the files, and/or identifiers associated with the files. 
     With further reference to  FIG. 20 , once the files are displayed using the single online interface, it is determined whether a file is selected. See operation  2006 . In this case, a file being selected may include selecting the file directly via a network browser displaying the single interface, of by selecting a tag associated with the file. 
     If a file is selected (e.g. to be accessed, saved, etc.), login information for an online application associated with that file is identified. See operation  2008 . For example, user may select a file to open that is associated with an online word processor application. User login information would then be identified for the online application, either automatically (e.g. using information stored on the user device, etc.) or manually, by prompting the user to enter login information. 
     Once the login information has been determined, the selected file is retrieved using the corresponding login information. See operation  2010 . In this case, the selected file may be retrieved from a network location of the online application associated with the file, a network location associated with the single online interface, a network location associated with a user space (e.g. individual, shared, work, etc.), and or any other network location associated with the file. 
       FIG. 21  shows a data structure  2100  of global login information for a single interface that includes a plurality of files associated with a plurality of different online applications, in accordance with one embodiment. As an option, the data structure  2100  may be implemented in the context of the functionality and architecture of  FIGS. 1-20 . Of course, however, the data structure  2100  may be implemented in any desired environment. It should also be noted that the aforementioned definitions may apply during the present description. 
     As shown, global login information  2102  may include login information for a plurality of different online applications  2104 . In use, a user may access an interface for displaying a plurality of files each associated with diverse file types corresponding to different online applications. Upon accessing the interface, or files displayed using the interface, the user may be prompted for global login information. As another option, global login information may be obtained automatically from information a device of the user or a server associated with the single interface, etc. 
     In one embodiment, the global login information  2100  may include a user name and password for accessing the single interface. Once the global login information is obtained, online application login information may be accessed and obtained automatically to allow the user to access all files displayed in the interface and all corresponding online applications, without entering login information for each online application. 
     Thus, the user may use one global login to the single interface to access a plurality of online applications. It should be noted that the login information for the plurality of online applications may be different for some or all of the applications. However, the global login information may allow access to all online application login information. 
     This may be accomplished in a variety of ways. For example, the login information for the online applications may be stored on the device of the user, a server associated with the single interface, a network location associated with the users, etc. Upon entering the global login information, the login information for the online applications associated with the user may be retrieved. In various embodiments, this may be facilitated utilizing a network browser, a network browser plugin, a JAVA script, etc. 
       FIG. 22  shows a file structure  2200  shown in a single interface that includes a plurality of files associated with a plurality of different online applications, in accordance with one embodiment. As an option, the file structure  2200  may be implemented in the context of the functionality and architecture of  FIGS. 1-21 . Of course, however, the file structure  2200  may be implemented in any desired environment. It should also be noted that the aforementioned definitions may apply during the present description. 
     As shown, a single interface may include a plurality of folders for organizing a plurality of files associated with various online applications. Although, the single interface may display a standard file structure with directories, folders, sub folders, and files located, appearing to be located at a common network location, the folders, files, etc. may be located on a plurality of different servers and/or network locations. 
     For example, the files may be stored at different servers each associated with a different online application. However, the single interface may have the ability to show files and folders as appearing in a single folder or subset of folders. In other words, the network location of various files may be transparent to the user, where the single interface only shows groupings of files in folders/directories (e.g. using meta data, etc.). 
     In this way, a virtual desktop and file structure is presented to the user using the single interface. As an option, the files may also be stored on a device on which the interface is displayed. For example, a user may chose to save a copy of the files on a device such that the user may work locally with the file. 
     In this case, the files stored on the device and the files stored on the server may be synchronized. For example, the files on the device and the files stored on the server may be synchronized upon saving the file to the device. As another option, the files may be synchronized periodically, based on a established time (e.g. every 5, 10, 15 minutes, etc.). In this case, synchronizing the files stored on the device and the files stored on the server refers to maintaining common copies of the files stored on the device and the files stored on the server. 
       FIG. 23  shows a network browser  2300  for displaying a single interface  2302  that includes a plurality of files, in accordance with one embodiment. As an option, the network browser  2300  may be implemented in the context of the details of  FIGS. 1-22 . Of course, however, the network browser  2300  may be implemented in any desired environment. It should also be noted that the aforementioned definitions may apply during the present description. 
     As shown, the single interface  2302  displays a plurality of files associated with different online applications. It should be noted that any folder displayed may include files associated with various online applications located at various network locations/servers. Furthermore, each of these online applications may require unique user login information. As noted above, one global login may be utilized to satisfy all login requirements, in accordance with one embodiment. 
     In addition to the illustrated functionality, the network browser  2300  and/or the interface  2302  may include functionality for searching for files/folders associated with the file structure illustrated in the interface  2300 . In this way, a search may be conducted with respect to the files, utilizing the interface. In one embodiment, the files may be indexed to facilitate the search with respect to the files. 
     For example, in one embodiment, tags may be utilized to index the files. In another embodiment, the files may be indexed by modification time/date, alphabetically, by size, network location, file type, content type, and any other suitable criteria. As an option, the searching may include searching files associated with the interface on network locations and/or the device of the user. 
       FIG. 24  shows a method  2400  for utilizing a network browser as a desktop, in accordance with one embodiment. As an option, the present method  2400  may be implemented in the context of the functionality and architecture of  FIGS. 1-23 . Of course, however, the method  2400  may be carried out in any desired environment. It should also be noted that the aforementioned definitions may apply during the present description. 
     As shown, a plurality of URLs in association with a network browser are stored, the URLs each associated with different online applications. See operation  2402 . Additionally, a plurality of identifiers in association with the network browser are displayed, each identifier associated with a different online applications. See operation  2404 . 
     In the context of the present description, an identifier refers to any character or number, series of characters or numbers, word, phrase, or object used for identification. For example, in various embodiments, the identifier may include, but is not limited to, icons, key words, pictures, links, and/or any other identifier that meets the above definition. 
     Further, a selection of at least one of the identifiers is displayed. See operation  2406 . Still yet, one of the online applications is accessed, in response to the selection of at least one of the identifiers. See operation  2408 . 
     More illustrative information will now be set forth regarding various optional architectures and features with which the foregoing framework may or may not be implemented, per the desires of the user. It should be strongly noted that the following information is set forth for illustrative purposes and should not be construed as limiting in any manner. Any of the following features may be optionally incorporated with or without the exclusion of other features described. 
       FIG. 25  shows a method  2500  for utilizing a network browser as a desktop, in accordance with another embodiment. As an option, the present method  2500  may be implemented in the context of the functionality and architecture of  FIGS. 1-24 . Of course, however, the method  2500  may be carried out in any desired environment. It should also be noted that the aforementioned definitions may apply during the present description. 
     As shown, a network browser is executed. See operation  2502 . For example, the network browser may be opened by a user on a user device. Once the network browser is executed, it is determined whether an online application menu is to be displayed. See operation  2504 . For example, in one embodiment, the user may select an option to display online applications. In another embodiment, the online application menu may be displayed automatically. In this case, an online application menu refers to a menu or list including available online applications. 
     If it is determined that the online application menu is to be displayed, the menu is displayed. See operation  2506 . In various embodiments, the menu may be displayed as a list, window, toolbar, tabbed screens, group of identifiers, etc. 
     It is then determined whether an online application has been selected. See operation  2508 . If an online application has been selected, a network browser window and/or browser window tab is opened with the online application. See operation  2510 . In one embodiment, this may include accessing user login information for the online application. Additionally, upon displaying the network browser in operation  2502 , a user may also be prompted for global login information, which allows access to the online application menu. 
     This global login information may also be utilized to automatically obtain login information for the online applications automatically such that one global login allows the user access to all available online applications without requiring the user to enter login information for each of the applications. This information may be stored on a device of the user, a server which includes the online application menu, and/or another network location. As shown further, it may also be determined whether the menu has been closed or remained open for the selection of other online applications. See operation  2512 . 
       FIG. 26  shows a network browser  2600  for using as a desktop, in accordance with another embodiment. As an option, the network browser  2600  may be implemented in the context of the functionality and architecture of  FIGS. 1-25 . Of course, however, network browser  2600  may be implemented in any desired environment. It should also be noted that the aforementioned definitions may apply during the present description. 
     As shown, upon executing the network browser  2600  to be used as a desktop, a user may be prompted to supply registration information  2602  for online applications that may be utilized in conjunction with the desktop environment. In this way, the user may configure and personalize an online desktop environment. Upon registration, entering the online application login information, and the URL associated with the online application, an identifier may be identified corresponding to the online application. 
     In one embodiment, the identifier may be selected by the user. In another embodiment, the identifier may automatically be selected (e.g. by the online application, a provider of the online desktop, etc.). Furthermore, in one case, the user may have the option to link or display an identifier associated with the online application. For example, the user may have the option to add a bookmark including a link to the online application. In another embodiment, the user may have the option to add the identifier to a desktop image. In this way, the user may be presented with a configurable online desktop including identifiers corresponding to various online applications, either shown on the desktop, or provided in a menu or list format. 
       FIG. 27  shows a network browser  2700  for using as a desktop, in accordance with another embodiment. As an option, the network browser  2700  may be implemented in the context of the functionality and architecture of  FIGS. 1-26 . Of course, however, network browser  2700  may be implemented in any desired environment. It should also be noted that the aforementioned definitions may apply during the present description. 
     In operation, a plurality of URLs in association with the network browser  2700  are stored, the URLs each associated with different online applications. In one embodiment, the URLs may include online application URLs. In this case, a plurality of bookmark URLs in association with the network browser may be stored, the bookmark URLs each associated with different web pages of interest. 
     Further, a plurality of identifiers  2702  in association with the network browser  2700  are displayed, each identifier associated with a different online applications. Using the identifiers  2702  one of the online applications may be accessed, in response to a selection of at least one of the identifiers  2702 . 
     As shown, the identifiers  2702  may be displayed utilizing an explorer bar  2704  to a side of a network browser window  2706  in which HTML content is displayed. In another embodiment, the identifiers may be displayed utilizing a tool bar  2708  above the network browser window  2706  in which HTML content is displayed. 
     As an option, the identifiers  2702  may be accessible via at least one network browser menu. In this way, the identifiers  2702  may be accessible when the network browser menu is selected. 
     As noted above, accessing online applications and/or information associated with the online applications may include entering or obtaining user login information. In one embodiment, each of the URLs may have login information associated therewith. In this case, the log-in information may be stored in and/or associated with the network browser  2700  and/or a device displaying the network browser  2700 . 
     In this way, the log-in information may be utilized to access the online application, in response to the selection of at least one of the identifiers  2702 . As noted above, in one embodiment, the log-in information may be capable of being entered when registering an associated one of the online applications in association with the network browser. 
     As an option, the online applications may be opened in a separate new browser tab, in response to the selection of at least one of the identifiers  2702 . For example, multiple tabs may appear across the top on the window  2706 , each tab corresponding to a different online application. In another embodiment, the online applications may be opened in a separate new browser window, in response to the selection of at least one of the identifiers  2702 . In this case, the new browser window may be included as a window within the network browser window  2706  or outside the network browser window  2706 . 
     In one embodiment, the identifiers  2702  may be displayed as computer icons, where computer icons refer to any pictogram. As an option, the identifiers  2702  may be user configurable. For example, the appearance of the identifiers may be configurable. Additionally, a location of display of the identifies may be configurable. For example, a user may have the ability to move the identifiers to various locations in the window  2706 . 
     Furthermore, the user may have the option to add/remove identifiers. Still yet, the configuration of the online desktop may be saved and stored on a user device and/or a network location. For example, an image on the configuration may be saved on a server hosting the online desktop. This may be accomplished by storing various data/metadata associated with the configuration. 
     In various embodiments, the network browser  2700  may include various other functionality. For example, in one embodiment, the network browser  2700  may display advertisements associated in conjunction with displaying online applications. 
       FIG. 28  shows a method  2800  of advertising in conjunction with online applications, in accordance with one embodiment. As an option, the present method  2800  may be implemented in the context of the functionality and architecture of FIGS.  1 - 27 . Of course, however, the method  2800  may be carried out in any desired environment. It should also be noted that the aforementioned definitions may apply during the present description. 
     As shown, a request to access a file associated with an online application is received. See operation  2802 . Additionally, at least one profile associated with the file is identified. See operation  2804 . 
     In the context of the present description, a profile refers to any information about an object. For example, in various embodiments, the profile may include, but is not limited to, a user profile of a user who initiated the request to access the file, a file profile associated with the file, a combination of a user and file profile, and/or any other profile that meets the above definition. In one case, the file profile may a function of a plurality of tags associated with the file. For example, tags associated with the file may include key words that may be attributed to a profile. 
     Further, an advertisement is presented in conjunction with the access of the file. See operation  2806 . In the context of the present description, the term advertisement may refer to a survey, questionnaire, promotional content, product/service information, and/or anything that is designed to attract attention. In one embodiment, the advertisement may include a digital advertisement. 
     Further, the advertisement may be presented in a variety of ways. In various embodiments, the advertisement may be presented on a computer, television, PDA, mobile phone, and/or any other mobile or stationary device capable of presenting advertisements. In such embodiments, the advertisement may be presented using web pages, television programs, movies, on-demand programming, audible media, and/or any other media capable of presenting advertisements. Of course, the foregoing examples are set forth for illustrative purposes only and should not be construed as limiting in any manner. 
       FIG. 29  shows a method  2900  of advertising in conjunction with online applications, in accordance with one embodiment. As an option, the present method  2900  may be implemented in the context of the functionality and architecture of  FIGS. 1-28 . Of course, however, the method  2900  may be carried out in any desired environment. It should also be noted that the aforementioned definitions may apply during the present description. 
     As shown, it is determined whether a request to access a file is received. See operation  2902 . If a request to access the file is received, a group profile is identified. See operation  2904 . In this case, the group profile may include the profile of a user group associated with the file. For example, the file may be attributable to a group of engineers in a specific area of engineering. Thus, the group profile may be associated with the specific area of engineering. 
     In another case, the group profile may include a profile of a group of files associated with the user or the particular file being accessed. In this case, file tags, file types, and a number of files may contribute to the group profile. 
     Once a group profile is identified, a profile of a user accessing the file is identified. See operation  2906 . For example, a profile of the user may have been determined when the user registered for an online application associated with the file. In this case, the user may have inputted preference information or the information may have been determined automatically based on user selections during the registration. Furthermore, the user may have inputted preference information or had preference information derived automatically after registration. Such preference information may have been derived based on internet browsing of the user, searches completed by the user, files generated by the user, file tags selected by the user, etc. 
     Once the profiles are identified, an advertisement is selected, based on the profiles, and then displayed. See operations  2908  and  2910 . For example, the advertisement may be displayed in a window associated with a network browser corresponding to an online application. In another embodiment, the advertisement may be sent to a mobile device of the user. In still another embodiment, the advertisement information may be provided to an advertisement agency such that the agency may facilitate the advertising (e.g. via a network browser, on demand television, etc.). In this way, directed advertising may be implemented in conjunction with utilizing online applications. 
       FIG. 30  shows a network browser  3000  for viewing advertisements in conjunction with files associated with online applications, in accordance with one embodiment. As an option, the network browser  3000  may be implemented in the context of the functionality and architecture of  FIGS. 1-29 . Of course, however, the method  3000  may be carried out in any desired environment. It should also be noted that the aforementioned definitions may apply during the present description. 
     In operation, a request to access a file associated with an online application may be received by the network browser  3000 . Additionally, at least one profile associated with the file may be identified. As mentioned above, in one embodiment, the profile may include a file profile associated with the file, where the file profile is a function of a plurality of tags associated with the file. 
     In this case, the tags may be manually entered or automatically determined. For example, the tags may be determined automatically by parsing words in the document. In another case, the tags may be manually entered using an interface including a folder directory. In one embodiment, the tags may be determined for a plurality of the files. the profile includes a group profile of a group of users who store a plurality of files to a network location. 
     As an option, the profile may include profile of a group of users who store a plurality of files to a network location. In this case, the profile may include a combination of a user profile and a group profile. In one case, the group profile may be a function of a plurality of tags associated with each of a plurality of the files. 
     Once the profile has been determined, an advertisement  3002  may be presented in conjunction the file, using the network browser  3000 . In this case the advertisement may correspond to the profile (e.g. of the user, group, file, aggregate of multiple profiles, etc.). In addition to potentially displaying the advertisement, the network browser  3000  may display various other items. For example, in one embodiment, the network browser  3000  may include a search interface for performing a search in addition to a window illustrating search results. 
       FIG. 31  shows a method  3100  for performing a search in conjunction with use of an online application, in accordance with one embodiment. As an option, the present method  3100  may be implemented in the context of the functionality and architecture of  FIGS. 1-30 . Of course, however, the method  3100  may be carried out in any desired environment. It should also be noted that the aforementioned definitions may apply during the present description. 
     In operation, a document editing interface is displayed for editing a document. See operation  3102 . Additionally, at least one term of the document is identified. See operation  3104 . 
     In the context of the present description, a term refers to any character or number, or sequence of characters or numbers. For example, in various embodiments, term may include, but is not limited to, a key word, a phrase, a date, an amount, and/or any other term that meets the above definition. 
     Further, a search interface is displayed. See operation  3106 . Still yet, a search is performed utilizing the search interface, based on the at least one term. See operation  3108 . 
       FIG. 32  shows an interface  3200  for performing a search in conjunction with use of an online application, in accordance with one embodiment. As an option, the interface  3200  may be implemented in the context of the functionality and architecture of  FIGS. 1-32 . Of course, however, the interface  3200  may be implemented in any desired environment. It should also be noted that the aforementioned definitions may apply during the present description. 
     In operation, a document editing interface  3202  is displayed for editing a document. Additionally, at least one term of the document is identified. Further, a search interface  3204  is displayed. Still yet, a search is performed utilizing the search interface  3204 , based on the at least one term. In various embodiments, may include a word processor document, a spreadsheet document; and/or a presentation document. 
     In one embodiment, the at least one term may be identified automatically. For example, the term may be identified by parsing words in the document. In this case, the parsing may include parsing nouns and/or verbs in the document. In one embodiment, the term may be identified by a frequency of use. In another embodiment, the term may be identified based on the same criteria used to automatically identify a tag for a document, as described above. 
     As an option, the at least one term may be identified manually. In this case, the term may be identified manually by highlighting the at least one term. In another embodiment, the term may be identified by typing the term in an interface search bar. As an option, the search may be performed by performing a right click operation. 
     As another option, a search term may be automatically suggested. In this case, a plurality of possible terms may be presented in a list. Thus, at least one of the terms in the list may be selected and searched. Further, this may be accomplished in conjunction with a manual or automatic search. 
     In one embodiment, the term may include includes a plurality of tags. In this case the tags may be determined automatically by parsing words in the document. In various embodiments, nouns, verbs, and/or repeated words in the document may be determined to be tags. 
     As shown further in  FIG. 32 , results of the search may be displayed simultaneously with the document. For example, the results may be positioned in a window associated with the interface  3200 . In one embodiment, the results may be displayed in a separate window from the document or on a tabbed page of interface  3200 . 
     In one case, the search results may include at least one additional document. In this case, the additional document may be associated with an online application corresponding to the document being displayed currently or another online application. Still yet, at least one additional term of the results may be identified (e.g. manually or automatically). Further, an additional search may be performed utilizing the search interface  3204 , based on the at least one additional term. In this way, the search may be focused to better improve search results. 
       FIG. 33  shows a method  3300  for focusing a search, in accordance with one embodiment. As an option, the present method  3300  may be implemented in the context of the functionality and architecture of  FIGS. 1-32 . Of course, however, the method  3300  may be carried out in any desired environment. It should also be noted that the aforementioned definitions may apply during the present description. 
     As shown, a first search is performed. See operation  3302 . Additionally, first search results of the first search are displayed. See operation  3304 . Further, at least one term of the first search results is identified. See operation  3306 . 
     Still yet, a second search is performed, based on the at least one term of the first search results. See operation  3308 . In addition, second search results of the second search are displayed. See operation  3310 . 
     More illustrative information will now be set forth regarding various optional architectures and features with which the foregoing framework may or may not be implemented, per the desires of the user. It should be strongly noted that the following information is set forth for illustrative purposes and should not be construed as limiting in any manner. Any of the following features may be optionally incorporated with or without the exclusion of other features described. 
       FIG. 34  shows an interface  3400  for focusing a search, in accordance with one embodiment. As an option, the interface  3400  may be implemented in the context of the functionality and architecture of  FIGS. 1-33 . Of course, however, the interface  3400  may be implemented in any desired environment. It should also be noted that the aforementioned definitions may apply during the present description. 
     In operation, a first search is performed using a search interface  3404 . Additionally, first search results of the first search are displayed. In one embodiment, the search results may be displayed in a search results window, in conjunction with displaying a document access by an online application. 
     Further, at least one term of the first search results is identified. A second search is then performed using the search interface  3404 , based on the at least one term of the first search results. In addition, second search results of the second search are displayed (e.g. in a search results window). 
     As an option, the terms may be identified manually. In one case, term may be identified manually by highlighting the at least one term. In this case, the second search may performed by performing a right click operation. 
     As another option, the terms may be identified automatically. For example, the may be identified automatically by parsing the first search results. In one case, nouns in the first search results may be identified as the at least one term. Additionally, verbs in the first search results may be identified as the at least one term. Still yet, repeated words in the first search results may be identified as the at least one term. 
     Further, as an option, at least one term may include a plurality of tags. As another option, the at least one term may be selected from a list of a plurality of suggested terms. In this case, the suggested terms may be generated automatically. Furthermore, in various embodiments, the suggested terms may be hierarchically ranked in order of a relevance value, a frequency of occurrence, alphabetically ranked, etc. As an additional option, the term may be selected by highlighting at least one of the suggested terms. 
     Furthermore, selecting the term may include selecting a term associated with a file corresponding to one or more online applications. In one case, exploration with this file may include opening or executing the online application. In various embodiments, this may be accomplished using any number of devices. 
       FIG. 35  shows a method  3500  for executing an online application on a mobile device, in accordance with one embodiment. As an option, the present method  3500  may be implemented in the context of the functionality and architecture of  FIGS. 1-34 . Of course, however, the method  3500  may be carried out in any desired environment. It should also be noted that the aforementioned definitions may apply during the present description. 
     As shown, an online application is accessed utilizing a mobile device. See operation  3502 . Additionally, at least a portion of a functionality of the online application utilizing an application executed on the mobile device. See operation  3504 . 
     In the context of the present description, a mobile device refers to any device which may be utilized in a mobile fashion. For example, in various embodiments, the mobile device may include, but is not limited to, a mobile phone, a PDA, a handheld computer, a laptop, and/or any other mobile device that meets the above definition. 
     More illustrative information will now be set forth regarding various optional architectures and features with which the foregoing framework may or may not be implemented, per the desires of the user. It should be strongly noted that the following information is set forth for illustrative purposes and should not be construed as limiting in any manner. Any of the following features may be optionally incorporated with or without the exclusion of other features described. 
       FIG. 36  shows an interface  3600  for executing an online application on a mobile device, in accordance with one embodiment. As an option, the interface  3600  may be implemented in the context of the functionality and architecture of  FIGS. 1-35 . Of course, however, the interface  3600  may be implemented in any desired environment. It should also be noted that the aforementioned definitions may apply during the present description. 
     In operation, an online application is accessed utilizing a mobile device  3602 . Additionally, at least a portion of a functionality of the online application utilizing an application executed on the mobile device  3602 . In one embodiment, the functionality may be performed by a client application separate from a network browser. As an option, the portion of the functionality may be performed by a network browser plug-in installed on the mobile device  3602 . 
     The functionality of the online application may include any functionality capable of being executed on the mobile device  3602 . For example, the portion of the functionality of the online application may include formatting functionality (e.g. text formatting, paragraph formatting, etc.). 
     Further, in one case, the portion of the functionality may include functionality that would otherwise be provided by a server that serves the online application. For example, the portion of the functionality may include responding to requests that would otherwise be provided by a server that serves the online application. As another example, the portion of the functionality of the online application may be provided by buffering requests of a user, and delaying sending the requests to a server that serves the online application. 
     In one embodiment, an online application utilizing may be accessed utilizing the mobile device  3602  and a request of a user to the online application may be buffered. Additionally, sending the requests to a server that serves the online application may be delayed. Still yet, a client application separate from the network browser may react to the request. 
     In this case, the reaction may be performed by a client application separate from the network browser. For example, in one case the reaction may be performed by a network browser plug-in installed on the mobile device  3602 . As an option, the reaction may simulate sending the request to a server that serves the online application. 
     It should be noted that all of the aforementioned functionality may be implemented on the mobile device  3602 . For example, the mobile device  3602  may be utilized to perform searches. Furthermore, various other commands may be implemented using the mobile device  3602  (e.g. cutting, pasting, etc.). 
       FIG. 37  shows a method  3700  for intelligent cutting and pasting, in accordance with one embodiment. As an option, the present method  3700  may be implemented in the context of the functionality and architecture of  FIGS. 1-36 . Of course, however, the method  3700  may be carried out in any desired environment. It should also be noted that the aforementioned definitions may apply during the present description. 
     As shown, a cut or copy command with respect to data is received. See operation  3702 . In this case the data may be any data capable of being cut or copied. For example, in various embodiments, the data may include text, objects, symbols, pictures, and/or any other data as defined above. 
     Additionally, a paste command with respect to the data is received. See operation  3704 . Further, an additional operation is performed on the data, before the past command is executed. See operation  3702 . 
     More illustrative information will now be set forth regarding various optional architectures and features with which the foregoing framework may or may not be implemented, per the desires of the user. It should be strongly noted that the following information is set forth for illustrative purposes and should not be construed as limiting in any manner. Any of the following features may be optionally incorporated with or without the exclusion of other features described. 
       FIG. 38  shows an interface  3800  for intelligent cutting and pasting, in accordance with one embodiment. As an option, the interface  3800  may be implemented in the context of the functionality and architecture of  FIGS. 1-37 . Of course, however, the interface  3800  may be implemented in any desired environment. It should also be noted that the aforementioned definitions may apply during the present description. 
     In operation, a cut or copy command with respect to data is received from the interface  3800 . Additionally, a paste command with respect to the data is received from the interface  3800 . Further, an additional operation is performed on the data, before the past command is executed. 
     In one embodiment, the additional operation may add or remove formatting to the data. In this case, the formatting may include text formatting, paragraph formatting, object formatting, picture formatting, and/or any other type of formatting. As an option, the additional operation may include converting a first formatting of the data to a second formatting. 
     In one embodiment, the second formatting may include a formatting of a destination associated with the paste command. In another embodiment, the additional operation may include performing an optical character recognition (OCR) on the data. In this case, the additional operation may include performing the optical character recognition on the data, such that the paste command results in parsed text being pasted into a document. 
     In one embodiment, the additional operation may be conditionally performed, based on a user instruction. In this case, the user instruction may include a right-click operation. In one case, a standard paste command may be distinguished from an intelligent paste command. Thus, it may be determined whether the paste command is an intelligent paste command. 
     In one embodiment, the additional operation may be performed if it is determined that the paste command is an intelligent paste command. In this case, it may be determined whether the paste command is an intelligent paste command, based on user input. 
     In one embodiment, the user may have an option to use a standard paste command or an intelligent paste command. In this case, the intelligent paste may be an optional preference under a settings menu. Thus, the user may select to apply the intelligent paste command indefinitely throughout a user session. 
     In another embodiment, the intelligent paste command may include spell check functionality. In this case, incorrect spelling of words copied may be remedied automatically upon invoking the paste command. As another option, the intelligent past command may include an option to paste using bullets. In this case, a user may paste copied text in a bullet format. The bullets may be divided in a variety of ways. For example, the bullets may be divided by carriage return, key word, periods, commas, or any other punctuation, etc. In one case, options for bullet division may be offered in a preferences or settings menu. 
     While various embodiments have been described above, it should be understood that they have been presented by way of example only, and not limitation. Thus, the breadth and scope of a preferred embodiment should not be limited by any of the above-described exemplary embodiments, but should be defined only in accordance with the following claims and their equivalents.