Abstract:
Disclosed herein is a data processing apparatus capable of controlling a peripheral device by using a driver program. The data processing apparatus comprises: an input device adapted to input a switch designation of the driver program; an acquisition device adapted to acquire data including specification information settable in a driver program of an original device before being switched and data including specification information settable in a driver program of a destination device to be switched to, based on the switch designation inputted by the input device; and a generation device adapted to generate setting information interpretable by an application program based on the specification information acquired by the acquisition device, method and program product for the data processing apparatus

Description:
FIELD THE INVENTION  
         [0001]    The present invention relates to a data processing apparatus, data processing method, program, and storage medium.  
         BACKGROUND OF THE INVENTION  
         [0002]    Data processing apparatuses using a driver program for controlling peripheral devices, e.g., printers, digital cameras, scanners or the like, have conventionally been known. Such data processing apparatuses are capable of setting up various configuration settings related to the peripheral devices by using the driver program.  
           [0003]    However, in the conventional data processing apparatuses, when a driver program is switched, unconditionally a partial setting only is inherited. Therefore, for those settings that are not inherited, a user must set up again.  
           [0004]    In general, a printer driver which is familiar with the data structure of DevMode can interpret the DevMode. However, an application program cannot refer to contents of a printer-native setting.  
           [0005]    For instance, in a case where a data processing apparatus, e.g., a computer, switches a printer for outputting an image, the print setting of the printer driver in the so-called public area only is inherited, and other settings that cannot be interpreted by the application program are reset to a default setting. In other words, conventionally in a case where a user performs print setting for a certain printer and thereafter changes an output destination to a different printer, the print setting, e.g., a layout, is not inherited except a specified setting, so that the user must perform setting again, causing poor usability.  
           [0006]    Furthermore, because print settings often include data or commands that depend upon a printer, it has been unable to come up with a usage pattern of a print setting that is applicable to a plurality of printers.  
         SUMMARY OF THE INVENTION  
         [0007]    The present invention has been proposed to solve at least one of the above-described problems of the conventional art, and has as its one of the features to provide a user-friendly data processing apparatus, data processing method, program, and storage medium.  
           [0008]    According to an aspect of the present invention, the present invention provides a data processing apparatus, capable of controlling a peripheral device by using a driver program, a method applicable to this apparatus, and a program product. The data processing apparatus comprises: an input device inputting a switch designation of the driver program; an acquisition device acquiring data which includes specification information settable in a driver program of an original device before being switched and data which includes specification information settable in a driver program of a destination device to be switched to, based on the switch designation inputted by the input device; and a generation device generating setting information interpretable by an application program based on the specification information acquired by the acquisition device.  
           [0009]    Other features and advantages of the present invention will be apparent from the following description taken in conjunction with the accompanying drawings, in which like reference characters designate the same or similar parts throughout the figures thereof. 
       
    
    
     BRIEF DESCRIPTION OF THE DRAWINGS  
       [0010]    The accompanying drawings, which are incorporated in and constitute a part of the specification, illustrate embodiments of the invention and, together with the description, serve to explain the principles of the invention.  
         [0011]    [0011]FIG. 1 is a block diagram showing a system construction which includes a computer provided as an embodiment of the present invention;  
         [0012]    [0012]FIG. 2 is a block diagram describing a typical print data generation method in the computer provided as an embodiment of the present invention;  
         [0013]    [0013]FIG. 3 shows an example of user interfaces provided respectively for performing printer selection and printer setting in the computer provided as an embodiment of the present invention;  
         [0014]    [0014]FIG. 4 shows a relation between an application program and printer drivers of respective printers in the computer provided as an embodiment of the present invention;  
         [0015]    [0015]FIG. 5 is a diagrammatic view showing a construction of a DevMode storing a print setting in the computer provided as an embodiment of the present invention;  
         [0016]    [0016]FIG. 6 is a flowchart describing conversion processing of the DevMode to XML data in the computer provided as an embodiment of the present invention;  
         [0017]    [0017]FIG. 7 is an example of an XML file obtained by converting the DevMode to XML data in the computer provided as an embodiment of the present invention;  
         [0018]    [0018]FIG. 8 is a flowchart showing merging processing of the DevMode in the computer provided as an embodiment of the present invention;  
         [0019]    [0019]FIG. 9 is a flowchart showing merging processing of a Private area of the DevMode in the computer provided as an embodiment of the present invention;  
         [0020]    [0020]FIG. 10 is a flowchart showing print setting processing of an application program using the DevMode in the XML format, in the computer provided as an embodiment of the present invention;  
         [0021]    [0021]FIG. 11 shows an example of a user interface (UI) for print setting processing of an application program using the DevMode in the XML format, in the computer provided as an embodiment of the present invention;  
         [0022]    [0022]FIG. 12 is a flowchart showing a processing performed by a printer driver in the print setting processing of the application program using the DevMode in the XML format, in the computer provided as an embodiment of the present invention;  
         [0023]    [0023]FIG. 13 is a flowchart showing processing of the DevMode in the computer provided as an embodiment of the present invention; and  
         [0024]    [0024]FIG. 14 is a flowchart showing merging processing of the DevMode in the computer provided as an embodiment of the present invention.  
     
    
     DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS  
       [0025]    Preferred embodiments of the present invention will now be described in detail in accordance with the accompanying drawings. Note that the scope of the present invention is not limited to relative arrangements of the components and display screens provided in this embodiment, unless there is a specific description.  
         [0026]    Hereinafter, a computer provided as an embodiment of a data processing apparatus according to the present invention is described. FIG. 1 is a block diagram showing a construction of a printer control system including the computer provided as the embodiment of the present invention. Note that unless specified otherwise, the present invention is applicable to a single device, a system comprising plural devices, or a system performing processing through a network, such as a LAN or WAN or the like, as long as functions according to the present invention are realized.  
         [0027]    Referring to FIG. 1, reference numeral  3000  denotes a host computer which includes a CPU  1  for executing processing of a document including graphics, images, characters, and tables (including spreadsheets or the like), based on a document processing program stored in a program ROM of the ROM  3  or an external memory  11 . The CPU  1  integrally controls each of the devices connected to a system bus  4 .  
         [0028]    The program ROM of the ROM  3  or the external memory  11  stores an operating system program (hereinafter referred to as an OS), serving as a control program of the CPU  1 . The font ROM of the ROM  3  or the external memory  11  stores font data and so forth used for the aforementioned document processing. The data ROM of the ROM  3  or the external memory  11  stores various data used for the aforementioned document processing.  
         [0029]    Reference numeral  2  denotes RAM serving as a main memory and work area of the CPU  1 . Reference numeral  5  denotes a keyboard controller (KBC) which controls key inputs from a keyboard  9  and a pointing device (not shown). Reference numeral  6  denotes a CRT controller (CRTC) which controls displaying operation of a CRT display device (CRT)  10 . Reference numeral  7  denotes a disk controller (DKC) which controls accessing the external memory  11 , e.g., hard disk (HD), floppy disk (FD) or the like, that stores a boot program, various application programs, font data, user file, edited file, print control command generation program (hereinafter referred to as a printer driver) and so on.  
         [0030]    Reference numeral  8  denotes a printer controller (PRTC) connected to a printer  1500  through a predetermined bi-directional interface unit  21  to execute communication control processing to communicate with the printer  1500 . Note that the CPU  1  executes developing (rasterizing) of an outline font in, for instance, a display data RAM set in the RAM  2 , realizing WYSIWYG on the CRT  10 .  
         [0031]    Furthermore, the CPU  1  opens various registered windows based on a command instructed by a mouse/cursor or the like (not shown) on the CRT  10  and executes various data processing. When printing is to be executed, a user can open a window related to print setting to set up a print configuration or set up a printing processing method including selection of a print mode, to be designated to a printer driver.  
         [0032]    In the printer  1500 , reference numeral  12  denotes a printer CPU, which outputs image signals as output data to a printing unit (printer engine)  17 , connected to a system bus  15 , based on a control program stored in a program ROM of ROM  13  or an external memory  14 .  
         [0033]    The program ROM of the ROM  13  stores a control program of the CPU  12 . The font ROM of the ROM  13  stores font data and so forth used to generate the aforementioned output data. The data ROM of the ROM  13  stores data used by the host computer, in a case where a printer does not have the external memory  14 , e.g., hard disk or the like.  
         [0034]    The CPU  12  is capable of communicating with the host computer through an input unit  18 , so that information in the printer can be informed to the host computer  3000 . Reference numeral  19  denotes RAM serving as a main memory and work area of the CPU  12 . The memory capacity of the RAM can be expanded by an optional RAM connected to an add-on port (not shown). Note that the RAM  19  is used as an output data rasterizing area, environmental data storage area, NVRAM or the like. The aforementioned hard disk (HD) and external memory  14 , such as an IC card or the like, are access-controlled by a memory controller (MC)  20 .  
         [0035]    The external memory  14 , connected as an option, stores font data, an emulation program, form data, and so forth. The input unit  18  comprises a switch for operating the aforementioned operation panel and an LED indicator. The aforementioned external memory is not limited to one, but one or more external memories may be provided. Thus, plural external memories may be connected to store an optional font card in addition to the font data already stored, and a program for interpreting a printer control language of different language systems. Moreover, NVRAM may be provided to store printer mode setting data set on an operation panel  1501 .  
         [0036]    [0036]FIG. 2 is a block diagram describing a typical print data generation method in the host computer.  
         [0037]    An application program  201 , graphic engine  202 , printer driver  203 , and system spooler  204  are stored as files in the external memory  11 . They are program modules, loaded to the RAM  2  by an OS or a module utilizing the OS, and executed. The application program  201  and printer driver  203  can be added to the HD of the external memory  11  through the FD of the external memory  11 , CD-ROM (not shown), or a network (not shown).  
         [0038]    The application program  201  stored in the external memory  11  is loaded to the RAM  2  and executed. When a printing command is sent from the application program  201  to the printer  1500 , the graphic engine  202  that has been similarly loaded to the RAM  2  and being executable is used to perform output (rendering) operation. The graphic engine  202  loads the printer driver  203 , provided for each printer, from the external memory  11  to the RAM  2 , and converts data outputted from the application program  201  to a printer control command by using the printer driver  203 . The printer control command is outputted to the printer  1500  through the system spooler  204 , loaded to the RAM  2  by the OS, and through the interface unit  21 .  
         [0039]    [0039]FIG. 3 shows an example of a user interface for selecting an arbitrary printer from plural printers registered in the system, and a user interface for setting up a print configuration of the selected printer. In this example, a print dialogue box  301  is a user interface provided by an operating system. Printers registered in the operating system are listed in the portion indicated by an oval in FIG. 3, and a user can select an arbitrary printer. By clicking a property button, a printer driver corresponding to the selected printer is called, and the printer driver opens a user interface  302  for performing print setting of the printer.  
         [0040]    [0040]FIG. 4 is a diagrammatic view showing a relation between an application program and printer drivers of respective printers. The application program calls various functions (API) provided by the operating system to perform processing, while the operating system calls a. function (DDI) provided by the printer driver of the selected printer to perform processing related to printing. Accordingly, printing is performed by the printer selected by the application program.  
         [0041]    [0041]FIG. 5 is a diagrammatic view showing a construction of a memory block (hereinafter referred to as DevMode), storing a print setting of the printer exchanged among the printer driver, operating system and application program shown in FIG. 4.  
         [0042]    The DevMode is constructed with a Public area, serving as a memory block defined by the operating system, and a Private area, serving as a memory block defined uniquely by each printer driver. Setting the Public area, which is defined by the operating system, can be performed by any of the application program, operating system, and printer driver. The private area, which is defined by each printer driver, stores a preferred example of printer-native setting information, and setting the Private area can be performed only by a printer driver. The size of the Private area is different for each printer driver. The Public area has a member called ExtraSize for storing the size of the Private area, so that determination of the entire size of the DevMode is possible. The operating system inquires the printer driver of the area size of the DevMode. Then, the application program or operating system secures the size of the area, and the printer driver performs initializing and setting of the area. When printing is to be executed, the printer driver performs printing in accordance with the setting of this area.  
         [0043]    Note that there is a printer driver which supports plural types of printers by one program module. In this case, the definition of the Private area does not change even if the type of printer changes.  
         [0044]    According to the present embodiment, the PrinterName storing a registration name of a printer registered in the system, and ExtraSize storing the size of the Private area are defined in the Public area. The DeviceName storing the type of printer, Nup storing a Nup print setting where printing is performed by allocating plural logical pages to one physical page, and stamp storing a stamp setting are defined in the Private area.  
         [0045]    [0045]FIG. 6 is a flowchart describing conversion processing of a content of the DevMode to XML-format data. This processing is performed when the setting of the DevMode is changed or a printer driver is added. First, when a setting content of the DevMode is changed in a printer property (S 601 ), the printer driver reads the DevMode and develops it in the memory (S 602 ). Then, the printer driver converts the DevMode developed in the memory to XML-format data, and stores it in a file (S 603 ). According to this process, the setting content of the DevMode is stored as XML-format data.  
         [0046]    [0046]FIG. 7 is an example of an XML file obtained by developing the DevMode according to the processing shown in FIG. 6. The upper portion of the program shown in FIG. 7 is a Document Type Definition (DTD) which is a preferred example of specification information that can be set in a driver program. The lower portion of the program in FIG. 7 shows XML data stored respectively in the Public area and Private area. As described above, the data structure of the setting information is described in the XML language having a text format, which is an example of a form interpretable by an application program or humans. Accordingly, the DevMode serving as print setting information can be utilized in various forms.  
         [0047]    [0047]FIG. 8 is a flowchart showing processing of the operating system calling the printer driver, so that when a printer is switched, a print setting of an original printer before being switched (hereinafter referred to as the original printer) is merged and reflected to a destination printer to be switched to (hereinafter referred to as the destination printer).  
         [0048]    The merging processing of the DevMode according to the present embodiment is described with reference to FIG. 8.  
         [0049]    When a printer-switch operation is performed (S 801 ), the printer driver of the destination printer acquires XML data of the original printer as well as the DTD which is a preferred example of specification information that can be set in the printer (S 802 ). Next, based on the DTD acquired in step S 802 , it is determined whether or not the content of the XML data is valid (S 803 ). If it is determined that the XML data is valid, the control proceeds to the next step; whereas if it is determined that the data is not valid, the control ends.  
         [0050]    Next, the XML data and DTD of the destination printer are acquired (S 804 ). Consistency of the XML data is determined as similar to step S 803  (S 805 ). If it is determined that the XML data is valid, the control proceeds to step S 806 ; otherwise, the control ends.  
         [0051]    By utilizing the XML data acquired in steps S 802  and S 805 , the setting in the Public area included in the XML data of the original printer is merged to the XML data of the destination printer (S 806 ).  
         [0052]    Next, the setting of the Private area is merged (S 807 ). This processing will be described in detail with reference to FIG. 9.  
         [0053]    [0053]FIG. 9 is a flowchart showing the merging processing of a Private area in step S 807 . First, the XML data of the original printer is compared with XML data of the destination printer to search the same element in the private area (S 901 ). Then, it is determined whether or not the same element is found in the search in step S 901  (S 902 ). If the same element is found, whether or not the content of the searched element is valid is determined by referring to the DTD of the destination printer acquired in step S 804  (S 903 ). When it is determined that the data is valid, the setting content of the original printer is merged to the XML data of the destination printer (S 904 ), and the control proceeds to the next step. Next, it is determined whether or not the search in step S 901  is performed until the end of the file (S 905 ). If YES, the control ends. If NO, the control returns to step S 901  to search the same element. Meanwhile, if it is determined that the data is not valid in step S 903 , the control proceeds to the next step without merging processing, and then it is determined whether or not the search in step S 901  is performed until the end of the file.  
         [0054]    When the merging processing of the Private area shown in FIG. 9 is completed, the merged XML data of the destination printer is converted to the DevMode (S 808 ), and the control ends. In this state, if there is a setting item provided by the XML data of the destination printer but not provided by the XML data of the original printer, a default value is set.  
         [0055]    According to the foregoing processing, in a case where a printer is switched for print execution, even if the type of printer is different before and after the switch, all the setting information that can be merged is inherited by the destination printer.  
         [0056]    [0056]FIG. 10 is a flowchart showing processing of an application program, which performs print setting based on the XML data converted from the DevMode by utilizing a unique user interface (UI), but not utilizing a UI function of the printer driver, and executes printing.  
         [0057]    The processing shown in FIG. 10 is described. The application program acquires XML data and DTD of the destination printer where the DevMode is converted as described in FIG. 6 (S 1001 ). It is determined whether or not the content of the acquired XML data is valid by referring to the DTD (S 1002 ). If it is determined that the data is valid, the control proceeds to the next step; whereas if it is determined that the data is not valid, the control ends. Next, the acquired XML data is developed in the memory, and the user interface unique to the application program, such as the example shown in FIG. 11, is displayed (S 1004 ) by referring to the content of the DevMode, including the Private area, described in XML data. Print setting is performed by using the displayed user interface (S 1005 ) . Referring to FIG. 11, a combo box indicative of a page layout is displayed in the area  1101  of the window  1100 , and a combo box indicative of a stamp is displayed in the area  1102 . When the OK button  1103  in FIG. 11 is clicked, the content set in step S 1005  is merged to the XML data of the destination printer (S 1006 ), and printing is executed (S 1007 ).  
         [0058]    [0058]FIG. 12 is a flowchart showing processing of the printer-driver side after printing is executed in step S 1007  in FIG. 10. Hereinafter, this processing is described. First, XML data and DTD of the destination printer are acquired (S 1201 ), and consistency of the XML data is determined based on the DTD (S 1202 ). If it is determined that the acquired XML data is valid in step S 1202 , the control proceeds to the next step; whereas if it is determined that the XML data is not valid, the control ends. Next, the acquired XML data is developed in the memory and converted to the DevMode (S 1203 ). Then, print processing is executed by utilizing the converted DevMode (S 1204 ).  
         [0059]    As described above, by converting the DevMode in a versatile data format like XML data, an application program can refer to the content stored in the Private area of the DevMode. Accordingly, items displayed in the user interface can be freely customized without utilizing the UI function of the printer driver.  
         [0060]    As a matter of course, the converted XML data may be transmitted from the computer  3000  to an external computer (not shown) to have the computer similarly execute the processing shown in FIG. 10 for displaying the screen shown in FIG. 11. Accordingly, the XML data can be used by various apparatuses.  
         [0061]    Furthermore, with regard to conversion processing of print setting data, the following embodiment may be considered. There are printer drivers in which one program module supports plural types of printers. In this case, the definition of the Private area is the same even if the type of printer is different.  
         [0062]    According to the present embodiment, the PrinterName storing a registration name of a printer registered in the system, and ExtraSize storing the size of the Private area are defined in the Public area. The DrvFamName storing a key for identifying a printer driver, DeviceName storing the type of printer, Nup storing a Nup print setting where printing is performed by allocating plural logical pages to one physical page, and stamp storing a stamp setting are defined in the Private area. For the same type of printer driver, that is, a driver constructed with the same program module, the same key is set in the DrvFamName even if the type of printer is different.  
         [0063]    [0063]FIG. 13 is a flowchart showing processing performed when an operating system calls a printer driver, so that when a printer is switched, a print setting of an original printer is reflected (merged) to a print setting of a destination printer.  
         [0064]    This processing is realized by the operating system transferring the DevMode area of the printer driver for the original printer and the DevMode area of the printer driver for the destination printer to the printer driver of the destination printer. The printer driver of the destination printer receives the memory area of the DevMode including a setting of the printer driver of the original printer and the memory area of the DevMode of the destination printer, and merges the setting of the printer driver of the original printer in the DevMode into the memory area of the DevMode of the destination printer.  
         [0065]    First, with respect to the Public area, the setting of the DevMode is merged (S 1302 ). Next, it is determined whether or not the ExtraSize of the Public area is the same (S 1303 ). If the ExtraSize is the same, it is determined whether or not the DrvFamName is the same (S 1304 ). If the ExtraSize or DrvFamName is not the same, it is determined to be a different program module from the printer driver of the original printer. In this case, since the setting of the Private area is unknown, a default setting is set in the Private area, and merging processing of the Private area is not performed (S 1311 ). If the ExtraSize and DrvFamName are the same in steps S 1303  and S 1304 , it is determined to be the same program module as the printer driver of the original printer. Then, merging processing of the Private area is performed (S 1310 ), and the control ends.  
         [0066]    [0066]FIG. 14 is a flowchart showing another example of merging processing of the Private area performed in step S 1310 . Merging processing of the Private area is described with reference to FIG. 14. First it is determined whether or not a Nup setting of the original DevMode is settable (S 1410 ). If YES, setting of the Nup is merged (S 1420 ), but if NO, a default setting is set in the Nup (S 1421 ). Next, it is determined whether or not a setting of the stamp in the original DevMode can be merged (S 1430 ). If YES, the setting of the stamp is merged (S 1440 ), but if NO, a default setting is set (S 1441 ). In the similar manner, it is determined whether or not other settings of the original DevMode stored in the Private area are settable, and each setting is merged (S 1450 ).  
         [0067]    According to the processing shown in FIGS. 13 and 14, in a case where a printer is switched at the time of print execution, as long as the printer drivers of the printers before and after the switch are the same module, all the mergeable settings are inherited even if the type of printer is not the same before and after the switch.  
         [0068]    Although the above description has been provided specifically on the printer driver, the present invention is not limited to this, but is applicable to a data processing apparatus having all types of drivers used for controlling peripheral devices.  
         [0069]    Note that the data processing apparatus according to the present invention is not limited to a computer, but includes all types of apparatuses, e.g., digital cameras, printers and so on, that can control drivers. Furthermore, the data processing method according to the present invention is applicable to a system constituted by a plurality of devices (e.g., host computer, interface unit, reader, and printer).  
         [0070]    Further, the present invention can be realized by providing a storage medium, storing program codes of software realizing the above-described functions of the embodiment, to a system or a computer (CPU or MPU) of an apparatus, reading the program codes stored in the storage medium by the system or computer of the apparatus, and executing the program.  
         [0071]    In this case, the program codes read from the storage medium realize the functions according to the above-described embodiment, and the storage medium storing the program codes constitutes the invention.  
         [0072]    The storage medium, such as a floppy disk, hard disk, optical disk, magneto-optical disk, CD-ROM, CD-R, a magnetic tape, a non-volatile type memory card, and ROM can be used for providing the program codes.  
         [0073]    Furthermore, besides aforesaid functions according to the above embodiment are realized by executing the program codes which are read by a computer, the present invention includes a case where an OS (operating system) or the like working on the computer performs a part or the entire processes in accordance with designations of the program codes and realizes the functions according to the above embodiment.  
         [0074]    Furthermore, the present invention also includes a case where, after the program codes read from the storage medium are written in a function expansion card which is inserted into the computer or in a memory provided in a function expansion unit which is connected to the computer, a CPU or the like contained in the function expansion card or unit performs a part or the entire process in accordance with designations of the program codes and realizes the functions of the above embodiment.  
         [0075]    In a case where the present invention is applied to the aforesaid storage medium, the storage medium stores program codes corresponding to the above-described flowcharts.  
         [0076]    As many apparently widely different embodiments of the present invention can be made without departing from the spirit and scope thereof, it is to be understood that the invention is not limited to the specific embodiments thereof except as defined in the claims.