TWI567563B - A user input screen generation system and a method thereof - Google Patents

Description

User input screen generating system and method thereof

The present invention relates to a picture generation system, and more particularly to a user input picture generation system and method thereof.

With the rapid development of the Internet, more and more web development technologies have come out. The early web development technology relied on the processing power of the remote server. That is to say, the request generated by the browser of the near-end host must be processed by the remote server, and then the corresponding data is returned. Give the near-end host. However, as the network usage population increases, the remote server is gradually unable to load too many requests from nearby local hosts. So a new generation of web development technology has emerged. The most popular of these is the Java (Java) architecture, as well as the asynchronous Javascript scripting language and the Asynchronous JavaScript and XML (AJAX) architecture.

In addition to providing a good user interaction experience, the above-mentioned new generation of web development technology is different from the previous concept of "Thin Client" and prefers the so-called "Fat Client" concept. It is said that most of the requests generated by the browser are handled by the near-end host, and only a small part of them are processed by the remote server. Therefore, the new generation of web development technology greatly reduces the computing burden of the remote server.

However, for system developers, the existing Java architecture and the asynchronous Java scripting language and the Extensible Markup Language architecture are completely independent development environments. Under the Java architecture, developers can reuse the fields defined by the class, so when developing a new system, Good use of the fields that have been defined in the previous development of the old system, so developers can efficiently develop new systems; in the asynchronous Java scripting language and the extensible markup language architecture, the Java scripting language is difficult to reuse. The characteristics, so every time a system developer wants to develop a new system, they must use the Java script language to write the source code from the beginning, so it is not very efficient.

So for developers, how to integrate the Java architecture with the non-synchronized Java scripting language and the extensible markup language architecture independent development environment, so that under the asynchronous Java scripting language and the extensible markup language architecture, It is an important issue to develop new systems from scratch and improve the efficiency of system developers in system development.

Accordingly, it is an object of the present invention to provide a user input screen generating system.

Thus, the user input screen generating system of the present invention comprises a server device and a user device.

The server device is configured to store a class of cells and an execution unit.

The user device includes a user interface unit for generating a user input screen.

After the user device downloads the category unit and the execution unit through the network and executes the execution unit, the user interface unit parses the category unit at a file location of the pair of execution units to generate a category information, and according to This category of data generates the user input screen for user input. .

Another object of the present invention is to provide a user input screen generating method.

Therefore, the user input screen generating method is applicable to a server device and a user device, wherein the server device is configured to store a category unit and an execution unit, and the user device includes a user interface unit. The user input screen generating method includes the following steps: (A) the user device downloads and executes the execution unit through the network; (B) the user interface unit is downloaded from the server in a file location of a pair of execution units. The category unit of the device is configured to generate a category of data; and (C) the user interface unit generates a user input screen for user input based on the category information.

The above and other technical contents, features and advantages of the present invention will be apparent from the following detailed description of the preferred embodiments of the invention.

Before the present invention is described in detail, it is noted that in the following description, similar elements are denoted by the same reference numerals.

Referring to Figures 1, 2 and 3, a first preferred embodiment of the user input screen generating system 1 of the present invention comprises a server device 11, and a user device 12. The server device 11 is configured to store a class unit 111 and an execution unit 112. The user device 12 includes a user interface unit 121 for generating a user input screen, and a memory unit 122. In the first preferred embodiment, the server device 11 is used by a system developer Java language development, the user device 12 was developed by a system developer using a Java scripting language, that is, the first preferred embodiment employs a non-synchronized Java scripting language and an extensible markup language architecture. The server device 11 is a computer host, and the user device 12 can be a computer host or a mobile device, such as a tablet or a smart phone. In addition, system developers use the existing Smart Editor as a development tool.

The category unit 111 includes an eXtensible Markup Language (XML) file having a plurality of pre-established field categories. In the first preferred embodiment, the extensible markup language file is mainly developed based on an Emerging Technologies Toolkit (ETTK), that is, the field categories are based on the emerging technology toolbox (example) , ETTK Bean) was established. In addition, each field category is an abstracted category, that is, the name of the field category is defined by the system developer according to its function, and is inherited from the Google Web Toolkit. Native categories in GWT). Further, in the first preferred embodiment, for the user device 12, the category unit 111 is read by means of a Java script language.

