Stack icons representing multiple objects

Information

  • Patent Grant
  • 7694236
  • Patent Number
    7,694,236
  • Date Filed
    Friday, July 22, 2005
    18 years ago
  • Date Issued
    Tuesday, April 6, 2010
    14 years ago
Abstract
The features described herein are directed to a method and system for use in a computing environment for representing files stored in stacks by using a stack icon. The stack icon may include multiple thumbnail images as top elements, and may use common characteristics among the files to define the appearance of the stack. The system may also use metadata or file characteristics (e.g., time of last edit, size, etc.) to identify one file for top representation in the stack icon. The system may additionally include an empty stack icon, a generic stack icon, property based icons, and custom thumbnail icons.
Description
BACKGROUND

In current computer operating system environments, icons are provided for representing items such as files, folders, shortcuts, applications, documents, tasks, and commands. Icons may be used in list views, toolbars, dialog boxes, menus, and other places. Icons may be used to represent all objects of a specific class, such as MICROSOFT WORD™ documents, MICROSOFT EXCEL™ files, jpeg files, or other types of files.


Icons may include thumbnail images used to represent specific objects, such as a specific jpeg or a specific folder. Icons may be dynamically generated by code run on a user's machine or may be cached. Application and component developers can, using custom icons and thumbnails, convey as much information about objects as their pixels will allow. However, existing systems do not provide a technique for graphically grouping multiple icons based on properties of the files represented.


Currently, when a user wants to group items having common characteristics, the user often groups the items into a folder. For example, a user can group documents by file type to include one group for MICROSOFT WORD™ text or word processing documents, one for MICROSOFT EXCEL™ spreadsheet documents, one for MICROSOFT POWERPOINT™ presentation documents, etc. A user may also group music by genre, creating separate groups for Pop, Classical, Hip-Hop, etc. While the conventional folder structure and icon may provide easy access to the documents, the generic folder icon fails to provide descriptive information pertaining to items within the folder.


BRIEF SUMMARY

Aspects described herein are directed to a method for representing files stored in stacks. In some aspects, the method includes providing a set of stack icons, each icon in the set having a stack height representing a range of stack sizes. The method may additionally include determining a stack size for a selected stack and selecting and displaying an appropriate stack icon from the set of stack icons based on the determined stack size.


In another aspect, a method is provided for representing a selected stack of files, wherein the selected stack is stored within one of multiple libraries. The method may include providing an icon for each library. Each icon for each library portrays information relevant to the library. The method may additionally include storing multiple icons portraying the relevant information for each library, wherein each of the multiple icons in each library represents a range of stack heights. The method may additionally include representing a selected stack by determining an appropriate library and an appropriate stack height and displaying a corresponding icon.


In yet an additional aspect, a system is provided for representing a selected stack of files. The system may include stored sets of default stack icons, each stored set of default stack icons representing and portraying information relevant to a corresponding library. Each stored set of default stack icons includes multiple icons and each included icon represents a range of stack heights. The system may additionally include icon selection tools for determining if the selected stack of files belongs to a library having a corresponding stored set of default icons and for determining an appropriate stack height. Upon locating an appropriate library and stack height, the icon selection tools select and display an appropriate icon from an appropriate set of default icons.


In further aspects, thumbnail icons and property-based icons may be provided. A top element of the stack may be determined based on characteristics of the files in the stack (e.g., last time of edit, size, etc.). The stack icon may also include multiple images, such as thumbnail images, as top elements in the stack. Additionally, each stored set of icons may include a unique empty set icon for indicating that a stack is empty.





BRIEF DESCRIPTION OF THE DRAWINGS

The features herein are described in detail below with reference to the attached drawings figures, wherein:



FIG. 1 is a block diagram illustrating a computerized environment in which the features herein may be implemented;



FIG. 2 is a block diagram illustrating a stack selection and display module;



FIGS. 3A and 3B are flow charts illustrating a stack icon selection and display process;



FIG. 4 is a diagram illustrating stack icons for documents;



FIGS. 5A-5E illustrate stack icons for various types of items;



FIG. 6 illustrates a stack icon that may be used as a default stack icon;



FIG. 7 illustrates a file type overlay on a stack icon;



FIG. 8 illustrates a thumbnail stack icon from a photo or video library; and



FIG. 9 illustrates a music stack icon for songs grouped by album in a music library.



FIGS. 10
a-c illustrate example stack icons having multiple images.





DETAILED DESCRIPTION
System Overview

Features described herein include a method and system for displaying stacks of items having common properties. The system and method may provide a technique for displaying the number of items in a stack on a stack icon. Furthermore, the stack icon may visually represent the height of the stack, such that the stack depicted in the icon varies depending on the relative size of the stack compared to other stacks in the view. Stack icons may be depicted to include different kinds of items (documents, photos, videos, music, contacts, etc.) depending on the library in which the stack is being represented. Furthermore, a different image may be used to represent empty stacks, as compared to images used for non-empty stacks. When there is an icon available to represent a certain property, that icon may be overlaid on the stack icon based on that property. For some special types of stacks, such as stacks of photos and videos, the stack icon includes thumbnails of items from within the stack itself.


The system and method may be implemented in a computerized environment. An exemplary operating environment is described in detail below with reference to FIG. 1.


Exemplary Operating Environment



FIG. 1 illustrates an example of a suitable computing system environment 100 on which the features herein may be implemented. The computing system environment 100 is only one example of a suitable computing environment and is not intended to suggest any limitation as to the scope of use or functionality of the features described herein. Neither should the computing environment 100 be interpreted as having any dependency or requirement relating to any one or combination of components illustrated in the exemplary operating environment 100.


The features herein are described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. Moreover, those skilled in the art will appreciate that the features may be practiced with other computer system configurations, including hand-held devices, multiprocessor systems, microprocessor-based or programmable consumer electronics, minicomputers, mainframe computers, and the like. The features may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.


With reference to FIG. 1, the exemplary system 100 for implementing the invention includes a general purpose-computing device in the form of a computer 110 including a processing unit 120, a system memory 130, and a system bus 121 that couples various system components including the system memory to the processing unit 120.


Computer 110 typically includes a variety of computer readable media. By way of example, and not limitation, computer readable media may comprise computer storage media and communication media. The system memory 130 includes computer storage media in the form of volatile and/or nonvolatile memory such as read only memory (ROM) 131 and random access memory (RAM) 132. A basic input/output system 133 (BIOS), containing the basic routines that help to transfer information between elements within computer 110, such as during start-up, is typically stored in ROM 131. RAM 132 typically contains data and/or program modules that are immediately accessible to and/or presently being operated on by processing unit 120. By way of example, and not limitation, FIG. 1 illustrates operating system 134, application programs 135, other program modules 136, and program data 137.


The computer 110 may also include other removable/nonremovable, volatile/nonvolatile computer storage media. By way of example only, FIG. 1 illustrates a hard disk drive 141 that reads from or writes to nonremovable, nonvolatile magnetic media, a magnetic disk drive 151 that reads from or writes to a removable, nonvolatile magnetic disk 152, and an optical disk drive 155 that reads from or writes to a removable, nonvolatile optical disk 156 such as a CD ROM or other optical media. Other removable/nonremovable, volatile/nonvolatile computer storage media that can be used in the exemplary operating environment include, but are not limited to, magnetic tape cassettes, flash memory cards, digital versatile disks, digital video tape, solid state RAM, solid state ROM, and the like. The hard disk drive 141 is typically connected to the system bus 121 through an non-removable memory interface such as interface 140, and magnetic disk drive 151 and optical disk drive 155 are typically connected to the system bus 121 by a removable memory interface, such as interface 150.


The drives and their associated computer storage media discussed above and illustrated in FIG. 1, may provide storage of computer readable instructions, data structures, program modules and other data for the computer 110. In FIG. 1, for example, hard disk drive 141 is illustrated as storing operating system 144, application programs 145, other program modules 146, and program data 147. Note that these components can either be the same as or different from operating system 134, application programs 135, other program modules 136, and program data 137. Operating system 144, application programs 145, other program modules 146, and program data 147 are given different numbers here to illustrate that, at a minimum, they are different copies. A user may enter commands and information into the computer 110 through input devices such as a keyboard 162 and pointing device 161, commonly referred to as a mouse, trackball or touch pad. Other input devices (not shown) may include a microphone, joystick, game pad, satellite dish, scanner, or the like. These and other input devices are often connected to the processing unit 120 through a user input interface 160 that is coupled to the system bus, but may be connected by other interface and bus structures, such as a parallel port, game port or a universal serial bus (USB). A monitor 191 or other type of display device is also connected to the system bus 121 via an interface, such as a video interface 190. In addition to the monitor, computers may also include other peripheral output devices such as speakers 197 and printer 196, which may be connected through an output peripheral interface 195.


The computer 110 may operate in a networked environment using logical connections to one or more remote computers, such as a remote computer 180. The remote computer 180 may be a personal computer, and typically includes many or all of the elements described above relative to the computer 110, although only a memory storage device 181 has been illustrated in FIG. 1. The logical connections depicted in FIG. 1 include a local area network (LAN) 171 and a wide area network (WAN) 173, but may also include other networks.


When used in a LAN networking environment, the computer 110 may be connected to the LAN 171 through a network interface or adapter 170. When used in a WAN networking environment, the computer 110 may include a modem 172 or other means for establishing communications over the WAN 173, such as the Internet. The modem 172, which may be internal or external, may be connected to the system bus 121 via the user input interface 160, or other appropriate mechanism. In a networked environment, program modules depicted relative to the computer 110, or portions thereof, may be stored in the remote memory storage device. By way of example, and not limitation, FIG. 1 illustrates remote application programs 185 as residing on memory device 181. It will be appreciated that the network connections shown are exemplary and other means of establishing a communications link between the computers may be used.


Stack Icon Selection and Display Module



FIG. 2 illustrates a stack icon selection and display module 10. The stack icon selection and display module 10 may be implemented in the computerized environment 100 illustrated in FIG. 1 and may operate from within the RAM 132 or other memory device. The stack icon selection and display module 10 may include a user selection module 12, a categorizing module 14, and counting tools 16. The stack icon selection and display module 10 may additionally include icon selection tools 20, default stack icons 22, property based icons 24, and custom thumbnail icons 26.


The user selection module 12 enables a user to group items having common properties into a stack. As described above, the stacks may share a common file type or other characteristic.


The categorizing module 14 categorizes the selected items in accordance with the shared common property. Stack icons are depicted to include different kinds of items such as documents, photos, videos, music, contacts, etc. The particular depiction may depend upon the library in which the stack is being represented.


The counting tools 16 count the number of selected items to be provided on the stack. As will be further illustrated below, the number of items in a stack may be displayed on the stack icon itself. Furthermore, the height of the stack depicted in a stack icon may vary depending on the relative size of the stack compared to other stacks in the view. Additionally, the counting tools 16 are capable of determining if a selected stack is empty. A completely different image may be used to represent empty stacks, as compared to images used for non-empty stacks.


The icon selection tools 20 select an appropriate icon from three categories of available icons. The three categories of available icons include default stack icons 22, property-based icons 24, and thumbnail icons 26. While typically a default icon is provided for each library, if there is an icon available to represent a certain property, that icon may be overlaid on the stack icon based on that property. The custom thumbnail icons 26 may be provided for some special types of stacks, such as stacks of photos and videos. The thumbnail stack icon includes thumbnails of items from within the stack itself.


With further reference to the icon selection tools 20, each icon is provided in multiple stack sizes as will be further described below. The icon selection tools 20 may implement an algorithm to select the appropriate stack size within a category.


Icon Characteristics


Three categories of stack icons may be provided for the system. As set forth above, these categories may include default stack icons, property-based stack icons, and thumbnail stack icons. Each of the main libraries including the document library, photo library, video library, music and radio library, contacts library, message library, and television and movie library may include a set of default stack icons. A set of generic default stack icons may be provided for use in non-library views.



FIG. 4 illustrates a wire-frame model of stack icons for documents. The illustrated display includes stacks 40, 42, 44, 46, 48, 50, 52, 54, 56, 58, 60, 62, and 64. Each stack includes a caption 80 appropriate for each item in the stack. Furthermore, on the face of each stack is designator 70 for indicating a number of items contained within the stack. For instance, the stack 52 includes a caption “marketing reports” and 92 documents are contained in the stack. Stack 60 includes a “to do” caption and two documents are contained within the stack. The size displayed for each stack is related to the number of items in the stack. For instance, the stack 52 is shown as larger than the stack 60 because the stack 52 contains more items than the stack 60.


As shown, each set of default stack icons includes multiple icons, each icon representing a stack of a distinct size. In some example aspects, five icons are provided for representing stacks of different sizes. In this instance, the sizes are characterized as large, medium, small, two, and zero. Various criteria may be relevant to selecting which stack icon is shown. The size of the stack icon may indicate the relative size of the stack compared to other stacks in that same view. In some aspects, a stack might not be visually represented as having more items than it actually contains, except in the case of a stack of just one item. An exemplary algorithm for selecting the appropriate size is described below.


Default Stack Icons



FIGS. 5A-5E illustrate multiple embodiments of default stack icons. Each of the main libraries in an operating system may have a set of default stack icons. A set of generic default stack icons may be included for non-library views. In the illustrated embodiments, the operating system provides a documents library, a photo and video library, a music and radio library, a contacts library, and a message library.



FIG. 5A illustrates multiple default stack icons 502, 504, 506, 508, and 510 within the documents library. The icons used for the stack emulate the documents they represent. Additionally, as shown in an upper left corner of each stack, the number of items contained within the stack is displayed. The larger stacks are shown with a greater number of icons than the smaller stacks. Stack 510 utilizes a unique “empty stack” icon.



FIG. 5B illustrates multiple default stack icons 512, 514, 516, 518, and 520 within the music and radio library. As set forth above, a number in the upper left corner of each stack indicates a number of items in the stack. The icons may be representative of the content of the library. In FIG. 5B, compact disc (CD) cases are used as icons. Furthermore, the final stack 520 is an empty stack and includes a unique icon showing an empty CD case. As set forth above, larger stacks are shown with a greater number of stacked icons than smaller stacks.



FIG. 5C illustrates multiple default stack icons 522, 524, 526, 528, and 530 within the photograph library. As set forth above, a number in the upper left corner of each stack indicates a number of items in the stack. The icons may be representative of the content of the library. In FIG. 5C, a photograph is used as an icon. Furthermore, the final stack 530 is an empty stack and includes a unique icon showing an empty picture frame. As set forth above, larger stacks are shown with a greater number of stacked icons than smaller stacks.



FIG. 5D illustrates multiple default stack icons 532, 534, 536, 538, and 540 within the contacts library. As set forth above, a number in the upper left corner of each stack indicates a number of items in the stack. Larger stacks are shown with a greater number of stacked icons than smaller stacks. The icons are representative of the content of the library. In FIG. 5D, a contact card is used as the stack icon. Furthermore, the final stack 540 is an empty stack and includes a unique icon showing an empty contact card.



FIG. 5E illustrates multiple default stack icons 542, 544, 546, 548, and 550 within the message library. As set forth above, a number in the upper left corner of each stack indicates a number of items in the stack. Larger stacks are shown with a greater number of stacked icons than smaller stacks. The icons are representative of the content of the library. In FIG. 5E, an envelope is used as the stack icon. Furthermore, the final stack 540 is an empty stack and includes a unique icon showing an empty inbox.


As illustrated in FIGS. 5A-5E, each set of default stack icons includes five icons representing stacks of different sizes. These sizes may include a large size, a medium size, a small size, a “two” sized icon, and an empty stack or “zero” icon. The selection of the appropriate default icon may be based on the size of the stack, and is further described below.



FIG. 6 illustrates a generic default stack icon 600. This icon may be used to represent items in non-library views. The generic default stack icon may also be provided in multiple sizes conforming to those described above.


Property-Based Stack Icons



FIG. 7 illustrates a property based stack icon 700. The icon 700 is the icon for the document library, but includes a file type overlay 710 indicating a file type. The property-based stack icons are composed from the appropriate default stack icon for the library and an additional icon that represents a property. Property-based stack icons may be available from multiple libraries. For example, in the document library, the music library, or the photo library, the additional icon may be provided to indicate file type. Alternatively, an additional icon may be provided in the document library or photo library to indicate the date or month in which the displayed stack was created. Other types of property-based stack icons may also be available.


The overlay 710 is used to convey what type of object the icon portrays. An application may provide such an overlay for each file-type it owns, but if none is provided for a particular file-type, then the application's own icon may be used as the overlay. The placement of the overlay is shown as aligned exactly along the bottom edge of the image such that it fits within the boundaries of the icon when the image is bottom-aligned. Horizontally, the type overlay may be centered on the right edge of the image, but can be shown in other positions.


Overlays may be stored in pixel sizes, such as the following pixel sizes: 48×48, 32×32, 24×24, 16×16, and 8×8. The following table describes an appropriate sized overlay for display on icons of different sizes.
















Icon Size
Corresponding Overlay Size









256 × 256
48 × 48



128 × 128
32 × 32



48 × 48
24 × 24



32 × 32
16 × 16



16 × 16
8 × 8











Thumbnail Stack Icons



FIG. 8 illustrates a custom thumbnail icon 800 from the photo library. The thumbnail icon may be generated to represent items actually contained within the stack. FIG. 9 illustrates a custom thumbnail stack from the music library. Custom thumbnail icons may be provided for stacks in the photo and video libraries. These thumbnail stacks should preview photographs from within the actual stack. Stacks of songs may be provided by album in the music library. Thus thumbnail stacks may show CD album art encased in a CD cover. The thumbnail icons may further include stacks of songs by artist in the music library. These thumbnails may display art relevant to the artist. If a custom thumbnail stack icon 26 is unavailable, the system displays the default stack icon from the stored default stack icons 22 for that stack.


In general, thumbnail icons may be treated just as other metadata on items. Thumbnail icons may be stored and extracted as bitmaps and may be referenced as a multi-valued property. Every item may have a flag that indicates one of three states regarding its thumbnails. In a first “yes” state, the flag indicates the existence of a cached thumbnail. In a second “no” state, there is no cached thumbnail one cannot be extracted. In a third “uncertain state” there is no cached thumbnail, and it may be undetermined whether a thumbnail can be extracted.


Icon Selection Method



FIG. 3A is a flow chart illustrating an example method for selecting and displaying stack icons. The process begins in step A0 and the stack icon selection and display module 10 receives a user request in step A02. In step A04, the categorizing module 12 locates the category that corresponds to the user selection. In step A06, the counting tools 16 determine the number of items in the stack. In step A08, the icon selection tools 20 implement a selection algorithm to select an icon appropriate for the size of the stack. This process is further explained below with respect to FIG. 3B.


In step A10, the stack icon selection and display module 10 locates any special properties or available thumbnails. If either is available in step A12, the stack icon selection and display module 10 displays the thumbnail or property based icon in step A18. If neither a property-based or thumbnail icon is available in step A12, the system looks for a default library in step A14. If the default icon is found in step A16, the system displays the default icon in step A20. If the default icon is not found in step A16, the system retrieves and displays the generic icon in step A22 to complete the process in step A24.


A limited number of stack icons may be provided for representing all sizes of stacks. For instance, whereas a stack may have any number of items from zero to hundreds or thousands, five different stack icons may be provided to represent all of these different stack sizes. FIG. 3B is a flowchart illustrating a technique for selecting the appropriate stack icon for display. The process begins in step B0. In step B02, the system divides a range of stacks between the largest stack and the smallest stack having more than two items into three equal ranges. In step B04, the system assigns stacks to an icon based on the range. The stacks that fall in the largest range get the largest stack icon, the second largest get the next largest stack icon, etc. Stacks with one or two items get the stack of size “two” icon. Stacks with zero items get the stack of size zero icon. It may be desirable to use a larger or smaller number of stack icons to represent all sizes of stacks. If desired, different selection algorithms may be used.


Although the discussion above uses examples of predefined stack icons (e.g., five predetermined stacks), the available stack icons need not be predetermined, and they need not be limited. For example, stack icons may be dynamically generated based on the file objects to be represented in the stack. The system may be configured to identify the number of objects in the stack, and may dynamically generate the stack icon using this number. For example, the system may follow an algorithm in which a plurality of individual icons are combined to form a stack icon, where the plurality includes an individual icon for each object, such that there is a one-to-one relationship between elements shown in the stack icon and the number of objects represented by the stack. Thus, for example, a stack icon for a group of five files may be assembled by combining five individual icons. This combining can be done in any desired manner, such as a layering, fanning, etc. Alternatively, some other ratio (besides one-to-one) may be used. For example, the system may use an element in the stack for every 1.5, 2, 3, 4, 5, 10, 20, or any other number of objects to be represented in the stack.


A stack icon may be dynamically generated to include a thumbnail image of one of the documents in the stack. The thumbnail image may be a miniaturized image visually depicting the contents, metadata, and/or characteristics of a file object. In some instances, multiple thumbnail images may be placed at the top of a stack icon, to help convey more information to the user regarding the objects represented by the stack icon. FIGS. 10a, 10b and 10c illustrate example icons having multiple thumbnail images on a stack icon. The FIG. 10a example includes four images 1001, and the stack appearance includes four icon elements 1002 indicating the size of the stack. The FIG. 10b example illustrates how each element in the stack may include an image or thumbnail image. Furthermore, as shown in the FIG. 10c example, the stack elements 1003 may actually appear superimposed over one or more of the thumbnail images 1004.


The system may determine which object to place at the top of the stack based on characteristics of the objects in the stack. For example, the system may automatically select the file (or files) that were most recently modified, and represent those files at the top of the stack (e.g., by placing their thumbnail(s) at the top of the stack icon), making it easier for the user to see what has been done to the files. As another example, the most active or most recently played audio file may be represented at the top of the stack, which may remind the user of the contents of the stack based on frequency of use. Other characteristics, such as file size, file type, project, etc. may also be used to make this determination.


Additionally, the process of selecting a stack type, or of selecting a thumbnail to appear on the top of the stack, may be based on characteristics of the objects represented by the stack. In some instances, the system may be configured to check the contents and/or metadata of the various objects in the stack, and identify common features to the objects. For example, if the user has created a group of objects that are all of the same type, the system may select and/or generate a stack icon corresponding to that type. If the various objects all relate to a common project, the system may select and/or generate a stack icon having an image identifying the project at the top of the stack. As another example, if the stack includes multiple songs by the same artist, the system may select and/or generate a stack icon having an image identifying the artist, or an image of a common album cover on which songs in the stack are contained, on top of the stack.


While particular embodiments have been illustrated and described in detail herein, it should be understood that various changes and modifications might be made. The features described herein are intended in all respects to be illustrative rather than restrictive, and alternatives may be used. It will be understood that certain features and sub-combinations are of utility and may be employed without reference to other features and sub-combinations.

Claims
  • 1. Computer-readable media having computer-executable instructions embodied thereon that, when executed, perform method for visually representing a plurality of computer data objects with a stack icon on a display, the method comprising the steps of: a computing device identifying a first plurality of computer data objects to be visually represented by a stack icon;determining whether all of the identified objects share at least one of a location in a library, and a file type as a common characteristic, and if said identified objects share a common characteristic, selecting a representative thumbnail image for said common characteristic comprising one of: a default image, a property-based image, and a thumbnail icon image, wherein the property-based image is a default image that includes a numeric designator for indicating a number of items represented by the stack icon, and wherein a default image is selected when a property-based image or a thumbnail icon image is not available;said computing device generating a stack icon to represent said first plurality of computer data objects, said stack icon having a second plurality of distinct elements corresponding to said first plurality of computer data objects, and having a topmost element that includes said representative thumbnail image for said common characteristic.
  • 2. The media of claim 1, wherein said first and second pluralities correspond by an integer ratio.
  • 3. The media of claim 1, wherein said top element depicts the contents of one of said computer data objects in visual form.
  • 4. The media of claim 1, wherein said second plurality of distinct elements are arranged in a layered, stacked orientation in said stack icon.
  • 5. The media of claim 4, wherein said distinct elements are rotated with respect to each other.
  • 6. The media of claim 5, wherein said top element is arranged horizontally.
  • 7. The media of claim 1, wherein said second plurality of distinct elements are superimposed over one or more thumbnail images in said stack icon.
  • 8. The media of claim 1, wherein said data objects are computer files, and said common characteristic is a file type.
  • 9. The media of claim 1, wherein said data objects are audio song files, and said common characteristic is an artist of the songs.
  • 10. A system for visually representing a plurality of computer data objects with a stack icon on a computer display, the system comprising: an identifying component that identifies a first plurality of computer data objects to be visually represented by said stack icon;a selection component that selects a representative image for a common characteristic of said first plurality of computer data objects comprising one of: a default image, a property-based image, and a thumbnail image, wherein the property-based image is a default image that includes one or more of a numeric designator that indicates a number of items represented by the stack icon and a file-type overlay that indicates a file type of at least one of the computer data objects in the first plurality, and wherein a default image is selected when a property-based image and a thumbnail image are not available;a generating component that generates a stack icon to represent said first plurality of computer data objects, said stack icon having a second plurality of distinct elements corresponding to said first plurality of computer data objects; anda displaying component that displays said stack icon on a computer display, wherein said stack icon includes, as a topmost element in the stack, said representative thumbnail image for said common characteristic.
  • 11. The system of claim 10, wherein said first and second pluralities correspond by an integer ratio.
  • 12. The system of claim 10, wherein a plurality of said distinct elements are arranged in a layered, stacked orientation in said stack icon.
  • 13. The system of claim 12, wherein said distinct elements are rotated with respect to each other.
  • 14. The system of claim 10, further comprising displaying the topmost element as a series of partially overlapping thumbnails at the top of the stack.
  • 15. A method for visually representing a plurality of computer data objects with a stack icon on a display, the method comprising the steps of: receiving a request from a user to display a stack icon;identifying a first plurality of computer data objects to be visually represented by the stack icon;determining whether all of the identified objects share at least one of a location in a library, and a file type as a common characteristic;determining a total number of computer data objects in said first plurality of computer data objects to be represented by the stack icon;selecting a representative image for said common characteristic comprising one of: a default icon image, a property-based icon image, and a thumbnail icon image, wherein the default icon image is a generic image that depicts the file type of at least one of the represented computer data objects, the property-based icon image is a default icon image with additional features including a numeric designator for indicating a number of items represented by the stack icon, and a file type overlay for indicating a file type of one or more computer data objects represented by the stack icon, wherein the file type overlay is positioned within a bounding rectangle about said property based icon image, and the thumbnail icon image displays at least a thumbnail image of one or more image or video files represented by the stack icon, and wherein a default icon is selected when a property-based icon image or a thumbnail icon image is not available;selecting a default icon image as a representative image, where the first plurality of computer data objects are determined not to have a common characteristic; andgenerating a stack icon to represent said first plurality of computer data objects, said stack icon having a second plurality of distinct elements corresponding to said first plurality of computer data objects, and having a topmost element that includes said representative image for said common characteristic, wherein the second plurality of elements are displayed rotated with respect to each other beneath the topmost element.
  • 16. The method claim 15, wherein a unique stack icon is provided when a stack icon represents zero data objects.
  • 17. The media of claim 1, wherein the property-based image also includes a file type overlay indicating the file type of one or more computer data objects represented by the stack icon, and wherein the file type overlay is positioned within a bounding rectangle about said property-based icon image.
  • 18. The media of claim 1, wherein generating a stack icon to represent said first plurality of computer data objects further comprises: in the alternative to generating a stack icon to represent said first plurality of computer data objects, selecting a stack icon from a limited number of available stack icons, wherein an available stack icon is associated with a quantity range of computer data objects that is represented by the available stack icon.
  • 19. The media of claim 18, wherein the limited number of available stack icons include at least three available stack icons for a common characteristic, and wherein the at least three available stack icons include stack icons to represent zero data objects, one or two data objects, and more than two data objects.
  • 20. The method of claim 15, wherein said topmost element is arranged horizontally.
CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation-in-part of copending U.S. application Ser. No. 10/830,224, entitled “System and Method for Displaying Stack Icons.”

US Referenced Citations (476)
Number Name Date Kind
4881179 Vincent Nov 1989 A
5060135 Levine et al. Oct 1991 A
5241671 Reed et al. Aug 1993 A
5297250 Leroy et al. Mar 1994 A
5327529 Fults Jul 1994 A
5333266 Boaz et al. Jul 1994 A
5333315 Saether et al. Jul 1994 A
5388196 Pajak et al. Feb 1995 A
5418946 Mori et al. May 1995 A
5420605 Vouri May 1995 A
5461710 Bloomfield et al. Oct 1995 A
5499364 Klein et al. Mar 1996 A
5504852 Thompson-Rohrlich Apr 1996 A
5513306 Mills et al. Apr 1996 A
5544360 Lewak et al. Aug 1996 A
5546527 Fitzpatrick et al. Aug 1996 A
5550852 Patel et al. Aug 1996 A
5559948 Bloomfield et al. Sep 1996 A
5583982 Matheny et al. Dec 1996 A
5590259 Anderson et al. Dec 1996 A
5596702 Stucka Jan 1997 A
5598524 Johnston, Jr. et al. Jan 1997 A
5600778 Swanson et al. Feb 1997 A
5606669 Bertin et al. Feb 1997 A
5625783 Ezekiel Apr 1997 A
5630042 McIntosh et al. May 1997 A
5648795 Vouri Jul 1997 A
5652876 Ashe Jul 1997 A
5675520 Pitt Oct 1997 A
5680563 Edelman Oct 1997 A
5684969 Ishida Nov 1997 A
5696486 Poliquin et al. Dec 1997 A
5696914 Nahaboo Dec 1997 A
5710926 Maurer Jan 1998 A
5757925 Faybishenko May 1998 A
5760770 Bliss Jun 1998 A
5790121 Sklar et al. Aug 1998 A
5802516 Shwarts et al. Sep 1998 A
5831606 Nakajima et al. Nov 1998 A
5835094 Ermel et al. Nov 1998 A
5838317 Bolnick et al. Nov 1998 A
5838322 Nakajima et al. Nov 1998 A
5855446 Disborg Jan 1999 A
5867163 Kurtenbach Feb 1999 A
5870088 Washington Feb 1999 A
5875446 Brown et al. Feb 1999 A
5875448 Boys Feb 1999 A
5878410 Zbikowski et al. Mar 1999 A
5886694 Breinberg et al. Mar 1999 A
5899995 Millier et al. May 1999 A
5905973 Yonezawa et al. May 1999 A
5907703 Kronenberg May 1999 A
5907837 Ferrel et al. May 1999 A
5909540 Carter et al. Jun 1999 A
5923328 Griesmer Jul 1999 A
5929854 Ross Jul 1999 A
5930801 Falkenhainer Jul 1999 A
5933139 Feigner et al. Aug 1999 A
5935210 Stark Aug 1999 A
5973686 Shimogori Oct 1999 A
5987454 Hobbs Nov 1999 A
5987506 Carter et al. Nov 1999 A
6003040 Mital et al. Dec 1999 A
6008806 Nakajima et al. Dec 1999 A
6014137 Burns Jan 2000 A
6016692 Schaenzer et al. Jan 2000 A
6021262 Cote et al. Feb 2000 A
6023708 Mendez et al. Feb 2000 A
6024843 Anderson Feb 2000 A
6025843 Sklar Feb 2000 A
6037944 Hugh Mar 2000 A
6055540 Snow Apr 2000 A
6055543 Christensen et al. Apr 2000 A
6061059 Taylor May 2000 A
6061692 Thomas et al. May 2000 A
6061695 Slivka et al. May 2000 A
6065012 Balsara et al. May 2000 A
6078924 Ainsbury et al. Jun 2000 A
6097389 Morris et al. Aug 2000 A
6101509 Hanson Aug 2000 A
6144968 Zellweger Nov 2000 A
6147601 Sandelman et al. Nov 2000 A
6160552 Wilsher Dec 2000 A
6175364 Wong et al. Jan 2001 B1
6181342 Niblack Jan 2001 B1
6202061 Khosla et al. Mar 2001 B1
6216122 Elson Apr 2001 B1
6237004 Dodson et al. May 2001 B1
6237011 Ferguson et al. May 2001 B1
6240407 Chang et al. May 2001 B1
6240421 Stolarz May 2001 B1
6243094 Sklar Jun 2001 B1
6243724 Mander et al. Jun 2001 B1
6246411 Strauss Jun 2001 B1
6256031 Meijer et al. Jul 2001 B1
6262732 Coleman et al. Jul 2001 B1
6268852 Lindhorst et al. Jul 2001 B1
6275829 Angiulo et al. Aug 2001 B1
6279016 De Vorchik et al. Aug 2001 B1
6301586 Yang et al. Oct 2001 B1
6308173 Glasser et al. Oct 2001 B1
6317142 Decoste et al. Nov 2001 B1
6324541 de l'Etraz et al. Nov 2001 B1
6324551 Lamping et al. Nov 2001 B1
6326953 Wana Dec 2001 B1
6330007 Isreal Dec 2001 B1
6339767 Rivette et al. Jan 2002 B1
6341280 Glass et al. Jan 2002 B1
6342907 Petty Jan 2002 B1
6356863 Sayle Mar 2002 B1
6356915 Chtchetkine et al. Mar 2002 B1
6363377 Kravets et al. Mar 2002 B1
6363400 Chtchetkine et al. Mar 2002 B1
6369840 Barnett et al. Apr 2002 B1
6377283 Thomas Apr 2002 B1
6401097 McCotter et al. Jun 2002 B1
6405265 Kronenberg Jun 2002 B1
6408298 Van Jun 2002 B1
6411311 Rich et al. Jun 2002 B1
6425120 Morganelli et al. Jul 2002 B1
6425121 Phillips Jul 2002 B1
6430575 Dourish et al. Aug 2002 B1
6430835 Ranucci et al. Aug 2002 B1
6437807 Berquist et al. Aug 2002 B1
6438590 Gartner Aug 2002 B1
6448985 McNally Sep 2002 B1
6453311 Powers, III Sep 2002 B1
6453319 Mattis et al. Sep 2002 B1
6462762 Ku Oct 2002 B1
6466228 Ulrich et al. Oct 2002 B1
6466238 Berry et al. Oct 2002 B1
6466932 Dennis et al. Oct 2002 B1
6470344 Kothuri et al. Oct 2002 B1
6473100 Beaumont et al. Oct 2002 B1
6480835 Light Nov 2002 B1
6483525 Tange Nov 2002 B1
6505233 Hanson et al. Jan 2003 B1
6513038 Hasegawa et al. Jan 2003 B1
6519612 Howard et al. Feb 2003 B1
6526399 Coulson et al. Feb 2003 B1
6535229 Kraft Mar 2003 B1
6535230 Celik Mar 2003 B1
6539399 Hazama et al. Mar 2003 B1
6544295 Bodnar Apr 2003 B1
6549217 De Greef et al. Apr 2003 B1
6549916 Sedlar Apr 2003 B1
6563514 Samar May 2003 B1
6571245 Huang et al. May 2003 B2
6573906 Harding et al. Jun 2003 B1
6573907 Madrane Jun 2003 B1
6583799 Manolis et al. Jun 2003 B1
6590585 Suzuki et al. Jul 2003 B1
6606105 Quartetti Aug 2003 B1
6613101 Mander et al. Sep 2003 B2
6628309 Dodson et al. Sep 2003 B1
6636238 Amir et al. Oct 2003 B1
6636250 Gasser Oct 2003 B1
6638313 Freeman et al. Oct 2003 B1
6658406 Mazner et al. Dec 2003 B1
6662198 Satyanarayanan et al. Dec 2003 B2
6684222 Cornelius et al. Jan 2004 B1
6721760 Ono Apr 2004 B1
6735623 Prust May 2004 B1
6738770 Gorman May 2004 B2
6745206 Mandler et al. Jun 2004 B2
6745207 Reuter et al. Jun 2004 B2
6751626 Brown et al. Jun 2004 B2
6754829 Butt et al. Jun 2004 B1
6760721 Chasen Jul 2004 B1
6762776 Huapaya Jul 2004 B2
6762777 Carroll Jul 2004 B2
6763458 Watanabe et al. Jul 2004 B1
6763777 Rosenberg Jul 2004 B1
6768999 Prager et al. Jul 2004 B2
6784900 Dobronsky et al. Aug 2004 B1
6784925 Tomat et al. Aug 2004 B1
6795094 Watanabe et al. Sep 2004 B1
6801909 Delgado et al. Oct 2004 B2
6801919 Hunt et al. Oct 2004 B2
6803926 Lamb et al. Oct 2004 B1
6810404 Ferguson et al. Oct 2004 B1
6813474 Robinson et al. Nov 2004 B2
6816863 Bates et al. Nov 2004 B2
6820083 Nagy et al. Nov 2004 B1
6823344 Isensee et al. Nov 2004 B1
6826443 Makinen Nov 2004 B2
6847959 Arrouye et al. Jan 2005 B1
6853391 Bates et al. Feb 2005 B2
6865568 Chau Mar 2005 B2
6871348 Cooper Mar 2005 B1
6876900 Takeda et al. Apr 2005 B2
6876996 Czajkowski et al. Apr 2005 B2
6880132 Uemura Apr 2005 B2
6883009 Yoo Apr 2005 B2
6883146 Prabhu et al. Apr 2005 B2
6906722 Hrebejk et al. Jun 2005 B2
6910049 Fenton et al. Jun 2005 B2
6922709 Goodman Jul 2005 B2
6925608 Neale et al. Aug 2005 B1
6938207 Haynes Aug 2005 B1
6944647 Shah et al. Sep 2005 B2
6947959 Gill Sep 2005 B1
6948120 Delgobbo Sep 2005 B1
6950818 Dennis et al. Sep 2005 B2
6950989 Rosenzweig et al. Sep 2005 B2
6952714 Peart Oct 2005 B2
6952724 Prust Oct 2005 B2
6980993 Horvitz et al. Dec 2005 B2
6983424 Dutta Jan 2006 B1
7010755 Anderson et al. Mar 2006 B2
7024427 Bobbitt et al. Apr 2006 B2
7028262 Estrada et al. Apr 2006 B2
7043472 Aridor et al. May 2006 B2
7047498 Lui May 2006 B2
7051291 Sciammarella et al. May 2006 B2
7062500 Hall et al. Jun 2006 B1
7062718 Kodosky et al. Jun 2006 B2
7068291 Roberts et al. Jun 2006 B1
7100150 Polk Aug 2006 B2
7106843 Gainsboro Sep 2006 B1
7139811 Lev Ran et al. Nov 2006 B2
7149729 Kaasten et al. Dec 2006 B2
7168051 Robinson et al. Jan 2007 B2
7194743 Hayton Mar 2007 B2
7203948 Mukundan et al. Apr 2007 B2
7216289 Kagle May 2007 B2
7216301 Moehrle May 2007 B2
7219302 O'Shaughnessy et al. May 2007 B1
7240292 Hally et al. Jul 2007 B2
7243334 Berger et al. Jul 2007 B1
7275063 Horn Sep 2007 B2
7290245 Skjolsvold Oct 2007 B2
7293031 Dusker et al. Nov 2007 B1
7383494 Krolczyk et al. Jun 2008 B2
7409382 Kido Aug 2008 B2
7415484 Tulkoff et al. Aug 2008 B1
7496859 Watanabe Feb 2009 B2
20010034733 Prompt et al. Oct 2001 A1
20010034771 Hutsch et al. Oct 2001 A1
20010047368 Oshinsky et al. Nov 2001 A1
20010049675 Mandler et al. Dec 2001 A1
20010053996 Atkinson Dec 2001 A1
20010056434 Kaplan et al. Dec 2001 A1
20010056508 Arneson et al. Dec 2001 A1
20020010736 Marques Jan 2002 A1
20020019935 Andrew et al. Feb 2002 A1
20020033844 Levy et al. Mar 2002 A1
20020046232 Adams et al. Apr 2002 A1
20020046299 Lefeber et al. Apr 2002 A1
20020049717 Routtenberg et al. Apr 2002 A1
20020052885 Levy May 2002 A1
20020054167 Hugh May 2002 A1
20020059199 Harvey May 2002 A1
20020062310 Marmor et al. May 2002 A1
20020063734 Khalfay et al. May 2002 A1
20020070965 Austin Jun 2002 A1
20020075310 Prabhu et al. Jun 2002 A1
20020075312 Amadio et al. Jun 2002 A1
20020075330 Rosenzweig et al. Jun 2002 A1
20020087652 Davis et al. Jul 2002 A1
20020087740 Castanho et al. Jul 2002 A1
20020087969 Brunheroto et al. Jul 2002 A1
20020089540 Geier et al. Jul 2002 A1
20020091679 Wright Jul 2002 A1
20020091697 Huang et al. Jul 2002 A1
20020091739 Ferlitsch et al. Jul 2002 A1
20020095416 Schwols Jul 2002 A1
20020097278 Mandler et al. Jul 2002 A1
20020100039 Iatropoulos et al. Jul 2002 A1
20020103998 DeBruine Aug 2002 A1
20020104069 Gouge et al. Aug 2002 A1
20020107973 Lennon et al. Aug 2002 A1
20020111942 Campbell et al. Aug 2002 A1
20020113821 Hrebejk et al. Aug 2002 A1
20020120505 Henkin et al. Aug 2002 A1
20020120604 Labarge et al. Aug 2002 A1
20020120757 Sutherland et al. Aug 2002 A1
20020129033 Hoxie et al. Sep 2002 A1
20020138552 DeBruine et al. Sep 2002 A1
20020138582 Chandra et al. Sep 2002 A1
20020138744 Schleicher et al. Sep 2002 A1
20020144155 Bate et al. Oct 2002 A1
20020149888 Motonishi et al. Oct 2002 A1
20020152262 Arkin et al. Oct 2002 A1
20020152267 Lennon Oct 2002 A1
20020156756 Stanley et al. Oct 2002 A1
20020156895 Brown Oct 2002 A1
20020161800 Eld et al. Oct 2002 A1
20020163572 Center et al. Nov 2002 A1
20020169678 Chao et al. Nov 2002 A1
20020174329 Bowler et al. Nov 2002 A1
20020181398 Szlam Dec 2002 A1
20020184357 Traversat et al. Dec 2002 A1
20020188605 Adya et al. Dec 2002 A1
20020188621 Flank et al. Dec 2002 A1
20020188735 Needham et al. Dec 2002 A1
20020194252 Powers, III Dec 2002 A1
20020196276 Corl et al. Dec 2002 A1
20020199061 Friedman et al. Dec 2002 A1
20030001964 Masukura et al. Jan 2003 A1
20030009484 Hamanaka et al. Jan 2003 A1
20030014415 Weiss et al. Jan 2003 A1
20030018657 Monday Jan 2003 A1
20030018712 Harrow et al. Jan 2003 A1
20030028610 Pearson Feb 2003 A1
20030033367 Itoh Feb 2003 A1
20030037060 Kuehnel Feb 2003 A1
20030041178 Brouk et al. Feb 2003 A1
20030046260 Satyanarayanan et al. Mar 2003 A1
20030063124 Melhem et al. Apr 2003 A1
20030069893 Kanai et al. Apr 2003 A1
20030069908 Anthony et al. Apr 2003 A1
20030074356 Kaier et al. Apr 2003 A1
20030076322 Ouzts et al. Apr 2003 A1
20030078918 Souvignier et al. Apr 2003 A1
20030079038 Robbin et al. Apr 2003 A1
20030081002 De Vorchik et al. May 2003 A1
20030081007 Cyr et al. May 2003 A1
20030085918 Beaumont et al. May 2003 A1
20030093321 Bodmer et al. May 2003 A1
20030093531 Yeung et al. May 2003 A1
20030093580 Thomas et al. May 2003 A1
20030097361 Huang et al. May 2003 A1
20030098881 Nolte et al. May 2003 A1
20030098893 Makinen May 2003 A1
20030098894 Sheldon et al. May 2003 A1
20030101200 Koyama et al. May 2003 A1
20030105745 Davidson et al. Jun 2003 A1
20030107597 Jameson Jun 2003 A1
20030110188 Howard et al. Jun 2003 A1
20030115218 Bobbitt et al. Jun 2003 A1
20030117403 Park et al. Jun 2003 A1
20030117422 Hiyama et al. Jun 2003 A1
20030120678 Hill et al. Jun 2003 A1
20030120928 Cato et al. Jun 2003 A1
20030120952 Tarbotton et al. Jun 2003 A1
20030122873 Dieberger et al. Jul 2003 A1
20030126136 Omoigui Jul 2003 A1
20030126212 Morris et al. Jul 2003 A1
20030135495 Vagnozzi Jul 2003 A1
20030135513 Quinn et al. Jul 2003 A1
20030135517 Kauffman Jul 2003 A1
20030135659 Bellotti et al. Jul 2003 A1
20030140115 Mehra Jul 2003 A1
20030154185 Suzuki et al. Aug 2003 A1
20030158855 Farnham et al. Aug 2003 A1
20030177422 Taroukhine et al. Sep 2003 A1
20030184587 Ording et al. Oct 2003 A1
20030195950 Huang et al. Oct 2003 A1
20030210281 Ellis et al. Nov 2003 A1
20030212664 Breining et al. Nov 2003 A1
20030212680 Bates et al. Nov 2003 A1
20030212710 Guy Nov 2003 A1
20030222915 Marion et al. Dec 2003 A1
20030225796 Matsubara Dec 2003 A1
20030227480 Polk Dec 2003 A1
20030227487 Hugh Dec 2003 A1
20030233419 Beringer Dec 2003 A1
20040001106 Deutscher et al. Jan 2004 A1
20040002993 Toussaint et al. Jan 2004 A1
20040003247 Fraser et al. Jan 2004 A1
20040004638 Babaria Jan 2004 A1
20040006549 Mullins et al. Jan 2004 A1
20040008226 Manolis et al. Jan 2004 A1
20040019584 Greening et al. Jan 2004 A1
20040019655 Uemura et al. Jan 2004 A1
20040019875 Welch Jan 2004 A1
20040030731 Iftode et al. Feb 2004 A1
20040044696 Frost Mar 2004 A1
20040044776 Larkin Mar 2004 A1
20040054674 Carpenter et al. Mar 2004 A1
20040056894 Zaika et al. Mar 2004 A1
20040056896 Doblmayr et al. Mar 2004 A1
20040059755 Farrington et al. Mar 2004 A1
20040068524 Aboulhosn et al. Apr 2004 A1
20040070612 Sinclair et al. Apr 2004 A1
20040073705 Madril, Jr. et al. Apr 2004 A1
20040083433 Takeya Apr 2004 A1
20040085581 Tonkin May 2004 A1
20040088374 Webb et al. May 2004 A1
20040091175 Beyrouti May 2004 A1
20040098370 Garland et al. May 2004 A1
20040098379 Huang May 2004 A1
20040098742 Hsieh et al. May 2004 A1
20040103073 Blake et al. May 2004 A1
20040103280 Balfanz et al. May 2004 A1
20040105127 Cudd et al. Jun 2004 A1
20040117358 Von Kaenel et al. Jun 2004 A1
20040117405 Short et al. Jun 2004 A1
20040128322 Nagy Jul 2004 A1
20040133572 Bailey et al. Jul 2004 A1
20040133588 Kiessig et al. Jul 2004 A1
20040133845 Forstall et al. Jul 2004 A1
20040142749 Ishimaru et al. Jul 2004 A1
20040143349 Roberts et al. Jul 2004 A1
20040148434 Matsubara et al. Jul 2004 A1
20040153451 Phillips et al. Aug 2004 A1
20040153968 Ching et al. Aug 2004 A1
20040167942 Oshinsky et al. Aug 2004 A1
20040168118 Wong et al. Aug 2004 A1
20040174396 Jobs et al. Sep 2004 A1
20040177116 McConn et al. Sep 2004 A1
20040177148 Tsimelzon, Jr. Sep 2004 A1
20040177319 Horn Sep 2004 A1
20040181516 Ellwanger et al. Sep 2004 A1
20040183824 Benson et al. Sep 2004 A1
20040189694 Kurtz et al. Sep 2004 A1
20040189704 Walsh et al. Sep 2004 A1
20040189707 Moore et al. Sep 2004 A1
20040193594 Moore et al. Sep 2004 A1
20040193599 Liu et al. Sep 2004 A1
20040193600 Kaasten et al. Sep 2004 A1
20040193621 Moore et al. Sep 2004 A1
20040193672 Samji et al. Sep 2004 A1
20040193673 Samji et al. Sep 2004 A1
20040199507 Tawa Oct 2004 A1
20040205168 Asher Oct 2004 A1
20040205625 Banatwala et al. Oct 2004 A1
20040205633 Martinez et al. Oct 2004 A1
20040205698 Schliesmann et al. Oct 2004 A1
20040215600 Aridor et al. Oct 2004 A1
20040220899 Barney et al. Nov 2004 A1
20040223057 Oura et al. Nov 2004 A1
20040225650 Cooper et al. Nov 2004 A1
20040230572 Omoigui Nov 2004 A1
20040230599 Moore et al. Nov 2004 A1
20040230917 Bales et al. Nov 2004 A1
20040233235 Rubin et al. Nov 2004 A1
20040243597 Jensen et al. Dec 2004 A1
20040249902 Tadayon et al. Dec 2004 A1
20040255048 Lev Ran et al. Dec 2004 A1
20040257169 Nelson Dec 2004 A1
20050004928 Hamer et al. Jan 2005 A1
20050010860 Weiss et al. Jan 2005 A1
20050015405 Plastina et al. Jan 2005 A1
20050022132 Herzberg et al. Jan 2005 A1
20050027757 Kiessig et al. Feb 2005 A1
20050050470 Hudson et al. Mar 2005 A1
20050055306 Miller et al. Mar 2005 A1
20050071355 Cameron et al. Mar 2005 A1
20050080807 Beilinson et al. Apr 2005 A1
20050097477 Camara et al. May 2005 A1
20050114672 Duncan et al. May 2005 A1
20050120242 Mayer et al. Jun 2005 A1
20050131903 Margolus et al. Jun 2005 A1
20050131905 Margolus et al. Jun 2005 A1
20050138567 Smith et al. Jun 2005 A1
20050149481 Hesselink et al. Jul 2005 A1
20050165753 Chen et al. Jul 2005 A1
20050166159 Mondry et al. Jul 2005 A1
20050171947 Gautestad Aug 2005 A1
20050192953 Neale et al. Sep 2005 A1
20050192966 Hilbert et al. Sep 2005 A1
20050207757 Okuno Sep 2005 A1
20050210416 MacLaurin et al. Sep 2005 A1
20050243993 McKinzie et al. Nov 2005 A1
20050246331 De Vorchik et al. Nov 2005 A1
20050246643 Gusmorino et al. Nov 2005 A1
20050246664 Michelman et al. Nov 2005 A1
20050256909 Aboulhosn et al. Nov 2005 A1
20050257169 Tu Nov 2005 A1
20050283476 Kaasten et al. Dec 2005 A1
20060004692 Kaasten et al. Jan 2006 A1
20060020586 Prompt et al. Jan 2006 A1
20060036568 Moore et al. Feb 2006 A1
20060053066 Sherr et al. Mar 2006 A1
20060059204 Borthakur et al. Mar 2006 A1
20060080308 Carpentier et al. Apr 2006 A1
20060090137 Cheng et al. Apr 2006 A1
20060129627 Phillips et al. Jun 2006 A1
20060173873 Prompt et al. Aug 2006 A1
20060200455 Wilson Sep 2006 A1
20060200466 Kaasten et al. Sep 2006 A1
20060200832 Dutton Sep 2006 A1
20060218122 Poston et al. Sep 2006 A1
20070180432 Gassner et al. Aug 2007 A1
Foreign Referenced Citations (28)
Number Date Country
1421800 Nov 2001 CN
2329492 Jul 1998 GB
05-089173 Sep 1993 JP
2001188702 Dec 1999 JP
2001188702 Dec 1999 JP
2001067250 Mar 2001 JP
2001142766 May 2001 JP
2001154831 Jun 2001 JP
2001-297022 Oct 2001 JP
2002099565 Apr 2002 JP
2002269145 Sep 2002 JP
2002182953 Nov 2002 JP
2002334103 Nov 2002 JP
20042749 May 2003 NO
2347258 Feb 2009 RU
WO 9322738 Mar 1993 WO
WO 9412944 Jun 1994 WO
WO 9414281 Jun 1994 WO
9938092 Jul 1999 WO
WO 9949663 Sep 1999 WO
WO 0157867 Mar 2000 WO
WO 0051021 Aug 2000 WO
WO 0167668 Aug 2000 WO
0163919 Aug 2001 WO
WO 0225420 Mar 2002 WO
WO 03001720 Jan 2003 WO
WO 2004107151 Sep 2004 WO
WO 2004097680 Nov 2004 WO
Related Publications (1)
Number Date Country
20050283742 A1 Dec 2005 US
Continuation in Parts (1)
Number Date Country
Parent 10830224 Apr 2004 US
Child 11186825 US