US20100313198A1

US20100313198A1 - User interface for assisting in the installation of an asset

Info

Publication number: US20100313198A1
Application number: US12/795,627
Authority: US
Inventors: Imran Chaudhri
Original assignee: Individual
Current assignee: Individual
Priority date: 2004-06-22
Filing date: 2010-06-07
Publication date: 2010-12-09
Also published as: US7761811B1

Abstract

Some embodiments of the invention provide a method that assists in the installation of an asset in a graphical user interface for a computer system. The method receives a selection of the asset that has not yet been installed on the computer system. It then responds to the selection of the asset by displaying a preview of the asset without installing the asset on the computer system. In some embodiments, the method receives a modification of an attribute of the asset. It then responds to the modification of the attribute of the asset by displaying a preview of the modification of the attribute of the asset without installing the asset on the computer system. In some embodiments, the preview of the asset is used to assist in the determination of whether to install the asset.

Description

FIELD OF THE INVENTION

The present invention relates to a user interface for assisting in the installation of an asset.

BACKGROUND OF THE INVENTION

Computer systems come packaged and pre-installed with a variety of fonts. In most instances, users will find the fonts that they want already installed on their computer system. However, there may be times when users need a particular type of font that is not installed on the computer system. In such a case, users can typically find fonts elsewhere and install it on their computer system. There are numerous ways for users to find and retrieve fonts for their computer system. For example, users can find fonts on a website and download it to their computer system.
Once the font has been retrieved to their computer system, a user can install the font on his computer system. In most cases, the user must copy the font into the right folder in order to install the font on the computer system. Therefore, if the user does not know where to copy the font, then he will be unable to install the retrieved font. Another drawback of the current font installation method is that users are unable to preview the retrieved font until it has been installed on the computer system. In some instances, it may be possible that users inadvertently retrieved the wrong font. Under current font installation methods, users will not know that they downloaded the wrong font until they install the font on their computer system. Once they figure out that a wrong font has been installed, then they have to uninstall the font.
Therefore, there is a need for a better way of installing fonts on a computer system. Specifically, there is a need for way for installing fonts on a computer system without having to manually copy the font to a folder. Additionally, there is a need for a way for previewing a font, before installing the font on the computer system. Ideally, this technique can be used to install other types of assets.

SUMMARY OF THE INVENTION

Some embodiments of the invention provide a method that assists in the installation of an asset in a graphical user interface of a computer system. The method receives a selection of the asset that has not yet been installed on the computer system. It then responds to the selection of the asset by displaying a preview of the asset without installing the asset on the computer system. In some embodiments, the method receives a modification of an attribute of the asset. It then responds to the modification of the attribute of the asset by displaying a preview of the modification of the attribute of the asset without installing the asset on the computer system. In some embodiments, the preview of the asset is used to assist in the determination of whether to install the asset.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an event-flow process of several embodiments of the invention.

FIG. 2 illustrates a portion of a GUI of several embodiments of the invention.

FIG. 3 illustrates a portion of a GUI for previewing an asset.

FIG. 4 illustrates a portion of a GUI for previewing an asset with a menu selected.

FIG. 5 illustrates a portion of a GUI for previewing an asset with a different view of an attribute of the asset.

FIG. 6 illustrates a GUI with a window once the asset has been installed on the computer system.

FIG. 7 illustrates a block diagram of a GUI with an option to install asset in different folders.

FIG. 8 illustrates a block diagram of a computer system.

DETAILED DESCRIPTION OF THE INVENTION

In the following detailed description of the invention, numerous details, examples and embodiments of the invention are set forth and described. However, it will be clear and apparent to one skilled in the art that the invention is not limited to the embodiments set forth and that the invention may be practiced without some of the specific details and examples discussed.

I. Definitions

A graphical user interface (“GUI”) is an interface of a computer system that allows users to interact with the computer system through images and text. A GUI allows users to interact with the computer system in an intuitive graphical manner. Instead of learning and writing complex command languages, users can perform many operations by simply interacting with the visual components of a GUI, which are often easy to understand. A GUI often includes a cursor pointer, icons, desktop, windows, etc. The cursor pointer (the “cursor”) is a pointer that a user can move across the GUI through the operation of a cursor controller, such as a mouse, a trackpad, trackball, etc. A user can use the cursor to select objects in the GUI. For instance, the user can select an object by dragging the cursor to the object and perform a click operation (e.g., through a button of the cursor controller):
Icons are examples of selectable objects in a GUI. Icons are used to represent folders, files, commands, etc. in the GUI. An icon can be represented by a text component, an image component, or both text and image components. The desktop refers to the contents on a display screen below any windows. A window is an area on the display screen that displays its own file, message, application, etc. independently of other windows that are displayed on the display screen.

II. Overview

Some embodiments of the invention provide a method that assists in the installation of an asset in a graphical user interface for a computer system. The method receives a selection of the asset that has not yet been installed on the computer system. It then responds to the selection of the asset by displaying a preview of the asset without installing the asset on the computer system.
In some embodiments, the method receives a modification of an attribute of the asset. It then responds to the modification of the attribute of the asset by displaying a preview of the modification of the attribute of the asset without installing the asset on the computer system. In some embodiments, the preview of the asset is used to assist in the determination of whether to install the asset.
In some embodiments, the method receives a request to install the asset. It then installs the asset on the computer system. An asset that is installed on the computer system is an asset that is available for use by a program or the operating system of the computer system. Accordingly, to install an asset, some embodiments perform a set of operations to make the asset available for use by the operating system and/or its applications.
The previewed and installed asset is a font in some embodiments. A font is typically a design for a set of text, numbers and/or characters. A font has various characteristics (attributes), such as typeface, size, spacing, and pitch, etc. Different embodiments install a font differently. For instance, in some embodiments, installing a font entails copying the font into an appropriate folder, e.g., a folder that contains other installed fonts.
Some embodiments facilitate the installation of a font by providing the user with an install icon in proximity to the preview display of the font. When the user selects the install icon, these embodiments then launch an application that automatically installs the font in the appropriate location on the computer system. Alternatively, some embodiments provide the user with a list of locations to install the font, when the user selects the install icon. Once the user specifies the installation location, these embodiments then install the font in this location.
Before or after installing a font, some embodiments determine whether an identical font is already installed on the computer system. If so, these embodiments display an indication that the identical font is already installed on the computer system.

III. Event Flow

FIG. 1 illustrates an event-flow process of some embodiments of the invention. In these embodiments, the invention is employed to preview and install an asset in a computer system. In some embodiments, the events illustrated in FIG. 1 are performed by more than one software module of a computer system.
The event-flow diagram of FIG. 1 will be described below by reference to examples illustrated in FIGS. 2-6. In these examples, the asset that is being previewed is a font. These figures and the description of these figures present numerous specific GUI elements (e.g., windows, buttons, displays, etc.) for implementing several embodiments of the invention. However, one of ordinary skill will realize that the invention can be practiced without these specific elements.
FIG. 2 illustrates a portion of a GUI 200 that includes a desktop 210, and a font file 220. The font file 220 is a selectable object (e.g., an icon) in the GUI 200. The font file 220 contains information about a font (e.g., the Times New Roman font). Within the font file, there are several ways to represent fonts. One way is to store font data in bit-mapped format. In bit-mapped format, every character is represented by an array of dots. Also, each font character is represented by its own data, even if for example, the typeface is the same. Another way to store font data is in a vector format. In vector format, the outline of each character is defined by geometric shape. An advantage of vector format over bit-mapped format is that the vector format is scalable. This means that, unlike the bit-mapped format, the same data can be used to represent fonts of different sizes.
The font file 220 has been copied to the computer system but may not have been installed on the computer system. A font can be copied to a location (e.g., to a folder or desktop) on a computer system in a number of different ways. For instance, at times, a font is downloaded over a network. Alternatively, a font can be copied from a removable storage medium, such as a CD.
Regardless of how an asset is received by the computer system, the event-flow process 100 of FIG. 1 allows a user to preview the asset without having to install it on the computer system. As shown in this figure, the event flow starts when a user selects (at 110) an asset for preview. A user can select an asset for preview in several different ways. For instance, in some embodiments, a user selects a font resource by moving a cursor over the font resource and performing a double-click operation.
Once an asset has been selected (at 110) for preview, the process 100 (at 120) opens a preview window in the graphical user interface. The process then displays (at 120) a preview presentation in the preview window without first installing the asset on the computer system.
FIG. 3 illustrates an example of such a preview operation. Specifically, this figure illustrates a preview window 300 that has been opened in the graphical user interface 200 after a user has selected the font resource 200 for preview. The window 300 includes a viewing section 310 for displaying one or more presentations of the font resource 220.
The window 300 further includes a menu section 320 for modifying an attribute relating to the presentation of the font resource 220. In this example, the attribute is the font style, which includes the styles Italic, Regular, Bold, and Bold Italic. Also, in this example, the menu section 320 is a pull down menu that allows the user to select one of the font styles for the font presentation that is displayed in the preview window. In FIG. 3, the menu section 320 indicates that the current font style of the font resource 220 is a bold typeface. Accordingly, the viewing section 310 displays a presentation of the font resource 220 in a bold typeface. The window 300 further includes an installation button 330 for installing the font resource being previewed on the computer system.
After a preview presentation of the asset 220 is displayed (at 120) in a preview window, the process 100 transitions to 130, where it waits for user input. As shown in FIG. 1, the process transitions from 130 to 140 when it receives a request to modify a presentation attribute of the asset. For instance, FIG. 4 illustrates an example where the user has opened the drop-down menu section 320 and changed the font style for the preview presentation of the font resource 220 from Bold to Regular.
At 140, the presentation attribute of the asset is modified according to the request. The presentation of the asset in the preview window is then modified (at 140) according to the modification of the presentation attribute. FIG. 5 illustrates an example of changing the presentation of the font resource 200. Specifically, this figure illustrate the viewing section 310 of the preview window 300 as displaying the presentation of the font resource 200 in a Regular font style, in accordance to the font style change previously illustrated in FIG. 4. FIG. 5 also illustrates in the menu section 320 that the Regular font style is the current preview font style. Once the process modifies the preview of the presentation of the asset in the preview window, the process transitions back to 130 to wait for the next user input.
The process 100 loops through 140 several times when the user makes several requests to modify of the presentation attribute. Each time the process loops through 140 it changes the preview presentation in accordance with the user's requested modification. In some embodiments, the user can change more than one presentation attribute of the preview presentation. For instance, in the font installation example, some embodiments allow the user to change not only the font style but also the font size of the presentation in the preview window. By allowing the user to repeatedly examine different preview presentations of an asset, the process 100 allows a user to robustly explore an asset before deciding to install it.
When the process receives (at 130) a user request to install a previewed asset, the process determines (at 150) whether it has previously installed the asset. If not, the process installs (at 160) the asset. In some embodiments, the process 100 launches another application to install the asset. For instance, in some embodiments, the process 100 launches a font application (e.g., a Font Book application) to install a font resource that it previously previewed. The process uses one of the known techniques in the art for installing a font on a computer. In some embodiments, the installation entails copying the font resource 220 from its current location on the computer system to a folder where other installed font resources are located. After installing the asset at 160, the process 100 terminates.
Once the font resource 220 is installed, the font installing application presents a window that displays the installed font resources. FIG. 6 illustrates an example of such a window. This window is displayed by the Font Book application. This window includes a font viewing section 610 that displays a presentation of the font resource 220, which has now been installed on the computer system. The font window 600 further includes a font listing section 200 for displaying a list of installed font resources, including the font resource 220.
When the process determines (at 150) that it has previously installed the asset, the process transitions to 170. At 170, the process installs the asset again. As before, the process can provide (at 170) a preview of the installed asset in a preview window, such as the font-installation preview window 300. In some embodiments, the process 100 also provides (at 170) a visual clue regarding the duplicate installation of the asset.
For instance, in the font-installation example discussed above, the Font Book application determines (at 150) that the font resource 220, representing the Times New Roman font, was previously installed. Hence, it transitions to 170, where it installs this resource one more time. At 170, the Font Book application indicates to the user that there is more than one copy of a Times New Roman font installed on the computer system. Specifically, as illustrated in FIG. 6, the Font Book application lists the Times New Roman font styles again as installed font styles in its listing display 620 of installed fonts, and places a dot next to each Times New Roman font style that has been installed more than once.
After 170, the process terminates. The process also terminates when while waiting at 130, it receives a user's request to terminate the previewing of an asset.
The process 100 of FIG. 1 and the examples of FIGS. 2-6 conceptually illustrate one manner for installing fonts. One of ordinary skill will realize that other embodiments install fonts differently. For instance, some embodiments might not provide a preview of a font, but instead simply install a font in an appropriate location. These embodiments can automatically install the font directly or indirectly through another application (e.g., the Font Book application).
Alternatively, other embodiments present a user with a list of folders to install a font, once a user selects a font file for installation. FIG. 7 illustrates an example of such a presentation. In this example, a window 700 provides a user with four possible folders 705-720 to install a font. The user can select one of these folders (e.g., by clicking on one of these folders) and then select the install icon 725 to install the font in the selected folder.
Before presenting the user with the list of installation folders, some embodiments provide the user with an opportunity to preview a font before installation. Other embodiments simply provide the list of installation folders when the user selects a font file that is not in one of the installation folders.
The process 100 was described above by reference to a font-installation example. This process, however, can be used to preview and install many other assets on the computer system. For instance, this process can be used to preview and install screen savers. In some embodiments, such a process would allow the user to modify attributes of the screen saver, such as its speed effects, etc.
Other assets employed in other embodiments include any resource that has an audible or visual presentation that a user might wish to preview before installing the resource on the computer. Examples of such assets include sounds, pictures, etc. The invention can also be used to automatically install an asset that does not contain code (i.e., an asset that is not executable).

IV. Computer System

FIG. 8 presents a computer system with which one embodiment of the invention is implemented. Computer system 800 includes a bus 805, a processor 810, a system memory 815, a read-only memory 820, a permanent storage device 825, input devices 830, and output devices 835. The bus 805 collectively represents all system, peripheral, and chipset buses that communicatively connect the numerous internal devices of the computer system 800. For instance, the bus 805 communicatively connects the processor 810 with the read-only memory 820, the system memory 815, and the permanent storage device 825.
From these various memory units, the processor 810 retrieves instructions to e3cute and data to process in order to e3cute the processes of the invention. The read-only-memory (ROM) 820 stores static data and instructions that are needed by the processor 810 and other modules of the computer system.
The permanent storage device 825, on the other hand, is read-and-write memory device. This device is a non-volatile memory unit that stores instruction and data even when the computer system 800 is off. Some embodiments of the invention use a mass-storage device (such as a magnetic or optical disk and its corresponding disk drive) as the permanent storage device 825.
Other embodiments use a removable storage device (such as a floppy disk or Zip® disk, and its corresponding disk drive) as the permanent storage device. Like the permanent storage device 825, the system memory 815 is a read-and-write memory device. However, unlike storage device 825, the system memory is a volatile read-and-write memory, such as a random access memory. The system memory stores some of the instructions and data that the processor needs at runtime. In some embodiments, the invention's processes are stored in the system memory 815, the permanent storage device 825, and/or the read-only memory 820.
The bus 805 also connects to the input and output devices 830 and 835. The input devices enable the user to communicate information and select commands to the computer system. The input devices 830 include alphanumeric keyboards and cursor-controllers. The output devices 835 display images generated by the computer system. The output devices include printers and display devices, such as cathode ray tubes (CRT) or liquid crystal displays (LCD).
Finally, as shown in FIG. 8, bus 805 also couples computer 800 to a network 865 through a network adapter (not shown). In this manner, the computer can be a part of a network of computers (such as a local area network (“LAN”), a wide area network (“WAN”), or an Intranet) or a network of networks (such as the Internet). Any or all of the components of computer system 800 may be used in conjunction with the invention. However, one of ordinary skill in the art would appreciate that any other system configuration may also be used in conjunction with the present invention.
One of ordinary skill will realize that the above-described embodiments have numerous advantages. For instance, as described above, some embodiments provide a user with an ability to preview an asset before installing it. This ability saves the user time in deciding whether to install an asset and reduces the instances the user has to uninstall a feature that the user no longer desires. Also, some embodiments automatically install a font without requiring a user to specify a particular location for the installation.
While the invention has been described with reference to numerous specific details, one of ordinary skill in the art will recognize that the invention can be embodied in other specific forms without departing from the spirit of the invention. Thus, one of ordinary skill in the art would understand that the invention is not to be limited by the foregoing illustrative details, but rather is to be defined by the appended claims.

