Evaluation page generation method and device, electronic equipment and storage medium
Patent Information
- Application Number
- CN202211640815.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2022-12-20
- Publication Date
- 2026-09-22
- Estimated Expiration
- 2042-12-20
AI Technical Summary
现有的这种仅完成组件信息封装调用的模式，对教师测评系统情景测评任务中，相同组件信息存在大量反复的展示，每次展示拥有不同属性状态和数据的情况下，无法提升研发效率和可维护性
[0051]本申请实施例中，通过调用渲染器获取目标用户访问测评任务时输入的用户数据，基于预先加载的JsonSchema规则对用户数据进行处理，得到测试任务所需的配置数据，以及配置数据对应的逻辑运算结果，对配置数据和逻辑运算结果进行渲染处理，生成测评页面。本申请实施例基于JsonSchema通过将页面组件信息和业务逻辑按照一定的规则进行配置化，以及根据测评场景封装的支持条件渲染、布尔逻辑、比较和算术表达式、动态函数以及HTML和第三方组件信息的渲染的全局统一Render，可以用少量的配置，代替大量重复的页面组件信息代码编写，实现一个页面上百个测评场景的高动态性的测评任务进行灵活快速研发，极大的提高了组件信息的复用性和研发效能，同时降低了维护成本。
Smart Images
Figure CN116149651B_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of page development technology, and in particular to a method, apparatus, electronic device and storage medium for evaluating page generation. Background Technology
[0002] In the current development of scenario-based assessment tasks in teacher assessment systems, there are numerous, discrete, variable, and repetitive requirements. During the development process, it is impossible to translate the assessment task requirements proposed by expert teachers in educational and teaching scenarios, which consumes a large amount of software development resources and causes slow progress in software engineering development.
[0003] To address the highly customized nature of scenario-based assessment tasks in teacher evaluation systems, technologies such as micro-frontends, component informatization, and JSON Schema are used to highly abstract the original assessment task component information, interface information, and behavior modules. This allows for centralized and unified management of various discrete system engineering configurations. The technical solution, combined with the component informatization abstraction feature, centrally encapsulates scenario-based assessment task activities, assessment scenarios, APIs (Application Programming Interfaces), functions, data states, and data collection forms into a stateless framework. Internally, highly accurate component information and behavior renderers are developed; externally, a fixed JSON Schema reference method is provided, reducing the difficulty of production and increasing product reusability.
[0004] With the increasing number of scenario-based assessment tasks in teacher evaluation systems, the rapid development and maintenance of assessment tasks that possess a large amount of identical component information yet are highly customized in detail has become an important research direction. JSONSchema, a descriptive language constraint, defines a set of vocabulary and rules for more effectively annotating and validating JSON documents. By finely encapsulating component information, behaviors, and requests in three dimensions—pre-processing, mid-processing, and post-processing—and binding them during rendering through corresponding relationships throughout the page lifecycle, using JSONSchema—which replaces code writing with configuration encapsulation—and corresponding scenario-based renderers, can effectively improve the efficiency of scenario task development and facilitate version iteration and maintenance.
[0005] Existing reusable front-end page architectures are generally achieved through the abstraction and encapsulation of component information. This involves dividing functionality into multiple small unit components and encapsulating and calling these components. However, this existing model, which only encapsulates and calls component information, fails to improve development efficiency and maintainability in teacher assessment systems where the same component information is repeatedly displayed in scenario-based assessment tasks, with each display having different attribute states and data. Summary of the Invention
[0006] The technical problem to be solved by the embodiments of this application is to provide a method, apparatus, electronic device and storage medium for generating evaluation pages, so as to realize the flexible and rapid development of highly dynamic evaluation tasks with hundreds of evaluation scenarios on a single page, greatly improve the reusability of component information and development efficiency, and reduce maintenance costs.
[0007] In a first aspect, embodiments of this application provide a method for generating an evaluation page, the method comprising:
[0008] Call the renderer to obtain the user data input when the target user accesses the evaluation task;
[0009] The user data is processed based on pre-loaded JsonSchema rules to obtain the configuration data required for the test task, as well as the logical operation results corresponding to the configuration data;
[0010] The configuration data and the logical operation results are rendered to generate an evaluation page.
[0011] Optionally, before calling the renderer to obtain the user data input when the target user accesses the evaluation task, the method further includes:
[0012] The renderer is invoked to obtain the JsonSchema configuration file written by the business personnel;
[0013] Verify the JsonSchema configuration file and obtain the verification result;
[0014] In response to the verification result indicating that the JsonSchema configuration file has passed verification, the JsonSchema rules are generated based on the JsonSchema configuration file.
[0015] Optionally, the step of calling the renderer to obtain the user data input by the target user when accessing the evaluation task includes:
[0016] The renderer is invoked to obtain the text information entered by the target user on the evaluation interface when accessing the evaluation task, and the target object selected by the target user in the evaluation interface.
[0017] The target object and the text information are used as the user data; wherein, the target object includes at least one of: images and animations.
[0018] Optionally, the process of processing the user data based on pre-loaded JSONSchema rules to obtain the configuration data required for the test task, and the logical operation results corresponding to the configuration data, includes:
[0019] The user data is parsed to obtain the data parsing results;
[0020] Based on the data parsing results, determine the interface information corresponding to the assessment task;
[0021] Based on the interface information, load the corresponding component information, obtain the component attribute information of the component information, and bind the component attribute information to the Runtime State;
[0022] The Hooks function is called to inject the component attribute information into the JsonSchema rule;
[0023] Logical operations are performed on the interface information and component information based on the JsonSchema rules to obtain the behavior information and event information corresponding to the component information and interface information.
[0024] Optionally, the step of rendering the configuration data and the logical operation result to generate an evaluation page includes:
[0025] The component information, interface information, behavior information, event information, and component information attributes are attached to the DOM node and the JS worker.
[0026] The renderer is invoked to render the component information, interface information, behavior information, event information, and component information attributes to generate the evaluation page.
[0027] Secondly, embodiments of this application provide an evaluation page generation apparatus, the apparatus comprising:
[0028] The user data acquisition module is used to call the renderer to obtain the user data input by the target user when accessing the evaluation task.
[0029] The configuration data acquisition module is used to process the user data based on pre-loaded JsonSchema rules to obtain the configuration data required for the test task, as well as the logical operation results corresponding to the configuration data;
[0030] The evaluation page generation module is used to render the configuration data and the logical operation results to generate the evaluation page.
[0031] Optionally, the device further includes:
[0032] The configuration file retrieval module is used to call the renderer to retrieve the JsonSchema configuration file written by the business personnel;
[0033] The verification result acquisition module is used to verify the JsonSchema configuration file and obtain the verification result.
[0034] The JsonSchema rule generation module is used to generate the JsonSchema rules based on the JsonSchema configuration file in response to the verification result indicating that the JsonSchema configuration file has passed verification.
[0035] Optionally, the user data acquisition module includes:
[0036] The text object acquisition unit is used to call the renderer to acquire the text information entered by the target user in the assessment interface when accessing the assessment task, and the target object selected by the target user in the assessment interface.
[0037] The user data acquisition unit is used to use the target object and the text information as the user data; wherein the target object includes at least one of the following: images and animations.
[0038] Optionally, the configuration data acquisition module includes:
[0039] The data parsing result acquisition unit is used to parse the user data and obtain the data parsing result;
[0040] The interface information determination unit is used to determine the interface information corresponding to the evaluation task based on the data parsing results.
[0041] The information binding unit is used to load the corresponding component information according to the interface information, obtain the component attribute information of the component information, and bind the component attribute information to the Runtime State;
[0042] The information injection unit is used to call Hooks functions to inject the component attribute information into the JsonSchema rules;
[0043] The behavior event acquisition unit is used to perform logical operations on the interface information and the component information based on the JsonSchema rules to obtain the behavior information and event information corresponding to the component information and the interface information.
[0044] Optionally, the evaluation page generation module includes:
[0045] An information mounting unit is used to mount the component information, the interface information, the behavior information, the event information, and the component information attributes to the DOM node and the JS worker;
[0046] The evaluation page generation unit is used to call the renderer to render the component information, the interface information, the behavior information, the event information and the component information attributes to generate the evaluation page.
[0047] Thirdly, embodiments of this application provide an electronic device, including:
[0048] A processor, a memory, and a computer program stored in the memory and executable on the processor, wherein the processor, when executing the program, implements the evaluation page generation method described above.
[0049] Fourthly, embodiments of this application provide a computer-readable storage medium that, when the instructions in the storage medium are executed by a processor of an electronic device, enables the electronic device to perform the evaluation page generation method described in any of the preceding claims.
[0050] Compared with the prior art, the embodiments of this application have the following advantages:
[0051] In this embodiment, user data input by the target user when accessing the evaluation task is obtained by calling the renderer. Based on pre-loaded JSONSchema rules, the user data is processed to obtain the configuration data required for the test task and the corresponding logical operation results. The configuration data and logical operation results are then rendered to generate the evaluation page. This embodiment, based on JSONSchema, configures page component information and business logic according to certain rules. It also provides a globally unified render based on the evaluation scenario, supporting conditional rendering, Boolean logic, comparisons and arithmetic expressions, dynamic functions, and HTML and third-party component information. This allows for the flexible and rapid development of highly dynamic evaluation tasks with hundreds of evaluation scenarios on a single page, replacing a large amount of repetitive page component information code with minimal configuration. This significantly improves the reusability of component information and development efficiency while reducing maintenance costs.
[0052] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and do not limit this application. Attached Figure Description
[0053] Figure 1 A flowchart illustrating the steps of an evaluation page generation method provided in this application embodiment;
[0054] Figure 2 A flowchart illustrating the steps of a JsonSchema rule generation method provided in this application embodiment;
[0055] Figure 3 A flowchart illustrating the steps of a user data acquisition method provided in this application embodiment;
[0056] Figure 4 A flowchart illustrating the steps of a method for obtaining the result of a logical operation, as provided in an embodiment of this application;
[0057] Figure 5 A flowchart illustrating the steps of another evaluation page generation method provided in this application embodiment;
[0058] Figure 6 A schematic diagram of a JSONSchema rendering process provided for an embodiment of this application;
[0059] Figure 7 A schematic diagram illustrating a JsonSchema rendering sequence provided in an embodiment of this application;
[0060] Figure 8 A schematic diagram of the structure of an evaluation page generation device provided in an embodiment of this application;
[0061] Figure 9 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation
[0062] To make the above-mentioned objectives, features and advantages of this application more apparent and understandable, the application will be further described in detail below with reference to the accompanying drawings and specific embodiments.
[0063] The terminology used in the embodiments of this application is for the purpose of describing particular embodiments only and is not intended to be limiting of this application. The singular forms “a,” “the,” and “the” used in the embodiments of this application and the appended claims are also intended to include the plural forms unless the context clearly indicates otherwise.
[0064] Reference Figure 1 The flowchart illustrates the steps of an evaluation page generation method provided in an embodiment of this application, such as... Figure 1 As shown, the method for generating the evaluation page may include steps 101, 102, and 103.
[0065] Step 101: Call the renderer to obtain the user data entered by the target user when accessing the evaluation task.
[0066] This application embodiment can be based on JsonSchema to configure page component information and business logic according to certain rules, and in a globally unified rendering scenario that supports conditional rendering, Boolean logic, comparison and arithmetic expressions, dynamic functions, and the rendering of HTML and third-party component information, according to the evaluation scenario.
[0067] JsonSchema (which describes your JSON data format): It uses keywords and data types to set detailed and flexible rules for all the graphical interfaces and business logic in the teacher assessment system, including a large number of assessment scenarios, component information, behaviors, tracking points, and 3D models. This ensures that any element in the assessment task can be described by JsonSchema, and only JSON that meets the JsonSchema rules can be rendered and loaded.
[0068] The Renderer reads and parses the JSON file configured according to the JsonSchema, initializing five modules: interface information, component information, behavior, events, and runtime state. Interface information attributes include three parts: pre-invocation, post-invocation, and post-invocation. Component information attributes include five parts: general component information, custom component information, component information state, component information style, and component information behavior. Behaviors include interface information behavior, component information behavior, and runtime behavior awaiting event invocation. Events include lifecycle, click, close, and timed JavaScript events. Runtime state is an abstract integration of the state of all interface information, component information, and behaviors at runtime, and is bidirectionally bound to the State variable.
[0069] In this embodiment, JsonSchema rules can be pre-loaded in the Renderer. These JsonSchema rules can be generated by business personnel configuring corresponding files. The generation process of JsonSchema rules can be combined with... Figure 2 The following is a detailed description.
[0070] Reference Figure 2 The flowchart illustrates the steps of a JSONSchema rule generation method provided in an embodiment of this application, as shown below. Figure 2 As shown, the JsonSchema rule generation method may include steps 201, 202 and 203.
[0071] Step 201: Call the renderer to obtain the JsonSchema configuration file written by the business personnel.
[0072] In this embodiment, when generating JsonSchema rules, business personnel can write JsonSchema configuration files. Business personnel can define interface information, call information between interface information, component information required for interface information calls, and other content in the JsonSchema configuration files.
[0073] After the business personnel write the JSONSchema configuration file, they can send the written JSONSchema configuration file to the renderer.
[0074] After the renderer is invoked to obtain the JSONSchema configuration file written by the business personnel, step 202 is executed.
[0075] Step 202: Verify the JsonSchema configuration file and obtain the verification result.
[0076] After the renderer obtains the JSONSchema configuration file written by the business personnel, the JSONSchema can be validated to obtain the validation results. Specifically, it can be checked whether there is any non-compliant code in the JSON program within the JSONSchema configuration file, and the corresponding validation results can be obtained.
[0077] After obtaining the verification result from the JsonSchema configuration file, proceed to step 203.
[0078] Step 203: In response to the verification result indicating that the JsonSchema configuration file has passed verification, generate the JsonSchema rules according to the JsonSchema configuration file.
[0079] After obtaining the verification result of the JsonSchema configuration file, it can be determined whether the verification result indicates that the JsonSchema configuration file has passed verification.
[0080] If the validation result indicates that the JsonSchema configuration file validation failed, the validation result can be returned to the business personnel, indicating the location in the JsonSchema configuration file that does not conform to the rules, so as to prompt the business personnel to adjust the JsonSchema configuration file.
[0081] If the validation result indicates that the JsonSchema configuration file has passed validation, then JsonSchema rules can be generated based on the JsonSchema configuration file.
[0082] This application embodiment pre-generates JSONSchema rules, thereby enabling rapid analysis of the component information required for user data and the logical call relationship between component information and interface information in subsequent processes, thus improving the generation efficiency of the evaluation page.
[0083] After the renderer generates the JSONSchema rules, the logical operations in the subsequent evaluation page generation process can be executed.
[0084] In practical use, the renderer can be invoked to obtain user data input during the target user's access assessment task. In this example, user data may include: text entered by the user, images and / or animations touched by the user, etc. The process of obtaining user data can be combined with... Figure 3 The following is a detailed description.
[0085] Reference Figure 3 The flowchart illustrates the steps of a user data acquisition method provided in an embodiment of this application, as shown below. Figure 3 As shown, the user data acquisition method may include steps 301 and 302.
[0086] Step 301: Invoke the renderer to obtain the text information entered by the target user on the evaluation interface when accessing the evaluation task, and the target object selected by the target user in the evaluation interface.
[0087] In this embodiment, when a target user wants to perform an assessment task, the interface corresponding to the assessment task can be opened. This interface can display text input boxes, images, animations, and other information. The target user can input the content required for the assessment task, such as the assessment content, in the text input boxes, or touch the images and / or animations to indicate the desired interface information. At this time, the renderer can obtain the text information input by the target user in the assessment interface, as well as the target object (such as an image or animation) selected by the target user in the assessment interface.
[0088] After the renderer is invoked to obtain the text information entered by the target user on the evaluation interface when accessing the evaluation task, and the target object selected by the target user in the evaluation interface, step 302 is executed.
[0089] Step 302: Use the target object and the text information as the user data; wherein the target object includes at least one of the following: images and animations.
[0090] After calling the renderer to obtain the text information entered by the target user in the evaluation interface when accessing the evaluation task, and the target object selected by the target user in the evaluation interface, the target object and text information can be used as user data.
[0091] After the renderer is invoked to obtain the user data entered when the target user accesses the evaluation task, step 102 is executed.
[0092] Step 102: Process the user data based on the pre-loaded JsonSchema rules to obtain the configuration data required for the test task, as well as the logical operation results corresponding to the configuration data.
[0093] In this embodiment, the configuration data may include: component information and the interface information.
[0094] After obtaining the user data input by the target user when accessing the evaluation task through the renderer, the user data can be processed based on pre-loaded JSONSchema rules to obtain the configuration data required for the test task and the corresponding logical operation results. Specifically, the user data can be parsed first to obtain the interface information required by the evaluation task. Then, the corresponding component information can be loaded according to the interface information, and the component information attributes can be bound to the RuntimeState. Then, the Hooks function can be called to inject the component information attributes into the JSONSchema rules for logical operations to obtain the corresponding behavior events. This implementation process can be combined with... Figure 4 The following is a detailed description.
[0095] Reference Figure 4 The flowchart illustrates the steps of a method for obtaining the result of a logical operation according to an embodiment of this application. Figure 4 As shown, the method for obtaining the result of the logical operation may include steps 401, 402, 403, 404 and 405.
[0096] Step 401: Parse the user data to obtain the data parsing result.
[0097] In this embodiment, after obtaining user data, the user data can be parsed to obtain data parsing results. Specifically, during the rendering process, the parsed data acquisition interface can be called during initialization, and the interface environment can be initialized and the request parameters can be encapsulated according to the preceding actions. The calling actions will perform the corresponding interface calls, and the subsequent actions will parse the returned data structure and encapsulate it according to the required format.
[0098] After parsing the user data and obtaining the data parsing results, proceed to step 402.
[0099] Step 402: Based on the data parsing results, determine the interface information corresponding to the evaluation task.
[0100] After parsing the user data to obtain the data parsing results, the interface information corresponding to the assessment task can be determined based on the data parsing results. This interface information is the information of the interface to be called to execute the assessment task.
[0101] After determining the interface information corresponding to the assessment task based on the data parsing results, proceed to step 403.
[0102] Step 403: Based on the interface information, load the corresponding component information, obtain the component attribute information of the component information, and bind the component attribute information to the Runtime State.
[0103] After determining the interface information corresponding to the evaluation task based on the data parsing results, the corresponding component information can be loaded according to the interface information, and the component attribute information can be obtained and bound to the RuntimeState. In the specific implementation, after obtaining the interface information, the corresponding component module can be loaded, the custom component can be rendered, and the general style and custom style can be read to calculate the width, height, position, visibility, animation and other information of all components, which can then be bound to the RuntimeState.
[0104] After obtaining the component property information and binding it to the Runtime State, proceed to step 404.
[0105] Step 404: Call the Hooks function to inject the component attribute information into the JsonSchema rule.
[0106] After obtaining the component attribute information and binding it to the Runtime State, the Hooks function can be called to inject the component attribute information into the JsonSchema rules.
[0107] Step 405: Perform logical operations on the interface information and component information based on the JsonSchema rules to obtain the behavior information and event information corresponding to the component information and interface information.
[0108] After injecting component attribute information into the JSONSchema rules by calling the Hooks function, logical operations can be performed on the interface and component information based on the JSONSchema rules to obtain the corresponding behavior and event information. In the specific implementation, all component and interface behaviors can be extracted and assembled. The Runtime State is injected into the behavior through Hooks to perform runtime logic operations, while simultaneously exposing it to events to await event triggering. Listeners for all events required to implement page behavior are attached to the events. When the page logic runs or the user interacts, the results of the logical operations and the user's interaction content are passed to the listeners and ultimately injected into the behavior processing module.
[0109] After processing the user data based on the pre-loaded JsonSchema rules to obtain the configuration data required for the test task and the logical operation results corresponding to the configuration data, step 103 is executed.
[0110] Step 103: Render the configuration data and the logical operation results to generate an evaluation page.
[0111] After obtaining the configuration data and logical operation results, these data and results can be rendered to generate an evaluation page. This implementation process can be combined with... Figure 5 The following is a detailed description.
[0112] Reference Figure 5 The flowchart illustrates another method for generating an evaluation page provided in an embodiment of this application. Figure 5 As shown, the method for generating the evaluation page may include steps 501 and 502.
[0113] Step 501: Mount the component information, interface information, behavior information, event information, and component information attributes to the DOM node and JS worker.
[0114] In this embodiment, after obtaining component information, interface information, behavior information, event information, component information attributes, and interface information attributes, the component information, interface information, behavior information, event information, component information attributes, and interface information attributes can be mounted to the DOM node and the JS worker.
[0115] After attaching component information, interface information, behavior information, event information, component information attributes, and interface information attributes to the DOM node and JS worker, proceed to step 502.
[0116] Step 502: Call the renderer to render the component information, interface information, behavior information, event information, and component information attributes to generate the evaluation page.
[0117] After mounting component information, interface information, behavior information, event information, component information attributes, and interface information attributes to DOM nodes and JS workers, the renderer can be called to render the component information, interface information, behavior information, event information, and component information attributes to generate the evaluation page.
[0118] This application's embodiments, based on JSONSchema, configure page component information and business logic according to certain rules, and globally unify rendering based on the evaluation scenario, supporting conditional rendering, Boolean logic, comparison and arithmetic expressions, dynamic functions, and HTML and third-party component information rendering. This allows for the flexible and rapid development of highly dynamic evaluation tasks with hundreds of evaluation scenarios on a single page, replacing a large amount of repetitive page component information code with minimal configuration. This greatly improves the reusability of component information and development efficiency, while reducing maintenance costs.
[0119] The above implementation process can be combined with Figure 6The following is a detailed description.
[0120] Reference Figure 6 This diagram illustrates a JSONSchema rendering process provided in an embodiment of this application. Figure 6 As shown, during the JsonSchema rendering process, when initializing the evaluation task, the parsed data acquisition interface can be called, and the interface environment can be initialized and the request parameters can be encapsulated according to the preceding behavior. The calling behavior will perform the corresponding interface call, and the subsequent behavior will parse the returned data structure and encapsulate it according to the required format.
[0121] Load the corresponding component modules, render the custom components, read the general styles and custom styles to calculate the width, height, position, visibility, animation and other information of all components, and bind them to the Runtime State.
[0122] Extract all components, interfaces, and other behaviors and assemble them. Inject runtime state into behaviors via Hook to perform runtime logic calculations, and expose it to events to wait for event triggering.
[0123] The event handler attaches listeners for all events required to implement page behavior. When the page logic runs or the user interacts with the page, the results of the logical operations and the content of the user interaction are passed to the listeners and finally injected into the behavior processing module.
[0124] Components, behaviors, events, and interfaces are attached to DOM nodes and JS workers to render the page and listen for events, thus completing the page rendering operation and generating the evaluation page.
[0125] The development team defines general JSON Schema rules based on business scenario requirements and the contextual assessment tasks of the teacher evaluation system. After the written JSON configuration file passes rule validation, the Renderer executes the configuration file and exposes the rendered page and events to the browser for user access. The Renderer then uses the Runtime State of the user's actions to perform logical calculations on the behaviors in the configuration file and re-renders and displays them to the user. Figure 7 The diagram shows the JsonSchema rendering sequence.
[0126] like Figure 7 As shown, business personnel can first write the JsonSchema, then validate the JsonSchema rules, and if the validation passes, generate JsonSchema rules and load the JsonSchema rules into the renderer.
[0127] When a user accesses an assessment task, user data can be obtained, and a corresponding assessment template can be generated based on the user data. Based on the user data and JsonSchema rules, behavior registration and page rendering can be performed, and the Run Time state is passed in. The JsonSchema performs the operation, modifies the Run Time state, and sends it back to the renderer. The renderer then performs page rendering and event listening on components, behaviors, events, and interfaces to complete the page rendering operation and generate the assessment page.
[0128] The evaluation page generation method provided in this application embodiment obtains user data input by the target user when accessing the evaluation task by calling the renderer, processes the user data based on pre-loaded JSONSchema rules to obtain the configuration data required for the test task and the logical operation results corresponding to the configuration data, and renders the configuration data and logical operation results to generate the evaluation page. This application embodiment, based on JSONSchema, configures page component information and business logic according to certain rules, and provides a globally unified render based on the evaluation scenario, supporting conditional rendering, Boolean logic, comparison and arithmetic expressions, dynamic functions, and HTML and third-party component information rendering. This allows for the flexible and rapid development of highly dynamic evaluation tasks with hundreds of evaluation scenarios on a single page, replacing a large amount of repetitive page component information code with minimal configuration. This greatly improves the reusability of component information and development efficiency, while reducing maintenance costs.
[0129] Reference Figure 8 The diagram shows a structural schematic of an evaluation page generation device provided in an embodiment of this application. Figure 8 As shown, the evaluation page generation device 800 may include the following modules:
[0130] User data acquisition module 810 is used to call the renderer to obtain user data input when the target user accesses the evaluation task.
[0131] The configuration data acquisition module 820 is used to process the user data based on pre-loaded JsonSchema rules to obtain the configuration data required for the test task, as well as the logical operation results corresponding to the configuration data;
[0132] The evaluation page generation module 830 is used to render the configuration data and the logical operation results to generate an evaluation page.
[0133] Optionally, the device further includes:
[0134] The configuration file retrieval module is used to call the renderer to retrieve the JsonSchema configuration file written by the business personnel;
[0135] The verification result acquisition module is used to verify the JsonSchema configuration file and obtain the verification result.
[0136] The JsonSchema rule generation module is used to generate the JsonSchema rules based on the JsonSchema configuration file in response to the verification result indicating that the JsonSchema configuration file has passed verification.
[0137] Optionally, the user data acquisition module 810 includes:
[0138] The text object acquisition unit is used to call the renderer to acquire the text information entered by the target user in the assessment interface when accessing the assessment task, and the target object selected by the target user in the assessment interface.
[0139] The user data acquisition unit is used to use the target object and the text information as the user data; wherein the target object includes at least one of the following: images and animations.
[0140] Optionally, the configuration data acquisition module 820 includes:
[0141] The data parsing result acquisition unit is used to parse the user data and obtain the data parsing result;
[0142] The interface information determination unit is used to determine the interface information corresponding to the evaluation task based on the data parsing results.
[0143] The information binding unit is used to load the corresponding component information according to the interface information, obtain the component attribute information of the component information, and bind the component attribute information to the Runtime State;
[0144] The information injection unit is used to call Hooks functions to inject the component attribute information into the JsonSchema rules;
[0145] The behavior event acquisition unit is used to perform logical operations on the interface information and the component information based on the JsonSchema rules to obtain the behavior information and event information corresponding to the component information and the interface information.
[0146] Optionally, the evaluation page generation module 830 includes:
[0147] An information mounting unit is used to mount the component information, the interface information, the behavior information, the event information, and the component information attributes to the DOM node and the JS worker;
[0148] The evaluation page generation unit is used to call the renderer to render the component information, the interface information, the behavior information, the event information and the component information attributes to generate the evaluation page.
[0149] The evaluation page generation device provided in this application embodiment obtains user data input by the target user when accessing the evaluation task by calling a renderer, processes the user data based on pre-loaded JSONSchema rules to obtain the configuration data required for the test task and the logical operation results corresponding to the configuration data, and renders the configuration data and logical operation results to generate the evaluation page. This application embodiment, based on JSONSchema, configures page component information and business logic according to certain rules, and provides a globally unified render based on the evaluation scenario, supporting conditional rendering, Boolean logic, comparison and arithmetic expressions, dynamic functions, and HTML and third-party component information rendering. This allows for the use of minimal configuration to replace a large amount of repetitive page component information code writing, enabling flexible and rapid development of highly dynamic evaluation tasks with hundreds of evaluation scenarios on a single page. This greatly improves the reusability of component information and development efficiency, while reducing maintenance costs.
[0150] This application also provides an electronic device, including: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program, when executed by the processor, implements the above-described evaluation page generation method.
[0151] Figure 9 A schematic diagram of the structure of an electronic device 900 according to an embodiment of the present invention is shown. Figure 9 As shown, the electronic device 900 includes a central processing unit (CPU) 901, which can perform various appropriate actions and processes according to computer program instructions stored in read-only memory (ROM) 902 or loaded from storage unit 908 into random access memory (RAM) 903. The RAM 903 can also store various programs and data required for the operation of the electronic device 900. The CPU 901, ROM 902, and RAM 903 are interconnected via a bus 904. Input / output (I / O) interface information 905 is also connected to the bus 904.
[0152] Multiple components in electronic device 900 are connected to I / O interface information 905, including: input unit 906, such as keyboard, mouse, microphone, etc.; output unit 907, such as various types of displays, speakers, etc.; storage unit 908, such as disk, optical disk, etc.; and communication unit 909, such as network card, modem, wireless transceiver, etc. Communication unit 909 allows electronic device 900 to exchange information / data with other devices through computer networks such as the Internet and / or various telecommunications networks.
[0153] The various processes and handling described above can be executed by processing unit 901. For example, the methods of any of the above embodiments can be implemented as computer software programs, which are tangibly contained in a computer-readable medium, such as storage unit 908. In some embodiments, part or all of the computer program can be loaded and / or installed on electronic device 900 via ROM 902 and / or communication unit 909. When the computer program is loaded into RAM 903 and executed by CPU 901, one or more actions of the methods described above can be performed.
[0154] Additionally, embodiments of this application also provide a computer-readable storage medium storing a computer program that, when executed by a processor, implements the aforementioned evaluation page generation method.
[0155] The various embodiments in this specification are described in a progressive manner, with each embodiment focusing on the differences from other embodiments. The same or similar parts between the various embodiments can be referred to each other.
[0156] Those skilled in the art will understand that embodiments of this application can be provided as methods, apparatus, or computer program products. Therefore, embodiments of this application can take the form of entirely hardware embodiments, entirely software embodiments, or embodiments combining software and hardware aspects. Furthermore, embodiments of this application can take the form of computer program products implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.
[0157] This application describes embodiments with reference to flowchart illustrations and / or block diagrams of methods, terminals (systems), and computer program products according to embodiments of this application. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing terminal to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing terminal, generate instructions for implementing the flowchart illustrations. Figure 1One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.
[0158] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing terminal to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.
[0159] These computer program instructions can also be loaded onto a computer or other programmable data processing terminal, causing a series of operational steps to be executed on the computer or other programmable terminal to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable terminal for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.
[0160] Although preferred embodiments of the present application have been described, those skilled in the art, upon learning the basic inventive concept, can make other changes and modifications to these embodiments. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments as well as all changes and modifications falling within the scope of the embodiments of the present application.
[0161] Finally, it should be noted that in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or terminal that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or terminal. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or terminal that includes said element.
[0162] The above provides a detailed description of the evaluation page generation method, evaluation page generation device, electronic device, and computer-readable storage medium provided in this application. Specific examples have been used to illustrate the principles and implementation methods of this application. The descriptions of the above embodiments are only for the purpose of helping to understand the method and core ideas of this application. At the same time, for those skilled in the art, there will be changes in the specific implementation methods and application scope based on the ideas of this application. Therefore, the content of this specification should not be construed as a limitation of this application.
Claims
1. A method for generating an assessment page, characterized in that, The method includes: Call the renderer to obtain the user data input when the target user accesses the evaluation task; The user data is processed based on pre-loaded JsonSchema rules to obtain the configuration data required for the test task, as well as the logical operation results corresponding to the configuration data; The configuration data and the logical operation results are rendered to generate an evaluation page; The user data is processed based on pre-loaded JSON Schema rules to obtain the configuration data required for the test task, and the logical operation results corresponding to the configuration data, including: The user data is parsed to obtain the data parsing results; Based on the data parsing results, determine the interface information corresponding to the assessment task; Based on the interface information, load the corresponding component information, obtain the component attribute information of the component information, and bind the component attribute information to the Runtime State; The Hooks function is called to inject the component attribute information into the JsonSchema rule; Logical operations are performed on the interface information and component information based on the JsonSchema rules to obtain the behavior information and event information corresponding to the component information and interface information; The step of rendering the configuration data and the logical operation results to generate an evaluation page includes: The component information, interface information, behavior information, event information, and component information attributes are attached to the DOM node and the JS worker. The renderer is invoked to render the component information, interface information, behavior information, event information, and component information attributes to generate the evaluation page.
2. The method according to claim 1, characterized in that, Before the process of calling the renderer to obtain the user data input during the target user access assessment task, the following steps are also included: The renderer is invoked to obtain the JsonSchema configuration file written by the business personnel; Verify the JsonSchema configuration file and obtain the verification result; In response to the verification result indicating that the JsonSchema configuration file has passed verification, the JsonSchema rules are generated based on the JsonSchema configuration file.
3. The method according to claim 1, characterized in that, The user data input when the renderer is invoked to obtain the target user's access assessment task includes: The renderer is invoked to obtain the text information entered by the target user on the evaluation interface when accessing the evaluation task, and the target object selected by the target user in the evaluation interface. The target object and the text information are used as the user data; wherein, the target object includes at least one of: images and animations.
4. An evaluation page generation device, characterized in that, The device includes: The user data acquisition module is used to call the renderer to obtain the user data input by the target user when accessing the evaluation task. The configuration data acquisition module is used to process the user data based on pre-loaded JsonSchema rules to obtain the configuration data required for the test task, as well as the logical operation results corresponding to the configuration data; The evaluation page generation module is used to render the configuration data and the logical operation results to generate an evaluation page; The configuration data acquisition module includes: The data parsing result acquisition unit is used to parse the user data and obtain the data parsing result; The interface information determination unit is used to determine the interface information corresponding to the evaluation task based on the data parsing results. The information binding unit is used to load the corresponding component information according to the interface information, obtain the component attribute information of the component information, and bind the component attribute information to the Runtime State; The information injection unit is used to call Hooks functions to inject the component attribute information into the JsonSchema rules; The behavior event acquisition unit is used to perform logical operations on the interface information and the component information based on the JsonSchema rules to obtain the behavior information and event information corresponding to the component information and the interface information; The assessment page generation module includes: An information mounting unit is used to mount the component information, the interface information, the behavior information, the event information, and the component information attributes to the DOM node and the JS worker; The evaluation page generation unit is used to call the renderer to render the component information, the interface information, the behavior information, the event information, and the component information attributes to generate the evaluation page.
5. The apparatus according to claim 4, characterized in that, The device further includes: The configuration file retrieval module is used to call the renderer to retrieve the JsonSchema configuration file written by the business personnel; The verification result acquisition module is used to verify the JsonSchema configuration file and obtain the verification result. The JsonSchema rule generation module is used to generate the JsonSchema rules based on the JsonSchema configuration file in response to the verification result indicating that the JsonSchema configuration file has passed verification.
6. The apparatus according to claim 4, characterized in that, The user data acquisition module includes: The text object acquisition unit is used to call the renderer to acquire the text information entered by the target user on the assessment interface when accessing the assessment task, and the target object selected by the target user in the assessment interface. The user data acquisition unit is used to use the target object and the text information as the user data; wherein the target object includes at least one of the following: images and animations.
7. An electronic device, characterized in that, include: A processor, a memory, and a computer program stored in the memory and executable on the processor, wherein the processor, when executing the program, implements the evaluation page generation method of any one of claims 1 to 3.
8. A computer-readable storage medium, characterized in that, When the instructions in the storage medium are executed by the processor of the electronic device, the electronic device is able to perform the evaluation page generation method according to any one of claims 1 to 3.