The memory unit 122 is a dynamic random access memory (DRAM) and includes a plurality of memory blocks. Each memory block corresponds to a memory interval of the dynamic random access memory (eg, memory addresses E000 to EFFF).

The execution unit 112 is a runtime program that can be loaded and executed by the user device 12, and includes a plurality of execution programs for the user device 12. Instructions. After the user device 12 executes the instructions, one of the memory blocks forms a runtime environment (Runtime Environment) for parsing the extensible markup language file.

The user interface unit 121 includes a browser 1211, a user interface 1212, and a check program 1213. The check program 1213 is developed based on the emerging technology toolkit. The user interface 1212 is used to generate the user input screen, and is also developed based on the emerging technology toolbox. The browser 1211 is configured to present the user input screen. In the first preferred embodiment, the browser 1211 is one of the existing IE (version 9.0), FireFox, Google Chrome, Safari, and Dolphin HD.

The interaction between the server device 11, the user device 12, the category unit 111, the execution unit 112, the user interface unit 121, and the memory unit 122 is further described below by a user input screen generating method. .

As shown in step S20, the user device 12 downloads and executes the execution unit 112 from the server device 11 via the network. In the first preferred embodiment, the user device 12 can download the execution unit 112 via a wired network or a wireless network.

In addition, the concept of the first preferred embodiment prefers the "Rich Client" concept, that is, the user device 12 is officially compared to the existing non-synchronized Java scripting language and the extensible markup language architecture. Before the operation, all the required data and files, such as the running program and the extensible markup language file, need to be downloaded from the server device 11.

As shown in step S21, the user interface unit 121 of the user device 12 parses the category unit 111 downloaded from the server device 11 at a file location of the pair of execution units 112 to generate a category of material. Moreover, the file location is one of the memory blocks of the memory unit. That is, the user device 12 also downloads the category unit 111 through the network, and the time point of downloading the category unit 111 may be earlier than the time point when the execution unit 112 is downloaded, or may be later than the time when the execution unit 112 is downloaded. point. The category information includes a number of fields corresponding to the category of the field. These fields are based on the native categories of the Guge Network Toolbox (ie, GWT Beans). It is to be noted that the verification program 1213 can also be stored in the server device 11 for downloading the user device 12 through the network, and is not limited to the preferred embodiment.

That is, after the user device 12 executes the instructions, the user interface unit 121 parses the extensible markup language file in the memory block to generate the fields. However, the correspondence between the execution unit 112 and the file location is easily understood by those skilled in the art, and therefore will not be described herein.

As shown in step S22, the user interface 1212 of the user interface unit 121 generates the user input screen for the user to input based on the category information. The user input screen includes at least one of the fields. Moreover, the user interface 1212 dynamically generates the field and the user input screen through the execution unit 112, that is, the user input screen is not a pre-designed static screen.

In addition, the user interface 1212 is configured to receive a user from the user. Enter an input message entered in the field of the screen and a user event triggered by the user in the field of the user input screen. The input information may be any data, such as an account number and password related to the user's online banking, or the user's identity card number. The user event corresponds to the user's operational behavior on the user input screen. For example, when the user inputs the input information and moves the mouse cursor to the corresponding field, a user event (eg, "OnBlur") for checking the input information may be triggered, or, When the user inputs the input information and presses a "send button" of the user input screen, the user event corresponding to the "send button" (for example, "OnClick") is triggered.

As shown in step S23 and step S24, when the user inputs the input information in the field of the user input screen and triggers the user event, the user interface 1212 calls the user interface unit 121 for checking. The program 1213 checks the input information. That is, the input information is associated with the user's identity card number. When the user inputs the input information on the user input screen and presses the "send button", the execution unit 112 determines whether the input information is needed. For further verification, if the check is required, the user interface 1212 will call the check program 1213. Then, the check program 1213 checks the input information received by the user interface 1212, for example, determines whether the input information conforms to the standard format of the identity card number.

It is worth mentioning that the work of checking the input information can also be performed by the server device 11, and is not limited to the first preferred embodiment. For example, when the user inputs the input information and presses the "send button" on the user input screen, the user device 12 will The input information is transmitted to the server device 11 for reception. Then, the server device 11 checks the input information and transmits the check result to the user device 12 for display by the network. However, the details of the check by the server device 11 are easily understood by those skilled in the art, and therefore will not be described here.

The second preferred embodiment of the user input screen generating system 1 of the present invention also includes the server device 11, and the user device 12. The server device 11 is also used to store the category unit 111 and the execution unit 112. The user device 12 also includes the user interface unit 121 and the memory unit 122. In the second preferred embodiment, the server device 11 is developed by a system developer using a Java language, and the user device 12 is also developed by a system developer using Java language, that is, different from the first comparison described above. In a preferred embodiment, the second preferred embodiment employs a Java architecture. The server device 11 is a computer host, and the user device 12 is also a computer host or a mobile device. In addition, system developers are still using the existing Smart Editor as a tool for development.

The category unit 111 includes an extensible markup language archive having a plurality of pre-established field categories and is developed based on the emerging technology toolkit. In addition, each field category is an abstraction category and inherits from the native category in the library "Swing" of Java's official graphical user interface.

Moreover, the functions of the memory unit 122 and the execution unit 112 are as described in the first preferred embodiment above, and thus are not described again.

The user interface unit 121 includes a Java virtual machine (Java Virtual Machine 1214, the user interface 1212, and the check program 1213. The development mode and function of the check program 1213 and the user interface 1212 are as described in the first preferred embodiment, and therefore will not be described again. The Java virtual machine 1214 is pre-downloaded and installed to the user device 12 and is used to present the user input screen. However, the operation flow and details of the Java Virtual Machine 1214 are easily understood by those skilled in the art, and are not the focus of the present invention, and therefore will not be described here. Further, in the second preferred embodiment, the category unit 111 is read by means of a Java Document Object Model (JDOM).

It is to be noted that the class unit 111 in the second preferred embodiment and the class unit 111 in the first preferred embodiment described above are shareable. In other words, system developers can use the field categories created by the Emerging Technology Toolbox to apply to Javanese architecture and non-synchronized Javascript scripting and extensible markup language architectures, ie, some of the field categories are inherited from Native categories (Beans) in GWT, some of the field categories are inherited from the native categories (Beans) in "Swing". The advantage is that system developers can integrate the Java architecture with a development environment where the asynchronous Java scripting language and the Extensible Markup Language architecture are independent of each other. Moreover, when the development environment is integrated, it also has the Java architecture feature for the asynchronous Javascript scripting language and the Extensible Markup Language architecture. That is, if the system developer wants to develop a new system, it can be properly The new system is developed using the previously created category unit 111 instead of the existing method, such as using the Javascript scripting language at the user device 12, or in conjunction with the HyperText Markup Language (HTML).

In the second preferred embodiment, the interaction between the server device 11, the user device 12, the category unit 111, the execution unit 112, the user interface unit 121, and the memory unit 122 is as described above. The first preferred embodiment is described and will not be described again.

It is worth mentioning that under the existing non-synchronized Java scripting language and extensible markup language architecture, for the user device 12, the system developer only develops in the Javascript scripting language, and does not combine the extensible markup. The language file and the concept of the operating environment, so the corresponding source code reuse rate is very low. However, with the present invention, system developers can fully utilize the field categories established during the development process under the existing non-synchronized Java scripting language and extensible markup language architecture.

For example, when a system developer wants to develop a teller system dedicated to different banks, the user terminal 12 can use the field categories established in the teller system of a bank that has been developed to develop other bank exclusive The teller system does not need to rewrite the source code to reproduce the source code. In addition, the check program 1213 can be reused without rewriting the source code, that is, the check program 1213 can be run under the non-synchronized Java scripting language and the extensible markup language architecture, or can be run under the Java architecture.

In summary, this category unit can be applied to both Java architecture and non-synchronized Java scripting language and extensible markup language architecture, so system developers can integrate different architecture development environments, and in asynchronous Java scripts When developing a new system under the Language and Extensible Markup Language architecture, combine the extensible markup language file with the concept of the runtime environment and use The established field category development, rather than rewriting the source code, does achieve the object of the present invention.

The above is only the preferred embodiment of the present invention, and the scope of the invention is not limited thereto, that is, the simple equivalent changes and modifications made by the scope of the invention and the description of the invention are All remain within the scope of the invention patent.

1‧‧‧User input screen generation system

11‧‧‧Server device

111‧‧‧Category

112‧‧‧Execution unit

12‧‧‧User device

121‧‧‧User interface unit

1211‧‧‧Browser

1212‧‧‧User interface

1213‧‧Checking program

1214‧‧‧Java virtual machine

122‧‧‧ memory unit

1 is a system diagram illustrating a first preferred embodiment of a user input screen generating system of the present invention; FIG. 2 is a system diagram illustrating a second preferred embodiment of the user input screen generating system of the present invention; 3 is a flowchart illustrating a user input screen generating method corresponding to the user input screen generating system of the present invention.

1‧‧‧User input screen generation system

11‧‧‧Server device

111‧‧‧Category

112‧‧‧Execution unit

12‧‧‧User device

121‧‧‧User interface unit

1211‧‧‧Browser

1212‧‧‧User interface

1213‧‧Checking program

122‧‧‧ memory unit

Claims (8)

A user input screen generating system comprising: a server device for storing a category unit and an execution unit; and a user device comprising a user interface unit for generating a user input screen; wherein the user device After downloading the category unit and the execution unit through the network and executing the execution unit, the user interface unit parses the category unit at a file location of the pair of execution units to generate a category information, and generates a category according to the category data. The user input screen is input by the user, and the user interface unit includes a check program. When the user inputs an input message on the user input screen and triggers a user event, the user interface unit calls The checker checks the input information. The user input screen generating system according to claim 1, wherein the user device further comprises a memory unit including a plurality of memory blocks, wherein the file location is one of the memory blocks. The category unit includes an eXtensible Markup Language file having a plurality of pre-established field categories, the category material including a plurality of fields corresponding to the field category, the execution unit including a plurality of instructions After the user device executes the instructions, the user interface unit parses the extensible markup language file in the memory block to generate the fields, and the user input screen includes at least the fields. One, and the user inputs the input information in the field. User input screen generation system according to item 2 of the patent application scope The user interface unit includes a browser and a user interface, the browser is configured to display the user input screen, and the user interface generates the user input screen and receives the user's use. Inputting the input information input by the field of the screen and the user event triggered by the user in the field of the user input screen, and the user interface receives the input information and the user event, Call the checker to check the input information. The user input screen generating system according to claim 2, wherein the user interface unit comprises a Java Virtual Machine and a user interface, and the Java virtual device is configured to present the user input screen. The user interface generates the user input screen, and receives the input information input by the user in the field of the user input screen, and the user triggered by the user in the field of the user input screen An event, and the user interface calls the check program to check the input information after receiving the input information and the user event. A user input screen generating method is applicable to a server device and a user device, wherein the server device is configured to store a category unit and an execution unit, and the user device includes a user interface having a check program. The user input screen generating method comprises the following steps: (A) the user device downloads and executes the execution unit through a network; and (B) the user interface unit is in a pair of execution unit files The location location is downloaded from the server unit of the server device to generate a category of data; (C) the user interface unit generates a user input screen for user input based on the category information; and (D) when used After inputting an input message and triggering a user event on the user input screen, the user interface unit calls the check program to check the input information. The user input screen generating method according to claim 5, wherein the user device further comprises a memory unit including a plurality of memory blocks, wherein the file location is one of the memory blocks. The category unit includes an eXtensible Markup Language file having a plurality of pre-established field categories, the category material including a plurality of fields corresponding to the field category, the execution unit including a plurality of instructions After the user device executes the instructions, the user interface unit parses the extensible markup language file in the memory block to generate the fields, and the user input screen includes at least the fields. One, and the user inputs the input information in the field. The user input screen generating method according to the sixth aspect of the invention, wherein the user interface unit comprises a browser and a user interface, the browser is configured to present the user input screen, the user The interface generates the user input screen, and receives the input information input by the user in the field of the user input screen, and the user event triggered by the user in the field of the user input screen, and the user event After receiving the input information and the user event, the user interface Call the checker to check the input information. The user input screen generating method according to claim 6, wherein the user interface unit comprises a Java Virtual Machine and a user interface, and the Java virtual device is configured to present the user input screen. The user interface generates the user input screen, and receives the input information input by the user in the field of the user input screen, and the user triggered by the user in the field of the user input screen An event, and the user interface calls the check program to check the input information after receiving the input information and the user event.