The present invention relates generally to digital imaging, and more particularly, to a user interface of a digital imaging system.
Digital imaging systems are well known and include, for example, digital image capture devices, digital cameras, digital displays, camcorders, digital video recorders, computers, and kiosks.
Current digital cameras can connect to a host computer by means of a dock in order to transfer digital data to a computer. This digital data can include digital still images (e.g., JPEG files) as well as motion video files (e.g., Quick Time files). One example is the Kodak EasyShare DX3600 digital camera, which is sold with an optional docking unit. The camera captures digital still images and motion video segments, and stores the images using Flash EPROM memory. The still images and motion video files can be downloaded from the digital camera to the computer using the docking unit.
While such a digital camera has achieved a certain degree of success in its particular applications, there is a need for a digital imaging system which is modular, transportable, and which can be employed to share/transmit/archive/print/display digital images with or without the use of a computer.
An object of the present invention is to provide a digital imaging system which is modular, transportable, and can share digital images with or without the employment of a computer.
Another object of the present invention is to provide a user interface for such a digital imaging system.
Yet another object of the present invention is to provide a variety of modular components that can be combined by a user to form a custom product that has the appearance and function of an integrated system.
These objects are given only by way of illustrative example. Thus, other desirable objectives and advantages inherently achieved by the disclosed invention may occur or become apparent to those skilled in the art. The invention is defined by the appended claims.
According to one aspect of the invention, there is provided a method for creating a graphical user interface. The method comprises the steps of: providing a removable display device having a display for displaying digital images stored on the display device, the display device including a graphical user interface, the display device having a electrical connector; providing a functional module electrically interfaceable with the display device, the functional module providing a function and including stored data to configure the graphical user interface to control the function of the functional module from the display device; automatically transferring the stored data from the functional module to the display device when the functional module is electrically interfaced with the display device; and using the transferred data to configure the graphical user interface.
According to another aspect of the invention, there is provided a method for creating a graphical user interface. The method comprises the steps of: providing a removable display device having a display for displaying digital images stored on the display device, the display device including a graphical user interface, the display device having a electrical connector; providing a first and second functional modules, each module being electrically interfaceable with the display device, the functional modules providing different functions and each including stored data to configure the graphical user interface to control the function of the functional module from the display device; automatically transferring the stored data from the first functional module to the display device using the electrical connector when the first functional module is electrically interfaced with the display device; automatically transferring the stored data from the second functional module to the display device using the electrical connector when the second functional module is electrically interfaced with the display device; and using the transferred data from the first and second functional modules to configure the graphical user interface.
According to yet another aspect of the invention, there is provided a system for creating a graphical user interface. The system comprises: a removable display device having a display for displaying digital images stored on the display device, the display device including a graphical user interface, the display device having a electrical connector; a functional module electrically interfaceable with the display device, the functional module providing a function and including stored data to configure the graphical user interface to control the function of the functional module from the display device; means for automatically transferring the stored data from the functional module to the display device when the functional module is electrically interfaced with the display device; and means for using the transferred data to configure the graphical user interface.
The foregoing and other objects, features, and advantages of the invention will be apparent from the following more particular description of the preferred embodiments of the invention, as illustrated in the accompanying drawings.
a) through (g) shows the movement of the cover member relative to the display device.
The following is a detailed description of the preferred embodiments of the invention, reference being made to the drawings in which the same reference numerals identify the same elements of structure in each of the several figures.
Reference is also made to commonly assigned application U.S. Ser. No. 10/393,834 entitled “MODULAR DIGITAL IMAGING SYSTEM”, filed on Mar. 21, 2003 and provisionally filed on Mar. 26, 2002 in the names of Manico et al, and which is assigned to the assignee of this application.
Reference is also made to commonly assigned application U.S. Ser. No. 10/394,862 entitled “DISPLAY MODULE FOR SUPPORTING A DIGITAL IMAGE DISPLAY DEVICE”, filed on Mar. 21, 2003 and provisionally filed on Mar. 26, 2002 in the names of Manico et al, and which is assigned to the assignee of this application.
Display device 10 can comprise a cover member 17, which is shown in
Display device 10 further comprises at least one selection member 18 for selecting and manipulating (e.g., zoom, crop, delete) a digital image displayed on display 12.
It is recognized that display device 10 can be an image capture device, such as a digital camera, video recorder, or camcorder, adapted to capture digital images, sound, and motion video images in addition to displaying digital images and motion video images. If display device 10 is configured as an image capture device, display device 10 would further comprise a flash member or other illumination device 22 as well as a lens and an activation member for activating display device 10 to capture an image. Still further, it is understood that display device 10 would then further include elements employed for image capture and image processing, such as an image sensor (e.g., CCD, CMOS), analog-to-digital converter, and digital image processor. An example of a digital camera which could be employed as display device 10 is disclosed in U.S. Pat. No. 6,292,218, issued Sep. 18, 2001, titled “Electronic camera for initiating capture of still images while previewing motion images”, by Parulski et al, herein incorporated by reference.
Display device 10 can further comprise a communication port 24 for communicating with another device. Communication port 24 is shown in
Referring now to
If display module 30 is provided with electrical connector 37, display module can be configured as a power source for display device 10 or as a charger for a power supply (e.g., battery) disposed within display device 10. Additionally, display recess 62 in display module 30 may incorporate an additional connector for charging additional batteries.
Disposed within recess 36 is a communication connector (not shown) which can be matingly connected with communication port 24 of display device 10 when display device 10 is docked within display module 30. When docked, a communication network is established by connecting communication port 24 and the communication connector, thereby permitting the transfer of digital data. For example, display module 30 can comprise a modem and a telephone connector 38 (shown in
Display module 30 is one example of a module that can be employed with display device 10. Additional modules can be employed with display device 10. A compact disc (CD) module 40 is shown in
Each module is configured to have a complementary shape such that when the modules abut, a modular system is provided.
Module 60 can be a “dummy” module. That is, it can be a decorative, functional, or non-functional module. For example, it can be a storage module having a recessed area for storage for batteries, cabling, manuals, print media, memory cards, CDs, or the like. Alternatively, the dummy module may serve as a base to raise the digital imaging system to a particular height for preferred viewing by a user. Alternatively, a transformer for providing electrical power can be disposed within a dummy module.
As configured, the modules are docking docks. That is, when a module is docked with another module, a system of docks is formed. The complementary shapes of the modules provides for an interlocking arrangement of the modules, which in addition to being aesthetically pleasing, provides a physically robust digital imaging system.
The modules can be arranged in a vertical orientation, as shown in
With a modular system, the order of the modules is not relevant; any order can be employed, though in a preferred embodiment display device 10 is disposed on top for optimal viewing.
Access to the modules (e.g., 30, 40, 50, 60) is preferably in the same direction (i.e., on the same side) of digital imaging system 55, as shown in
Referring again to
As aforementioned, the order of the modules is irrelevant since they are configured to be interchangeable. Referring now to
CD module 40 comprises a plurality of support members or footers 70 disposed on a bottom side 72, as well as a female electrical connection portion 74. Disposed on a top side 75 of CD module 40 is a male electrical connection portion 76 adapted to mate with female portion 74 of an abutting module (for the particular example, display module 30, best shown in
In a preferred embodiment, attachment opening 82 and female portion 74 are protected by a cover from dust/dirt/debris when not being employed. When the module is to be docked with another module, the cover is moved to provide access to attachment opening 82 and female portion 74.
Once docked, the electrical connection of the module is made with the other modules, particularly display module 30 which provides an interface to display device 10.
In a preferred embodiment, the user interface for digital imaging system 35, 55 is not contained with module 40, 50, 60. Rather, user control would be provided by display device 10 or display module 30. Accordingly, each time a module 40, 50, 60 is docked, software for the module would be uploaded or accessed by display device 10 or display module 30. This software may be uploaded from firmware within the modules or via the communications link 38 or via the removable digital memory device 16. As such, a cumulative user interface is provided. The user interface can be designed with a consistent look and feel for all modules added to the system.
Further, with such an arrangement, the user interface of digital imaging system 35, 55 could be changed/modified by changing a display/screen of display device 10. That is, different features could be accessible or not accessible depending on the display/screen of display device 10. For example, for a new user of a digital camera, a limited feature set could be provided whereas for a professional photographer, a more advanced feature set could be provided. In another example, display device 10 provides zoom and crop features only when a particular display/screen is used.
With the modules docked, the modules can be monitored and managed. For example, power management can be monitored, and power shifted to different modules as required. For example, printing images may be suspended during the time a CD is being written. In another example, memory can be shared between modules as required for example for queuing a large number of images or long segment of video.
Display module 30 can comprise more than one support member 34 to accommodate more than one display device 10. For example, it may be desired to charge more than one display device 10 at one time. Indeed, support member 34 (i.e., display module 30) can be configured to accept/receive more than one type/model of display device. Additionally, display devices 10 may be able to share data when connected to display module 30.
When display device 10 is docked within support member 34 of display module 30, CD module 40 can be configured to automatically download to a CD all new images stored on digital storage device 16 or newly transmitted images to display device 10 by means of a communication network. Printer module 50 can be likewise configured so that new images are automatically printed. The modules may store the filenames or other identification of digital data files that have been stored or printed so as to facilitate the identification of new digital data files for storage or printing. This technique may also be used for sharing images by means of the communications link 38.
As shown in
Referring now to
If display device 10 is a digital camera (i.e., is adapted to capture images), then cover member 17 would be positioned as shown in
As such, cover member 17 has three positions for three modes of operation: a camera mode (shown in
Referring now to
Hinged mechanism 90 provides for the movement of cover member 17 between the three modes.
Cover member 17 may comprise a coating on one or more sides. For example, as shown in
Materials which are suitable for use as coating 95 are known to those skilled in the art, and can comprise polymers, non-slip polymers, rubber materials, polyurethane materials, non-transfer adhesives.
a) through (g) provide another illustration of the movement of cover member 17 relative to display 12, and positioning display device 10 into the three modes of operation.
Cover member 17 is shown as being opaque, such as being comprised of a metal or rigid plastic. However, portions of or all of cover member 17 may be transparent, whereby display 12 would be visible when cover member 17 is disposed in front of display 12. For example,
The position of cover member 17 can automatically provide the mode of operation of display device 10. That is, automatic mode detection can be determined by the position of cover member 17. For example, moving cover member 17 to the camera mode would automatically activate the power of display device 10. Similarly, when cover member 17 is moved to the closed mode, display device 10 may be automatically powered down. Likewise, when cover member 17 is moved to the closed mode, other features of display device 10 may automatically powered down or moved/rotated to a “closed/off” position. For example, flash member 22 (shown in
Other arrangements for hinged mechanism 90 may be known to those skilled in the art. For example,
It is noted that the electrical connection between display module 30 and the other functional modules (e.g., CD module 40, printer module 50) provides an electrical interface between all the devices. Therefore, the display device 10 is electrically interfaceable with all the functional modules, including CD module 40 and printer module 50 even though the electrical connector 99 on display device 10 does not physically mate/contact/connect to the modules.
Those skilled in the art will recognize that other types of clutches can be employed, for example, pressure clutches, magnetic clutches, friction clutches, and interference fit.
As indicated above, a cumulative user interface can be generated for the system. This cumulative user interface can control, from display device 10, all the various configurations that can be formed from stacking the different modules in different orders.
In a preferred embodiment, the cumulative graphical user interface is developed using a user interface design tool (for example, the tool called UiMagi, as described below) that uses a simple script-like language for producing various file system streams that describes the graphical user interface which controls the functions of the various modules. Each of the modules stores a file system stream to control the function of that module. When modules are “docked” (i.e., stacked, mated) with the display device, the file system stream data is automatically transferred to the display device from the module, for example by means of electrical connector 99. The display device then employs a runtime engine (for example, the engine called Chimera, further described below) that uses the file system stream data from the various modules to provide a graphical user interface to control the module(s).
The tool called UiMagi and the engine called Chimera are more particularly described in commonly assigned provisional application Ser. No. 60/358,815 filed on Feb. 22, 2002 and perfected as U.S. Ser. No. 10/368,171, titled “SYSTEM AND METHOD FOR CREATING GRAPHICAL USER INTERFACES” on Feb. 18, 2003 in the names of Belz et al, herein incorporated by reference.
Using Chimera allows the GUI of display device 10 to be readily changed upon the docking of additional modules. To accomplish this, Chimera provides mechanisms to create dynamically bound user interface elements to other user interface elements.
Similarly, data stream 1012 is stored in printer module memory 1022 within printer module 50 and controls the normal operation of printer module 50 by providing data to configure the graphical user interface of display device 10 to control the function of printer module 50 from display device 10 when printer module 50 is stacked/docked with display device 10.
Likewise, data stream 1014 is stored in CD module memory 1024 within CD module 40 and controls the normal operation of CD module 40 by providing data to configure the graphical user interface of display device 10 to control the function of CD module 40 from display device 10 when CD module 40 is stacked/docked with display device 10.
As indicated above, other modules can be employed. As such, data stream 1016 is stored in other module memory 1026 within the other module and controls the normal operation of the other module by providing data to configure the graphical user interface of display device 10 to control the function of the other module from display device 10 when the other module is stacked/docked with display device 10.
Referring to
An adapter layer 1056 is provided in conjunction with Chimera runtime engine 1046 in such a way that it can be bound to the user-interface as encoded in the interface definition files. Widgets 1052 can also bind to resources in Chimera file system stream as well as other widgets, again as specified by the interface definition files. Chimera loader 1048 is responsible for switching interfaces as various functional modules are docked/stacked/mated, providing access to resources available in the data streams 1010-1016 and binding data and events using Chimera binding mechanisms 1058.
UiMagi 1040 is a host-based tool that allows a non-technical person to act as a GUI designer to create embedded GUIs graphically on a host computer. The design can then be exported in a platform specific format to be deployed on display device 10 without further involvement from the embedded software developer. UiMagi 1040 uses Platform Definition Files (PDF) 1060 to tailor the editing process for the type of microprocessor used in the specific display device 10. PDFs 1060 describe the characteristics of the particular microprocessor using a simple, ASCII text based language called the Platform Definition Language (bv, not shown). The PDF is maintained by the embedded GUI developer 1022 and thus guarantees that the resulting data streams 1010-1016 from UiMagi 1040 will be compatible with the microprocessor within display device 10 when the cumulative user interface is rendered.
A Platform Export Module 1061 (PEM) converts platform independent designs to a platform specific format. UiMagi is modular and only contains the core functionality needed to provide graphical editing of user interfaces. It utilizes this PEM to generate platform specific format that can be used by the Chimera runtime engine 1046 on display device 10.
Chimera runtime engine 1046 uses data streams 1010-1016 to dynamically instantiate and present the user interfaces created with UiMagi. The data streams 1010-1016 store a variety of resources, which include the Chimera Definition Files (CDFs) that describe individual interfaces.
UiMagi generates the CDFs (one of the intermediate files 1062) that contain the complete specification of the components that make up specific user interfaces. This includes the definition of the widgets that need to be created and the platform specific functionality that they bind to. Chimera runtime engine 1046 employs dynamic binding mechanisms to tie together the GUI to the rest of the device platform. The CDF also contains references to graphics, fonts and other resources that are provided to the runtime engine by Chimera file stream. This promotes modularity and allows each of these components (graphics, fonts, sound, etc.) to be changed independently of each other. In one embodiment, an x86/Win32 form of Chimera is used by UiMagi tool as an emulator and debugger for interfaces.
A computer program product may include one or more storage medium, for example; magnetic storage media such as magnetic disk (such as a floppy disk) or magnetic tape; optical storage media such as optical disk, optical tape, or machine readable bar code; solid-state electronic storage devices such as random access memory (RAM), or read-only memory (ROM); or any other physical device or media employed to store a computer program having instructions for controlling one or more computers to practice the method according to the present invention.
The invention has been described in detail with particular reference to a presently preferred embodiment, but it will be understood that variations and modifications can be effected within the spirit and scope of the invention. The presently disclosed embodiments are therefore considered in all respects to be illustrative and not restrictive. The scope of the invention is indicated by the appended claims, and all changes that come within the meaning and range of equivalents thereof are intended to be embraced therein.
Priority is claimed from Provisional Application U.S. Ser. No. 60,367,586 filed on Mar. 26, 2002, entitled “MODULAR DIGITAL IMAGING SYSTEM”.
| Number | Name | Date | Kind |
|---|---|---|---|
| 4642678 | Cok | Feb 1987 | A |
| 5396264 | Falcone et al. | Mar 1995 | A |
| 5477264 | Sarbadhikari et al. | Dec 1995 | A |
| 5887165 | Martel et al. | Mar 1999 | A |
| 5905486 | Brittenham et al. | May 1999 | A |
| 5999213 | Tsushima et al. | Dec 1999 | A |
| 6012083 | Savitzky et al. | Jan 2000 | A |
| 6023587 | Watts et al. | Feb 2000 | A |
| 6137686 | Saye | Oct 2000 | A |
| 6141221 | Tong et al. | Oct 2000 | A |
| 6144888 | Lucas et al. | Nov 2000 | A |
| 6179489 | So et al. | Jan 2001 | B1 |
| 6275882 | Cheever et al. | Aug 2001 | B1 |
| 6292218 | Parulski et al. | Sep 2001 | B1 |
| 6300976 | Fukuoka | Oct 2001 | B1 |
| 6310648 | Miller et al. | Oct 2001 | B1 |
| 6337712 | Shiota et al. | Jan 2002 | B1 |
| 6470413 | Ogawa | Oct 2002 | B1 |
| 6505087 | Lucas et al. | Jan 2003 | B1 |
| 6587129 | Lavendel et al. | Jul 2003 | B1 |
| 6608650 | Torres et al. | Aug 2003 | B1 |
| 6661648 | Dayley | Dec 2003 | B2 |
| 6700592 | Kou et al. | Mar 2004 | B1 |
| 6734915 | Nagaoka | May 2004 | B2 |
| 6738091 | Eouzan et al. | May 2004 | B1 |
| 6750902 | Steinberg et al. | Jun 2004 | B1 |
| 6774885 | Even-Zohar | Aug 2004 | B1 |
| 6774935 | Morimoto et al. | Aug 2004 | B1 |
| 6795318 | Haas et al. | Sep 2004 | B2 |
| 6819355 | Niikawa | Nov 2004 | B1 |
| 6833867 | Anderson | Dec 2004 | B1 |
| 6886056 | Ohmura | Apr 2005 | B2 |
| 6944700 | Bateman et al. | Sep 2005 | B2 |
| 6980234 | Kitawaki | Dec 2005 | B2 |
| 7039876 | Lavendel et al. | May 2006 | B2 |
| 7050042 | Watanabe | May 2006 | B2 |
| 7073124 | Suetsugu et al. | Jul 2006 | B1 |
| 7119835 | Gennetten et al. | Oct 2006 | B2 |
| 7301561 | Ohmura | Nov 2007 | B2 |
| 20010034803 | Sorek et al. | Oct 2001 | A1 |
| 20020064255 | Mohammadian et al. | May 2002 | A1 |
| 20020071035 | Sobol | Jun 2002 | A1 |
| 20020101534 | Liu | Aug 2002 | A1 |
| 20020149695 | Kayanuma | Oct 2002 | A1 |
| 20030038880 | No | Feb 2003 | A1 |
| 20030117499 | Bianchi et al. | Jun 2003 | A1 |
| 20030149816 | Poo et al. | Aug 2003 | A1 |
| 20030160822 | Belz et al. | Aug 2003 | A1 |
| 20030160890 | Caspe et al. | Aug 2003 | A1 |
| 20030174813 | Mohammadian et al. | Sep 2003 | A1 |
| 20030185302 | Abrams, Jr. | Oct 2003 | A1 |
| 20040004737 | Kahn et al. | Jan 2004 | A1 |
| 20040061783 | Choi et al. | Apr 2004 | A1 |
| 20040141066 | Ohmori et al. | Jul 2004 | A1 |
| 20040201680 | Gennetten et al. | Oct 2004 | A1 |
| 20040201774 | Gennetten | Oct 2004 | A1 |
| 20040208293 | Mohammadian et al. | Oct 2004 | A1 |
| 20040259499 | Oba et al. | Dec 2004 | A1 |
| 20050275729 | Billerbeck | Dec 2005 | A1 |
| 20060010374 | Corrington et al. | Jan 2006 | A1 |
| 20060066753 | Gennetten et al. | Mar 2006 | A1 |
| 20060070108 | Renkis | Mar 2006 | A1 |
| 20060116787 | Etter et al. | Jun 2006 | A1 |
| Number | Date | Country | |
|---|---|---|---|
| 20030202013 A1 | Oct 2003 | US |
| Number | Date | Country | |
|---|---|---|---|
| 60367586 | Mar 2002 | US |