CN111859204A - Information publishing method, device, equipment and storage medium - Google Patents
Information publishing method, device, equipment and storage medium Download PDFInfo
- Publication number
- CN111859204A CN111859204A CN202010623175.3A CN202010623175A CN111859204A CN 111859204 A CN111859204 A CN 111859204A CN 202010623175 A CN202010623175 A CN 202010623175A CN 111859204 A CN111859204 A CN 111859204A
- Authority
- CN
- China
- Prior art keywords
- user interface
- applet
- link information
- markup language
- interface element
- 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.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/955—Retrieval from the web using information identifiers, e.g. uniform resource locators [URL]
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/958—Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
Abstract
The embodiment of the application provides an information issuing method, an information issuing device, information issuing equipment and a storage medium, wherein the method comprises the following steps: in a rich text editor, if a first preset operation trigger aiming at an applet plug-in is monitored, calling the applet plug-in to acquire link information; generating a hypertext markup language tag corresponding to the link information by using the applet plug-in, wherein the hypertext markup language tag carries the link information; rendering the hypertext markup language tag to generate a user interface element; and publishing the user interface element on the current hypertext markup language page. Therefore, through the applet plug-in provided by the embodiment of the application, a user can insert the uniform resource positioning system of the applet into the rich text editor, the uniform resource positioning system of the applet published on a common hypertext markup language page is effective, and the user can jump to a corresponding page after clicking the uniform resource positioning system of the applet.
Description
Technical Field
The present application relates to the field of internet technologies, and in particular, to an information publishing method, apparatus, device, and storage medium.
Background
An RTE (Rich Text Editor) is a Text Editor that can be embedded in a browser and is what you see is what you get, and a user can edit an article or information conveniently by using the Rich Text Editor, so that the article or information can be published as soon as possible on a common HTML (hypertext Markup Language) page.
In the related art, a user may insert information such as a URL (Uniform Resource Locator), a picture, and a video into a rich text editor, so as to publish the information as soon as possible in a common HTML page.
Because the operating mechanism of the applet is not consistent with the standard of the HTML, if the information such as the URL, the picture, the video and the like of the applet is directly inserted into the rich text editor and is used for publishing the information in the ordinary HTML page as soon as possible, the URL of the applet published on the ordinary HTML page is invalid, and the specific expression is that the user cannot jump to the corresponding page after clicking the URL of the applet.
Disclosure of Invention
An object of the embodiments of the present application is to provide an information publishing method, apparatus, device, and storage medium, so as to achieve the beneficial effects that a URL of an applet published on a common HTML page is valid, and a user can jump to a corresponding page after clicking the URL of the applet. The specific technical scheme is as follows:
The application provides an information issuing method, which comprises the following steps:
in a rich text editor, if a first preset operation trigger for an applet plug-in is monitored, calling the applet plug-in to acquire link information, wherein the link information at least comprises one of the following information: a uniform resource positioning system of the small program and a uniform resource positioning system of the hypertext page;
generating a hypertext markup language tag corresponding to the link information by using the applet plug-in, wherein the hypertext markup language tag carries the link information;
rendering the hypertext markup language tag to generate a user interface element;
and publishing the user interface element on the current hypertext markup language page.
The application provides an information issuing method, which is applied to a client and comprises the following steps:
displaying user interface elements in a client display interface, wherein the user interface elements are generated by calling small program plug-ins in a rich text editor according to link information; the link information includes at least one of the following information: a uniform resource positioning system of the small program and a uniform resource positioning system of the hypertext page;
And if monitoring that the first preset operation aiming at the user interface element is triggered, jumping from a client display interface to an interface corresponding to the link information according to the link information corresponding to the user interface element.
The application provides an information issuing device, the device includes:
the plug-in calling module is used for calling the applet plug-in to acquire link information if a first preset operation trigger aiming at the applet plug-in is monitored in the rich text editor, wherein the link information at least comprises one of the following information: a uniform resource positioning system of the small program and a uniform resource positioning system of the hypertext page;
a tag generation module, configured to generate a hypertext markup language tag corresponding to the link information by using the applet plug-in, where the hypertext markup language tag carries the link information;
the label rendering module is used for rendering the hypertext markup language label to generate a user interface element;
and the element publishing module is used for publishing the user interface element on the current hypertext markup language page.
The application provides equipment which comprises a processor, a communication interface, a memory and a communication bus, wherein the processor and the communication interface are used for realizing mutual communication by the memory through the communication bus;
A memory for storing a computer program;
and the processor is used for realizing the information issuing method when executing the program stored in the memory.
The present application provides a storage medium having stored therein instructions that, when run on a computer, cause the computer to execute the information distribution method described above.
The present application provides a computer program product or a computer program comprising computer instructions stored on a computer-readable storage medium, which are read by a processor of a computer device from the computer-readable storage medium, and which are executed by the processor, so that the computer device executes the information distribution method provided above.
According to the technical scheme provided by the embodiment of the application, in a rich text editor, if a first preset operation trigger aiming at an applet plug-in is monitored, the applet plug-in is called to obtain link information, wherein the link information at least comprises one of the following information: the uniform resource positioning system of the small program and the uniform resource positioning system of the hypertext page utilize the small program plug-in to generate a hypertext markup language tag corresponding to the link information, wherein the hypertext markup language tag carries the link information, the hypertext markup language tag is rendered to generate a user interface element, and the user interface element is published on the current hypertext markup language page. Therefore, through the applet plug-in provided by the embodiment of the application, a user can insert the uniform resource positioning system of the applet into the rich text editor, the uniform resource positioning system of the applet published on a common hypertext markup language page is effective, and the user can jump to a corresponding page after clicking the uniform resource positioning system of the applet.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and together with the description, serve to explain the principles of the application.
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly described below, and it is obvious for those skilled in the art to obtain other drawings without inventive exercise.
Fig. 1 is a schematic view of an implementation flow of an information publishing method shown in an embodiment of the present application;
FIG. 2 is a schematic illustration of an applet plug-in interface shown in an embodiment of the present application;
FIG. 3 is a schematic diagram of a user interface element shown in an embodiment of the present application;
fig. 4 is a schematic flow chart of another information distribution method shown in the embodiment of the present application;
fig. 5 is a schematic flow chart of another information distribution method shown in the embodiment of the present application;
fig. 6 is a schematic structural diagram of an information distribution apparatus shown in an embodiment of the present application;
fig. 7 is a schematic structural diagram of an apparatus shown in an embodiment of the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
It should be noted that the terms "first," "second," and the like in the description and claims of this application and in the drawings described above are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the application described herein are capable of operation in sequences other than those illustrated or described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
In the embodiment of the present application, the provided information distribution method is particularly applicable to an electronic device, which may be a terminal, a server, or the like, and the information distribution method may be particularly executed by a processor in the electronic device.
As shown in fig. 1, an implementation flow diagram of an information publishing method provided in an embodiment of the present application is shown, where the method specifically includes the following steps:
s101, in a rich text editor, if a first preset operation trigger aiming at an applet plug-in is monitored, the applet plug-in is called to obtain link information.
In the embodiment of the application, based on the plug-in development capability provided by the rich text editor, the applet plug-in is provided, so that for operators, the applet plug-in can be used for smoothly releasing relevant information such as a Uniform Resource Locator (URL) of the applet without concerning the environmental problem.
In the rich text editor, if a first preset operation trigger for an applet plug-in is monitored, the applet plug-in can be called to obtain link information in the embodiment of the application. For rich text editors, the information is typically embedded in a browser to facilitate publishing of relevant information in a hypertext markup language (HTML) page.
Specifically, in the rich text editor, if a first preset operation trigger for a button corresponding to an applet plug-in is monitored, the applet plug-in may be called to obtain link information in the embodiment of the present application.
For the rich text editor, for example, tinymec, Ckeditor, UEditor, wangdeditor, etc. may be used, and this is not limited in this embodiment of the application.
The first preset operation may be, for example, a click operation, a slide operation, a selection operation, and the like, which is not limited in this embodiment of the application.
For example, taking tinymace as an example, in tinymace, when it is monitored that a click operation of a user on a button corresponding to an applet plug-in is triggered, the embodiment of the present application may call the applet plug-in to receive link information input by the user, where a schematic diagram of an interface of the applet plug-in is shown in fig. 2.
Wherein, for the link information, at least one of the following information is included: the URL of the applet and the URL of the hypertext page. In addition, the user may input information such as a link text, a link picture, and the like in the applet plug-in, and the applet plug-in may be used to receive the link text, the link picture, and the like input by the user, which is not limited in this application embodiment.
For example, the embodiment of the present application receives, by using an applet plug-in, a URL of an applet input by a user, as follows:
％2Fpages％2Fproduct％2Fdiscovery％2FriskAssessment％2FriskAsk％2Finde；
the URL of the hypertext page entered by the user is received with the applet plug-in as follows:
https://www.wesure.cn"data-type＝。
note that the hypertext page may be an HTML5 page, which is referred to as an H5 page for short, and this is not limited in the embodiment of the present application.
And S102, generating a hypertext markup language tag corresponding to the link information by using the applet plug-in, wherein the hypertext markup language tag carries the link information.
S103, rendering is carried out on the hypertext markup language tag to generate a user interface element.
And S104, publishing the user interface element on the current hypertext markup language page.
For link information received by the applet plug-in, the embodiment of the application can publish the link information in the current HTML page. Specifically, the link information may be published in the current HTML page upon receiving a publication instruction input by the user.
The link information may be specifically published in the current HTML page in the following manner:
generating an HTML (hypertext markup language) tag corresponding to the link information by using the applet plug-in, wherein the HTML tag carries the link information; rendering the HTML tag to generate a user interface element (namely a UI element); and publishing the user interface element on the current HTML page. Thus, the publishing of the link information is completed by publishing the user interface element on the current HTML page.
For example, for the URL of the applet and the URL of the HTML5 page received by the applet plug-in, an HTML tag corresponding to the URL of the applet and the URL of the HTML5 page is generated by the applet plug-in, where the HTML tag carries the URL of the applet and the URL of the HTML5 page as follows:
<span contenteditable＝"false"
data-url-mp＝"％2Fpages％2Fproduct％2Fdiscovery％2FriskAssessment％2FriskAsk％2Finde"
data-url-h5＝"https://www.wesure.cn"data-type＝"mplink">
click me to jump
</span>。
Wherein, URL of applet: data-URL-mp, URL of HTML5 page: data-URL-h5, mplink, for identifying the tag as "URL of applet".
For the generated HTML tag, rendering the HTML tag according to the embodiment of the present application may generate a user interface element, that is, a UI element, for example, as shown in fig. 3, the user interface element is published on the current HTML page, and thus, the publishing of the link information is completed by publishing the user interface element in the current HTML page. For the user, the effect seen is not distinguished from the ordinary URL insertion effect.
The method comprises the following steps of rendering the HTML label to generate a corresponding user interface element, wherein the specific rendering process comprises the following steps: and generating a rendering tree according to the HTML tag and a preset style, drawing the rendering tree by using a rendering engine, and generating a user interface element corresponding to the HTML tag.
In addition, the user interface element may be a picture chain or a text chain, which is not limited in the embodiment of the present application. The link information may thus be published in the form of a user interface element.
It should be noted that, for the HTML tag corresponding to the link information, when the link information includes the URL of the applet, an HTML tag corresponding to the URL of the applet is generated, when the link information includes the URL of the hypertext page, an HTML tag corresponding to the URL of the hypertext page is generated, and when the link information includes the URL of the applet and the URL of the hypertext page, an HTML tag corresponding to the URL of the applet and the URL of the hypertext page is generated, which means that an HTML tag corresponding to the link information may be generated in the embodiment of the present application.
Through the above description of the technical solution provided in the embodiment of the present application, in a rich text editor, if a first preset operation trigger for an applet plug-in is monitored, the applet plug-in is called to obtain link information, where the link information at least includes one of the following information: the uniform resource positioning system of the small program and the uniform resource positioning system of the hypertext page utilize the small program plug-in to generate a hypertext markup language tag corresponding to the link information, wherein the hypertext markup language tag carries the link information, the hypertext markup language tag is rendered to generate a user interface element, and the user interface element is published on the current hypertext markup language page. Therefore, through the applet plug-in provided by the embodiment of the application, a user can insert the uniform resource positioning system of the applet into the rich text editor, the uniform resource positioning system of the applet published on a common hypertext markup language page is effective, and the user can jump to a corresponding page after clicking the uniform resource positioning system of the applet.
As shown in fig. 4, an implementation flow diagram of another information publishing method provided in the embodiment of the present application is provided, where the method specifically includes the following steps:
s401, in a rich text editor, if a first preset operation trigger aiming at an applet plug-in is monitored, the applet plug-in is called to obtain link information.
S402, generating a hypertext markup language tag corresponding to the link information by using the applet plug-in, wherein the hypertext markup language tag carries the link information.
S403, rendering the hypertext markup language tag to generate a user interface element.
S404, publishing the user interface element on the current hypertext markup language page.
S405, after the user interface element is published on the current hypertext markup language page, if a second preset operation trigger aiming at the user interface element is monitored, extracting link information in the hypertext markup language tag corresponding to the user interface element by using a preset script.
In the embodiment of the application, the applet plug-in is used for generating an HTML tag corresponding to the link information, rendering is performed on the HTML tag to generate a user interface element, and the user interface element is published on the current HTML page. Therefore, the user interface element exists in the current HTML page, and the link information is published in the form of the user interface element, so that the user can conveniently forward, share and read the link information subsequently.
For the user interface element, in the embodiment of the application, after the user interface element is published on the current HTML page, the link information in the HTML tag corresponding to the user interface element can be extracted by using a preset script under the condition that a second preset operation trigger for the user interface element is monitored.
The second preset operation may be, for example, a click operation, a slide operation, a selection operation, and the like, which is not limited in this embodiment of the application.
For example, as shown in fig. 3, after the user interface element is published on the current HTML page, when it is monitored that a click operation is triggered for the user interface element, the JavaScript script may be used to extract the URL of the applet and the URL of the HTML5 page in the HTML tag corresponding to the user interface element.
The HTML tag further comprises a target identifier corresponding to the link information, the target identifier in the HTML tag corresponding to the user interface element can be captured by using a preset script, and then the link information in the HTML tag corresponding to the user interface element can be extracted according to the target identifier.
For example, for the HTML tag corresponding to the user interface element, the tag further includes a target identifier corresponding to the link information, as follows:
<span contenteditable＝"false"
data-url-mp＝"％2Fpages％2Fproduct％2Fdiscovery％2FriskAssessment％2FriskAsk％2Finde"
data-url-h5＝"https://www.wesure.cn"data-type＝"mplink">
click me to jump
</span>。
Wherein, URL of applet: data-URL-mp, URL of HTML5 page: data-URL-h5, where an mplink is present, and is used to identify the tag as "URL of applet", in an embodiment of the present application, a target identifier mplink in the HTML tag corresponding to the user interface element may be captured by using a JavaScript script, and then, according to the target identifier mplink, the URL of the applet in the HTML tag corresponding to the user interface element may be extracted: data-URL-mp, URL of HTML5 page: data-url-h 5.
S406, executing corresponding jump operation according to the link information.
And for at least one of the link information extracted through the steps, namely the URL of the small program and the URL of the hypertext page, executing corresponding jump operation according to the link information so as to jump to the page corresponding to the link information.
Specifically, as shown in fig. 5, the embodiment of the present application may determine whether the user interface element is located in an applet; if the user interface element is positioned in the small program, skipping from the current HTML page to the small program page corresponding to the link information; and if the user interface element is not positioned in the applet, jumping from the current HTML page to an HTML5 page corresponding to the link information. Thus, different jump operations can be executed based on different environments in which the user interface elements are located.
For example, for a user interface element as shown in fig. 3, it is determined whether the user interface element is located within an applet; if the user interface element is positioned in the small program, skipping from the current HTML page to the small program page corresponding to the link information; and if the user interface element is not positioned in the applet, jumping from the current HTML page to an HTML5 page corresponding to the link information. Thus, different jump operations can be executed based on different environments in which the user interface elements are located.
Wherein for an applet there is a unique application identity, as for a browser. Therefore, the application identifier of the application corresponding to the HTML page where the user interface element is currently located can be obtained, and whether the user interface element is currently located in the applet or not is judged based on the application identifier.
For example, assuming that the applet has a unique application identifier a, and as for the browser, there is a unique application identifier B, the application identifier a of the application corresponding to the HTML page where the user interface element is currently located may be obtained, and it may be determined that the user interface element is currently located in the applet based on the application identifier a, so that the applet page corresponding to the link information is jumped from the current HTML page.
For another example, an application identifier B of an application corresponding to the HTML page where the user interface element is currently located may be obtained, and it may be determined that the user interface element is not currently located in the applet based on the application identifier B, so that the current HTML page jumps to the HTML5 page corresponding to the link information.
In addition, because the environments of the user interface elements are different, in the process of executing the jump operation, the jump operation is distinguished:
if the user interface element is located in the applet, a jump component corresponding to the applet can be obtained, and the jump component is utilized to jump from the current HTML page to the applet page corresponding to the link information.
For example, if the user interface element is located in the WeChat applet, an SDK jump component corresponding to the WeChat applet can be obtained, and the current HTML page is jumped to the applet page corresponding to the link information by using the SDK jump component, specifically, the current HTML page is jumped to the applet page corresponding to the link information by using the wx.
If the user interface element is located in the hundred-degree applet, the SDK jump component corresponding to the hundred-degree applet can be obtained, and the SDK jump component is utilized to jump from the current HTML page to the applet page corresponding to the link information.
If the user interface element is not located in the applet currently, a preset page jump instruction can be used for jumping from the current HTML page to the HTML5 page corresponding to the link information.
For example, if the user interface element is not located in the applet, the jump can be made using window.
Through the above description of the technical solution provided in the embodiment of the present application, in a rich text editor, if a first preset operation trigger for an applet plug-in is monitored, the applet plug-in is called, and link information input by a user is received by using the applet plug-in, where the link information at least includes one of the following information: the method comprises the steps of utilizing an applet plug-in to generate a hypertext markup language tag corresponding to link information, conducting rendering aiming at the hypertext markup language tag to generate a user interface element, utilizing the user interface element to publish the link information in a current hypertext markup language page, after the user interface element is published in the current hypertext markup language page, if a second preset operation trigger aiming at the user interface element is monitored, utilizing a preset script to extract the link information in the hypertext markup language tag corresponding to the user interface element, and executing corresponding jump operation according to the link information. Therefore, by the applet plug-in provided by the embodiment of the application, a user can directly plug in the uniform resource positioning system of the applet in the rich text editor without concerning the environment, the uniform resource positioning system of the applet published on a common hypertext markup language page is effective, and the user can jump to the corresponding page after clicking the uniform resource positioning system of the applet.
The embodiment of the present application provides another information publishing method, which is applied to a client, and the method specifically may include:
displaying user interface elements in a client display interface, wherein the user interface elements are generated by calling small program plug-ins in a rich text editor according to link information; the link information includes at least one of the following information: a uniform resource location system for applets and a uniform resource location system for hypertext pages.
In the embodiment of the present invention, a user interface element (i.e., a UI element) may be displayed in the client display interface, where the user interface element is generated by invoking an applet plug-in a rich text editor and according to link information, where the link information at least includes one of the following information: a uniform resource location system for applets and a uniform resource location system for hypertext pages.
And if monitoring that the first preset operation aiming at the user interface element is triggered, jumping from a client display interface to an interface corresponding to the link information according to the link information corresponding to the user interface element.
In the embodiment of the invention, for a user interface element, if a first preset operation trigger for the user interface element is monitored, the user interface element can jump from a client display interface to an interface corresponding to link information according to the link information corresponding to the user interface element. The above embodiments may be referred to for specific execution flows, and the embodiments of the present invention are not described in detail herein.
The user interface element can be specifically generated in the following way: if a second preset operation trigger aiming at the applet plug-in is monitored, calling the applet plug-in to acquire link information; generating a hypertext markup language tag corresponding to the link information by using the applet plug-in, wherein the hypertext markup language tag carries the link information; and rendering the hypertext markup language tag to generate a user interface element. The above embodiments may be referred to for specific execution flows, and the embodiments of the present invention are not described in detail herein.
Corresponding to the foregoing method embodiment, an embodiment of the present application further provides an information issuing apparatus, and as shown in fig. 6, the apparatus may include: a plug-in calling module 610, a label generating module 620, a label rendering module 630 and an element publishing module 640.
The plug-in calling module 610 is configured to, in the rich text editor, call an applet plug-in to obtain link information if a first preset operation trigger for the applet plug-in is monitored, where the link information at least includes one of the following information: a uniform resource positioning system of the small program and a uniform resource positioning system of the hypertext page;
A tag generation module 620, configured to generate a hypertext markup language tag corresponding to the link information by using the applet plug-in, where the hypertext markup language tag carries the link information;
a tag rendering module 630, configured to render the hypertext markup language tag to generate a user interface element;
and the element publishing module 640 is configured to publish the user interface element on the current hypertext markup language page.
In a specific implementation manner of the embodiment of the present application, after publishing the user interface element on the current html page, the apparatus further includes:
an information extraction module 650, configured to, if it is monitored that a second preset operation for the user interface element is triggered, extract link information in the hypertext markup language tag corresponding to the user interface element by using a preset script;
and the page jump module 660 is configured to execute a corresponding jump operation according to the link information.
In a specific implementation manner of the embodiment of the present application, the hypertext markup language tag further includes a target identifier corresponding to the link information; the information extraction module 650 is specifically configured to:
Capturing a target identifier in the hypertext markup language tag corresponding to the user interface element by using a preset script;
and extracting link information in the hypertext markup language tag corresponding to the user interface element according to the target identifier.
In a specific implementation manner of the embodiment of the present application, the page jump module 660 specifically includes:
a first skip submodule 661, configured to skip from a current html page to an applet page corresponding to the link information when the ui element is currently located in the applet;
and a second skip submodule 662, configured to skip from the current hypertext markup language page to the hypertext page corresponding to the link information when the user interface element is not currently located in the applet.
In a specific implementation manner of the embodiment of the present application, the first skip sub-module 661 is specifically configured to:
acquiring an application identifier of an application corresponding to a hypertext markup language page where the user interface element is currently located;
judging whether the application identifier of the application corresponding to the hypertext markup language page where the user interface element is currently located is matched with the application identifier corresponding to the applet or not;
If the application identifier of the application corresponding to the hypertext markup language page where the user interface element is currently located is matched with the application identifier corresponding to the applet, determining that the user interface element is currently located in the applet;
under the condition that the user interface element is currently positioned in the small program, skipping from the current hypertext markup language page to the small program page corresponding to the link information;
the second skip sub-module 662 is specifically configured to:
if the application identifier of the application corresponding to the hypertext markup language page where the user interface element is currently located is not matched with the application identifier corresponding to the applet, determining that the user interface element is not currently located in the applet;
and under the condition that the user interface element is not positioned in the applet currently, skipping from the current hypertext markup language page to the hypertext page corresponding to the link information.
In a specific implementation manner of the embodiment of the present application, the first skip sub-module 661 is specifically configured to:
under the condition that the user interface element is currently located in an applet, acquiring a jump component corresponding to the applet;
and jumping to the small program page corresponding to the link information from the current hypertext markup language page by utilizing the jumping component.
In a specific implementation manner of the embodiment of the present application, the second skip sub-module 662 is specifically configured to:
and under the condition that the user interface element is not positioned in the small program currently, jumping to the hypertext page corresponding to the link information from the current hypertext markup language page by using a preset page jumping instruction.
The embodiment of the present application further provides an apparatus, as shown in fig. 7, including a processor 71, a communication interface 72, a memory 73, and a communication bus 74, where the processor 71, the communication interface 72, and the memory 73 complete mutual communication through the communication bus 74,
a memory 73 for storing a computer program;
the processor 71, when executing the program stored in the memory 73, implements the following steps:
in a rich text editor, if a first preset operation trigger for an applet plug-in is monitored, calling the applet plug-in to acquire link information, wherein the link information at least comprises one of the following information: a uniform resource positioning system of the small program and a uniform resource positioning system of the hypertext page; generating a hypertext markup language tag corresponding to the link information by using the applet plug-in, wherein the hypertext markup language tag carries the link information; rendering the hypertext markup language tag to generate a user interface element; and publishing the user interface element on the current hypertext markup language page.
The communication bus mentioned in the above device may be a Peripheral Component Interconnect (PCI) bus, an Extended Industry Standard Architecture (EISA) bus, or the like. The communication bus may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown, but this does not mean that there is only one bus or one type of bus.
The communication interface is used for communication between the above-mentioned device and other devices.
The Memory may include a Random Access Memory (RAM) or a non-volatile Memory (non-volatile Memory), such as at least one disk Memory. Optionally, the memory may also be at least one memory device located remotely from the processor.
The Processor may be a general-purpose Processor, and includes a Central Processing Unit (CPU), a Network Processor (NP), and the like; the device can also be a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other Programmable logic device, a discrete Gate or transistor logic device, or a discrete hardware component.
In another embodiment provided by the present application, a storage medium is further provided, where instructions are stored, and when the instructions are executed on a computer, the instructions cause the computer to execute the information distribution method in any one of the above embodiments.
In yet another embodiment provided by the present application, there is also provided a computer program product containing instructions which, when run on a computer, cause the computer to perform the information distribution method described in any of the above embodiments.
In the above embodiments, the implementation may be wholly or partially realized by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loaded and executed on a computer, cause the processes or functions described in accordance with the embodiments of the application to occur, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored on a storage medium or transmitted from one storage medium to another, for example, from one website, computer, server, or data center to another website, computer, server, or data center via wire (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The storage medium may be any available medium that can be accessed by a computer or a data storage device including one or more available media integrated servers, data centers, and the like. The usable medium may be a magnetic medium (e.g., floppy Disk, hard Disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., Solid State Disk (SSD)), among others.
It is noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
All the embodiments in the present specification are described in a related manner, and the same and similar parts among the embodiments may be referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the system embodiment, since it is substantially similar to the method embodiment, the description is simple, and for the relevant points, reference may be made to the partial description of the method embodiment.
The above description is only for the preferred embodiment of the present application, and is not intended to limit the scope of the present application. Any modification, equivalent replacement, improvement and the like made within the spirit and principle of the present application are included in the protection scope of the present application.
Claims (12)
1. An information distribution method, characterized in that the method comprises:
in a rich text editor, if a first preset operation trigger for an applet plug-in is monitored, calling the applet plug-in to acquire link information, wherein the link information at least comprises one of the following information: a uniform resource positioning system of the small program and a uniform resource positioning system of the hypertext page;
generating a hypertext markup language tag corresponding to the link information by using the applet plug-in, wherein the hypertext markup language tag carries the link information;
rendering the hypertext markup language tag to generate a user interface element;
and publishing the user interface element on the current hypertext markup language page.
2. The method of claim 1, wherein after publishing the user interface element on a current hypertext markup language page, the method further comprises:
If monitoring that a second preset operation trigger aiming at the user interface element is triggered, extracting link information in the hypertext markup language tag corresponding to the user interface element by using a preset script;
and executing corresponding jump operation according to the link information.
3. The method according to claim 2, wherein the hypertext markup language tag further comprises a target identifier corresponding to the link information; the extracting, by using a preset script, the link information in the hypertext markup language tag corresponding to the user interface element includes:
capturing a target identifier in the hypertext markup language tag corresponding to the user interface element by using a preset script;
and extracting link information in the hypertext markup language tag corresponding to the user interface element according to the target identifier.
4. The method of claim 2, wherein the performing the corresponding jump operation according to the link information comprises:
under the condition that the user interface element is currently positioned in the small program, skipping from the current hypertext markup language page to the small program page corresponding to the link information;
And under the condition that the user interface element is not positioned in the applet currently, skipping from the current hypertext markup language page to the hypertext page corresponding to the link information.
5. The method of claim 4, wherein jumping from a current hypertext markup language page to an applet page corresponding to the link information in the case that the user interface element is currently located in the applet comprises:
acquiring an application identifier of an application corresponding to a hypertext markup language page where the user interface element is currently located;
judging whether the application identifier of the application corresponding to the hypertext markup language page where the user interface element is currently located is matched with the application identifier corresponding to the applet or not;
if the application identifier of the application corresponding to the hypertext markup language page where the user interface element is currently located is matched with the application identifier corresponding to the applet, determining that the user interface element is currently located in the applet;
under the condition that the user interface element is currently positioned in the small program, skipping from the current hypertext markup language page to the small program page corresponding to the link information;
and when the user interface element is not currently located in the applet, jumping from the current hypertext markup language page to a hypertext page corresponding to the link information, including:
If the application identifier of the application corresponding to the hypertext markup language page where the user interface element is currently located is not matched with the application identifier corresponding to the applet, determining that the user interface element is not currently located in the applet;
and under the condition that the user interface element is not positioned in the applet currently, skipping from the current hypertext markup language page to the hypertext page corresponding to the link information.
6. The method of claim 4, wherein jumping from a current hypertext markup language page to an applet page corresponding to the link information in the case that the user interface element is currently located in the applet comprises:
under the condition that the user interface element is currently located in an applet, acquiring a jump component corresponding to the applet;
and jumping to the small program page corresponding to the link information from the current hypertext markup language page by utilizing the jumping component.
7. The method of claim 4, wherein in the case that the user interface element is not currently located in an applet, jumping from a current hypertext markup language page to a hypertext page corresponding to the link information comprises:
And under the condition that the user interface element is not positioned in the small program currently, jumping to the hypertext page corresponding to the link information from the current hypertext markup language page by using a preset page jumping instruction.
8. An information publishing method applied to a client, the method comprising:
displaying user interface elements in a client display interface, wherein the user interface elements are generated by calling small program plug-ins in a rich text editor according to link information; the link information includes at least one of the following information: a uniform resource positioning system of the small program and a uniform resource positioning system of the hypertext page;
and if monitoring that the first preset operation aiming at the user interface element is triggered, jumping from a client display interface to an interface corresponding to the link information according to the link information corresponding to the user interface element.
9. The method according to claim 8, wherein the user interface element is generated in the rich text editor by calling an applet plug-in based on the link information, and specifically comprises:
if a second preset operation trigger aiming at the applet plug-in is monitored, calling the applet plug-in to acquire link information;
Generating a hypertext markup language tag corresponding to the link information by using the applet plug-in, wherein the hypertext markup language tag carries the link information;
and rendering the hypertext markup language tag to generate a user interface element.
10. An information distribution apparatus, characterized in that the apparatus comprises:
the plug-in calling module is used for calling the applet plug-in to acquire link information if a first preset operation trigger aiming at the applet plug-in is monitored in the rich text editor, wherein the link information at least comprises one of the following information: a uniform resource positioning system of the small program and a uniform resource positioning system of the hypertext page;
a tag generation module, configured to generate a hypertext markup language tag corresponding to the link information by using the applet plug-in, where the hypertext markup language tag carries the link information;
the label rendering module is used for rendering the hypertext markup language label to generate a user interface element;
and the element publishing module is used for publishing the user interface element on the current hypertext markup language page.
11. The device is characterized by comprising a processor, a communication interface, a memory and a communication bus, wherein the processor and the communication interface are used for realizing mutual communication by the memory through the communication bus;
a memory for storing a computer program;
a processor for implementing the method steps of any one of claims 1 to 9 when executing a program stored in the memory.
12. A storage medium on which a computer program is stored which, when being executed by a processor, carries out the method according to any one of claims 1-9.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010623175.3A CN111859204A (en) | 2020-06-30 | 2020-06-30 | Information publishing method, device, equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010623175.3A CN111859204A (en) | 2020-06-30 | 2020-06-30 | Information publishing method, device, equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111859204A true CN111859204A (en) | 2020-10-30 |
Family
ID=72988935
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010623175.3A Pending CN111859204A (en) | 2020-06-30 | 2020-06-30 | Information publishing method, device, equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111859204A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112799561A (en) * | 2021-02-05 | 2021-05-14 | 北京字节跳动网络技术有限公司 | Information display method and device and computer storage medium |
| CN115309298A (en) * | 2022-08-30 | 2022-11-08 | 医渡云（北京）技术有限公司 | Text structuring method and device, medium and equipment based on rich text editor |
-
2020
- 2020-06-30 CN CN202010623175.3A patent/CN111859204A/en active Pending
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112799561A (en) * | 2021-02-05 | 2021-05-14 | 北京字节跳动网络技术有限公司 | Information display method and device and computer storage medium |
| CN115309298A (en) * | 2022-08-30 | 2022-11-08 | 医渡云（北京）技术有限公司 | Text structuring method and device, medium and equipment based on rich text editor |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107562620B (en) | Automatic buried point setting method and device | |
| CN110708346B (en) | Information processing system and method | |
| CN108304498B (en) | Webpage data acquisition method and device, computer equipment and storage medium | |
| CN109739717B (en) | Page data acquisition method and device and server | |
| CN110955428A (en) | Page display method and device, electronic equipment and medium | |
| CN110263070B (en) | Event reporting method and device | |
| CN110598135A (en) | Network request processing method and device, computer readable medium and electronic equipment | |
| CN110442286B (en) | Page display method and device and electronic equipment | |
| CN112637361B (en) | Page proxy method, device, electronic equipment and storage medium | |
| CN111859204A (en) | Information publishing method, device, equipment and storage medium | |
| CN111552633A (en) | Interface abnormal call testing method and device, computer equipment and storage medium | |
| CN103559222A (en) | Method and device for displaying page loading time in browsers | |
| CN111177519A (en) | Webpage content acquisition method and device, storage medium and equipment | |
| CN113076294A (en) | Information sharing method and device | |
| CN113934913A (en) | Data capture method and device, storage medium and electronic equipment | |
| CN109829121B (en) | Method and device for reporting click behavior data | |
| CN109542501B (en) | Browser table compatibility method and device, computer equipment and storage medium | |
| CN109862074B (en) | Data acquisition method and device, readable medium and electronic equipment | |
| CN110321504B (en) | Page processing method and device | |
| CN104899203B (en) | Webpage generation method and device and terminal equipment | |
| CN108509228B (en) | Page loading method, terminal equipment and computer readable storage medium | |
| CN107038117B (en) | Web automatic testing method based on definition-reference between event processing functions | |
| CN112882933A (en) | Script recording method, device, equipment and storage medium | |
| CN109446451B (en) | Webpage display method, device, medium and computing equipment | |
| CN108037914B (en) | Method and device for developing android native system by combining js |
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 |