1. Technical Field
Embodiments of the present disclosure relate to information management, and more specifically relates to an electronic device and a method for reading help files of a software program.
2. Description of Related Art
A help file is a documentation component of a software program that explains features of the software program and helps a user understand capabilities of the features.
The help file's purpose is to provide answers that a user needs to understand to use the software program effectively.
However, for most help files, it is difficult for the user to check corresponding explanation of particular features of the software program rapidly.
In general, the word “module,” as used hereinafter, refers to logic embodied in hardware or firmware, or to a collection of software instructions, written in a programming language, such as, for example, Java, C, or assembly. One or more software instructions in the modules may be embedded in firmware. It will be appreciated that modules may comprise connected logic units, such as gates and flip-flops, and may comprise programmable units, such as programmable gate arrays or processors. The modules described herein may be implemented as either software and/or hardware modules and may be stored in any type of non-transitory computer-readable storage medium or other computer storage device.
The help file reading system 14 includes a plurality of function modules (see
The storage device 10 may include any type(s) of non-transitory computer-readable storage medium, such as a hard disk drive, a compact disc, a digital video disc, or a tape drive. The storage device 11 stores the help file reading system 14 as mentioned above, and further data needed by the help file reading system 14, the software program 13, and the help file 15.
The processing device 11 may be a processor, a microprocessor, an application-specific integrated circuit (ASIC), and a field programmable gate array (FPGA), for example.
In step S01, the relating module 140 generates relationships between graphical interfaces of the software program 13 and the help items in the help file 15, and stores the relationships into the storage device 10. One graphical interface of the software program 13 can be related to one or more of the help items in the help file 15. For example, referring to
In step S02, the setting module 141 sets display parameters of the help file 15, and stores the display parameters into the storage device 10. The display parameters include a display style, a display period, a display pattern. In one embodiment, the display style includes a separate display style and an embedded display style. The separate display style indicates displaying the help items of the help file 15 using a document separate from the graphical interfaces of the software program 13. The embedded display style indicates displaying the help items of the help file 15 on the graphical interfaces of the software program 13, and making the help items point to corresponding features on the graphical interfaces using, an arrow, for example. The display period includes display periods of the help items. The display pattern includes automatically invoking the help file 15 and triggered invoking the help file 15. Automatically invoking the help file 15 indicates that invoking help items relating to features appearing on a current graphical interface of the software program 13 automatically. For example, referring to
In step S03, the data loading module 142 checks a graphical interface of the software program 13 which is currently displayed on the display device 12, loads one or more related help items according to the relationships stored in the storage device 10. It may be understood that, the graphical interface may includes a plurality of features of the software program 13, the data loading module 142 loads the help items related to all the features on the currently displayed graphical interface according to the relationships. In addition, the data loading module 142 further classifies the related help items according to the contents of the related help items to generate a help list which includes a plurality of information items. For example, the related help items include contents such as a basic function description of each of the features on the currently displayed graphical interface, an operation descriptions of each of the features on the currently displayed graphical interface, for example. Thus, the help list may includes information items, such as a function description of the feature A, a function description of the feature B, an operation description of the feature A, an operation description of the feature B, for example.
In step S04, the checking module 143 determines if the help file 15 is invoked automatically according to the set display pattern. Step S05 is implemented when the help file 15 is not invoked automatically. Otherwise, step S06 is implemented when the help file 15 is invoked automatically.
In step S05, the checking module 143 further determines if a predetermined event that triggers the help file 15 being invoked has happened. The predetermined event may be, for example, a key (physical or virtual) has been pressed. Step S06 is implemented when the predetermined event has happened. Otherwise, step S09 is implemented when no predetermined event has happened.
In step S06, the interaction module 144 displays the help list on the graphical interface to the user for selecting an information item in the help list.
In step S07, the displaying module 145 displays the related help items on the display device 12 according to the selected information item, the set display style and the display period. In one embodiment, a control panel, which includes options of “pause,” “playing,” “previous,” and “next”, can be used to pause display, resume play, play previous, and play next of the help items.
In step S08, the determination module 146 determines if the currently displayed graphical interface exits. Step S06 is implemented when the currently displayed graphical interface does not exit. Otherwise, step S09 is implemented when the currently displayed graphical interface exits.
In step S09, the determination module 146 further determines if the software program 13 exits. Step S03 is implemented when the software program 13 does not exit. Otherwise, the procedure ends when the software program 13 exits.
It should be emphasized that the above-described embodiments of the present disclosure, including any particular embodiments, are merely possible examples of implementations, set forth for a clear understanding of the principles of the disclosure. Many variations and modifications may be made to the above-described embodiment(s) of the disclosure without departing substantially from the spirit and principles of the disclosure. All such modifications and variations are intended to be included herein within the scope of this disclosure and protected by the following claims.
Number | Date | Country | Kind |
---|---|---|---|
101139199 | Oct 2012 | TW | national |