JP2008147961A - Image forming apparatus, screen managing method and screen management program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide an image forming apparatus capable of simplifying the customization work of a display screen of an operation panel, a screen managing method and a screen management program. <P>SOLUTION: The image forming apparatus 1 provided with an operation panel comprises: a configuration information managing means for managing the configuration information of a display component arranged on a display screen and the arrangement information of the display component on the display screen in each display screen displayed on the operation panel; a display component managing means for managing display component data in each display component; a display control means for acquiring configuration information and arrangement information corresponding to a display screen made to be a display target and display component data of the display component defined in the configuration information and displaying the display screen by arranging the acquired display component on the basis of the arrangement information; and an editing means for changing at least configuration information corresponding to a display screen to be an editing target in accordance with an input of an editing instruction of the display screen. <P>COPYRIGHT: (C)2008,JPO&INPIT

Description

  The present invention relates to an image forming apparatus, a screen management method, and a screen management program, and more particularly to an image forming apparatus including an operation panel, a screen management method for the operation panel, and a screen management program.

  In recent years, a liquid crystal panel (touch panel) on an operation panel of a digital copying machine or a multi-function machine has been increased in size, and the display content has been enhanced. For example, a user-friendly user interface is provided by displaying various display screens using icons or the like based on control of software (hereinafter referred to as “display software”) (for example, Patent Document 1). ).