Claims

1-31. (canceled)

32. A computer readable medium storing a computer program comprising a user interface (“UI”) for installing an asset on a computing device, the computer program executable by at least one processor, the computer program comprising:

a set of instructions for displaying a preview of the asset in a UI display area without installing the asset on the computing device;

a set of instructions for receiving a selection of a UI item; and

a set of instructions for installing the asset on the computing device in response to the selection.

33. The computer readable medium of claim 32, wherein the preview of the asset is displayed when a user selects a file comprising information about the asset.

34. The computer readable medium of claim 33, wherein the set of instructions for installing the asset comprises a set of instructions for copying the file to a folder that includes other installed assets.

35. The computer readable medium of claim 32, wherein the asset is a font.

36. The computer readable medium of claim 32, wherein the UI item is a first UI item, wherein the computer program further comprises:

a set of instructions for receiving selection a second UI item for modifying an attribute of the asset; and

a set of instructions for displaying a preview of the asset with the attribute modified without installing the asset on the computing device.

37. The computer readable medium of claim 36, wherein the attribute is a font style or font size.

38. The computer readable medium of claim 32, wherein the computer program further comprises:

a set of instructions for determining whether the asset is installed on the computing device; and

a set of instructions for displaying a visual indication that the asset is installed on the computing device when the determination is made that the asset is installed.

39. The computer readable medium of claim 32, wherein the set of instructions for installing the asset comprises sets of instructions for:

displaying a list of locations to install the asset,

receiving identification of a location, and

installing the asset to the identified location.

40. The computer readable medium of claim 32, wherein the set of instructions for installing the asset comprises sets of instructions for:

displaying a list of accounts to install the asset,

receiving identification of an account, and

installing the asset to the identified account.

41. The computer readable medium of claim 32, wherein the asset is an asset that is not installed on the computing device.

42. A computer readable medium storing a computer program for execution by at least one processor to provide a graphical user interface (“GUI”), the GUI comprising:

a first display area for displaying a list of fonts installed on a computing device;

a second display area for displaying different collections of fonts; and

a third display area for displaying a preview of a particular font when the particular font is selected from the list of fonts displayed in the first display area.

43. The computer readable medium of claim 42, wherein the GUI further comprises a visual indication that is displayed adjacent to the particular font in the first display area when the particular font has been installed multiple times.

44. The computer readable medium of claim 42, wherein the GUI further comprises a user selectable item for disabling an installed font.

45. The computer readable medium of claim 42, wherein the first display area allows a user of the GUI to select an attribute of the particular font to modify the preview of the particular font displayed in the third display area.

46. The computer readable medium of claim 45, wherein the attribute is a font style or font size.

47. A method of installing a font on a computing device, the method comprising:

displaying a preview of the font in a UI display area without installing the font on the computing device;

receiving a selection of a UI item; and

installing the font on the computing device in response to the selection.

48. The method of claim 47, wherein the preview of the font is displayed when a user selects a file comprising information about the font.

49. The method of claim 48, wherein installing the font comprises automatically copying the file to a folder that includes other installed fonts.

50. The method of claim 47, wherein the UI item is a first UI item, the method further comprising:

receiving selection a second UI item for modifying an attribute of the font; and

displaying a preview of the font with the attribute modified without installing the font on the computing device.

51. The method of claim 47, wherein the attribute is a font style or font size.