CN107562496B - Method and device for page configuration and page display - Google Patents
Method and device for page configuration and page display Download PDFInfo
- Publication number
- CN107562496B CN107562496B CN201710598853.3A CN201710598853A CN107562496B CN 107562496 B CN107562496 B CN 107562496B CN 201710598853 A CN201710598853 A CN 201710598853A CN 107562496 B CN107562496 B CN 107562496B
- Authority
- CN
- China
- Prior art keywords
- page
- app
- module
- template
- service information
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Landscapes
- User Interface Of Digital Computer (AREA)
- Stored Programmes (AREA)
Abstract
The application discloses a method and a device for page configuration and page display, in the method, after a configuration request of a page is received, a page module matched with a page module identifier can be determined from preset page modules according to the page module identifier contained in the configuration request, and a page template is configured according to the determined page module.
Description
Technical Field
The present application relates to the field of computer technologies, and in particular, to a method and an apparatus for page configuration and page display.
Background
In order to provide users with better and more convenient services, currently, applications (apps) released by various manufacturers can support calls of other apps, and users can complete processing work of multiple services through one App.
In practical applications, a user may call another App through one App to execute a service, where the called App is referred to as a first App and the called App is referred to as a second App. When the first App calls the second App to execute the service, the second App needs to display the service information of the first App. The second App displays the service information of the first App through a pre-configured page template, and the page template is configured by developers of the second App according to the first App.
Based on the prior art, there is a need for a more efficient way of page configuration.
Disclosure of Invention
The present specification provides a page allocation method, which is used to solve the problem of low efficiency of page allocation in the prior art.
The present specification provides a method of page configuration, comprising:
receiving a configuration request of a page, wherein the page is used for displaying service information of a first application App;
determining a page module identifier contained in the configuration request;
determining a page module corresponding to the page module identification from preset page modules;
and configuring a page template through the determined page module, so that when the first App calls a second App to execute the service, the second App displays the service information of the first App according to the page template.
The present specification provides a page allocation apparatus, which is used to solve the problem of low page allocation efficiency in the prior art.
The present specification provides an apparatus for page configuration, comprising:
the receiving module is used for receiving a configuration request of a page, and the page is used for displaying the service information of the first application App
The identification determining module is used for determining the page module identification contained in the configuration request;
the determining module is used for determining a page module corresponding to the page module identifier from all preset page modules;
and the configuration module is used for configuring a page template through the determined page module so that when the first App calls a second App to execute the service, the second App displays the service information of the first App according to the page template.
The present specification provides a page allocation device, which is used to solve the problem of low page allocation efficiency in the prior art.
The present specification provides a page configuring apparatus, comprising: one or more memories and a processor, the memories storing programs and configured to perform, by the one or more processors:
receiving a configuration request of a page, wherein the page is used for displaying service information of a first application App;
determining a page module identifier contained in the configuration request;
determining a page module corresponding to the page module identification from preset page modules;
and configuring a page template through the determined page module, so that when the first App calls a second App to execute the service, the second App displays the service information of the first App according to the page template.
The present specification provides a page display method, which is used to solve the problem of low efficiency of page allocation in the prior art.
The present specification provides a page display method, including:
the second application App receives a calling request of the first App;
executing the service of the first App according to the calling request, and obtaining the service information of the first App;
acquiring a page template corresponding to the first App;
and displaying the service information through the page template, wherein the page template is configured in advance according to a configuration request of a page for displaying the service information of the first App, the page template comprises at least one page module, and the page module corresponds to a page module identifier contained in the configuration request.
The present specification provides a page display device, which is used to solve the problem of low efficiency of page allocation in the prior art.
This specification provides a device of page show, includes:
the receiving module is used for receiving a calling request of the first App;
the execution module executes the service of the first App according to the calling request and obtains the service information of the first App;
the acquisition module acquires a page template corresponding to the first App;
and the display module displays the service information through the page template, the page template is configured in advance according to a configuration request of a page for displaying the service information of the first App, the page template comprises at least one page module, and the page module corresponds to a page module identifier contained in the configuration request.
The present specification provides a page display client, which is used to solve the problem of low efficiency of page configuration in the prior art.
This specification provides a client for page display, including: one or more memories and a processor, the memories storing programs and configured to perform, by the one or more processors:
receiving a calling request of a first App;
executing the service of the first App according to the calling request, and obtaining the service information of the first App;
acquiring a page template corresponding to the first App;
and displaying the service information through the page template, wherein the page template is configured in advance according to a configuration request of a page for displaying the service information of the first App, the page template comprises at least one page module, and the page module corresponds to a page module identifier contained in the configuration request.
The above-mentioned at least one technical scheme that this application adopted can reach following beneficial effect:
in one or more embodiments of the present specification, after receiving a configuration request for a page, a page module that matches with a page module identifier may be determined from preset page modules according to the page module identifier included in the configuration request, and a page template may be configured according to the determined page module. Due to the fact that various page templates can be obtained through the assembly of the page modules, the method does not need to independently develop the corresponding page template for each first App, and the page template corresponding to each first App can be assembled through the pre-developed page modules. Therefore, the configuration time of each page template is greatly shortened, the cost consumed by configuring the page template is reduced, the flexibility of the configuration of the page template is enhanced, and the configuration efficiency of the page template is improved.
Drawings
The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the application and together with the description serve to explain the application and not to limit the application. In the drawings:
fig. 1A and 1B are schematic diagrams of pages developed by a developer of a second App for two different first apps in the prior art;
fig. 2 is a schematic diagram of a page configuration process provided in an embodiment of the present application;
FIG. 3 is a schematic diagram of the relationship between a page module and a page template provided in the present specification;
FIG. 4 is a schematic process diagram of page display provided in the present specification;
FIG. 5 is a schematic diagram of a page layout apparatus provided herein;
FIG. 6 is a schematic view of a page display apparatus provided herein;
FIG. 7 is a schematic diagram of a page layout apparatus provided in the present specification;
fig. 8 is a schematic diagram of a client side of a page display provided in this specification.
Detailed Description
In the prior art, in order to enable a first App to call a second App to execute a service, developers of the second App need to provide Software Development Kit (SDK), a calling interface and other accessories to developers of the first apps, and also need to independently develop pages corresponding to the first apps according to requirements of the developers of the first apps, as shown in fig. 1A and 1B.
Fig. 1A and 1B are schematic diagrams of pages developed by a developer of a second App for two different first apps in the prior art.
Assuming that the developer B requires, when calling the AppA developed by the developer a to execute the financing service, AppB (AppB is developed by the developer B, i.e. the first App), needs to display a result page in the form of progress + advertisement. The developer a can independently develop the page template shown in fig. 1A according to the requirement of the developer B. In this way, when the subsequent AppB calls the AppA to perform the financial transaction, the obtained result can be displayed through the page template shown in fig. 1A.
FIG. 1B is a page template developed by developer A for the requirements set forth by developer C. When the developer C requests the App C (i.e., the first App developed by the developer C) to call the App a to perform the payment service, the App a can display the final payment result in the page template as shown in fig. 1B, where the page template not only displays the final payment result and the attached advertisement, but also displays the offer information for the payment.
Fig. 1A and 1B illustrate two different forms of page templates, which were developed independently by developer a according to the requirements set forth by developer B, C. In the independent development, even when the developer a develops each page template, the page template needs to be developed from beginning to end according to the needs of the developers (developers who develop other apps). Because the development of each page is independently carried out by developers, the cost consumed by the configuration of the page template is greatly improved, and the configuration efficiency of the page template is reduced.
After receiving a configuration request of a page, a page module matching the page module identifier may be determined from preset page modules according to the page module identifier included in the configuration request, and a page template may be configured according to the determined page module. Due to the fact that various page templates can be obtained through the assembly of the page modules, the method does not need to independently develop the corresponding page template for each first App, and the page template corresponding to each first App can be assembled through the pre-developed page modules. Therefore, the configuration time of each page template is greatly shortened, the cost consumed by configuring the page template is reduced, the flexibility of the configuration of the page template is enhanced, and the configuration efficiency of the page template is improved.
It should be noted that, in this specification, the first App and the second App may be distinguished by a call relationship therebetween, that is, a call to another App to execute a service may be referred to as a first App, and a call to another App to execute a service may be referred to as a second App. Therefore, one App may be the first App or the second App, and which App belongs to may depend on whether the App is in a calling party or a called party in the service execution process. Of course, one second App may correspond to a plurality of first apps, and one first App may also correspond to a plurality of second apps.
In this specification, the function of the page template is that when the first App calls the second App to execute the service, the second App can display the service information of the first App in a certain form through the page template. Therefore, the page template is not an actual page, and the displayed actual page is obtained by adding the service information in the page template.
In this specification, a developer developing a first App may be referred to as a first developer, and a developer developing a second App may be referred to as a second developer.
In order to make those skilled in the art better understand the technical solutions in one or more embodiments of the present disclosure, the technical solutions in one or more embodiments of the present disclosure will be clearly and completely described below with reference to the drawings in one or more embodiments of the present disclosure, and it is obvious that the described embodiments are only a part of the embodiments of the present disclosure, and not all embodiments. All other embodiments obtained by a person skilled in the art based on the embodiments in the present description without making any creative effort shall fall within the protection scope of the present application.
In this specification, an execution subject for executing page allocation may be a server, a terminal, or a system for page allocation, and a page allocation method provided in this specification will be described below by taking the server as the execution subject.
Fig. 2 is a schematic diagram of a page configuration process provided in an embodiment of the present application, which specifically includes the following steps:
s100: a configuration request for a page is received.
When the server corresponding to the second App performs page configuration, the server can perform configuration according to the configuration request sent by the first developer. In this description, the server may provide an interface in which each first developer may fill its own requirements, and the server may receive and determine a configuration request for each page according to the information filled in by the first developer in the interface. The page mentioned here refers to a page in the second App for showing the service information of the first App.
Certainly, the page configuration may also be performed manually, that is, the first developer may notify a second developer configuring the page of its own requirement through a telephone, a mail sending mode, and the like, and the second developer may input a configuration request to the server according to the obtained requirement of the first developer and the requirement of the second developer, and configure the page template in the second App for displaying the service information of the first App.
S102: and determining the page module identification contained in the configuration request.
After receiving the configuration request, the server may further determine each page module identifier included in the configuration request, so as to configure a page template through the page module corresponding to each determined page module identifier in a subsequent process.
In this specification, the server may configure a variety of page templates through preset page modules, where the page templates are various in form, but the page templates may be generally regarded as being composed of some basic page modules, as shown in fig. 3.
Fig. 3 is a schematic diagram of a relationship between a page module and a page template provided in this specification.
For example, taking the example that a first App calls a second App to execute a payment service, although the payment pages displayed after each first App calls the same second App to perform payment processing are different, some payment pages are displayed in the form of progress + benefit + advertisement, and some payment pages are displayed in the form of standard result + service recommendation (the standard result mentioned here refers to directly presenting a final payment result), however, no matter what form each payment page is displayed, each payment page is generally composed of the parts shown in fig. 3.
Therefore, the parts shown in fig. 3 can be modularized to obtain each page module, so that the page template corresponding to the first App can be assembled through each page module according to the actual requirement of the first developer during subsequent page configuration, and the page template does not need to be developed from beginning to end. The different page modules mentioned in the specification show different information forms.
In this specification, the information displayed in the page module can be divided into two types, one is static information of the page, and the information is generally not changed or has a relatively long update period. Generally, the page static information is irrelevant to the service information involved in the service processing, in other words, the page static information is not changed due to the service processing.
For example, in a payment service, when a payment is completed, four words of "payment success" are usually displayed, and the four words are page static information, and no matter what payment service is entered, the four words are displayed by the payment completion, and the four words do not change along with the change of the payment service. For another example, some remark information displayed in the page often does not change with the change of the service, so the remark information that does not change may be referred to as page static information.
Another kind of information that can be displayed in the page module can be called service information, which is opposite to the above-mentioned static information of the page, and the service executed by the service information user has close connection. For example, although each user displays information of successful payment after completing payment, the specific amount paid is different, and the payment amount displayed in the page is the service information after the user performs the payment service. Similarly, the points, the preference information, and the like are all service information.
It should be noted that some information may be regarded as page static information, and may also be regarded as service information. For example, if the first developer requests that the information such as advertisements and service recommendations displayed on the pages last for a certain period of time, that is, the advertisements and service recommendations displayed on the pages are the same during a certain period of time. At this time, the advertisement, service recommendation and other information may be referred to as page static information, i.e. the update period is long. When the information such as advertisement and service recommendation changes due to the service executed by the user, the information may be referred to as service information.
In this specification, some page modules may only display some page static information, and some page modules need to display the page static information and the service information together. For example, in each page module shown in fig. 3, when the page module a (i.e., the standard form) displays information, it is necessary to display page static information such as "successful payment" and business information such as payment amount together. When the page module D (i.e. payment information) displays information, it is also necessary to display static page information such as four words of "payment method" and business information such as specific payment method and payment amount.
S104: and determining a page module corresponding to the page module identification from all preset page modules.
Since each page module is configured in advance, after the server determines each page module identifier included in the configuration request from the configuration request, each page module matched with each page module identifier can be determined from preset page modules.
It should be noted that in this specification, the page modules may be divided into two types, one type may be referred to as a basic page module, and these page modules may display general form information, such as the page modules shown in fig. 3. For some information in specific forms, the basic page modules are not suitable for displaying the information, and for this reason, the personalized page modules are required to display the information in specific forms.
The personalized page module can be configured in advance in a preset form by a second developer in charge of page configuration, and can also be configured by the second developer according to the actual requirements of the first developer. When the configuration request of the page is received by the server, and the first developer needs to show some information in the page in a specific form, a personalized page module suitable for the information in the characteristic form can be configured according to the requirement of the first developer, and the personalized page module is sent to the first developer. When it is determined that the first developer agrees to present the particular form of information to the personalized page module, the personalized page module is configured in a page.
S106: and configuring a page template through the determined page module, so that when the first App calls a second App to execute the service, the second App displays the service information of the first App according to the page template.
And after determining each page module matched with each page module identifier through each page module identifier contained in the configuration request, the server can configure the page template through each determined page module. The page template configured here does not refer to a page that is finally presented by the user when the service is executed. The page template only indicates that when a subsequent user calls a second App to execute the service through the first App, the second App displays the service information of the first App in the form.
Specifically, in this specification, the server may determine, from the configuration request, an arrangement manner of the page module corresponding to each page module identifier in the page template, that is, what manner each page module is arranged in the page template. The server can arrange the page modules in the page template according to the arrangement mode to obtain the page template. The arrangement mode mentioned here may be that the page modules are arranged from top to bottom, or from left to right, or arranged at designated positions in the page template according to other arrangement modes.
The server can send the configured page template to a first developer for checking, when the first developer confirms that the information display is carried out through the page template, the page template and the service in the first App can be correspondingly stored, so that in the subsequent process, when a user calls a second App through the first App to execute the service, the second App displays the service information of the first App through the page template.
In the method, the server can determine each page module for configuring the required page template according to the configuration request of the page, and configure the page template through the determined page modules. In other words, the server can assemble the page templates in various forms corresponding to the first apps through the preset page modules, and the page templates corresponding to the first apps do not need to be independently developed according to the requirements of each first developer, so that the configuration time of the page templates is greatly shortened, the cost consumed by configuring the page templates is reduced, the flexibility of the configuration of the page templates is enhanced, and the configuration efficiency of the page templates is improved.
Since the page form is not a real page, the server needs to display some information (i.e. service information) generated based on the service processing according to the service processing performed by the user, as shown in fig. 4.
Fig. 4 is a schematic view of a page display process provided in this specification, which specifically includes the following steps:
s400: the second App receives the calling request of the first App.
S402: and executing the service of the first App according to the calling request, and obtaining the service information of the first App.
In this specification, when a user calls a second App to execute a service through a first App, the first App may be started through a terminal, and the second App is called through the first App, and the second App receives a call request of the first App, and executes a service corresponding to the first App according to the call request, and obtains service information corresponding to the first App.
S404: and acquiring a page template corresponding to the first App.
The second App can display the service information through a pre-configured page template, wherein the second App can acquire the page template from the server, and the page template can also be pre-stored in the second App.
S406: and displaying the service information through the page template.
After the second App acquires the page template, the second App can further determine a page template corresponding to the service information from the page template, and then add the service information to the corresponding page module for display.
It should be noted that, in the process of executing the service, an information loss situation may occur, and the lost information may not affect the final service execution, but may affect the final information display effect.
Therefore, in this specification, when part of the finally obtained service information is missing due to information loss in the service execution process, the page module that should originally add the missing part of the service information in the page template may hide the missing part of the service information because the missing part of the service information is not added. The second App can hide the page module when monitoring that the page module does not add the part of the service information after the set time. Of course, the second App may hide the page module when monitoring that the page module meets other conditions. And if the situation that the specified field is not added to the page module is monitored, hiding the page module.
In this specification, the server may periodically send a message to the first developer to determine whether the first developer needs to update a page template previously configured by the server. When it is determined that the first developer needs to update the page template, the update information for the page template can be obtained from the first developer, and then the page template is updated according to the update information, and the updated page template is stored.
It should be noted that, in the page configuration method provided in the present specification, a pay field is taken as an example. The page configuration method provided by the present specification is not only applicable to the configuration of pages in a payment scenario, but also applicable to the configuration of pages in other scenarios, and thus, is not illustrated in detail herein.
Based on the same idea, the present specification further provides a page configuring apparatus and a page displaying apparatus, as shown in fig. 5 and 6.
Fig. 5 is a schematic diagram of a page configuration apparatus provided in this specification, which specifically includes:
the receiving module 501 receives a configuration request of a page, where the page is used for displaying service information of a first application App;
an identifier determining module 502, which determines the page module identifier contained in the configuration request;
a determining module 503, configured to determine, from preset page modules, a page module corresponding to the page module identifier;
the configuration module 504 configures a page template through the determined page module, so that when the first App calls a second App to execute a service, the second App displays service information of the first App according to the page template.
The configuration module 504 determines, according to the configuration request, an arrangement manner of each page module corresponding to the page module identifier in the page; and arranging the determined page modules according to the arrangement mode to obtain the page template.
The configuration module 504, when the configuration request includes page static information, determines a page module corresponding to the page static information through a page module identifier corresponding to the page static information; and adding the page static information into a page module corresponding to the page static information to obtain the page template.
Fig. 6 is a schematic view of a page display apparatus provided in this specification, which specifically includes:
the receiving module 601 is used for receiving a calling request of a first App;
the execution module 602 executes the service of the first App according to the call request, and obtains service information of the first App;
the obtaining module 603 is configured to obtain a page template corresponding to the first App;
the presentation module 604 is configured to present the service information through the page template, where the page template is configured in advance according to a configuration request for presenting a page of the service information of the first App, the page template includes at least one page module, and the page module corresponds to a page module identifier included in the configuration request.
The presentation module 604 determines a page module corresponding to the service information in the page template; adding the service information into a corresponding page module for displaying; and hiding the page module which is not added with the service information in the page template.
Based on the above-described page configuration method, the present specification further provides a page configuration device, as shown in fig. 7. The page configuring device includes one or more processors and a memory, the memory storing a program and configured to perform the following steps by the one or more processors:
receiving a configuration request of a page, wherein the page is used for displaying service information of a first application App;
determining a page module identifier contained in the configuration request;
determining a page module corresponding to the page module identification from preset page modules;
and configuring a page template through the determined page module, so that when the first App calls a second App to execute the service, the second App displays the service information of the first App according to the page template.
Based on the above-described page display method, the present specification further provides a page display client, as shown in fig. 8. The page showing client includes one or more processors and memory, the memory storing a program and configured to perform the following steps by the one or more processors:
receiving a calling request of a first App;
executing the service of the first App according to the calling request, and obtaining the service information of the first App;
acquiring a page template corresponding to the first App;
and displaying the service information through the page template, wherein the page template is configured in advance according to a configuration request of a page for displaying the service information of the first App, the page template comprises at least one page module, and the page module corresponds to a page module identifier contained in the configuration request.
In one or more embodiments of the present description, after receiving a configuration request of a page, a page module that matches with a page module identifier may be determined from preset page modules according to the page module identifier included in the configuration request, and a page template may be configured according to the determined page module. Due to the fact that various page templates can be obtained through the assembly of the page modules, the method does not need to independently develop the corresponding page template for each first App, and the page template corresponding to each first App can be assembled through the pre-developed page modules. Therefore, the configuration time of each page template is greatly shortened, the cost consumed by configuring the page template is reduced, the flexibility of the configuration of the page template is enhanced, and the configuration efficiency of the page template is improved.
In the 90 s of the 20 th century, improvements in a technology could clearly distinguish between improvements in hardware (e.g., improvements in circuit structures such as diodes, transistors, switches, etc.) and improvements in software (improvements in process flow). However, as technology advances, many of today's process flow improvements have been seen as direct improvements in hardware circuit architecture. Designers almost always obtain the corresponding hardware circuit structure by programming an improved method flow into the hardware circuit. Thus, it cannot be said that an improvement in the process flow cannot be realized by hardware physical modules. For example, a Programmable Logic Device (PLD), such as a Field Programmable Gate Array (FPGA), is an integrated circuit whose Logic functions are determined by programming the Device by a user. A digital system is "integrated" on a PLD by the designer's own programming without requiring the chip manufacturer to design and fabricate application-specific integrated circuit chips. Furthermore, nowadays, instead of manually making an Integrated Circuit chip, such Programming is often implemented by "logic compiler" software, which is similar to a software compiler used in program development and writing, but the original code before compiling is also written by a specific Programming Language, which is called Hardware Description Language (HDL), and HDL is not only one but many, such as abel (advanced Boolean Expression Language), ahdl (alternate Hardware Description Language), traffic, pl (core universal Programming Language), HDCal (jhdware Description Language), lang, Lola, HDL, laspam, hardward Description Language (vhr Description Language), vhal (Hardware Description Language), and vhigh-Language, which are currently used in most common. It will also be apparent to those skilled in the art that hardware circuitry that implements the logical method flows can be readily obtained by merely slightly programming the method flows into an integrated circuit using the hardware description languages described above.
The controller may be implemented in any suitable manner, for example, the controller may take the form of, for example, a microprocessor or processor and a computer-readable medium storing computer-readable program code (e.g., software or firmware) executable by the (micro) processor, logic gates, switches, an Application Specific Integrated Circuit (ASIC), a programmable logic controller, and an embedded microcontroller, examples of which include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320, the memory controller may also be implemented as part of the control logic for the memory. Those skilled in the art will also appreciate that, in addition to implementing the controller as pure computer readable program code, the same functionality can be implemented by logically programming method steps such that the controller is in the form of logic gates, switches, application specific integrated circuits, programmable logic controllers, embedded microcontrollers and the like. Such a controller may thus be considered a hardware component, and the means included therein for performing the various functions may also be considered as a structure within the hardware component. Or even means for performing the functions may be regarded as being both a software module for performing the method and a structure within a hardware component.
The systems, devices, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions. One typical implementation device is a computer. In particular, the computer may be, for example, a personal computer, a laptop computer, a cellular telephone, a camera phone, a smartphone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.
For convenience of description, the above devices are described as being divided into various units by function, and are described separately. Of course, the functionality of the units may be implemented in one or more software and/or hardware when implementing the present application.
As will be appreciated by one skilled in the art, embodiments of the present description may be provided as a method, system, or computer program product. Accordingly, the description may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the description may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The description has been presented with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to one or more embodiments of the description. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.
Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.
It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
This description may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. One or more embodiments of the specification may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.
The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the system embodiment, since it is substantially similar to the method embodiment, the description is simple, and for the relevant points, reference may be made to the partial description of the method embodiment.
The foregoing description has been directed to specific embodiments of this disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims may be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing may also be possible or may be advantageous.
The above description is merely one or more embodiments of the present disclosure and is not intended to limit the present disclosure. Various modifications and alterations to one or more embodiments of the present description will be apparent to those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of one or more embodiments of the present specification should be included in the scope of claims of the present application.
Claims (10)
1. A method of page configuration, comprising:
receiving a configuration request of a page, wherein the page is used for displaying service information of a first App, the first App is an App for calling other Apps to execute services, the page is a page for displaying the service information of the first App in a second App, and the second App is an App for being called by other Apps to execute services; the configuration request is determined according to requirement information input by a first developer; or the configuration request is input by a second developer according to the requirement of the first developer;
determining a page module identifier contained in the configuration request;
determining a page module corresponding to the page module identification from preset page modules;
determining the arrangement mode of each page module corresponding to the page module identification in the page according to the configuration request;
and arranging the determined page modules according to the arrangement mode to obtain the page template, so that when the first App calls the second App to execute the service, the second App displays the service information of the first App according to the page template, the page template is not an actual page, the displayed actual page is obtained by adding the service information into the page template, and the page template is composed of the page modules.
2. The method according to claim 1, wherein the step of configuring the page template through the determined page module specifically comprises the steps of:
when the configuration request contains page static information, determining a page module corresponding to the page static information through a page module identifier corresponding to the page static information;
and adding the page static information into a page module corresponding to the page static information to obtain the page template.
3. A method for displaying a page comprises the following steps of;
the method comprises the steps that a second App receives a calling request of a first App, the first App is an App calling other App to execute business, and the second App is an App called by other App to execute business;
executing the service of the first App according to the calling request, and obtaining the service information of the first App;
acquiring a page template corresponding to the first App, wherein the page template is not an actual page, the displayed actual page is obtained by adding the service information into the page template, and the page template is composed of the page modules;
displaying the service information through the page template, wherein the page template is configured in advance according to a configuration request of a page for displaying the service information of the first App, the page template comprises at least one page module, and the page module corresponds to a page module identifier contained in the configuration request;
the configuration request is determined according to requirement information input by a first developer; or the configuration request is input by a second developer according to the requirement of the first developer.
4. The method of claim 3, wherein the displaying the service information through the page template specifically comprises:
determining a page module corresponding to the service information in the page template;
adding the service information into a corresponding page module for displaying;
and hiding the page module which is not added with the service information in the page template.
5. An apparatus of page configuration, comprising:
the device comprises a receiving module, a processing module and a display module, wherein the receiving module is used for receiving a configuration request of a page, the page is used for displaying service information of a first App, the first App is an App for calling other Apps to execute services, the page is used for displaying the service information of the first App in a second App, and the second App is an App for being called by other Apps to execute the services; the configuration request is determined according to requirement information input by a first developer; or the configuration request is input by a second developer according to the requirement of the first developer;
the identification determining module is used for determining the page module identification contained in the configuration request;
the determining module is used for determining a page module corresponding to the page module identifier from all preset page modules;
the configuration module is used for determining the arrangement mode of each page module corresponding to the page module identification in the page according to the configuration request; and arranging the determined page modules according to the arrangement mode to obtain the page template, so that when the first App calls a second App to execute the service, the second App displays the service information of the first App according to the page template, the page template is not an actual page, the displayed actual page is obtained by adding the service information into the page template, and the page template is composed of the page modules.
6. The apparatus according to claim 5, wherein the configuration module, when the configuration request includes page static information, determines a page module corresponding to the page static information by a page module identifier corresponding to the page static information; and adding the page static information into a page module corresponding to the page static information to obtain the page template.
7. An apparatus for page presentation, comprising:
the device comprises a receiving module, a processing module and a processing module, wherein the receiving module is used for receiving a calling request of a first App, and the first App is an App for calling other Apps to execute services;
the execution module executes the service of the first App according to the calling request and obtains the service information of the first App;
the acquisition module is used for acquiring a page template corresponding to the first App, wherein the page template is not an actual page, the displayed actual page is obtained by adding the service information into the page template, and the page template is composed of the page modules;
the display module displays the service information through the page template, the page template is configured in advance according to a configuration request of a page for displaying the service information of the first App, the page template comprises at least one page module, and the page module corresponds to a page module identifier contained in the configuration request;
the configuration request is determined according to requirement information input by a first developer; or the configuration request is input by a second developer according to the requirement of the first developer.
8. The apparatus of claim 7, wherein the presentation module determines a page module corresponding to the service information in the page template; adding the service information into a corresponding page module for displaying; and hiding the page module which is not added with the service information in the page template.
9. An apparatus for page configuration, comprising: one or more memories and a processor, the memories storing programs and configured to perform, by the one or more processors:
receiving a configuration request of a page, wherein the page is used for displaying service information of a first App, the first App is an App for calling other Apps to execute services, the page is a page for displaying the service information of the first App in a second App, and the second App is an App for being called by other Apps to execute services; the configuration request is determined according to requirement information input by a first developer; or the configuration request is input by a second developer according to the requirement of the first developer;
determining a page module identifier contained in the configuration request;
determining a page module corresponding to the page module identification from preset page modules;
determining the arrangement mode of each page module corresponding to the page module identification in the page according to the configuration request;
and arranging the determined page modules according to the arrangement mode to obtain the page template, so that when the first App calls a second App to execute the service, the second App displays the service information of the first App according to the page template, the page template is not an actual page, the displayed actual page is obtained by adding the service information into the page template, and the page template is composed of the page modules.
10. A client for page presentation, comprising: one or more memories and a processor, the memories storing programs and configured to perform, by the one or more processors:
receiving a calling request of a first App, wherein the first App is an App calling other App to execute services;
executing the service of the first App according to the calling request, and obtaining the service information of the first App;
acquiring a page template corresponding to the first App, wherein the page template is not an actual page, the displayed actual page is obtained by adding the service information into the page template, and the page template is composed of the page modules;
displaying the service information through the page template, wherein the page template is configured in advance according to a configuration request of a page for displaying the service information of the first App, the page template comprises at least one page module, and the page module corresponds to a page module identifier contained in the configuration request;
the configuration request is determined according to requirement information input by a first developer; or the configuration request is input by a second developer according to the requirement of the first developer.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710598853.3A CN107562496B (en) | 2017-07-21 | 2017-07-21 | Method and device for page configuration and page display |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710598853.3A CN107562496B (en) | 2017-07-21 | 2017-07-21 | Method and device for page configuration and page display |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107562496A CN107562496A (en) | 2018-01-09 |
| CN107562496B true CN107562496B (en) | 2021-03-30 |
Family
ID=60974543
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710598853.3A Active CN107562496B (en) | 2017-07-21 | 2017-07-21 | Method and device for page configuration and page display |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107562496B (en) |
Families Citing this family (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108845749B (en) * | 2018-06-01 | 2021-03-09 | 阿里巴巴（中国）有限公司 | Page display method and device |
| CN109040822B (en) * | 2018-07-16 | 2021-06-22 | 北京奇艺世纪科技有限公司 | Player configuration method and device and storage medium |
| CN109388397B (en) * | 2018-09-26 | 2024-05-03 | 中国平安财产保险股份有限公司 | Product page generation method, system, computer device and storage medium |
| CN111027299A (en) * | 2019-10-18 | 2020-04-17 | 深圳智慧园区信息技术有限公司 | Form generation method and system |
| CN111008058A (en) * | 2019-12-09 | 2020-04-14 | 北京爱奇艺科技有限公司 | Page display method and device |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102637184A (en) * | 2011-02-15 | 2012-08-15 | 北京千橡网景科技发展有限公司 | Method and system for customizing webpages |
| CN105607910A (en) * | 2015-12-22 | 2016-05-25 | 北京奇虎科技有限公司 | Method and apparatus for realizing universal payment front-end service |
| CN106095549A (en) * | 2016-06-07 | 2016-11-09 | 中国建设银行股份有限公司 | The jump method of a kind of Mobile solution App and redirect device |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106569800B (en) * | 2016-10-17 | 2020-10-23 | 北京小米移动软件有限公司 | Front-end interface generation method and device |
-
2017
- 2017-07-21 CN CN201710598853.3A patent/CN107562496B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102637184A (en) * | 2011-02-15 | 2012-08-15 | 北京千橡网景科技发展有限公司 | Method and system for customizing webpages |
| CN105607910A (en) * | 2015-12-22 | 2016-05-25 | 北京奇虎科技有限公司 | Method and apparatus for realizing universal payment front-end service |
| CN106095549A (en) * | 2016-06-07 | 2016-11-09 | 中国建设银行股份有限公司 | The jump method of a kind of Mobile solution App and redirect device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN107562496A (en) | 2018-01-09 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107562496B (en) | Method and device for page configuration and page display | |
| CN107038042B (en) | Service execution method and device | |
| CN107391114B (en) | Page visual rendering method and device | |
| CN111176802B (en) | Task processing method and device, electronic equipment and storage medium | |
| CN107070858B (en) | Service processing method and device | |
| CN109710340B (en) | Software tool calling method and device and software tool packaging method and device | |
| CN107045438B (en) | Application top view processing method, device and component | |
| CN107092475B (en) | Calling method and device of interactive control | |
| CN111796823A (en) | Method and device for updating page and displaying page and page maintenance system | |
| CN107479868B (en) | Interface loading method, device and equipment | |
| CN111639278A (en) | Webpage loading method and device | |
| CN111767499A (en) | Page configuration method and device | |
| CN107528885B (en) | Service request processing method and device | |
| CN110648034A (en) | Method and device for distributing customer service | |
| CN111402058B (en) | Data processing method, device, equipment and medium | |
| CN112862293A (en) | Resource allocation method, device, storage medium and electronic equipment | |
| CN111861454B (en) | Method and device for displaying unique identifier of digital object | |
| CN114331403A (en) | Data processing, resource transfer and payment method, device, equipment and medium | |
| CN113434063B (en) | Information display method, device and equipment | |
| CN110675162A (en) | Contract processing method, device and equipment | |
| CN113342330A (en) | Front-end engineering generation method and device | |
| CN111538667A (en) | Page testing method and device | |
| CN110022351B (en) | Service request processing method and device | |
| CN111443945B (en) | Component code modification method and device | |
| CN107402749B (en) | Method and device for realizing picture loading library |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20200925 Address after: Cayman Enterprise Centre, 27 Hospital Road, George Town, Grand Cayman Islands Applicant after: Innovative advanced technology Co.,Ltd. Address before: Cayman Enterprise Centre, 27 Hospital Road, George Town, Grand Cayman Islands Applicant before: Advanced innovation technology Co.,Ltd. Effective date of registration: 20200925 Address after: Cayman Enterprise Centre, 27 Hospital Road, George Town, Grand Cayman Islands Applicant after: Advanced innovation technology Co.,Ltd. Address before: A four-storey 847 mailbox in Grand Cayman Capital Building, British Cayman Islands Applicant before: Alibaba Group Holding Ltd. |
|
| TA01 | Transfer of patent application right | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |