WO2020020248A1 - 移动端页面构建方法、系统和移动端 - Google Patents

移动端页面构建方法、系统和移动端 Download PDF

Info

Publication number
WO2020020248A1
WO2020020248A1 PCT/CN2019/097553 CN2019097553W WO2020020248A1 WO 2020020248 A1 WO2020020248 A1 WO 2020020248A1 CN 2019097553 W CN2019097553 W CN 2019097553W WO 2020020248 A1 WO2020020248 A1 WO 2020020248A1
Authority
WO
WIPO (PCT)
Prior art keywords
floor
page
template
mobile terminal
configuration data
Prior art date
Application number
PCT/CN2019/097553
Other languages
English (en)
French (fr)
Inventor
李俊涛
Original Assignee
北京京东尚科信息技术有限公司
北京京东世纪贸易有限公司
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by 北京京东尚科信息技术有限公司, 北京京东世纪贸易有限公司 filed Critical 北京京东尚科信息技术有限公司
Publication of WO2020020248A1 publication Critical patent/WO2020020248A1/zh

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/30Creation or generation of source code
    • G06F8/38Creation or generation of source code for implementing user interfaces
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44Arrangements for executing specific programs
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00Commerce
    • G06Q30/06Buying, selling or leasing transactions
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00Commerce
    • G06Q30/06Buying, selling or leasing transactions
    • G06Q30/0601Electronic shopping [e-shopping]
    • G06Q30/0641Shopping interfaces

Definitions

  • the present disclosure relates to the field of mobile Internet, and in particular, to a method, system, and mobile terminal page construction method.
  • the mobile terminal list interface includes a list display interface for e-commerce search, classification, product details, and application markets. For different business needs, the contents displayed by each member of the list are different. During the basic development process, every time the status of a member changes, the content of the original list needs to be changed and maintained.
  • a technical problem to be solved by the present disclosure is to provide a method, a system and a mobile terminal for building a mobile page, which can solve the requirement for page maintenance due to high-frequency business requirements in the current agile development process.
  • a method for constructing a mobile page includes: receiving floor template configuration data issued by a server, wherein the floor template configuration data includes a list of floor identifiers; traversing the floor template configuration data, and Corresponding relationship, select the corresponding template entity for each floor; generate template data corresponding to each floor according to the template entity; create a floor entity class list according to the template data, so as to construct each floor on the page according to the floor entity class list.
  • the method further includes: judging whether each floor needs to be displayed on the page; setting a flag bit of each floor according to the judgment result, the flag bit is used to identify whether each floor is displayed on the page; Each floor flag generates a floor display list to display each floor on the page according to the floor display list.
  • the method further includes: judging whether a new floor needs to be added according to business requirements; if new floors need to be added, obtaining new floor information, wherein the new floor information includes a floor identifier; and adding the floor in the new floor information The identifier is compared with the floor identifier in the floor display list to determine the position of the new floor on the page; according to the position of the new floor on the page, a new floor is inserted into the page.
  • the method further includes: judging whether to delete the predetermined floor according to business requirements; if it is necessary to delete the predetermined floor, determining the position of the predetermined floor on the page according to the floor identifier of the predetermined floor; and according to the position of the predetermined floor on the page To delete the reserved floor from the page.
  • the floor template configuration data further includes floor dividing line information
  • the method further includes: if at least one floor between adjacent floors is in a hidden mode, merging the floor dividing lines of adjacent floors.
  • the method further includes: dividing different business units into different floors according to attribute information between the business units in the page.
  • the attribute information between the business units includes at least one of a sequential logical relationship, a functional relationship, a coupling relationship, and a content relationship.
  • the floor template configuration data previously downloaded from the server is read locally in response to the page construction request; or the floor template configuration data is obtained at the server in response to the page construction request.
  • a mobile terminal including: a configuration data receiving unit configured to receive floor template configuration data issued by a server, wherein the floor template configuration data includes a floor identification list; a template entity selection unit , Is configured to traverse the floor template configuration data, select the corresponding template entity for each floor according to the correspondence between the floor identifier and the template entity; the template data generating unit is configured to generate the template data corresponding to each floor according to the template entity; list generation The unit is configured to create a floor entity class list according to the template data, so that each floor is displayed on the page according to the floor entity class list.
  • the mobile terminal further includes: a display judging unit configured to judge whether each floor needs to be displayed on the page; a flag bit setting unit configured to set a flag bit of each floor according to the judgment result, and the flag bit is used for It is used to identify whether each floor is displayed on the page; the list generating unit is further configured to add a floor flag to the floor entity class list to generate a floor display list, so as to display each floor on the page according to the floor display list.
  • the mobile terminal further includes: a floor addition / deletion determination unit configured to determine whether a new floor needs to be added according to business requirements; and a position determination unit configured to obtain new floor information if a new floor needs to be added, where The new floor information includes the floor identifier.
  • the floor identifier in the new floor information is compared with the floor identifier in the floor display list to determine the position of the new floor on the page.
  • the floor addition and deletion execution unit is configured to Position in the page to insert a new floor into the page.
  • the floor addition / deletion determination unit is further configured to determine whether a predetermined floor needs to be deleted according to business requirements; the position determination unit is further configured to determine that the predetermined floor is on the page according to the floor identification of the predetermined floor if the predetermined floor needs to be deleted.
  • the floor addition / deletion execution unit is also configured to delete the predetermined floor from the page according to the position of the predetermined floor on the page.
  • the floor template configuration data further includes floor dividing line information
  • the mobile terminal further includes: a dividing line processing unit configured to, if at least one floor between adjacent floors is in a hidden mode, the floor of the adjacent floor Dividing lines merge.
  • the mobile terminal further includes: a floor splitting unit configured to divide different business units into different floors according to attribute information between the business units on the page.
  • the attribute information between the business units includes at least one of a sequential logical relationship, a functional relationship, a coupling relationship, and a content relationship.
  • the configuration data receiving unit is configured to locally read the floor template configuration data previously downloaded from the server in response to the page construction request; or is configured to obtain the floor template configuration data at the server in response to the page construction request.
  • a mobile terminal including: a memory; and a processor coupled to the memory, the processor being configured to execute the mobile-side page construction method as described above based on instructions stored in the memory.
  • a mobile page construction system which includes a server and the mobile terminal described above; wherein the server is configured to send the floor template configuration data to the mobile terminal.
  • a computer-readable storage medium is further provided with computer program instructions stored thereon, which are executed by a processor to implement the above-mentioned method for building a mobile page.
  • the idea of “Lego building blocks” is used to achieve the purpose of random page construction.
  • the pages are divided into as small independent floors as possible, and the required floors are configured to form floor-level pages. Meet the requirements for page maintenance due to high-frequency business needs in the current agile development process.
  • FIG. 1 is a schematic flowchart of some embodiments of a method for constructing a mobile terminal page according to the present disclosure.
  • FIG. 2 is a schematic flowchart of another embodiment of a mobile terminal page construction method according to the present disclosure.
  • FIG. 3 is a schematic flowchart of another embodiment of a method for constructing a mobile terminal page according to the present disclosure.
  • FIG. 4 is a schematic flowchart of another embodiment of a method for constructing a mobile terminal page according to the present disclosure.
  • FIG. 5 is a schematic structural diagram of some embodiments of a mobile terminal of the present disclosure.
  • FIG. 6 is a schematic structural diagram of another embodiment of a mobile terminal of the present disclosure.
  • FIG. 7 is a schematic structural diagram of still another embodiment of a mobile terminal of the present disclosure.
  • FIG. 8 is a schematic structural diagram of still another embodiment of a mobile terminal of the present disclosure.
  • FIG. 9 is a schematic structural diagram of some embodiments of a mobile-side page construction system of the present disclosure.
  • any specific value should be construed as exemplary only and not as a limitation. Therefore, other examples of the exemplary embodiments may have different values.
  • FIG. 1 is a schematic flowchart of some embodiments of a method for constructing a mobile terminal page according to the present disclosure. The method in this embodiment is executed by a mobile terminal.
  • step 110 the floor template configuration data issued by the server is received, wherein the floor template configuration data includes a floor identification list.
  • the server can send the floor template configuration data to the mobile terminal through independent nodes in the display order through a dynamic interface, and the floor identifier can identify the floor display order.
  • step 120 the floor template configuration data is traversed, and a corresponding template entity is selected for each floor according to the correspondence between the floor identifier and the template entity.
  • the mobile terminal locally stores the correspondence between mId (floor identification) and template (template) entities, traverses the template data issued by the server, and selects the corresponding template entity for each floor.
  • step 130 template data corresponding to each floor is generated according to the template entity.
  • a floor entity class list is created according to the template data, so that each floor is constructed in the page according to the floor entity class list.
  • the pages are divided into as small independent floors as possible, and the required floors are configured to form floor-level pages, which can meet the requirements for page maintenance due to high-frequency business requirements in the current agile development process.
  • FIG. 2 is a schematic flowchart of another embodiment of a mobile terminal page construction method according to the present disclosure.
  • the floor template configuration data issued by the server is received, where the floor template configuration data includes a floor identification list.
  • the floor identification list can reflect floor style information.
  • the process can be implemented in two ways. For example, the mobile terminal responds to the page construction request and locally reads the floor template configuration data downloaded from the server in advance. The mobile terminal can quickly respond to user operations. Alternatively, the mobile terminal obtains the floor template configuration data from the server in response to the request for building a page. For example, the mobile terminal supports JS calls, and uses native assembly components such as Weex to send floor template configuration data to the local through JS calls.
  • the templates are dynamically generated locally, but the use of JS calls requires consideration of loading timing and performance loss.
  • step 220 the floor template configuration data is traversed, and a corresponding template entity is selected for each floor according to the correspondence between the floor identifier and the template entity.
  • step 230 template data corresponding to each floor is generated according to the template entity.
  • step 240 a list of floor entity classes is created based on the template data.
  • step 250 it is determined whether each floor needs to be displayed on the page.
  • the server is not sure whether a certain floor is displayed, and it can set a default delivery, and the mobile terminal determines whether the floor is displayed or hidden. For example, the mobile terminal can determine whether these floors should be displayed on the page by requesting other interfaces.
  • a flag bit of each floor is set according to the judgment result, and the flag bit is used to identify whether each floor is displayed on the page. For example, if a floor needs to be displayed, the floor flag bit is set to true; if it is not required to be displayed, the floor flag bit is set to false.
  • a floor flag corresponding to each floor is added to the floor entity class list to generate a floor display list, so that each floor is displayed on the page according to the floor display list. Iterate through all the floors, generate the floor display list, find out all the floors whose flag bit is true according to the floor display list, start creating real floors, and display the data. By setting the flag bit, the floor can be positioned more accurately.
  • the mobile terminal selects the corresponding template entity to generate the template data corresponding to each floor, and sets the flag bit of each floor according to whether each floor needs to be displayed on the page.
  • the floor flags corresponding to each floor are added to generate a floor display list, so that each floor can be displayed on the page according to the floor display list. Since the page is split into independent floors, each can be configured separately For floors, the process of modifying the list becomes a process of maintaining a single floor, so that it can meet the realization of complex services without having to maintain all the list contents.
  • FIG. 3 is a schematic flowchart of another embodiment of a method for constructing a mobile terminal page according to the present disclosure.
  • step 310 the mobile terminal determines whether a new floor needs to be added according to the service requirements.
  • the server will return part of the floor data and some floor data through the main interface, and the mobile terminal needs to obtain it through other interfaces.
  • step 320 if a new floor needs to be added, the new floor information is acquired, where the new floor information includes a floor identifier.
  • the floor ID identifies the position of the floor on the page.
  • the floor identifier in the new floor information is compared with the floor identifier in the floor display list to determine the position of the new floor on the page. For example, if the floor identifier in the new floor information is the last floor, then the new floor can be added to the last floor position on the page. If the floor identifier in the new floor information is the third floor, but there is already a third floor in the floor display list, the new floor will be set at the original third floor position according to the pre-arrangement, and the original third floor to the Nth floor. Modify from the fourth floor to the N + 1th floor in turn. Or the new floor position is set to the next floor of the original third floor, that is, the fourth floor position, and the original fourth floor to the Nth floor are modified to the fifth floor to the N + 1th floor in turn.
  • step 340 a new floor is inserted in the page according to the position of the new floor in the page.
  • the mobile terminal can insert the floor in the page, that is, the mobile terminal can quickly respond to the demand, and friendly output the development capabilities to third parties, which can effectively support the main logic.
  • the development of various complex business needs is realized.
  • FIG. 4 is a schematic flowchart of another embodiment of a method for constructing a mobile terminal page according to the present disclosure.
  • step 410 it is determined whether the predetermined floor needs to be deleted according to the business requirements.
  • step 420 if the predetermined floor needs to be deleted, the position of the predetermined floor on the page is determined according to the floor identifier of the predetermined floor.
  • step 430 the predetermined floor is deleted from the page according to the position of the predetermined floor on the page.
  • a predetermined floor can be deleted from the page, but the entire page content will not be affected, which facilitates page maintenance.
  • different business units may be divided into different floors as required, that is, minimized floors. That is, different business units are divided into different floors according to the attribute information between the business units on the page.
  • the attribute information between the business units includes sequential logical relationships, functional relationships, coupling relationships, and content relationships.
  • the price of the product in the page can be The unit and the shopping cart unit are split into different floors.
  • the product details unit and the product price unit have separate functions, so the product details unit and the product price unit in the page can be split into Different floors.
  • the product details unit and the most recently viewed product unit in the page can be split into different floors.
  • the commodity price and the mark-up purchase so the price unit and the mark-up purchase unit in the page can be split into different floors.
  • the process of dismantling the floors can be split from the aspects of sequence logic, function, coupling, content, etc., but there may also be related associations between the floors.
  • the floors are distinguished by dividing lines, but the dividing lines do not belong to a certain floor, and the dividing lines to be displayed need to be determined according to the floors displayed.
  • the dividing line can also be treated as an independent floor.
  • the server sends the floor configuration
  • the corresponding floor dividing line will be sent down, that is, the floor template configuration data also includes the floor dividing line information, but the dividing line issued by the server may It is inaccurate.
  • all the dividing lines are created accordingly, and the flag is set to true by default.
  • an algorithm is performed on the dividing line during the process of traversing the list of floor entity classes. If at least one of the adjacent floors on the mobile page is in hidden mode, the floor dividing lines of the adjacent floors are merged. That is, one of the two dividing lines will be retained by weight because of the hidden floors.
  • FIG. 5 is a schematic structural diagram of some embodiments of a mobile terminal of the present disclosure.
  • the mobile terminal includes a configuration data receiving unit 510, a template entity selecting unit 520, a template data generating unit 530, and a list generating unit 540.
  • the configuration data receiving unit 510 is configured to receive floor template configuration data issued by the server, where the floor template configuration data includes a floor identification list.
  • the server can send the floor template configuration data to the mobile terminal through the independent node in the dynamic interface according to the display order, and the floor identifier can identify the floor display order.
  • the configuration data receiving unit 510 is configured to locally read the floor template configuration data downloaded in advance from the server in response to the page construction request; or is configured to acquire the floor template configuration data on the server in response to the page construction request.
  • the template entity selection unit 520 is configured to traverse the floor template configuration data, and select a corresponding template entity for each floor according to the correspondence between the floor identifier and the template entity.
  • the mobile terminal locally stores the corresponding relationship of the mId-template entity, traverses the template data issued by the server, and selects the corresponding template entity for each floor.
  • the template data generating unit 530 is configured to generate template data corresponding to each floor according to a template entity.
  • the list generating unit 540 is configured to create a floor entity class list according to the template data so that each floor is displayed on the page according to the floor entity class list.
  • the "Lego bricks" idea is used to achieve the purpose of random page construction.
  • the page is divided into as small independent floors as possible, and the required floors are configured to form a floored page that can meet the current agile development process Due to high-frequency business requirements, the requirements for page maintenance.
  • the mobile terminal further includes a display determination unit 610 and a flag setting unit 620.
  • the display determination unit 610 is configured to determine whether each floor needs to be displayed on a page. Among them, the server is not sure whether a certain floor is displayed, and it can set a default delivery, and the mobile terminal determines whether the floor is displayed or hidden. For example, the mobile terminal can determine whether these floors should be displayed on the page by requesting other interfaces.
  • the flag bit setting unit 620 is configured to set a flag bit of each floor according to a determination result, and the flag bit is used to identify whether each floor is displayed on the page. For example, if a floor needs to be displayed, the floor flag bit is set to true; if it is not required to be displayed, the floor flag bit is set to false.
  • the list generating unit 540 is further configured to add a floor flag corresponding to each floor to the floor entity class list, and generate a floor display list, so as to display each floor on the page according to the floor display list.
  • the mobile terminal selects the corresponding template entity, thereby generating template data corresponding to each floor, and setting the flag bit of each floor on the page according to whether each floor needs to be displayed.
  • Create the floor entity class list according to the template data add the floor flags corresponding to each floor, and generate a floor display list so that each floor can be displayed on the page according to the floor display list. Since the page is split into independent floors, each floor can be configured separately. The process of modifying the list becomes a process of maintaining a single floor, so that it can meet the realization of complex services without having to maintain all the list contents.
  • the mobile terminal further includes a floor addition / deletion determination unit 630, a location determination unit 640, and a floor addition / deletion execution unit 650.
  • the floor addition / deletion judging unit 630 is configured to determine whether a new floor needs to be added according to a service requirement.
  • the server will return part of the floor data and some floor data through the main interface, and the mobile terminal needs to obtain it through other interfaces.
  • the position determining unit 640 is configured to obtain new floor information if a new floor is required, wherein the new floor information includes a floor identifier, and the floor identifier in the new floor information is compared with the floor identifier in the floor display list to determine The position of the new floor on the page.
  • the floor ID is used to identify the position of the floor on the page. If the floor identification in the new floor information is the last floor, then the new floor can be added to the last floor position on the page. If the floor identifier in the new floor information is the third floor, but there is already a third floor in the floor display list, the new floor will be set at the original third floor position according to the pre-arrangement, and the original third floor to the Nth floor.
  • the new floor position is set to the next floor of the original third floor, that is, the fourth floor position, and the original fourth floor to the Nth floor are modified to the fifth floor to the N + 1th floor in turn.
  • the floor addition / deletion execution unit 650 is configured to insert a new floor in the page according to the position of the new floor in the page.
  • the third-party developed floor content is supported, and the mobile terminal can insert the floor in the page, that is, the mobile terminal can quickly respond to demand, and friendly output development capabilities to third parties, which can effectively support the main logic.
  • the mobile terminal Under the premise of ensuring the list structure, the development of various complex business needs is realized.
  • the floor addition / deletion judging unit 630 is further configured to determine whether a predetermined floor needs to be deleted according to business requirements.
  • the position determining unit 640 is further configured to determine the position of the predetermined floor on the page according to the floor identifier of the predetermined floor if the predetermined floor needs to be deleted.
  • the floor addition / deletion execution unit 650 is further configured to delete the predetermined floor from the page according to the position of the predetermined floor on the page.
  • a predetermined floor can be deleted from the page, but the entire page content will not be affected, which facilitates page maintenance.
  • the mobile terminal further includes a floor splitting unit 660 configured to divide different business units into different floors according to attribute information between the business units on the page.
  • the attribute information between the business units includes sequential logical relationships, functional relationships, coupling relationships, and content relationships.
  • the process of dismantling the floors can be split from the aspects of sequence logic, function, coupling, content, etc., but there may also be related associations between the floors.
  • the minimum principle that can be used in the process of splitting floors is divided.
  • the floor template configuration data further includes floor dividing line information
  • the mobile terminal further includes a dividing line processing unit 670 configured to, if at least one floor between adjacent floors is in a hidden mode, The floor dividing lines of adjacent floors merge.
  • the floors are distinguished by the dividing line, but the dividing line does not belong to a certain floor.
  • the dividing line to be displayed needs to be determined according to the floor to be displayed.
  • the dividing line can also be treated as an independent floor.
  • the server sends the floor configuration the corresponding floor dividing line will be sent down, that is, the floor template configuration data also includes the floor dividing line information, but the dividing line issued by the server may It is inaccurate.
  • all the dividing lines are created accordingly, and the flag is set to true by default.
  • an algorithm is performed on the dividing line during the process of traversing the generation of the floor entity class list.
  • One of the dividing lines will be retained by weighting because the floors are hidden together.
  • FIG. 7 is a schematic structural diagram of still another embodiment of a mobile terminal of the present disclosure.
  • the mobile terminal includes a memory 710 and a processor 720, where:
  • the memory 710 may be a magnetic disk, a flash memory, or any other non-volatile storage medium.
  • the memory is configured to store the instructions in the embodiment corresponding to FIGS. 1-4.
  • the processor 720 is coupled to the memory 710 and may be implemented as one or more integrated circuits, such as a microprocessor or a microcontroller.
  • the processor 720 is configured to execute instructions stored in a memory.
  • the mobile terminal 800 includes a memory 810 and a processor 820.
  • the processor 820 is coupled to the memory 810 through a BUS bus 830.
  • the mobile terminal 800 can also be connected to the external storage device 850 through the storage interface 840 to call external data, and can also be connected to the network or another computer system (not shown) through the network interface 860, which will not be described in detail here.
  • data instructions are stored in the memory, and the instructions are processed by the processor, which can meet the requirements for page maintenance due to high-frequency business requirements in the current agile development process.
  • FIG. 9 is a schematic structural diagram of some embodiments of a mobile-side page construction system of the present disclosure.
  • the system includes a server 910 and a mobile terminal 920.
  • the mobile terminal 920 has been described in detail in the above embodiments, and will not be further described here.
  • the server 910 is configured to send the floor template configuration data to the mobile terminal 920. Wherein, when the server 910 delivers the floor template configuration data, it cannot determine whether these floors need to be displayed on the page. Therefore, according to the default configuration data of all floor templates, the mobile terminal 920 determines whether the floors are displayed or hidden.
  • the multi-service concurrency problem in agile development can be solved, and the floor content developed by a third party according to the specific business can be supported to facilitate page maintenance.
  • a computer-readable storage medium stores computer program instructions thereon, which, when executed by a processor, implement the steps of the method in the embodiment corresponding to FIG. 1-4.
  • a processor implements the steps of the method in the embodiment corresponding to FIG. 1-4.
  • the embodiments of the present disclosure may be provided as a method, an apparatus, or a computer program product. Therefore, the present disclosure may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Moreover, the present disclosure may take the form of a computer program product implemented on one or more computer-usable non-transitory storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code therein .
  • These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to work in a particular manner such that the instructions stored in the computer-readable memory produce a manufactured article including an instruction device, the instructions
  • the device implements the functions specified in one or more flowcharts and / or one or more blocks of the block diagram.
  • These computer program instructions can also be loaded on a computer or other programmable data processing device, so that a series of steps can be performed on the computer or other programmable device to produce a computer-implemented process, which can be executed on the computer or other programmable device.
  • the instructions provide steps for implementing the functions specified in one or more flowcharts and / or one or more blocks of the block diagrams.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Software Systems (AREA)
  • Business, Economics & Management (AREA)
  • General Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Accounting & Taxation (AREA)
  • Finance (AREA)
  • Human Computer Interaction (AREA)
  • Development Economics (AREA)
  • Economics (AREA)
  • Marketing (AREA)
  • Strategic Management (AREA)
  • General Business, Economics & Management (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

本公开提供了一种移动端页面构建方法、系统和移动端,涉及移动互联网领域。该方法包括:接收服务器下发的楼层模版配置数据,其中,楼层模版配置数据包括楼层标识列表;遍历楼层模版配置数据,根据楼层标识与模版实体的对应关系,为各楼层选择对应的模版实体;根据模版实体生成各楼层对应的模版数据;根据模版数据创建楼层实体类列表,以便根据楼层实体类列表在页面中构建各楼层。本公开构建楼层化的页面,能够满足当前敏捷开发过程中因高频业务需求,而对页面维护的要求。

Description

移动端页面构建方法、系统和移动端
相关申请的交叉引用
本申请是以CN申请号为201810847473.3,申请日为2018年7月27日的申请为基础,并主张其优先权,该CN申请的公开内容在此作为整体引入本申请中。
技术领域
本公开涉及移动互联网领域,尤其涉及一种移动端页面构建方法、系统和移动端。
背景技术
移动端列表界面包括电商的搜索、分类、商品详情以及应用市场等的列表展示界面。针对不同的业务需求,列表各成员所展示的内容也不同。在基础开发过程中,每次成员状态的改变,都需要对原始列表的内容进行更改、维护。
发明内容
发明人发现,列表界面使用列表控件进行展示,每次发表新版本需要修改列表实现代码、列表主逻辑,同时,修改列表内容容易引出其他问题。这使得页面维护成本增加,且不能保证维护后其他功能的正确性,不利于页面维护。
本公开要解决的一个技术问题是提供一种移动端页面构建方法、系统和移动端,能够解决当前敏捷开发过程中因高频业务需求,而对页面维护的要求。
根据本公开一方面,提出一种移动端页面构建方法,包括:接收服务器下发的楼层模版配置数据,其中,楼层模版配置数据包括楼层标识列表;遍历楼层模版配置数据,根据楼层标识与模版实体的对应关系,为各楼层选择对应的模版实体;根据模版实体生成各楼层对应的模版数据;根据模版数据创建楼层实体类列表,以便根据楼层实体类列表在页面中构建各楼层。
在一些实施例中,该方法还包括:判断各楼层是否需要显示在页面上;根据判断结果设置各楼层的标志位,标志位用于标识各楼层是否显示在页面中;在楼层实体类列表增加各楼层标志位生成楼层展示列表,以便根据楼层展示列表在页面展示各楼层。
在一些实施例中,该方法还包括:根据业务需求判断是否需要增加新楼层;若需 要增加新楼层,则获取新楼层信息,其中,新楼层信息中包括楼层标识;将新楼层信息中的楼层标识与楼层展示列表中的楼层标识进行比对,确定新楼层在页面中的位置;根据新楼层在页面中的位置,在页面中插入新楼层。
在一些实施例中,该方法还包括:根据业务需求判断是否需要删除预定楼层;若需要删除预定楼层,则根据预定楼层的楼层标识,确定预定楼层在页面的位置;根据预定楼层在页面的位置,在页面中删除预定楼层。
在一些实施例中,楼层模版配置数据还包括楼层分割线信息,方法还包括:若相邻楼层间至少有一个楼层处于隐藏模式,则将相邻楼层的楼层分割线合并。
在一些实施例中,该方法还包括:根据页面中各业务单元间的属性信息,将不同的业务单元划分为不同的楼层。
在一些实施例中,各业务单元间的属性信息包括顺序逻辑关系、功能关系、耦合关系和内容关系中的至少一项。
在一些实施例中,响应于构建页面请求,在本地读取预先从服务器下载的楼层模版配置数据;或者响应于构建页面请求,在服务器获取楼层模版配置数据。
根据本公开的另一方面,还提出一种移动端,包括:配置数据接收单元,被配置为接收服务器下发的楼层模版配置数据,其中,楼层模版配置数据包括楼层标识列表;模版实体选择单元,被配置为遍历楼层模版配置数据,根据楼层标识与模版实体的对应关系,为各楼层选择对应的模版实体;模版数据生成单元,被配置为根据模版实体生成各楼层对应的模版数据;列表生成单元,被配置为根据模版数据创建楼层实体类列表,以便根据楼层实体类列表在页面中显示各楼层。
在一些实施例中,该移动端还包括:显示判断单元,被配置为判断各楼层是否需要显示在页面上;标志位设置单元,被配置为根据判断结果设置各楼层的标志位,标志位用于标识各楼层是否显示在页面中;列表生成单元还被配置为在楼层实体类列表增加各楼层标志位生成楼层展示列表,以便根据楼层展示列表在页面展示各楼层。
在一些实施例中,该移动端还包括:楼层增删判断单元,被配置为根据业务需求判断是否需要增加新楼层;位置确定单元,被配置为若需要增加新楼层,则获取新楼层信息,其中,新楼层信息中包括楼层标识,将新楼层信息中的楼层标识与楼层展示列表中的楼层标识进行比对,确定新楼层在页面中的位置;楼层增删执行单元,被配置为根据新楼层在页面中的位置,在页面中插入新楼层。
在一些实施例中,楼层增删判断单元还被配置为根据业务需求判断是否需要删除 预定楼层;位置确定单元还被配置为若需要删除预定楼层,则根据预定楼层的楼层标识,确定预定楼层在页面的位置;楼层增删执行单元还被配置为根据预定楼层在页面的位置,在页面中删除预定楼层。
在一些实施例中,楼层模版配置数据还包括楼层分割线信息,移动端还包括:分割线处理单元,被配置为若相邻楼层间至少有一个楼层处于隐藏模式,则将相邻楼层的楼层分割线合并。
在一些实施例中,该移动端还包括:楼层拆分单元,被配置为根据页面中各业务单元间的属性信息,将不同的业务单元划分为不同的楼层。
在一些实施例中,各业务单元间的属性信息包括顺序逻辑关系、功能关系、耦合关系和内容关系中的至少一项。
在一些实施例中,配置数据接收单元被配置为响应于构建页面请求,在本地读取预先从服务器下载的楼层模版配置数据;或者被配置为响应于构建页面请求,在服务器获取楼层模版配置数据。
根据本公开的另一方面,还提出一种移动端,包括:存储器;以及耦接至存储器的处理器,处理器被配置为基于存储在存储器的指令执行如上述的移动端页面构建方法。
根据本公开的另一方面,还提出一种移动端页面构建系统,包括服务器和上述的移动端;其中,服务器被配置为向移动端下发楼层模版配置数据。
根据本公开的另一方面,还提出一种计算机可读存储介质,其上存储有计算机程序指令,该指令被处理器执行时实现上述的移动端页面构建方法。
与相关技术相比,本公开实施例中,借用“乐高积木”思想来实现页面随意搭建的目的,把页面拆成尽可能小的独立楼层,配置需要的楼层,从而形成楼层化的页面,能够满足当前敏捷开发过程中因高频业务需求,而对页面维护的要求。
通过以下参照附图对本公开的示例性实施例的详细描述,本公开的其它特征及其优点将会变得清楚。
附图说明
构成说明书的一部分的附图描述了本公开的实施例,并且连同说明书一起用于解释本公开的原理。
参照附图,根据下面的详细描述,可以更加清楚地理解本公开,其中:
图1为本公开移动端页面构建方法的一些实施例的流程示意图。
图2为本公开移动端页面构建方法的另一些实施例的流程示意图。
图3为本公开移动端页面构建方法的再一些实施例的流程示意图。
图4为本公开移动端页面构建方法的又一些实施例的流程示意图。
图5为本公开移动端的一些实施例的结构示意图。
图6为本公开移动端的另一些实施例的结构示意图。
图7为本公开移动端的又一些实施例的结构示意图。
图8为本公开移动端的再一些实施例的结构示意图。
图9为本公开移动端页面构建系统的一些实施例的结构示意图。
具体实施方式
现在将参照附图来详细描述本公开的各种示例性实施例。应注意到:除非另外具体说明,否则在这些实施例中阐述的部件和步骤的相对布置、数字表达式和数值不限制本公开的范围。
同时,应当明白,为了便于描述,附图中所示出的各个部分的尺寸并不是按照实际的比例关系绘制的。
以下对至少一个示例性实施例的描述实际上仅仅是说明性的,决不作为对本公开及其应用或使用的任何限制。
对于相关领域普通技术人员已知的技术、方法和设备可能不作详细讨论,但在适当情况下,所述技术、方法和设备应当被视为授权说明书的一部分。
在这里示出和讨论的所有示例中,任何具体值应被解释为仅仅是示例性的,而不是作为限制。因此,示例性实施例的其它示例可以具有不同的值。
应注意到:相似的标号和字母在下面的附图中表示类似项,因此,一旦某一项在一个附图中被定义,则在随后的附图中不需要对其进行进一步讨论。
为使本公开的目的、技术方案和优点更加清楚明白,以下结合具体实施例,并参照附图,对本公开进一步详细说明。
图1为本公开移动端页面构建方法的一些实施例的流程示意图。该实施例中的方法由移动端执行。
在步骤110,接收服务器下发的楼层模版配置数据,其中,楼层模版配置数据包括楼层标识列表。其中,服务器可以在动态接口,通过独立的节点按照显示顺序,向 移动端下发楼层模版配置数据,楼层标识可以标识楼层显示顺序。
在步骤120,遍历楼层模版配置数据,根据楼层标识与模版实体的对应关系,为各楼层选择对应的模版实体。其中,移动端本地保存有mId(楼层标识)-template(模版)实体的对应关系,遍历服务器下发的template数据,为各楼层选择对应的模版实体。
在步骤130,根据模版实体生成各楼层对应的模版数据。
在步骤140,根据模版数据创建楼层实体类列表,以便根据楼层实体类列表在页面中构建各楼层。根据模板创建楼层实体类列表,该实体类列表维护真正的楼层顺序,以及要显示的楼层,完成所有楼层的占位及分割线显示等,其中,所有的楼层插入或者隐藏的位置信息都通过这个列表来控制和维护。
在该实施例中,把页面拆成尽可能小的独立楼层,配置需要的楼层,从而形成楼层化的页面,能够满足当前敏捷开发过程中因高频业务需求,而对页面维护的要求。
图2为本公开移动端页面构建方法的另一些实施例的流程示意图。
在步骤210,接收服务器下发的楼层模版配置数据,其中,楼层模版配置数据包括楼层标识列表。楼层标识列表能够反映出楼层样式信息。其中,该过程可以通过两种方式实现,例如,移动端响应于构建页面请求,在本地读取预先从服务器下载的楼层模版配置数据,移动端能够快速的响应用户操作。或者,移动端响应于构建页面请求,在服务器获取楼层模版配置数据。例如,移动端支持JS调用,利用Weex等原生组装化组件通过JS调用将楼层模版配置数据下发到本地,由本地动态生成模版,但使用JS调用需要考虑加载时机及性能损耗问题。
在步骤220,遍历楼层模版配置数据,根据楼层标识与模版实体的对应关系,为各楼层选择对应的模版实体。
在步骤230,根据模版实体生成各楼层对应的模版数据。
在步骤240,根据模版数据创建楼层实体类列表。
在步骤250,判断各楼层是否需要显示在页面上。其中,服务器不确定某个楼层是否显示,可以设置默认下发,由移动端决定楼层显示或隐藏。例如,移动端可以通过请求其它接口等方式,确定这些楼层是否要显示在页面上。
在步骤260,根据判断结果设置各楼层的标志位,标志位用于标识各楼层是否显示在页面中。例如,若某楼层需要显示,则将该楼层标志位flag置为true,若不需要显示,则将该楼层标志位flag置为false。
在步骤270,在楼层实体类列表增加各楼层对应的楼层标志位,生成楼层展示列表,以便根据楼层展示列表在页面展示各楼层。遍历所有楼层,生成楼层展示列表,根据楼层展示列表将所有标志位为true的楼层找出来,开始创建真正的楼层,并显示数据。通过设置标志位能够更加准确的对楼层进行定位。
在该实施例中,在服务器下发楼层模版配置数据后,移动端选择对应的模版实体,从而生成各楼层对应的模版数据,根据各楼层是否需要显示在页面上,设置各楼层的标志位,在根据模版数据创建楼层实体类列表中,增加各楼层对应的楼层标志位,生成楼层展示列表,以便根据楼层展示列表在页面展示各楼层,由于将页面拆分成独立的楼层,能够单独配置各楼层,修改列表的过程变成了维护单个楼层的过程,这样既可以满足复杂业务的实现,又不需要再去维护所有的列表内容。
图3为本公开移动端页面构建方法的再一些实施例的流程示意图。
在步骤310,移动端根据业务需求判断是否需要增加新楼层。服务器通过主接口会返回一部分楼层的数据,还有部分楼层数据,移动端需要通过其他接口获取。
在步骤320,若需要增加新楼层,则获取新楼层信息,其中,新楼层信息中包括楼层标识。楼层标识即标识楼层在页面中的位置。
在步骤330,将新楼层信息中的楼层标识与楼层展示列表中的楼层标识进行比对,确定新楼层在页面中的位置。例如,若新楼层信息中的楼层标识为末尾楼层,则将新楼层添加到页面中最末楼层位置即可。若新楼层信息中的楼层标识为第三楼层,但楼层展示列表中已有第三楼层,则根据预先约定将该新楼层设置在原始第三楼层位置,原始第三楼层至第N楼层,则依次修改为第四楼层至第N+1楼层。或者将新楼层位置设置在原始第三楼层的下一层,即第四楼层位置,而原始第四楼层至第N楼层,则依次修改为第五楼层至第N+1楼层。
在步骤340,根据新楼层在页面中的位置,在页面中插入新楼层。
在该实施例中,其他开发人员直接开发楼层,然后移动端可以在页面中插入该楼层,即移动端能够快速响应需求,并友好的向第三方输出开发能力,可以有效的支持主逻辑,在保证列表架构的前提下,开发各种复杂业务的需求实现。
图4为本公开移动端页面构建方法的又一些实施例的流程示意图。
在步骤410,根据业务需求判断是否需要删除预定楼层。
在步骤420,若需要删除预定楼层,则根据预定楼层的楼层标识,确定预定楼层在页面的位置。
在步骤430,根据预定楼层在页面的位置,在页面中删除预定楼层。
在该实施例中,根据业务需求,可以在页面中删除预定楼层,但不会影响整个页面内容,便于页面维护。
在本公开的另一些实施例中,可以根据需要将不同的业务单元划分为不同的楼层,即最小化楼层。即根据页面中各业务单元间的属性信息,将不同的业务单元划分为不同的楼层,各业务单元间的属性信息包括顺序逻辑关系、功能关系、耦合关系和内容关系等。
在一些实施例中,在购物页面中,商品的价格和商品购物车之间具有顺序逻辑关系,一般用户看到商品价格后会决定是否将商品加入购物车中,因此,可以将页面中商品价格单元和商品购物车单元拆分为不同的楼层。
在一些实施例中,商品详情和商品价格之间没有直接关系,也就是说是商品详情单元和商品价格单元具有单独功能的,因此,可以将页面中的商品详情单元和商品价格单元拆分为不同的楼层。
在一些实施例中,商品详情和最近浏览商品之间没有耦合关系,因此,可以将页面中的商品详情单元和最近浏览商品单元拆分为不同的楼层。另外,商品价格和加价购商品之间具有耦合关系,因此,可以将页面中的商品价格单元和加价购商品单元拆分为不同的楼层。
在一些实施例中,商品标题和商品详情的内容之间具有关系,因此,可以将页面中的商品标题单元和商品详情单元拆分为不同的楼层。
在上述实施例中,拆楼层的过程可以从顺序逻辑、功能、耦合、内容等方面进行楼层的拆分,但楼层之间也可以有相关关联。为保证充分的解耦合,在拆分楼层的过程中,可以使用最小原则进行划分。例如根据业务单元属性将楼层进行更细化的拆分,可以按左右划分,也可以按照上下划分,主要是通过动态分割,完成功能的独立以及业务的独立,使得页面拆成尽可能小的独立楼层,便于页面维护。
在本公开的另一些实施例中,楼层间是通过分割线来区分的,但是分割线又不属于某一个楼层,需要根据展示的楼层来决定要显示的分割线。分割线也可当作独立的楼层处理,服务器下发楼层配置的时候便会将相应的楼层分割线下发下来,即楼层模版配置数据还包括楼层分割线信息,但服务器下发的分割线可能是不准确的,在创建楼层实体类的时候相应将所有的分割线创建出来,并默认将flag标志为true,最后在遍历生成楼层实体类列表的过程中对分割线进行一个算法处理,例如若移动端页面的 相邻楼层间至少有一个楼层处于隐藏模式,则将相邻楼层的楼层分割线合并。即凡是两条分割线因为楼层的隐藏碰到一起就会通过权重的方式保留其中的一条。
图5为本公开移动端的一些实施例的结构示意图。该移动端包括配置数据接收单元510、模版实体选择单元520、模版数据生成单元530和列表生成单元540。
配置数据接收单元510被配置为接收服务器下发的楼层模版配置数据,其中,楼层模版配置数据包括楼层标识列表。其中,服务器可以在动态接口通过独立的节点,按照显示顺序向移动端下发楼层模版配置数据,楼层标识可以标识楼层显示顺序。
其中,配置数据接收单元510被配置为响应于构建页面请求,在本地读取预先从服务器下载的楼层模版配置数据;或者被配置为响应于构建页面请求,在服务器获取楼层模版配置数据。
模版实体选择单元520被配置为遍历楼层模版配置数据,根据楼层标识与模版实体的对应关系,为各楼层选择对应的模版实体。其中,移动端本地保存有mId-template实体的对应关系,遍历服务器下发的template数据,为各楼层选择对应的模版实体。
模版数据生成单元530被配置为根据模版实体生成各楼层对应的模版数据。
列表生成单元540被配置为根据模版数据创建楼层实体类列表,以便根据楼层实体类列表在页面中显示各楼层。
在该实施例中,借用“乐高积木”思想来实现页面随意搭建的目的,首先把页面拆成尽可能小的独立楼层,配置需要的楼层,从而形成楼层化的页面,能够满足当前敏捷开发过程中因高频业务需求,而对页面维护的要求。
在本公开的另一些实施例中,如图6所示,该移动端还包括显示判断单元610和标志位设置单元620。
显示判断单元610被配置为判断各楼层是否需要显示在页面上。其中,服务器不确定某个楼层是否显示,可以设置默认下发,由移动端决定楼层显示或隐藏。例如,移动端可以通过请求其它接口等方式确定这些楼层是否要显示在页面上。
标志位设置单元620被配置为根据判断结果设置各楼层的标志位,标志位用于标识各楼层是否显示在页面中。例如,若某楼层需要显示,则将该楼层标志位flag置为true,若不需要显示,则将该楼层标志位flag置为false。
列表生成单元540还被配置为在楼层实体类列表增加各楼层对应的楼层标志位,生成楼层展示列表,以便根据楼层展示列表在页面展示各楼层。
在该实施例中,在服务器下发楼层模版配置数据后,移动端选择对应的模版实体, 从而生成各楼层对应的模版数据,根据各楼层是否需要显示在页面上设置各楼层的标志位,在根据模版数据创建楼层实体类列表中增加各楼层对应的楼层标志位,生成楼层展示列表,以便根据楼层展示列表在页面展示各楼层,由于将页面拆分成独立的楼层,能够单独配置各楼层,修改列表的过程变成了维护单个楼层的过程,这样既可以满足复杂业务的实现,又不需要再去维护所有的列表内容。
在本公开的另一些实施例中,该移动端还包括楼层增删判断单元630、位置确定单元640、楼层增删执行单元650。
楼层增删判断单元630被配置为根据业务需求判断是否需要增加新楼层。服务器通过主接口会返回一部分楼层的数据,还有部分楼层数据,移动端需要通过其他接口获取。
位置确定单元640被配置为若需要增加新楼层,则获取新楼层信息,其中,新楼层信息中包括楼层标识,将新楼层信息中的楼层标识与楼层展示列表中的楼层标识进行比对,确定新楼层在页面中的位置。楼层标识用于标识楼层在页面中的位置。若新楼层信息中的楼层标识为末尾楼层,则将新楼层添加到页面中最末楼层位置即可。若新楼层信息中的楼层标识为第三楼层,但楼层展示列表中已有第三楼层,则根据预先约定将该新楼层设置在原始第三楼层位置,原始第三楼层至第N楼层,则依次修改为第四楼层至第N+1楼层。或者将新楼层位置设置在原始第三楼层的下一层,即第四楼层位置,而原始第四楼层至第N楼层,则依次修改为第五楼层至第N+1楼层。
楼层增删执行单元650被配置为根据新楼层在页面中的位置在页面中插入新楼层。
在该实施例中,支持第三方开发的楼层内容,移动端可以在页面中插入该楼层,即移动端能够快速响应需求,并友好的向第三方输出开发能力,可以有效的支持主逻辑,在保证列表架构的前提下,开发各种复杂业务的需求实现。
在本公开的另一些实施例中,楼层增删判断单元630还被配置为根据业务需求判断是否需要删除预定楼层。
位置确定单元640还被配置为若需要删除预定楼层,则根据预定楼层的楼层标识确定预定楼层在页面的位置。
楼层增删执行单元650还被配置为根据预定楼层在页面的位置,在页面中删除预定楼层。
在该实施例中,根据业务需求,可以在页面中删除预定楼层,但不会影响整个页 面内容,便于页面维护。
在本公开的另一些实施例中,可以根据需要将不同的业务单元划分为不同的楼层,即最小化楼层。该移动端还包括楼层拆分单元660,被配置为根据页面中各业务单元间的属性信息,将不同的业务单元划分为不同的楼层。各业务单元间的属性信息包括顺序逻辑关系、功能关系、耦合关系和内容关系等。
在上述实施例中,拆楼层的过程可以从顺序逻辑、功能、耦合、内容等方面进行楼层的拆分,但楼层之间也可以有相关关联。为保证充分的解耦合,在拆分楼层的过程中可以使用的最小原则进行划分。
在本公开的另一些实施例中,楼层模版配置数据还包括楼层分割线信息,该移动端还包括分割线处理单元670,被配置为若相邻楼层间至少有一个楼层处于隐藏模式,则将相邻楼层的楼层分割线合并。
楼层间是通过分割线来区分的,但是分割线又不属于某一个楼层,需要根据展示的楼层来决定要显示的分割线。分割线也可当作独立的楼层处理,服务器下发楼层配置的时候便会将相应的楼层分割线下发下来,即楼层模版配置数据还包括楼层分割线信息,但服务器下发的分割线可能是不准确的,在创建楼层实体类的时候相应将所有的分割线创建出来,并默认将flag标志为true,最后在遍历生成楼层实体类列表的过程中对分割线进行一个算法处理,凡是两条分割线因为楼层的隐藏碰到一起就会通过权重的方式保留其中的一条。
图7为本公开移动端的又一些实施例的结构示意图。该移动端包括存储器710和处理器720,其中:
存储器710可以是磁盘、闪存或其它任何非易失性存储介质。存储器被配置为存储图1-4所对应实施例中的指令。处理器720耦接至存储器710,可以作为一个或多个集成电路来实施,例如微处理器或微控制器。该处理器720被配置为执行存储器中存储的指令。
在一些实施例中,还可以如图8所示,该移动端800包括存储器810和处理器820。处理器820通过BUS总线830耦合至存储器810。该移动端800还可以通过存储接口840连接至外部存储装置850以便调用外部数据,还可以通过网络接口860连接至网络或者另外一台计算机系统(未标出),此处不再进行详细介绍。
在该实施例中,通过存储器存储数据指令,再通过处理器处理上述指令,能够满足当前敏捷开发过程中因高频业务需求,而对页面维护的要求。
图9为本公开移动端页面构建系统的一些实施例的结构示意图。该系统包括服务器910和移动端920,其中,移动端920已在上述实施例中进行了详细介绍,此处不再进一步阐述。服务器910被配置为向移动端920下发楼层模版配置数据。其中,服务器910下发楼层模板配置数据的时候,并不能确定这些楼层是不是需要在页面上显示,因此,按照默认下发所有楼层模版配置数据,由移动端920确定楼层是显示还是隐藏。
在该实施例中,能够解决敏捷化开发中多业务并发问题,并且支持第三方根据具体业务开发的楼层内容,以便于页面维护。
在另一些实施例中,一种计算机可读存储介质,其上存储有计算机程序指令,该指令被处理器执行时实现图1-4所对应实施例中的方法的步骤。本领域内的技术人员应明白,本公开的实施例可提供为方法、装置、或计算机程序产品。因此,本公开可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且,本公开可采用在一个或多个其中包含有计算机可用程序代码的计算机可用非瞬时性存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
本公开是参照根据本公开实施例的方法、设备(系统)和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器,使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中,使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品,该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上,使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理,从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
至此,已经详细描述了本公开。为了避免遮蔽本公开的构思,没有描述本领域所公知的一些细节。本领域技术人员根据上面的描述,完全可以明白如何实施这里公开的技术方案。
虽然已经通过示例对本公开的一些特定实施例进行了详细说明,但是本领域的技术人员应该理解,以上示例仅是为了进行说明,而不是为了限制本公开的范围。本领域的技术人员应该理解,可在不脱离本公开的范围和精神的情况下,对以上实施例进行修改。本公开的范围由所附权利要求来限定。

Claims (19)

  1. 一种移动端页面构建方法,包括:
    接收服务器下发的楼层模版配置数据,其中,所述楼层模版配置数据包括楼层标识列表;
    遍历所述楼层模版配置数据,根据楼层标识与模版实体的对应关系,为各楼层选择对应的模版实体;
    根据模版实体生成各楼层对应的模版数据;
    根据所述模版数据创建楼层实体类列表,以便根据所述楼层实体类列表在所述页面中构建各楼层。
  2. 根据权利要求1所述的移动端页面构建方法,还包括:
    判断各楼层是否需要显示在所述页面上;
    根据判断结果设置各楼层的标志位,所述标志位用于标识各楼层是否显示在页面中;
    在所述楼层实体类列表增加各楼层对应的楼层标志位,生成楼层展示列表,以便根据所述楼层展示列表在所述页面展示各楼层。
  3. 根据权利要求2所述的移动端页面构建方法,还包括:
    根据业务需求判断是否需要增加新楼层;
    若需要增加新楼层,则获取新楼层信息,其中,所述新楼层信息中包括楼层标识;
    将所述新楼层信息中的楼层标识与所述楼层展示列表中的楼层标识进行比对,确定新楼层在所述页面中的位置;
    根据新楼层在所述页面中的位置,在所述页面中插入新楼层。
  4. 根据权利要求2所述的移动端页面构建方法,还包括:
    根据业务需求判断是否需要删除预定楼层;
    若需要删除预定楼层,则根据所述预定楼层的楼层标识,确定所述预定楼层在所述页面的位置;
    根据所述预定楼层在所述页面的位置,在所述页面中删除所述预定楼层。
  5. 根据权利要求1所述的移动端页面构建方法,其中,所述楼层模版配置数据还包括楼层分割线信息,所述方法还包括:
    若相邻楼层间至少有一个楼层处于隐藏模式,则将相邻楼层的楼层分割线合并。
  6. 根据权利要求1-5任一所述的移动端页面构建方法,还包括:
    根据所述页面中各业务单元间的属性信息,将不同的业务单元划分为不同的楼层。
  7. 根据权利要求6所述的移动端页面构建方法,其中,
    各业务单元间的属性信息包括顺序逻辑关系、功能关系、耦合关系和内容关系中的至少一项。
  8. 根据权利要求1-5任一所述的移动端页面构建方法,其中,
    响应于构建页面请求,在本地读取预先从服务器下载的楼层模版配置数据;或者
    响应于构建页面请求,在服务器获取楼层模版配置数据。
  9. 一种移动端,包括:
    配置数据接收单元,被配置为接收服务器下发的楼层模版配置数据,其中,所述楼层模版配置数据包括楼层标识列表;
    模版实体选择单元,被配置为遍历所述楼层模版配置数据,根据楼层标识与模版实体的对应关系,为各楼层选择对应的模版实体;
    模版数据生成单元,被配置为根据模版实体生成各楼层对应的模版数据;
    列表生成单元,被配置为根据所述模版数据创建楼层实体类列表,以便根据所述楼层实体类列表在所述页面中显示各楼层。
  10. 根据权利要求9所述的移动端,还包括:
    显示判断单元,被配置为判断各楼层是否需要显示在所述页面上;
    标志位设置单元,被配置为根据判断结果设置各楼层的标志位,所述标志位用于标识各楼层是否显示在页面中;
    所述列表生成单元还被配置为在所述楼层实体类列表增加各楼层对应的楼层标志位,生成楼层展示列表,以便根据所述楼层展示列表在所述页面展示各楼层。
  11. 根据权利要求10所述的移动端,还包括:
    楼层增删判断单元,被配置为根据业务需求判断是否需要增加新楼层;
    位置确定单元,被配置为若需要增加新楼层,则获取新楼层信息,其中,所述新楼层信息中包括楼层标识,将所述新楼层信息中的楼层标识与所述楼层展示列表中的楼层标识进行比对,确定新楼层在所述页面中的位置;
    楼层增删执行单元,被配置为根据新楼层在所述页面中的位置,在所述页面中插入新楼层。
  12. 根据权利要求11所述的移动端,其中,
    所述楼层增删判断单元还被配置为根据业务需求判断是否需要删除预定楼层;
    所述位置确定单元还被配置为若需要删除预定楼层,则根据所述预定楼层的楼层标识,确定所述预定楼层在所述页面的位置;
    所述楼层增删执行单元还被配置为根据所述预定楼层在所述页面的位置,在所述页面中删除所述预定楼层。
  13. 根据权利要求9所述的移动端,其中,所述楼层模版配置数据还包括楼层分割线信息,所述移动端还包括:
    分割线处理单元,被配置为若相邻楼层间至少有一个楼层处于隐藏模式,则将相邻楼层的楼层分割线合并。
  14. 根据权利要求9-13任一所述的移动端,还包括:
    楼层拆分单元,被配置为根据所述页面中各业务单元间的属性信息,将不同的业务单元划分为不同的楼层。
  15. 根据权利要求14所述的移动端,其中,
    各业务单元间的属性信息包括顺序逻辑关系、功能关系、耦合关系和内容关系中的至少一项。
  16. 根据权利要求9-13任一所述的移动端,其中,
    所述配置数据接收单元被配置为响应于构建页面请求,在本地读取预先从服务器下载的楼层模版配置数据;或者被配置为响应于构建页面请求,在服务器获取楼层模版配置数据。
  17. 一种移动端,包括:
    存储器;以及
    耦接至所述存储器的处理器,所述处理器被配置为基于存储在所述存储器的指令执行如权利要求1至8任一项所述的移动端页面构建方法。
  18. 一种移动端页面构建系统,包括服务器和权利要求9-17任一所述的移动端;
    其中,所述服务器被配置为向所述移动端下发楼层模版配置数据。
  19. 一种计算机可读存储介质,其上存储有计算机程序指令,该指令被处理器执行时实现权利要求1至8任一项所述的移动端页面构建方法。
PCT/CN2019/097553 2018-07-27 2019-07-24 移动端页面构建方法、系统和移动端 WO2020020248A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810847473.3 2018-07-27
CN201810847473.3A CN110764763B (zh) 2018-07-27 2018-07-27 移动端页面构建方法、系统和移动端

Publications (1)

Publication Number Publication Date
WO2020020248A1 true WO2020020248A1 (zh) 2020-01-30

Family

ID=69182153

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/097553 WO2020020248A1 (zh) 2018-07-27 2019-07-24 移动端页面构建方法、系统和移动端

Country Status (2)

Country Link
CN (1) CN110764763B (zh)
WO (1) WO2020020248A1 (zh)

Cited By (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111445288A (zh) * 2020-03-31 2020-07-24 苏宁云计算有限公司 广告位楼层的配置方法及其展示方法、装置、介质及设备
CN111767050A (zh) * 2020-05-20 2020-10-13 贝壳技术有限公司 列表页生成方法及装置
CN112052001A (zh) * 2020-09-04 2020-12-08 上海浦东发展银行股份有限公司 App客户端的ui动态显示设计架构、方法、设备及存储介质
CN112307372A (zh) * 2020-10-29 2021-02-02 北京沃东天骏信息技术有限公司 数据处理方法和装置
CN112306491A (zh) * 2020-11-30 2021-02-02 北京博瑞彤芸科技股份有限公司 一种业务配置方法、装置、终端及存储介质
CN113626029A (zh) * 2020-05-09 2021-11-09 中国人寿财产保险股份有限公司 一种动态生成页面的数据处理方法和系统
CN113703809A (zh) * 2021-08-31 2021-11-26 康键信息技术(深圳)有限公司 一种首页应用数据配置更新方法、装置、设备和介质
CN115562670A (zh) * 2022-11-15 2023-01-03 深圳市客路网络科技有限公司 页面配置方法、装置、电子设备及介质
WO2023045412A1 (zh) * 2021-09-26 2023-03-30 北京沃东天骏信息技术有限公司 页面创建方法、装置和系统、计算机装置和存储介质

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111984259A (zh) * 2020-07-10 2020-11-24 浙江大搜车软件技术有限公司 界面创建方法、装置、设备及存储介质
CN112579138A (zh) * 2020-12-02 2021-03-30 京东数字科技控股股份有限公司 页面展示方法、装置、电子设备及存储介质
CN112905262B (zh) * 2021-03-09 2024-06-04 中国人民解放军63920部队 一种航天测控系统配置方法及装置

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105468377A (zh) * 2015-12-10 2016-04-06 北京中科汇联科技股份有限公司 一种移动端页面生成方法及系统
CN107784076A (zh) * 2017-09-25 2018-03-09 北京京东尚科信息技术有限公司 可视化构建用户行为数据的方法和装置
CN108256025A (zh) * 2018-01-10 2018-07-06 链家网(北京)科技有限公司 基于html5的页面的构建方法及装置

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9317490B2 (en) * 2012-09-19 2016-04-19 TagMan Inc. Systems and methods for 3-tier tag container architecture
CN103019684B (zh) * 2012-11-20 2016-03-16 北京思特奇信息技术股份有限公司 一种基于动态模板的配置业务页面的方法
CN105549973A (zh) * 2015-12-11 2016-05-04 上海斐讯数据通信技术有限公司 一种列表控件中视图列表的数据更新方法及系统
CN106294816B (zh) * 2016-08-16 2022-03-25 腾讯科技(深圳)有限公司 页面信息的处理方法和装置
CN108008954A (zh) * 2017-12-01 2018-05-08 深圳乐信软件技术有限公司 页面配置方法、装置、服务器及介质

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105468377A (zh) * 2015-12-10 2016-04-06 北京中科汇联科技股份有限公司 一种移动端页面生成方法及系统
CN107784076A (zh) * 2017-09-25 2018-03-09 北京京东尚科信息技术有限公司 可视化构建用户行为数据的方法和装置
CN108256025A (zh) * 2018-01-10 2018-07-06 链家网(北京)科技有限公司 基于html5的页面的构建方法及装置

Cited By (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111445288A (zh) * 2020-03-31 2020-07-24 苏宁云计算有限公司 广告位楼层的配置方法及其展示方法、装置、介质及设备
CN113626029A (zh) * 2020-05-09 2021-11-09 中国人寿财产保险股份有限公司 一种动态生成页面的数据处理方法和系统
CN113626029B (zh) * 2020-05-09 2024-04-26 中国人寿财产保险股份有限公司 一种动态生成页面的数据处理方法和系统
CN111767050A (zh) * 2020-05-20 2020-10-13 贝壳技术有限公司 列表页生成方法及装置
CN112052001A (zh) * 2020-09-04 2020-12-08 上海浦东发展银行股份有限公司 App客户端的ui动态显示设计架构、方法、设备及存储介质
CN112052001B (zh) * 2020-09-04 2023-11-24 上海浦东发展银行股份有限公司 App客户端的ui动态显示设计架构、方法、设备及存储介质
CN112307372A (zh) * 2020-10-29 2021-02-02 北京沃东天骏信息技术有限公司 数据处理方法和装置
CN112306491A (zh) * 2020-11-30 2021-02-02 北京博瑞彤芸科技股份有限公司 一种业务配置方法、装置、终端及存储介质
CN113703809A (zh) * 2021-08-31 2021-11-26 康键信息技术(深圳)有限公司 一种首页应用数据配置更新方法、装置、设备和介质
CN113703809B (zh) * 2021-08-31 2024-04-26 康键信息技术(深圳)有限公司 一种首页应用数据配置更新方法、装置、设备和介质
WO2023045412A1 (zh) * 2021-09-26 2023-03-30 北京沃东天骏信息技术有限公司 页面创建方法、装置和系统、计算机装置和存储介质
CN115562670A (zh) * 2022-11-15 2023-01-03 深圳市客路网络科技有限公司 页面配置方法、装置、电子设备及介质

Also Published As

Publication number Publication date
CN110764763A (zh) 2020-02-07
CN110764763B (zh) 2022-04-26

Similar Documents

Publication Publication Date Title
WO2020020248A1 (zh) 移动端页面构建方法、系统和移动端
CN111045655A (zh) 一种页面渲染的方法、装置、渲染服务器和存储介质
US20120188242A1 (en) Three-dimensional virtual world pattern positioning using templates
CN110019330B (zh) 信息输出方法和装置
JP2018518733A (ja) ファイル操作方法及び装置
US11620444B2 (en) Providing action associated with event detected within communication
US20210125144A1 (en) Bill of material conversion method, electronic apparatus and non-transitory computer-readable storage medium
US20140331179A1 (en) Automated Presentation of Visualized Data
US20180293257A1 (en) Method for accessing distributed database and distributed data service apparatus
US20150120508A1 (en) Purchasing Systems and Methods
CN111949832A (zh) 批量作业依赖关系的解析方法及装置
CN112905441A (zh) 测试用例生成方法、测试方法、装置及设备
CN107621951A (zh) 一种视图层级优化的方法及装置
CN111708961A (zh) 页面数据获取方法、装置、设备及可读存储介质
US20100049747A1 (en) Apparatus and method for storing log in a thread oriented logging system
US20180060787A1 (en) Information processing method, information processing device and client terminal
CN112148287B (zh) 一种表格动态显示方法、装置以及电子设备
CN115794917A (zh) 一种资源数据的导入方法及装置
CN111367500A (zh) 数据的处理方法和装置
TW201905669A (zh) App應用展示介面的方法、裝置和電子設備
CN111124386B (zh) 基于Unity的动画事件处理方法、装置、设备和存储介质
CN114281461A (zh) 一种可配置数据源属性的管理方法、设备及介质
CN113763069A (zh) 物品信息展示页面生成方法、装置、设备和存储介质
CN112330304A (zh) 一种合同审批方法和装置
CN109218063B (zh) 一种展示网络拓扑的方法和装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 19840686

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 19.05.2021)

122 Ep: pct application non-entry in european phase

Ref document number: 19840686

Country of ref document: EP

Kind code of ref document: A1