With the enhancement of the display content of the liquid crystal panel, there is an increasing demand for different display screens depending on the user's authority and preferences. In some cases, it is necessary to add a screen or the like corresponding to a newly added function as a function is enhanced.
JP-A-11-174910

  However, conventionally, the display content of the display screen has been incorporated as logic of the display software, so that the source code of the display software has to be modified to customize the display content. Even if the display content can be customized for each user, the range of customization is limited to the range of fixed options built into the display software, and there is a problem of lack of flexibility in customization. was there.

  SUMMARY An advantage of some aspects of the invention is that it provides an image forming apparatus, a screen management method, and a screen management program capable of simplifying a customization operation of a display screen of an operation panel.

  Accordingly, in order to solve the above-described problems, the present invention provides an image forming apparatus including an operation panel, the configuration information of display components arranged on the display screen for each display screen displayed on the operation panel, and the display Configuration information management means for managing arrangement information of the display parts on the screen, display part management means for managing display part data for each display part, and the configuration information and the arrangement corresponding to the display screen to be displayed Display control means for acquiring information and display component data of a display component defined in the configuration information, and displaying the display screen by arranging the acquired display component based on the arrangement information; and the display And editing means for changing the configuration information corresponding to at least a display screen to be edited in response to an input of a screen editing instruction.

  In such an image forming apparatus, the operation for customizing the display screen of the operation panel can be simplified.

  According to the present invention, it is possible to provide an image forming apparatus, a screen management method, and a screen management program that can simplify the customization work of the display screen of the operation panel.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings. FIG. 1 is a diagram illustrating a hardware configuration example of an image forming apparatus according to an embodiment of the present invention. FIG. 1 shows main hardware in the image forming apparatus 1.

  In FIG. 1, the image forming apparatus 1 is roughly divided into an operation unit 10 and a controller unit 20. The operation unit 10 includes a ROM 101, a RAM 102, a CPU 103, an operation panel 104 (operation panel), and the like, and executes display control of an operation screen (display screen) on the operation panel 104. The ROM 101 stores a program for executing display control and the like, data used by the program, and the like. The RAM 102 is used as a storage area for loading the program and the like when the program is executed. The CPU 103 executes a display process of the operation panel 104 by executing a program loaded in the RAM 102. The operation panel 104 is hardware for an operator to input to the image forming apparatus 1 and hardware for an operator to obtain an output from the image forming apparatus 1.

  FIG. 2 is a diagram illustrating an example of the operation panel. As shown in FIG. 2, the operation panel 104 includes a touch panel 311, a numeric keypad 312, a start button 313, a reset button 314, a function key 315, and an initial setting button 316. The touch panel 311 is hardware (touch operation unit) for inputting by a touch operation and hardware (screen display unit) for obtaining an output by screen display. The numeric keypad 312 is hardware for inputting numbers by operating keys (buttons). The start button 313 is hardware for performing a start operation by a button operation. The reset button 314 is hardware for performing a reset operation by a button operation. The function key 315 is hardware for displaying various operation screens by key (button) operation. The initial setting button 316 is hardware for displaying an initial setting screen by button operation.

  Returning to FIG. The controller unit 20 includes a ROM 201, a RAM 202, a CPU 203, a scanner 204, a plotter 205, an HDD (Hard Disk Drive) 206, and the like, and is a part that mainly executes control of hardware resources of the image forming apparatus 1. The ROM 201 stores a program for realizing the functions of the controller unit 20, data used by the program, and the like. The RAM 202 is used as a storage area for loading the program and the like when the program is executed. The CPU 203 executes the function of the controller unit 20 by executing a program loaded in the RAM 202. The scanner 204 is a device (hardware resource) for reading image data from a paper document. The plotter 205 is a device (hardware resource) for outputting (printing) image data on printing paper. The HDD 206 provides a large-scale storage area for storing various types of information, and is used, for example, for storing image data read by the scanner 204.

  The operation unit 10 and the controller unit 20 are connected by a bus or a USB (Universal Serial Bus) cable. An input to the operation panel 104 is notified to the controller unit 20 as an event. The controller unit 20 executes processing according to the event. On the other hand, an event detected by the controller unit 20 (for example, an event generated by the scanner 204, the plotter 205, or the like) is notified to the operation unit 10. The operation unit 10 executes display processing according to the notified event.

  FIG. 3 is a diagram illustrating a software configuration example of the image forming apparatus according to the embodiment of the present invention. In FIG. 3, the operation unit 10 includes an OS 11, a web browser 12, a content display plug-in 13, a framework content 14, a display content 15, and the like. These function by the CPU 103 of the operation unit 10 executing the programs related thereto.

  The OS 11 is a general OS such as Linux. The Web browser 12 is a general Web browser, and performs display control of the touch panel 311 based on HTML (HyperText Markup Language) data, XML (eXtensible Markup Language) data, and the like. The content display plug-in 13 is a plug-in for the Web browser 12, and an operation screen defined for the content by processing content configured in a predetermined format (for example, a format unique to the content display plug-in 13). Display control. The content is, for example, display data or a display program that can provide an expressive user interface that is difficult to express with HTML data or XML data. Therefore, the content display plug-in 13 is plugged into the web browser 12, so that the display function of the web browser 12 is expanded and the operation screen displayed on the touch panel 311 can be more expressive.

  The framework content 14 is one of the content processed by the content display plug-in 13. However, the framework content 14 is not actually visualized. The framework content 14 is a content in which a common part of various display contents 15 that are actually visualized is mounted, and the display content 15 is loaded onto the content display plug-in 13 and display control is executed. The display content 15 is content displayed on the touch panel 311 by the content display plug-in 13 and the framework content 14. By displaying the display content 15, an operation screen for operating the image forming apparatus 1 is displayed on the touch panel.

  On the other hand, the controller unit 20 includes an OS 21, a Java (registered trademark) VM (Virtual Machine) 22, an OSGi (Open Services Gateway Initiative) framework 23, a UI control unit 24, a display definition unit 25, a data management unit 26, and a session management unit. 27, a logic unit 28, a content management unit 31, a screen management unit 32, and the like. These function by the CPU 203 of the controller unit 20 executing the programs related thereto.

  The OS 11 is a general OS such as Linux. The Java (registered trademark) VM 22 is a so-called Java (registered trademark) virtual machine that interprets and executes a program based on an intermediate code (Java (registered trademark) bytecode) generated by a Java (registered trademark) compiler. The OSGi framework 23 realizes a software execution environment based on open software componentization technology (standardization technology by OSGi Alliance) based on Java (registered trademark). The UI control unit 24 determines the content to be displayed on the content display plug-in 13 and the framework content 14 according to the state of the image forming apparatus 1. By the way, software executed on the OSGi framework 23 is mounted as a component called “bundle”. The UI control unit 24 is implemented as one of such bundles.

  The data management unit 26 provides access means for data managed by the screen configuration information management unit 32. That is, access to data managed by the screen configuration information management unit 32 is performed via the data management unit 26. The session management unit 27 identifies a user who operates the image forming apparatus 1. The identification of the user is performed based on a session established in response to user authentication executed before the operation is started. The logic unit 28 executes control for causing the image forming apparatus 1 to function in response to an input to the display content 15.

  The content management unit 31 manages various display contents 15 and framework contents 14 that differ depending on the operation screen displayed on the touch panel 311. The screen configuration information management unit 32 manages information (screen configuration information) constituting an operation screen displayed based on the display content 15. The display content 15 is displayed by the framework content 14 based on the screen configuration information.

  The display definition unit 25 selects screen configuration information corresponding to the state of the image forming apparatus 1 (whether or not the user has logged in) as a display target.

  The framework content 14 and the display content 15 in the operation unit 10 will be described in more detail. FIG. 4 is a diagram for explaining framework content and display content in the operation unit.

  In FIG. 4, the framework content 14 includes a base content 141 and a common component 142. The base content 141 is a main part of the framework content 14, and includes a communication unit 1411, a display content control unit 1412, and the like. The communication unit 1411 performs communication (HTTP communication) with the controller unit 20 via the communication module 131 of the content display plug-in 13. Through the communication, screen configuration information, display content 15 and the like are acquired from the controller unit 20. Further, through the communication, an event detected in the display content 15 (for example, an event based on an input operation by the user via the touch panel 311 on the operation screen displayed by the display content 15) is notified to the controller unit 20. Note that the communication module 131 in the content display plug-in 13 provides the communication unit 1411 with an interface to the HTTP communication function of the Web browser 12.

  The display content control unit 1412 executes display control of the display content 15. Specifically, the screen configuration information is analyzed, and a file group configuring the display content 15 to be displayed is loaded. The loaded file is displayed by the content display plug-in 13.

  The common component content 142 is content related to display components (buttons, backgrounds, logos, etc.) that are commonly used in various display contents 15. The common part content 142 is filed for each part, for example.

  As the display content 15, as an example, a menu UI content 151, a customized UI content 152, a copy UI content 153, a FAX UI content 154, a scanner UI content 155, and the like are illustrated. Each content corresponds to a different operation screen. For example, the menu UI content 151 is content for displaying a menu screen. The customized UI content 152 is content for displaying a customization setting screen. The customization setting screen is a screen for editing (customizing) the configuration of the operation screen. The copy UI content 153, the FAX UI content 154, and the scanner UI content 155 are contents for displaying a copy screen, a FAX screen, and a scanner screen, respectively. Note that each display content 15 does not necessarily have to be composed of one file. Also in the present embodiment, the display content 15 displays one operation screen by a plurality of file groups each having a different data format.

  The framework content 14 is composed of the following class group, for example. FIG. 5 is a diagram illustrating an example of a class diagram of framework content. In FIG. 5, the framework content 14 includes a connection class 1411a, an XML conversion class 1411b, a display control class 1412a, an intermediate data class 1413a, and the like.

  The connection class 1411a and the XML conversion class 1411b constitute a communication unit 1411. The connection class 1411 a is a class that realizes communication with the controller unit 20 using the communication module 131 of the Web browser 13. The connection class 1411a has a transmission method and an event method. The transmission method is a method for outputting the XML data specified as the argument to the communication module 131. The event method is a method for receiving reply data from the communication module 131.

  The display control class 1412a is a class constituting the display content control unit 1412. The display control class 1412a has an event method, a screen transition method, a display method, and the like. The event method is a method for receiving data transmitted from the controller unit 20. The screen transition method is a method for acquiring the display content 15 as a transition destination when the display content 15 to be displayed is updated. The display method is a method for displaying the acquired display content 15 on the content display plug-in 13.

  The XML conversion class 1411b is a data format (XML format) used in communication between data in a data format interpretable by the display control class 1412a (hereinafter, data in the data format is referred to as “intermediate data”) and the controller unit 20. ) Class that realizes conversion processing. Due to the presence of the XML conversion class 1411b, the display control class 1412a can be implemented without depending on the data format used for communication. The XML conversion class 1411b has an XML conversion method and an event method. The XML conversion method is a method for converting intermediate data into XML data. The event method is a method for receiving XML data transmitted from the controller unit 20.

  The intermediate data class 1413a is a class that represents the above-described intermediate data.

  On the other hand, the display content 15 is configured as follows, for example. FIG. 6 is a diagram illustrating an example of a class diagram of display content. In FIG. 6, the display content 15 includes an operation screen class 1501, a template class 1502, a part file 1503, a specification file 1504, a layout file 1505, and the like.

  The operation screen class 1501 is a class that represents one operation screen, and one instance exists in one display content 15 (operation screen). The template class 1502 is a class that represents a virtual part (hereinafter referred to as “template”) for arranging display parts on the operation screen.

  FIG. 7 is a diagram illustrating the relationship between the operation screen and the template. FIG. 7 shows a display image of the operation screen on the touch panel 311. In the drawing, an example in which templates 1502T-1, 1502T-2, 1052T-3, and 1052T-4 are arranged on the operation screen 1501G is shown. As shown in the drawing, a plurality of templates can be arranged on one operation screen, and each template forms one partitioned display area. It is also possible to arrange a template in the template. In the drawing, an example in which a template 1502T-2 is arranged in the template 1502T-1 and a template 1502T-4 is arranged in the template 1502T-3 is shown. Such a point is expressed by the fact that the template class 1502 aggregates the template class 1502.

  Returning to FIG. The part file 1503, the specification file 1504, and the layout file 1505 correspond to data (files) constituting the screen configuration information described above, not a class. Each template includes a plurality of component files 1503, one specification file 1504, and one layout file.

  The component file 1503 is a file that stores data for realizing various display components (buttons, images, etc.) arranged on the template, and is filed for each display component. Each display component is configured in various data formats such as image data, moving image data, text data, and data representing a GUI component according to each characteristic.

  The specification file 1504 is a file in which information (component configuration information) indicating the configuration (list) of display components arranged in the template is defined. FIG. 8 is a diagram illustrating a definition example of a specification file. In FIG. 8, an example in which the component configuration information is described in XML is shown, but the definition format of the component configuration information is not limited to XML. In the drawing, each child element of the root element corresponds to one display component arranged in the template. The tag name of each element indicates the type of display component to which the element corresponds. For example, “img” indicates image data (image data). “Btn” indicates a button. “Msg” indicates a message. Each element has an id attribute and a name attribute defined therein. The id attribute is an ID for uniquely identifying the display component. The name attribute is the file name of the component file 1503 of the display component.

  For example, the element 1504-1 has an ID “1a”, copy. A display component relating to image data stored in a component file 1503 called jpg is defined. An element 1504-2 has an ID “3b”, ok. A button stored in a part file 1503 called xxx is defined. As described above, in the specification file 1504, IDs, file names, and the like are defined for all components arranged in one template.

  The layout file 1505 is a file in which information (component arrangement information) indicating the arrangement position of each display component in the template is defined. FIG. 9 is a conceptual diagram showing the definition contents of the layout file. FIG. 9 conceptually shows the contents of the component arrangement information, not the specific definition format of the component arrangement information. In the figure, a rectangle T indicates a display area of one template. A symbol in each circle arranged in the template T indicates an ID of each display component defined in the specification file 1504. The position of the circle indicates the arrangement position of the display component in the template T. That is, the layout file 1505 defines the arrangement position for each display component defined in the specification file 1504. A specific definition format may be, for example, an XML format. In this case, an element may be assigned to each display component, and a coordinate value indicating an arrangement position may be designated as the attribute.

  The specification file 1504 and the layout file 1505 are managed by the following table in the screen configuration information management unit 32, for example. FIG. 10 is a diagram illustrating a configuration example of the screen configuration information management table. In the screen configuration information management table 321 of FIG. 10, a specification file 1504 and a layout file 1505 for each operation screen are registered for each user or group. As described above, the specification file 1504 and the layout file 1505 are defined and managed for each user or group and for each operation screen. Therefore, it is possible to display different operation screens for each user or for each group according to the definition contents of both files. In the screen configuration information management table 321, “default” corresponds to a state where the user is not logged in to the image forming apparatus 1.

  Next, the UI control unit 24 and the logic unit 28 of the controller unit 20 will be described. FIG. 11 is a diagram for explaining a UI control unit and a logic unit in the controller unit.

  In FIG. 11, the UI control unit 24 includes a UI control framework 241 and a UI controller 242. The UI control unit 24 is a part that executes processing control common to each operation screen among processing control corresponding to input to various operation screens (display content 15) displayed on the operation unit 10, and includes a communication unit 2411 and It is comprised from the control part 2412.

  The communication unit 2411 performs communication (HTTP communication) with the operation unit 10 via the HTTP server 231 (see FIG. 3) in the OSGi framework 23. Through the communication, screen configuration information, display content 15 and the like are provided to the operation unit 10. In addition, an event detected in the display content 15 is notified from the operation unit 10 through the communication.

  The control unit 2412 controls processing according to a request (HTTP request) transmitted from the operation unit 10 through communication by the communication unit 2411. For example, the control unit 2412 calls the UI controller 242 corresponding to the currently displayed display content 15.

  As an example of the UI controller 242, a menu UI controller 2421, a customized UI controller 2422, a copy UI controller 2423, a FAX UI controller 2424, a scanner UI controller 2425, and the like are illustrated. The UI controller 242 is mounted for each display content 15 (for each operation screen), and controls processing to be executed according to an event that occurs in each display content 15. For example, the menu UI controller 2421 corresponds to the menu UI content 151. The customized UI controller 2422 corresponds to the customized UI content 152. The copy UI controller 2423, the FAX UI controller 2424, and the scanner UI controller 2425 correspond to the copy UI content 153, the FAX UI content 154, and the scanner UI content 155, respectively.

  The logic unit 28 is mounted for each UI controller 242. Also in FIG. 11, a menu logic 281, a customization logic 282, a copy logic 283, a FAX logic 284, and a scanner logic 285 are illustrated in correspondence with each UI controller 242. Each logic unit 28 performs control of hardware of the image forming apparatus 1 in response to a request from each UI controller 242.

  The UI control unit 24 includes, for example, the following class group. FIG. 12 is a diagram illustrating an example of a class diagram of the UI control unit. 12, the UI control unit 24 includes an HTTP connector class 2411a, an event controller class 2412a, a screen operation class 2420a, a menu screen operation class 2421a, a customized screen operation class 2422a, a copy screen operation class 2423a, a FAX screen operation class 2424a, and It is composed of a scanner screen operation class 2425a and the like.

  The HTTP connector class 2411a is a class constituting the communication unit 2411. The HTTP connector class 2411a has a transmission method. The transmission method is a method for transmitting data specified as an argument to the Web browser 12 by HTTP communication (HTTP response).

  The event controller class 2412a is a class constituting the control unit 2412. The event controller class 2412a has an event method. The event method is a method for receiving an event detected by the operation unit 10.

  The screen operation class 2420 a is a class in which operations common to the UI controllers 242 are defined, and is included in the UI control framework 241. The screen operation class 2420a also defines a common interface for each UI controller 242. Examples of the common interface (method) include an onCreate method and an action method. The onCreate method is a method for defining a process to be executed in response to an event (onCreate event) that occurs when the corresponding display content 15 is displayed. The action method is a method for defining a process to be executed in response to an event other than onCreate, such as a button press.

  Each UI controller 242 is an extended portion configured by a class that inherits the screen operation class 2420a. That is, the classes (menu screen operation class 2421a, customized screen operation class 2422a, copy screen operation class 2423a, FAX screen operation class 2424a, scanner screen operation class 2425a) constituting each UI controller 242 are differential programming with respect to the screen operation class 2420a. Can be implemented. Each subclass defines an operation specific to the corresponding operation screen in the interface (such as the onCreate method and theation method) defined by the screen operation class 2420a. When a new operation screen (display content 15) is added by the UI controller 242 having such a class configuration, a class corresponding to the operation screen is implemented as a subclass of the screen operation class 2420a and is necessary. Accordingly, the logic unit 28 corresponding to the operation screen may be mounted.

  Hereinafter, the processing procedure of the image forming apparatus 1 will be described. FIG. 13 is a sequence diagram for explaining display processing of the operation screen when the user is not logged in. When the user is not logged in, a default operation screen is displayed on the touch panel 311 as a common operation screen for all users, not an operation screen unique to the user.

  When the image forming apparatus 1 is activated and the operation screen is displayed on the touch panel 311, the content display plug-in 13 instructs the framework content 14 to display a menu screen (initial screen) (S 101). . In response to the instruction to display the menu screen, the framework content 14 requests initialization from the UI control framework 241 via HTTP communication (S102). Note that HTTP communication by the framework content 14 is performed via the communication module 131 of the content display plug-in 13 and the Web browser 12. However, this point will be omitted for convenience.

  In response to the initialization request, the UI control framework 241 stores the location information (for example, URL (Uniform Resource Locator)) of the specification file 1504 and the layout file 1505 corresponding to the “fixed portion” of the menu screen in a predetermined storage area. (S103), and the acquired information (menu screen information) is returned to the framework content 14 (S104). Here, the fixed portion of the menu screen refers to a portion that cannot be customized for each user on the menu screen. Therefore, a part that can be customized for each user (hereinafter referred to as “variable part”) is in a perforated state (not defined) in the specification file 1504 and the layout file 1505 corresponding to the fixed part.

  Subsequently, the framework content 14 requests the HTTP server 231 to provide the specification file 1504 of the fixed part of the menu screen based on the URL of the specification file 1504 included in the returned menu screen information. (S105), the specification file 1504 is acquired from the HTTP server 231 (S106). Subsequently, the framework content 14 requests the HTTP server 231 to provide the layout file 1505 for the fixed portion of the menu screen based on the URL of the layout file 1505 included in the menu screen information (S107). ), The layout file 1505 is acquired from the HTTP server 231 (S108).

  Subsequently, the framework content 14 requests the HTTP server 231 to provide the component file 1503 whose file name is described (defined) in the specification file 1504 of the menu screen (S109), thereby the HTTP server 231. Thus, the component file 1503 is acquired (S110).

  Subsequently, the display content control unit 1412 of the framework content 14 generates a menu screen by arranging each display component stored in the acquired component file 1503 at a position defined in the acquired layout file 1505. Then, the menu screen is displayed on the touch panel 311 (S111). However, only the fixed part of the menu screen is displayed at this stage. Therefore, the variable part is not displayed.

  Therefore, in order to fill the variable part, the framework content 14 transmits an update request for the state of the currently displayed screen (here, the menu screen) to the HTTP server 231 (S112). The update request is notified to the display definition unit 25 via the UI control framework 241, the menu UI controller 2421, and the menu logic 281.

  The display definition unit 25 inquires of the session management unit 27 about the user who is currently logged in (S113). Here, since the user is not logged in, the session management unit 27 returns that the user is not logged in (S114). Therefore, the display definition unit 25 requests the data management unit 26 to acquire the specification file 1504 and the layout file 1505 (hereinafter referred to as “default file”) corresponding to the variable part of the default menu screen (S115). The data management unit 26 specifies a default file based on the screen configuration information management table 321, acquires the default file (S 116), and returns it to the display definition unit 25 (S 117). The default file is returned to the framework content 14 via the display definition unit 25, the menu logic 281, the menu UI controller 2421, the UI control framework 231, and the HTTP server 231 (S118).

  The framework content 14 displays the variable part of the menu screen based on the returned default file (S119). At this time, the framework content 14 acquires the component file 1503 corresponding to the variable part from the HTTP server 231 as necessary. As described above, the default menu screen is completely displayed on the touch panel 311.

  Next, a case where the user is logged in to the image forming apparatus 1 will be described. FIG. 14 is a sequence diagram for explaining display processing of the operation screen when the user is logged in.

  For example, when the user ID and password are input on the menu screen displayed on the touch panel 311 and the login button is pressed, the framework content 14 logs the user into the menu UI controller 2421 via HTTP communication. A request is transmitted (S151). The login request includes the input user ID and password. The menu UI controller 2421 designates the user ID and password included in the login request and requests the session management unit 27 to log in the user (S152). The session management unit 27 authenticates the user based on the user ID and password (S153). When the user is authenticated, the session management unit 27 opens a session for the user (hereinafter referred to as “current user”), and returns a response indicating successful login to the menu UI controller 2421 (S154). The menu UI controller 2421 returns an HTTP response indicating successful login to the framework content 14 (S155).

  The framework content 14 updates the menu screen currently displayed to the menu screen corresponding to the current user (that is, the menu screen customized for the current user) in response to the successful login. An update request is transmitted (S156). The update request is notified to the display definition unit 25 via the UI control framework 241, the menu UI controller 2421, and the menu logic 281.

  The display definition unit 25 inquires of the session management unit 27 about the user who is currently logged in (S157). The session management unit 27 identifies the current user based on the currently established session, and returns identification information (for example, a user name) of the current user (S158). The display definition unit 25 designates the user name of the current user, and the data management unit 26 performs data management to acquire the specification file 1504 and layout file 1505 (hereinafter referred to as “user file”) corresponding to the current user. Request is made to the unit 26 (S159). The data management unit 26 identifies the user file based on the screen configuration information management table 321, acquires the user file (S 160), and returns it to the display definition unit 25 (S 161). The user file is returned to the framework content 14 via the display definition unit 25, the menu logic 281, the menu UI controller 2421, the UI control framework 231, and the HTTP server 231 (S162).

  The framework content 14 updates the variable part of the menu screen based on the returned user file (S163). At this time, the framework content 14 acquires a new component file 1503 from the HTTP server 231 as necessary. As described above, a menu screen customized for the current user is displayed on the touch panel 311.

  Next, customization of the operation screen will be described. Each operation screen is customized using the customization setting screen as an entrance. FIG. 15 is a diagram illustrating a display example of the customization setting screen. In FIG. 15, the customization setting screen 510 includes a copy button 511, a FAX button 512, a scanner button 513, a menu button 514, and the like. Each button is for displaying a screen for customizing an operation screen corresponding to each button name. For example, when the copy button 511 is pressed, a screen for customizing the copy screen (hereinafter referred to as “copy UI setting screen”) is displayed on the touch panel 311. In the following, the customization procedure will be described with the copy screen as the customization target.

  FIG. 16 is a sequence diagram for explaining a copy UI setting screen display process.

  If the copy button 511 is selected (pressed) while the customization setting screen 510 of FIG. 15 is displayed on the touch panel 311, the framework content 14 detects the selection of the copy button 511, and the copy button 511 selects it. This is notified to the HTTP server 231 (S201). The selection of the copy button 511 is notified to the customization logic 282 via the UI control framework 241 and the customization UI controller 2422.

  The customization logic 282 acquires information including the URL of the customization screen corresponding to the copy button 511, that is, the copy UI setting screen (hereinafter referred to as “URL information”) from a predetermined storage area (S202).

  FIG. 17 is a diagram showing URL information on the copy UI setting screen. The URL information 521 in FIG. 17 shows an example described in the XML format. In the URL information 521, the value of the url element (“theme / copy-customize”) defined as a child element of the transitioninfo element corresponds to the URL of the copy UI setting screen. The URL corresponds to the “fixed part” URL on the copy UI setting screen.

  The URL information 521 is returned to the framework content 14 via the customization logic 282, the customization UI controller 2422, the UI control framework 241, and the HTTP server 231 (S203).

  The framework content 14 that has received the URL information 521 acquires the specification file 1504 and layout file 1505 of the fixed part of the copy UI setting screen from the HTTP server 231 based on the URL included in the URL information 521 (S204 to S204). S207). The framework content 14 acquires the component file 1503 whose file name is described in the acquired specification file 1504 from the HTTP server 231 (S208, S209). The framework content 14 further generates a fixed part of the copy UI setting screen by arranging each display component stored in the acquired component file 1503 at a position defined in the acquired layout file 1505, and It is displayed on the touch panel 311 (S210).

  FIG. 18 is a diagram illustrating a display example of a fixed portion of the copy UI setting screen. 18, a copy UI setting screen 530 includes a copy screen display area 531, a screen common setting area 532, a button individual setting area 533, a non-display button display area 534, a save button 535, a cancel button 536, an end button 537, and the like. It is configured. Of these, areas other than the copy screen display area 531 are fixed portions. Accordingly, in FIG. 18 as well, the area other than the copy screen display area 531 is displayed in a complete state.

  The copy screen display area 531 is an area in which the current setting state (customization state) of the copy screen is displayed. The copy screen customization status varies depending on the user. Therefore, the copy screen display area 531 corresponds to a variable part.

  Subsequently, in order to display the variable part of the copy UI setting screen 530, that is, the copy screen, the framework content 14 transmits an inquiry about the URL information of the copy screen to the HTTP server 231 (S211). The inquiry is notified to the copy logic 283 via the HTTP server 231, UI control framework 241, customized UI controller 2422, and copy UI controller 2423. The copy logic 283 acquires information (URL information) including the URL of the copy screen from a predetermined storage area (S212).

  FIG. 19 is a diagram showing URL information of the copy screen. The URL information 522 in FIG. 19 is shown in XML format. In the URL information 522, the value of the url element (“theme / copy”) defined as a child element of the transitioninfo element corresponds to the URL of the copy screen.

  The URL information 522 is returned to the framework content 14 via the copy logic 283, the copy UI controller 2423, the UI control framework 241, and the HTTP server 231 (S213).

  Subsequently, the framework content 14 designates the URL included in the URL information 522 in order to update the display state of the copy UI setting screen 530 (that is, to display the copy screen in the copy screen display area 531). Then, an update request for the copy UI setting screen 530 is transmitted to the HTTP server 231 (S214). The update request is notified to the display definition unit 25 via the UI control framework 241, the copy UI controller 2423, and the copy logic 283.

  The display definition unit 25 inquires of the session management unit 27 about the user who is currently logged in (S215). The session management unit 27 identifies the current user based on the currently established session, and returns identification information (for example, a user name) of the current user (S216). The display definition unit 25 specifies the user name of the current user, and acquires the specification file 1504 and layout file 1505 (hereinafter referred to as “user file”) of the copy screen corresponding to the current user from the data management unit 26. Is requested to the data management unit 26 (S217). The data management unit 26 identifies the user file based on the screen configuration information management table 321, acquires the user file (S 218), and returns it to the display definition unit 25 (S 219). The user file is returned to the framework content 14 via the display definition unit 25, the copy logic 283, the copy UI controller 2423, the UI control framework 231, and the HTTP server 231 (S220).

  The framework content 14 updates the variable part (copy screen display area 531) of the copy UI setting screen 530 based on the returned user file (S221). In other words, the current copy screen of the current user is displayed in the copy screen display area 531. At this time, the framework content 14 acquires a new component file 1503 from the HTTP server 231 as necessary. As described above, the complete many-copy UI setting screen is displayed on the touch panel 311.

  FIG. 20 is a diagram illustrating a display example of a complete copy UI setting screen. In the copy UI setting screen 530 in FIG. 20, a copy screen is displayed in the copy screen display area 530. The copy screen is customized (edited) by a user operation on the copy UI setting screen in such a state.

  FIG. 21 is a sequence diagram for explaining a copy screen customization process.

  When any button (for example, AUTO button 5311) constituting the copy screen displayed in the copy screen display area 531 of the copy UI setting screen 530 is selected (pressed), the framework content 14 displays the AUTO button 5311. Is detected, and data indicating that the AUTO button 5311 has been pressed (event notification data) is notified to the HTTP server 231 (S251).

  FIG. 22 is a diagram illustrating an example of event notification data. The event notification data 523 in FIG. 22 shows an example described in XML. In the event notification data 523, the value of the wid element 5231 (“copy_customize”) indicates the ID of the operation screen in which the event has occurred. copy_customize is the ID of the copy UI setting screen 530. The value of the cid element 5232 (“btn_auto”) indicates the ID of the display component that is the target of the event. btn_auto is the ID of the AUTO button 5311. The value of the evt element 5233 (“press”) indicates the type of event. “press” is an identifier indicating a press event. Therefore, the event notification data 523 describes that the AUTO button 5311 has been pressed.

  The event notification data 523 is notified to the customization logic 282 via the UI control framework 241 and the customization UI controller 2422. Based on the event notification data 523, the customization logic 282 recognizes that the AUTO button 5311 has been pressed and, as a process corresponding to the event, data indicating an instruction to update the display state of the screen according to the selection of the AUTO button 5311 (state (Update instruction data) is generated (S252).

  FIG. 23 is a diagram illustrating an example of state update instruction data. The state update instruction data 524 in FIG. 23 shows an example described in XML. In the state update instruction data 524, the value of the wid element 5241 (“copy_customize”) indicates the ID of the operation screen to be updated. copy_customize is the ID of the copy UI setting screen 530. The state update instruction data 524 includes item elements as many as the number of display components to be updated. The item element includes a cid element and a status element as child elements. The value of the cid element indicates the ID of the display component to be updated. The status element indicates the state after update. In the figure, a cid element 5243 and a status element 5244 are included as child elements of the item element 5242. The value of the cid element 5243 is “btn_auto” (AUTO button 5311). The value of the status element is “select”. Therefore, in the update instruction data 524, an instruction for setting the AUTO button 5311 in the selected state is described.

  The state update instruction data 524 is returned to the framework content 14 via the customization logic 282, the customization UI controller 2422, the UI control framework 241, and the HTTP server 231 (S253). The framework content 14 that has received the state update instruction data 524 updates the display state of the copy UI setting screen 530 in accordance with the state update instruction data 524 (S254). That is, the AUTO button 5311 is selected (edited).

  Subsequently, on the copy UI setting screen 530, an instruction to change the display setting of the copy screen is input by the user. For example, in the common screen setting area 532, the display color, display size, presence / absence of logo display, etc. can be set for the entire copy screen. Further, in the button individual setting area 533, it is possible to set display or non-display for a button to be edited. For example, when the OFF button 5332 is pressed, the button to be edited is set to non-display, and the button moves to the non-display button display area 534. When a button displayed in the non-display button display area 534 is selected and the display button 5331 is pressed, the button returns to the original display position and is displayed.

  Here, it is assumed that the OFF button 5332 is pressed in the button individual setting area 533. In this case, the framework content 14 transmits event notification data indicating that the OFF button 5332 has been pressed to the HTTP server 231 (S255). The event notification data is notified to the customization logic 282 via the UI control framework 241 and the customization UI controller 2422.

  The customization logic 282 recognizes that the OFF button 5332 has been pressed based on the event notification data, and retains in the memory the setting change content that hides the AUTO button 5311 as a process corresponding to the event (S255). Further, the customization logic 282 generates state update instruction data indicating that the AUTO button 5311 should be moved to the non-display button display area 534 on the copy UI setting screen 530. The state update instruction data is returned to the framework content 14 via the customization logic 282, the customization UI controller 2422, the UI control framework 241, and the HTTP server 231 (S257).

  The framework content 14 that has received the state update instruction data moves the display position of the AUTO button 5311 to the non-display button display area 534 in accordance with the state update instruction data 524 (S258).

  Thereafter, the user can continue to change settings on the copy UI setting screen 530 with respect to the settings of other buttons and the entire screen. The customization logic 282 holds the contents of the input setting change in the memory.

  When the input of the setting change is completed and the save button 535 is pressed, the framework content 14 transmits event notification data indicating the press of the save button 535 to the HTTP server 231 (S259). The event notification data is notified to the customization logic 282 via the UI control framework 241 and the customization UI controller 2422. When the customization logic 282 recognizes that the save button 535 has been pressed based on the event notification data, the customization logic 282 instructs the display definition unit 25 to save the setting change contents held in the memory so far (S260).

  The display definition unit 25 inquires of the session management unit 27 about the user who is currently logged in (S261). The session management unit 27 identifies the current user based on the currently established session, and returns identification information (for example, user name) of the current user (S262). The display definition unit 25 specifies the user name of the current user, and changes the setting of the copy screen specification file 1504 (or layout file 1505 as necessary) corresponding to the current user to the data management unit 26. The storage (reflection) of the contents is requested (S263). The data management unit 26 specifies the copy specification file 1504 for the requested user based on the screen configuration information management table 321 and saves the setting change contents in the specification file 1504 (S264). Here, the AUTO button 5311 is not displayed. Accordingly, the specification file 1504 of the copy screen of the current user is updated and saved as follows, for example.

  FIG. 24 is a diagram illustrating an example of updating the specification file. In FIG. 24, a specification file 1054a is a specification file 1054 before update, and a specification file 1054b is a specification file 1054 after update. In the specification file 1054a, an element 1054a-1 is a definition for the AUTO button 5311. When the AUTO button 5311 is set to non-display, the element 1054a-1 is deleted as shown in the specification file 1054b. Thereafter, when the user logs in, a copy screen is generated based on the specification file 1054b. Since the specification file 1054b has no definition regarding the AUTO button 5311, the AUTO button 5311 is not displayed on the copy screen.

  In the above, customization of the operation screen has been described with respect to an example displayed on the operation panel of the image forming apparatus 1, but may be performed remotely from a computer such as a PC (Personal Computer) connected via a network. .

  FIG. 25 is a diagram illustrating a configuration example when remote customization is performed. In FIG. 25, the same parts as those in FIG. 25, the PC 40 is connected to the image forming apparatus 1 via a network (whether wired or wireless), and includes an OS 41, a Web browser 42, a content display plug-in 43, and the like. The OS 41, the Web browser 42, and the content display plug-in 43 are the same software as the OS 11, the Web browser 12, and the content display plug-in 13 in the operation unit 10 of the image forming apparatus 1, respectively. However, the OS 41 and the Web browser 42 do not have to be the same type as those in the operation unit 10. In FIG. 25, the components of the operation unit 10 are not shown for convenience. According to the configuration shown in FIG. 25, the framework content 14 and the content 15 corresponding to the customization setting screen 510 and the copy UI setting screen 530 are downloaded from the image forming apparatus 1 on the content display plug-in 43 of the PC 40. As a result, the customization setting screen 510, the copy UI setting screen 530, and the like can be displayed on the display device of the PC 40. Therefore, by operating the screen displayed on the display device of the PC 40, various operation screens can be customized by remote operation (remote operation).

  As described above, the image forming apparatus 1 in the embodiment of the present invention displays each operation screen based on the screen configuration information (specification file 1504, layout file 1505) defined for each operation screen. Each display component arranged on the operation screen is managed as independent data (file). Therefore, the display mode of the operation screen can be easily changed (customized) by changing the screen configuration information. For example, if it is desired to hide a certain display component, the definition of the display component in the specification file 1504 may be deleted. If the display mode of the display component is to be changed, the component file 1503 for the display component may be changed.

  Further, since the screen configuration information is defined and managed for each user, the display mode of each operation screen can be different for each user.

  As mentioned above, although the Example of this invention was explained in full detail, this invention is not limited to such specific embodiment, In the range of the summary of this invention described in the claim, various deformation | transformation・ Change is possible.

1 is a diagram illustrating an example of a hardware configuration of an image forming apparatus according to an embodiment of the present invention. It is a figure which shows the example of an operation panel. FIG. 3 is a diagram illustrating a software configuration example of an image forming apparatus according to an embodiment of the present invention. It is a figure for demonstrating the framework content and display content in an operation part. It is a figure which shows an example of the class diagram of framework content. It is a figure which shows an example of the class diagram of a display content. It is a figure which shows the relationship between an operation screen and a template. It is a figure which shows the example of a definition of a specification file. It is a conceptual diagram which shows the definition content of a layout file. It is a figure which shows the structural example of a screen structure information management table. It is a figure for demonstrating the UI control part and logic part in a controller part. It is a figure which shows an example of the class diagram of UI control part. It is a sequence diagram for demonstrating the display process of the operation screen when the user is not logging in. It is a sequence diagram for demonstrating the display process of the operation screen when a user logs in. It is a figure which shows the example of a display of a customization setting screen. FIG. 10 is a sequence diagram for explaining display processing of a copy UI setting screen. It is a figure which shows URL information of a copy UI setting screen. It is a figure which shows the example of a display of the fixed part of a copy UI setting screen. It is a figure which shows the URL information of a copy screen. FIG. 10 is a diagram illustrating a display example of a complete copy UI setting screen. FIG. 10 is a sequence diagram for explaining a copy screen customization process. It is a figure which shows the example of event notification data. It is a figure which shows the example of state update instruction data. It is a figure which shows the example of the update of a specification file. It is a figure which shows the structural example in the case of performing remote customization.

Explanation of symbols

1 Image forming apparatus 10 Operation unit 11 OS
12 Web browser 13 Content display plug-in 14 Framework content 15 Display content 20 Controller unit 21 OS
22 Java (registered trademark) VM
23 OSGi framework 24 UI control unit 25 Display definition unit 26 Data management unit 27 Session management unit 28 Logic unit 31 Content management unit 32 Screen management unit 101 ROM
102 RAM
103 CPU
104 Operation Panel 131 Communication Module 141 Base Content 142 Common Component 151 Menu UI Content 152 Customized UI Content 153 Copy UI Content 154 FAXUI Content 155 Scanner UI Content 201 ROM
202 RAM
203 CPU
204 Scanner 205 Plotter 206 HDD
241 UI control unit 242 UI controller 281 Menu logic 282 Customization logic 283 Copy logic 284 FAX logic 285 Scanner logic 311 Touch panel 312 Numeric keypad 313 Start button 314 Reset button 315 Function key 316 Initial setting button 1411 Communication unit 1412 Display content control unit 1411a Connection class 1411b XML conversion class 1412a Display control class 1413a Intermediate data class 1501 Operation screen class 1502 Template class 1503 Display part 1504 Specification file 1505 Layout file 2411 Communication unit 2412 Control unit 2421 Menu UI controller 2423 Customization UI controller 2423 Copy UI controller 2424 F XUI controller 2425 Scanner UI controller 1411a Connection class 1411b XML conversion class 1412a Display control class 1413a Intermediate data class 2411a HTTP connector class 2412a Event controller class 2420a Screen operation class 2421a Menu screen operation class 2422a Customize screen operation class 2423a Copy screen operation class 2424a FAX Screen operation class 2425a Scanner screen operation class

Claims (15)

An image forming apparatus having an operation panel,
Configuration information management means for managing the configuration information of the display components arranged on the display screen and the arrangement information of the display components on the display screen for each display screen displayed on the operation panel;
Display component management means for managing display component data for each display component;
The configuration information and the arrangement information corresponding to the display screen that is the display target, and display component data of the display component defined in the configuration information are acquired, and the acquired display component is arranged based on the arrangement information Display control means for displaying the display screen by,
An image forming apparatus comprising: an editing unit that changes at least the configuration information corresponding to a display screen to be edited in response to an input of an instruction to edit the display screen. The display control means converts the display screen to be edited into a partial area of a customization screen, which is a display screen for receiving an input of the editing instruction, into the configuration information and the arrangement information corresponding to the display screen. Display based on
The image forming apparatus according to claim 1, wherein the editing unit changes the configuration information corresponding to the display screen displayed in a partial area of the customization screen. The configuration information and the arrangement information are defined according to the user,
The display control unit displays the display screen in a partial area of the customization screen based on the configuration information and the arrangement information corresponding to a user who is logged in to the image forming apparatus. The image forming apparatus according to claim 2. A web browser for controlling display of the display screen on the operation panel;
The image forming apparatus according to claim 1, wherein the display control unit is configured as a plug-in of the Web browser. The display control means includes content processed by the plug-in of the web browser,
The content acquires the configuration information and the arrangement information corresponding to the display screen that is the display target, and the display component data of the display component defined in the configuration information, and the acquired display component is the arrangement information. The image forming apparatus according to claim 4, wherein the display screen is displayed by arranging the display screen based on the display. A screen management method executed by an image forming apparatus having an operation panel,
Configuration information management procedure for managing the configuration information of the display components arranged on the display screen and the arrangement information of the display components on the display screen for each display screen displayed on the operation panel;
A display component management procedure for managing display component data for each display component;
The configuration information and the arrangement information corresponding to the display screen that is the display target, and display component data of the display component defined in the configuration information are acquired, and the acquired display component is arranged based on the arrangement information Display control procedure to display the display screen by,
A screen management method comprising: an editing procedure for changing at least the configuration information corresponding to a display screen to be edited in response to an input of an instruction to edit the display screen. In the display control procedure, the display screen targeted for editing in a partial area of a customization screen that is a display screen for receiving an input of the editing instruction is used as the configuration information and the arrangement information corresponding to the display screen. Display based on
The screen management method according to claim 6, wherein the editing procedure changes the configuration information corresponding to the display screen displayed in a partial area of the customization screen. The configuration information and the arrangement information are defined according to the user,
The display control procedure displays the display screen in a partial area of the customization screen based on the configuration information and the arrangement information corresponding to a user who is logged in to the image forming apparatus. The screen management method according to claim 7. A web browser for controlling display of the display screen on the operation panel;
The screen management method according to claim 6, wherein the display control procedure is executed by a plug-in of the Web browser. The content processed by the plug-in of the Web browser acquires the configuration information and the arrangement information corresponding to the display screen to be displayed, and the display component data of the display component defined in the configuration information, The screen management method according to claim 9, wherein the display screen is displayed by arranging the acquired display component based on the arrangement information. An image forming apparatus equipped with an operation panel
Configuration information management means for managing the configuration information of the display components arranged on the display screen and the arrangement information of the display components on the display screen for each display screen displayed on the operation panel;
Display component management means for managing display component data for each display component;
The configuration information and the arrangement information corresponding to the display screen that is the display target, and display component data of the display component defined in the configuration information are acquired, and the acquired display component is arranged based on the arrangement information Display control means for displaying the display screen by,
The screen management program for functioning as an edit means which changes the said structure information corresponding to the display screen made into edit object at least according to the input of the edit instruction | indication of the said display screen. The display control means converts the display screen to be edited into a partial area of a customization screen, which is a display screen for receiving an input of the editing instruction, into the configuration information and the arrangement information corresponding to the display screen. Display based on
12. The screen management program according to claim 11, wherein the editing unit changes the configuration information corresponding to the display screen displayed in a partial area of the customization screen. The configuration information and the arrangement information are defined according to the user,
The display control unit displays the display screen in a partial area of the customization screen based on the configuration information and the arrangement information corresponding to a user who is logged in to the image forming apparatus. The screen management program according to claim 12. A web browser for controlling display of the display screen on the operation panel;
The screen management program according to claim 11, wherein the display control unit is configured as a plug-in of the Web browser. The display control means includes content processed by the plug-in of the web browser,
The content acquires the configuration information and the arrangement information corresponding to the display screen that is the display target, and the display component data of the display component defined in the configuration information, and the acquired display component is the arrangement information. The screen management program according to claim 14, wherein the display screen is displayed by arranging based on the screen.

Images