CN111475138B - Routing method and device based on weex framework, electronic equipment and readable medium - Google Patents
Routing method and device based on weex framework, electronic equipment and readable medium Download PDFInfo
- Publication number
- CN111475138B CN111475138B CN201910063691.2A CN201910063691A CN111475138B CN 111475138 B CN111475138 B CN 111475138B CN 201910063691 A CN201910063691 A CN 201910063691A CN 111475138 B CN111475138 B CN 111475138B
- Authority
- CN
- China
- Prior art keywords
- page
- routing
- interface
- weex
- context object
- 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
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/20—Software design
- G06F8/22—Procedural
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/31—Programming languages or programming paradigms
- G06F8/315—Object-oriented languages
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/40—Transformation of program code
- G06F8/41—Compilation
- G06F8/43—Checking; Contextual analysis
Landscapes
- Engineering & Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computing Systems (AREA)
- Stored Programmes (AREA)
- User Interface Of Digital Computer (AREA)
Abstract
The embodiment of the application provides a routing method, a routing device, electronic equipment and a computer readable medium based on a weex framework. Wherein the method comprises the following steps: inquiring registration routing information according to a received page routing request based on a weex frame so as to determine context object information corresponding to the page routing request; and if the context object information is a custom page route interface class, executing page interface operation defined by the custom page route interface class. According to the embodiment of the application, when the context object information is the custom page route interface class, the page interface operation defined by the custom page route interface class is executed, so that the routing capability of the weex framework can be enhanced.
Description
Technical Field
The embodiment of the application relates to the technical field of internet, in particular to a routing method, a routing device, electronic equipment and a computer readable medium based on a weex framework.
Background
The Weex framework aims to enable developers to build Android, iOS and Web applications using the same set of code based on contemporary advanced Web development technologies. Specifically, after integrating the Weex SDK, you can develop mobile applications using JavaScript language and the modern popular front-end framework. Due to the limitation of the poor experience of the native page frames of mobile applications, a custom set of page frames is required. However, the routing capability of the Weex framework only supports routing to interface classes that use the native page framework, and not to interface classes that use the custom page framework, and thus it can be seen that the routing capability of the Weex framework is weak and needs to be enhanced.
Disclosure of Invention
The application aims to provide a routing method, a routing device, electronic equipment and a computer readable medium based on a Weex framework, which are used for solving the problem of how to enhance the routing capability of the Weex framework in the prior art.
According to a first aspect of embodiments of the present application, a routing method based on a weex framework is provided. The method comprises the following steps: inquiring registration routing information according to a received page routing request based on a weex frame so as to determine context object information corresponding to the page routing request; and if the context object information is a custom page route interface class, executing page interface operation defined by the custom page route interface class.
According to a second aspect of embodiments of the present application, a routing device based on a weex framework is provided. The device comprises: the determining module is used for inquiring the registered routing information according to the received page routing request based on the weex frame so as to determine the context object information corresponding to the page routing request; and the first execution module is used for executing the page interface operation defined by the custom page routing interface class if the context object information is the custom page routing interface class.
According to a third aspect of embodiments of the present application, there is provided an electronic device, including: one or more processors; a computer readable medium configured to store one or more programs which, when executed by the one or more processors, cause the one or more processors to implement a weex frame based routing method as described in the first aspect of the above embodiments.
According to a fourth aspect of embodiments of the present application, there is provided a computer readable medium having stored thereon a computer program which when executed by a processor implements a weex frame based routing method according to the first aspect of the above embodiments.
According to the technical scheme provided by the embodiment of the application, the registration route information is queried according to the received page route request based on the weex frame so as to determine the context object information corresponding to the page route request, if the context object information is a custom page route interface class, the page interface operation defined by the custom page route interface class is executed, and compared with other existing modes, when the context object information is the custom page route interface class, the page interface operation defined by the custom page route interface class is executed, so that the routing capability of the weex frame can be enhanced.
Drawings
Other features, objects and advantages of the present application will become more apparent upon reading of the detailed description of non-limiting embodiments, made with reference to the following drawings, in which:
fig. 1 is a flowchart of a procedure of a routing method based on a weex framework according to a first embodiment of the present application;
fig. 2 is a flow chart of steps of a routing method based on a weex frame in a second embodiment of the present application;
fig. 3 is a schematic structural diagram of a routing device based on a weex frame in a third embodiment of the present application;
fig. 4 is a schematic structural diagram of a routing device based on a weex frame in a fourth embodiment of the present application;
fig. 5 is a schematic structural diagram of an electronic device in a fifth embodiment of the present application;
fig. 6 is a hardware structure of an electronic device in the sixth embodiment of the present application.
Detailed Description
The present application is described in further detail below with reference to the drawings and examples. It is to be understood that the specific embodiments described herein are merely configured to illustrate the related invention, and are not limiting of the invention. It should be noted that, for convenience of description, only the portions related to the present invention are shown in the drawings.
It should be noted that, in the case of no conflict, the embodiments and features in the embodiments may be combined with each other. The present application will be described in detail below with reference to the accompanying drawings in conjunction with embodiments.
Referring to fig. 1, a flowchart illustrating steps of a method for routing based on a weex framework according to an embodiment of the present application is shown.
Specifically, the routing method based on the weex framework provided in this embodiment includes the following steps:
in step S101, registration routing information is queried according to a received web frame-based page routing request, so as to determine context object information corresponding to the page routing request.
In the embodiments of the present application, the weex framework may be understood as a framework that uses the Web development experience to develop high performance native applications. The page routing request carries a page link address and corresponding page operation information, such as page opening information, page closing information and the like. The registration routing information can be understood as a code block obtained after the routing protocol modification of a native code block of the weex framework for realizing the page routing function. Specifically, the open interface, close interface, push interface, pop interface and other interfaces in the native code block are rewritten to enable each interface to judge whether the context object information is a custom page route interface class, if the context object information is judged to be the custom page route interface class, the page interface operation defined by the custom page route interface class is executed, and if the context object information is judged to be the native page route interface class, the method executed by the interface is executed. The context object information may be understood as information describing an application running environment, i.e. a context, representing a process of interaction with an operating system from the perspective of an Android system. From a program perspective, it is understood that Context (Context object information) is an abstract class, and Activity, service, application, etc. are one implementation of this class. It will be appreciated that the above description is exemplary only, and that the embodiments of the present application are not limited in any way.
In some alternative embodiments, the route registration information is stored in a Map, which may be understood as a Map container stored in the form of a key-value, in which the key field is unique and unrepeatable, and when a new key-value pair is added, it is detected whether the content of the key field already exists, if so, the content of the corresponding value field is replaced, and if not, a pair of key-values is newly inserted. Thus, the replacement of native code blocks of the page routing function can be achieved with this feature of the Map container. Specifically, since the name of the native code block is stored in the key field of the Map container, and the native code block is stored in the value field of the Map container, the name of the code block obtained after the modification of the routing protocol can be set as the name of the native code block, and the original code block can be successfully replaced with the code block obtained after the modification of the routing protocol. By querying the change of the code block stored in the value field, the context object information corresponding to the page routing request can be determined. It will be appreciated that the above description is exemplary only, and that the embodiments of the present application are not limited in any way.
In step S102, if the context object information is a custom page routing interface class, a page interface operation defined by the custom page routing interface class is executed.
In this embodiment of the present application, the page interfaces in the custom page routing interface class may be used by a service party to implement a corresponding function according to service requirements, for example, to open a page corresponding to a page link address in the page routing request by using a custom page frame, to open a page corresponding to a page link address in the page routing request by using a simple page opening method, or to close a page corresponding to a page link address in the page routing request by using a simple page closing method. The page interface operation comprises a page opening operation or a page closing operation. Thereby, the routing capability of the weex frame can be enhanced. It will be appreciated that the above description is exemplary only, and that the embodiments of the present application are not limited in any way.
In some optional embodiments, after the determining the context object information corresponding to the page routing request, the method further includes: and if the context object information is a native page routing interface class, executing a native page interface operation of the native page routing interface class. The native page interface operation includes a page opening operation or a page closing operation. The native page routing interface class can be understood as a page routing interface class formed by an open interface, a close interface, a push interface and a pop interface in a native code block. It will be appreciated that the above description is exemplary only, and that the embodiments of the present application are not limited in any way.
According to the routing method based on the weex frame, the registration routing information is queried according to the received page routing request based on the weex frame, so that the context object information corresponding to the page routing request is determined, if the context object information is a custom page routing interface class, the page interface operation defined by the custom page routing interface class is executed, and compared with other existing modes, when the context object information is the custom page routing interface class, the page interface operation defined by the custom page routing interface class is executed, so that the routing capability of the weex frame can be enhanced.
The weex frame-based routing method of the present embodiment may be performed by any suitable device having data processing capabilities, including, but not limited to: cameras, terminals, mobile terminals, PCs, servers, vehicle-mounted devices, entertainment devices, advertising devices, personal Digital Assistants (PDAs), tablet computers, notebook computers, palm-top gaming devices, smart glasses, smart watches, wearable devices, virtual display devices or display enhancement devices (e.g., google Glass, oculus lift, hollens, gear VR), and the like.
Referring to fig. 2, a flowchart illustrating steps of a method for routing based on a weex framework according to a second embodiment of the present application is shown.
Specifically, the routing method based on the weex framework provided in this embodiment includes the following steps:
in step S201, the definition of the routing interface class is performed for the interface of the page operation.
In this embodiment of the present application, the page operation includes a page opening operation or a page closing operation, and correspondingly, the interface of the page operation includes an interface for implementing the page opening operation or an interface for implementing the page closing operation. In particular implementations, an interface class that includes an interface that implements a page open operation and an interface that implements a page close operation may be defined as a routing interface class. It will be appreciated that the above description is exemplary only, and that the embodiments of the present application are not limited in any way.
In some alternative embodiments, the method further comprises: and providing the interface of the page operation for the corresponding service to perform the page operation. Specifically, the interface of the page operation may be used by the service party to implement a corresponding function according to the service requirement, for example, to open a page corresponding to the page link address in the page route request by using a custom page frame, to open a page corresponding to the page link address in the page route request by using a simple page opening method, or to close a page corresponding to the page link address in the page route request by using a simple page closing method, and so on. Thereby, the service side can conveniently expand the functions. It will be appreciated that the above description is exemplary only, and that the embodiments of the present application are not limited in any way.
In step S202, registration routing information is queried according to a received web frame-based page routing request, so as to determine context object information corresponding to the page routing request.
Since this step S202 is similar to the step S101 described above, the description thereof will not be repeated here.
In step S203, if the context object information is a custom page routing interface class, a page interface operation defined by the custom page routing interface class is performed.
Since this step S203 is similar to the step S102 described above, the description thereof will not be repeated here.
According to the routing method based on the weex framework, the routing interface class is defined for the page operation interface, the received page routing request based on the weex framework is used for inquiring the registered routing information to determine the context object information corresponding to the page routing request, if the context object information is the custom page routing interface class, the page interface operation defined by the custom page routing interface class is executed, and compared with other existing modes, when the context object information is the custom page routing interface class, the page interface operation defined by the custom page routing interface class is executed, so that the routing capability of the weex framework can be enhanced.
The weex frame-based routing method of the present embodiment may be performed by any suitable device having data processing capabilities, including, but not limited to: cameras, terminals, mobile terminals, PCs, servers, vehicle-mounted devices, entertainment devices, advertising devices, personal Digital Assistants (PDAs), tablet computers, notebook computers, palm-top gaming devices, smart glasses, smart watches, wearable devices, virtual display devices or display enhancement devices (e.g., google Glass, oculus lift, hollens, gear VR), and the like.
Referring to fig. 3, a schematic structural diagram of a routing device based on a weex frame in a third embodiment of the present application is shown.
The routing device based on the weex framework of the embodiment includes: a determining module 301, configured to query registration routing information according to a received web frame-based page routing request, so as to determine context object information corresponding to the page routing request; the first execution module 302 is configured to execute the page interface operation defined by the custom page routing interface class if the context object information is the custom page routing interface class.
The routing device based on the weex frame in this embodiment is configured to implement the corresponding routing method based on the weex frame in the foregoing multiple method embodiments, and has the beneficial effects of the corresponding method embodiments, which are not described herein again.
Referring to fig. 4, a schematic structural diagram of a routing device based on a weex frame in a fourth embodiment of the present application is shown.
The routing device based on the weex framework of the embodiment includes: a determining module 403, configured to query the registration routing information according to the received web frame-based page routing request, so as to determine context object information corresponding to the page routing request; the first execution module 404 is configured to execute the page interface operation defined by the custom page routing interface class if the context object information is the custom page routing interface class.
Optionally, the route registration information is stored in a map.
Optionally, before the determining module, the apparatus further includes: the definition module 401 is configured to define a routing interface class for an interface of a page operation.
Optionally, the apparatus further comprises: and the providing module 402 is configured to provide the interface for page operation for the corresponding service to perform page operation.
Optionally, the page operation includes a page open operation or a page close operation.
Optionally, after the determining module 403, the apparatus further includes: and the second execution module 405 is configured to execute a native page interface operation of a native page routing interface class if the context object information is the native page routing interface class.
The routing device based on the weex frame in this embodiment is configured to implement the corresponding routing method based on the weex frame in the foregoing multiple method embodiments, and has the beneficial effects of the corresponding method embodiments, which are not described herein again.
Fig. 5 is a schematic structural diagram of an electronic device in a fifth embodiment of the present application; the electronic device may include:
one or more processors 501;
computer readable media 502, which may be configured to store one or more programs,
the one or more programs, when executed by the one or more processors, cause the one or more processors to implement the weex frame-based routing method as described in the first or second embodiments.
Fig. 6 is a hardware structure of an electronic device in a sixth embodiment of the present application; as shown in fig. 6, the hardware structure of the electronic device may include: a processor 601, a communication interface 602, a computer readable medium 603 and a communication bus 604;
wherein the processor 601, the communication interface 602, and the computer readable medium 603 communicate with each other via a communication bus 604;
alternatively, the communication interface 602 may be an interface of a communication module, such as an interface of a GSM module;
wherein the processor 601 may specifically be configured to: inquiring registration routing information according to a received page routing request based on a weex frame so as to determine context object information corresponding to the page routing request; and if the context object information is a custom page route interface class, executing page interface operation defined by the custom page route interface class.
The processor 601 may be a general-purpose processor, including a central processing unit (Central Processing Unit, CPU for short), a network processor (Network Processor, NP for short), and the like; but may also be a Digital Signal Processor (DSP), application Specific Integrated Circuit (ASIC), an off-the-shelf programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components. The disclosed methods, steps, and logic blocks in the embodiments of the present application may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
The computer readable medium 603 can be, but is not limited to, random access Memory (Random Access Memory, RAM), read Only Memory (ROM), programmable Read Only Memory (Programmable Read-Only Memory, PROM), erasable Read Only Memory (Erasable Programmable Read-Only Memory, EPROM), electrically erasable Read Only Memory (Electric Erasable Programmable Read-Only Memory, EEPROM), etc.
In particular, according to embodiments of the present disclosure, the processes described above with reference to flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code configured to perform the method shown in the flow chart. In such embodiments, the computer program may be downloaded and installed from a network via a communication portion, and/or installed from a removable medium. The above-described functions defined in the method of the present application are performed when the computer program is executed by a Central Processing Unit (CPU). It should be noted that, the computer readable medium described in the present application may be a computer readable signal medium or a computer readable storage medium, or any combination of the two. The computer readable medium can be, for example but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples of the computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage media element, a magnetic storage media element, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In the present application, however, a computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, with computer-readable program code embodied therein. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, fiber optic cable, RF, etc., or any suitable combination of the foregoing.
Computer program code configured to carry out operations of the present application may be written in one or more programming languages, including an object oriented programming language such as Java, smalltalk, C ++ and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of remote computers, the remote computers may be connected via any kind of network: including a Local Area Network (LAN) or a Wide Area Network (WAN), to connect to the user's computer, or may be connected to external computers (e.g., by way of the internet using an internet service provider).
The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present application. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions configured to implement the specified logical function(s). The specific relationships in the embodiments described above are merely exemplary, and fewer, more, or an adjusted order of execution of the steps may be possible in a specific implementation. That is, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The modules involved in the embodiments described in the present application may be implemented by software, or may be implemented by hardware. The described modules may also be provided in a processor, for example, as: a processor includes a determination module, a first execution module. The names of these modules do not limit the module itself in some cases, for example, the determining module may also be described as "a module that queries registered routing information according to a received web frame-based page routing request to determine context object information corresponding to the page routing request".
As another aspect, the present application also provides a computer readable medium having stored thereon a computer program which, when executed by a processor, implements a weex frame-based routing method as described in the above embodiment one or embodiment two.
As another aspect, the present application also provides a computer-readable medium that may be contained in the apparatus described in the above embodiments; or may be present alone without being fitted into the device. The computer readable medium carries one or more programs which, when executed by the apparatus, cause the apparatus to: inquiring registration routing information according to a received page routing request based on a weex frame so as to determine context object information corresponding to the page routing request; and if the context object information is a custom page route interface class, executing page interface operation defined by the custom page route interface class.
The terms "first," "second," "the first," or "the second," as used in various embodiments of the present disclosure, may modify various components without regard to order and/or importance, but these terms do not limit the corresponding components. The above description is only configured for the purpose of distinguishing an element from other elements. For example, the first user device and the second user device represent different user devices, although both are user devices. For example, a first element could be termed a second element, and, similarly, a second element could be termed a first element, without departing from the scope of the present disclosure.
When an element (e.g., a first element) is referred to as being "coupled" (operatively or communicatively) to "another element (e.g., a second element) or" connected "to another element (e.g., a second element), it is understood that the one element is directly connected to the other element or the one element is indirectly connected to the other element via yet another element (e.g., a third element). In contrast, it will be understood that when an element (e.g., a first element) is referred to as being "directly connected" or "directly coupled" to another element (a second element), then no element (e.g., a third element) is interposed therebetween.
The foregoing description is only of the preferred embodiments of the present application and is presented as a description of the principles of the technology being utilized. It will be appreciated by persons skilled in the art that the scope of the invention referred to in this application is not limited to the specific combinations of features described above, but it is intended to cover other embodiments in which any combination of features described above or equivalents thereof is possible without departing from the spirit of the invention. Such as the above-described features and technical features having similar functions (but not limited to) disclosed in the present application are replaced with each other.
Claims (14)
1. A method of routing based on a weex framework, the method comprising:
inquiring registration routing information according to a received page routing request based on a weex frame to determine context object information corresponding to the page routing request, wherein the registration routing information is a code block obtained after a routing protocol modification is carried out on a native code block of the weex frame for realizing a page routing function;
and if the context object information is a custom page route interface class, executing page interface operation defined by the custom page route interface class.
2. The method of claim 1, wherein the route registration information is stored in a map.
3. The method of claim 1, wherein before querying registration routing information according to the received web frame-based page routing request to determine the context object information corresponding to the page routing request, the method further comprises:
and defining a routing interface class for the page operation interface.
4. A method according to claim 3, characterized in that the method further comprises:
and providing the interface of the page operation for the corresponding service to perform the page operation.
5. A method according to claim 3, wherein the page operation comprises a page open operation or a page close operation.
6. The method according to any one of claims 1-5, wherein after the querying the registration routing information according to the received web frame-based page routing request to determine the context object information corresponding to the page routing request, the method further comprises:
and if the context object information is a native page routing interface class, executing a native page interface operation of the native page routing interface class.
7. A weex frame-based routing device, the device comprising:
the determining module is used for inquiring the registration routing information according to the received page routing request based on the weex frame so as to determine the context object information corresponding to the page routing request, wherein the registration routing information is a code block obtained after the routing protocol transformation of the native code block of the weex frame for realizing the page routing function;
and the first execution module is used for executing the page interface operation defined by the custom page routing interface class if the context object information is the custom page routing interface class.
8. The apparatus of claim 7, wherein the route registration information is stored in a map.
9. The apparatus of claim 7, wherein prior to the determining module, the apparatus further comprises:
and the definition module is used for defining the routing interface class of the page operation interface.
10. The apparatus of claim 9, wherein the apparatus further comprises:
and the providing module is used for providing the interface of the page operation for the corresponding service to carry out the page operation.
11. The apparatus of claim 9, wherein the page operation comprises a page open operation or a page close operation.
12. The apparatus according to any of claims 7-11, wherein after the determining module, the apparatus further comprises:
and the second execution module is used for executing the native page interface operation of the native page routing interface class if the context object information is the native page routing interface class.
13. An electronic device, comprising:
one or more processors;
a computer readable medium configured to store one or more programs,
when the one or more programs are executed by the one or more processors, the one or more processors are caused to implement the weex frame based routing method of any of claims 1-6.
14. A computer readable medium on which a computer program is stored, which program, when being executed by a processor, implements a weex frame based routing method according to any of claims 1-6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910063691.2A CN111475138B (en) | 2019-01-23 | 2019-01-23 | Routing method and device based on weex framework, electronic equipment and readable medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910063691.2A CN111475138B (en) | 2019-01-23 | 2019-01-23 | Routing method and device based on weex framework, electronic equipment and readable medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111475138A CN111475138A (en) | 2020-07-31 |
| CN111475138B true CN111475138B (en) | 2023-04-25 |
Family
ID=71743367
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910063691.2A Active CN111475138B (en) | 2019-01-23 | 2019-01-23 | Routing method and device based on weex framework, electronic equipment and readable medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111475138B (en) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104063415A (en) * | 2014-02-27 | 2014-09-24 | 优视科技有限公司 | Method and system for displaying webpage user-defined content |
| CN107329978A (en) * | 2017-05-31 | 2017-11-07 | 北京京东尚科信息技术有限公司 | The method for routing and device of multi-platform fusion |
| CN107368487A (en) * | 2016-05-12 | 2017-11-21 | 阿里巴巴集团控股有限公司 | A kind of page assembly Dynamic Distribution method, apparatus and client |
| CN107968841A (en) * | 2017-12-20 | 2018-04-27 | 深圳乐信软件技术有限公司 | Dynamic routing method, device, storage medium and the client of Webpage |
| CN109086114A (en) * | 2018-07-26 | 2018-12-25 | 郑州云海信息技术有限公司 | A kind of method, apparatus and terminal generating web front-end interactive interface |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20170277390A1 (en) * | 2016-03-23 | 2017-09-28 | International Business Machines Corporation | Providing user-defined application start pages |
-
2019
- 2019-01-23 CN CN201910063691.2A patent/CN111475138B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104063415A (en) * | 2014-02-27 | 2014-09-24 | 优视科技有限公司 | Method and system for displaying webpage user-defined content |
| CN107368487A (en) * | 2016-05-12 | 2017-11-21 | 阿里巴巴集团控股有限公司 | A kind of page assembly Dynamic Distribution method, apparatus and client |
| CN107329978A (en) * | 2017-05-31 | 2017-11-07 | 北京京东尚科信息技术有限公司 | The method for routing and device of multi-platform fusion |
| CN107968841A (en) * | 2017-12-20 | 2018-04-27 | 深圳乐信软件技术有限公司 | Dynamic routing method, device, storage medium and the client of Webpage |
| CN109086114A (en) * | 2018-07-26 | 2018-12-25 | 郑州云海信息技术有限公司 | A kind of method, apparatus and terminal generating web front-end interactive interface |
Non-Patent Citations (2)
| Title |
|---|
| Alban Mouton 等.Exploiting Routing Information Encoded into Backlinks to Improve Topical Crawling.2009 International Conference of Soft Computing and Pattern Recognition.2009,全文. * |
| 呙森林 等.Weex 跨平台开发方案研究与应用.信息通信.2017,全文. * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111475138A (en) | 2020-07-31 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111581563B (en) | Page response method and device, storage medium and electronic equipment | |
| US20140195663A1 (en) | Method and System for Providing Cloud-Based Common Distribution Applications | |
| CN110391938B (en) | Method and apparatus for deploying services | |
| CN112214408B (en) | Dependency conflict detection method, dependency conflict detection device, electronic equipment and computer readable medium | |
| CN111510466B (en) | Data updating method and device for client, electronic equipment and readable medium | |
| CN111309304B (en) | Method, device, medium and electronic equipment for generating IDL file | |
| CN110865852B (en) | Webpage component loading method and device, electronic equipment and storage medium | |
| CN113886336A (en) | Flow detection method, device, equipment and medium | |
| CN111459685A (en) | Communication method, device, equipment and readable medium of page end and native end | |
| CN110704833A (en) | Data permission configuration method, device, electronic device and storage medium | |
| CN111796865A (en) | Byte code file modification method and device, terminal equipment and medium | |
| CN111459581B (en) | Page switching method, device, electronic equipment and computer readable medium | |
| CN110489162A (en) | Installation kit SO file compressing method, device, medium and equipment | |
| CN112416303B (en) | Software development kit hot repair method and device and electronic equipment | |
| CN110888773B (en) | Method, device, medium and electronic equipment for acquiring thread identification | |
| CN109669720B (en) | Chain type asynchronous request processing method and device based on Promise and electronic equipment | |
| CN111752644A (en) | Interface simulation method, device, equipment and storage medium | |
| CN111475138B (en) | Routing method and device based on weex framework, electronic equipment and readable medium | |
| CN109857430B (en) | Data processing method, payment method and device for cross-container offline package and client | |
| CN111309406A (en) | Event processing method and device of application program and electronic equipment | |
| CN111797270A (en) | Audio playing method and device, electronic equipment and computer readable storage medium | |
| CN112379967B (en) | Simulator detection method, device, equipment and medium | |
| CN111460020B (en) | Method, device, electronic equipment and medium for resolving message | |
| CN109669679B (en) | Service detection and processing method and device and electronic equipment | |
| US9477448B2 (en) | Screen-oriented computing program refactoring |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |