CN112114800A - Browser interface processing method and device - Google Patents

Browser interface processing method and device Download PDF

Info

Publication number
CN112114800A
CN112114800A CN202011062447.3A CN202011062447A CN112114800A CN 112114800 A CN112114800 A CN 112114800A CN 202011062447 A CN202011062447 A CN 202011062447A CN 112114800 A CN112114800 A CN 112114800A
Authority
CN
China
Prior art keywords
event
browser
interface
type
processing
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.)
Granted
Application number
CN202011062447.3A
Other languages
Chinese (zh)
Other versions
CN112114800B (en
Inventor
刘文华
安晓江
蒋红宇
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Beijing Haitai Fangyuan High Technology Co Ltd
Original Assignee
Beijing Haitai Fangyuan High Technology Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Beijing Haitai Fangyuan High Technology Co Ltd filed Critical Beijing Haitai Fangyuan High Technology Co Ltd
Priority to CN202011062447.3A priority Critical patent/CN112114800B/en
Publication of CN112114800A publication Critical patent/CN112114800A/en
Application granted granted Critical
Publication of CN112114800B publication Critical patent/CN112114800B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/30Creation or generation of source code
    • G06F8/34Graphical or visual programming
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/30Creation or generation of source code
    • G06F8/38Creation or generation of source code for implementing user interfaces
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46Multiprogramming arrangements
    • G06F9/54Interprogram communication
    • G06F9/542Event management; Broadcasting; Multicasting; Notifications
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46Multiprogramming arrangements
    • G06F9/54Interprogram communication
    • G06F9/545Interprogram communication where tasks reside in different layers, e.g. user- and kernel-space

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Human Computer Interaction (AREA)
  • Multimedia (AREA)
  • User Interface Of Digital Computer (AREA)

Abstract

The application discloses a browser interface processing method and device. After a browser event of a browser framework monitored by an operating system is obtained, performing event type verification on the browser event according to a configured browser event set; if the browser event is a first type event, performing graph drawing processing on the browser event; if the browser event is the second type of event, the browser event is sent to a browser kernel so that the browser kernel can process the browser event; and displaying the event processing result on the browser interface. The method can separate the processing of the browser kernel event from the processing of the browser interface graphic drawing event, simplify the design process of an interface designer, and improve the user experience.

Description

Browser interface processing method and device
Technical Field
The present application relates to the field of computer technologies, and in particular, to a browser interface processing method and apparatus.
Background
The existing browser Interface design method is a scheme heavily dependent on the kernel of an open-source browser engine webkit, and developers need to fully know that each component of a User Interface (UI) in a browser with a chrome architecture can modify Interface elements such as skin color, buttons and icons.
The browser interface of the existing chromium architecture has high development difficulty and numerous concepts, and the problem that a graphical user interface development framework commonly used by a Linux operating system, such as Qt, Gtk, DUILib and the like, is incompatible needs to be solved by professional technicians familiar with the design of the browser interface, so that the browser interface development method has high limitation on designers, and reduces user experience.
Disclosure of Invention
The embodiment of the application provides a browser interface processing method and device, solves the problems in the prior art, and improves user experience.
In a first aspect, a browser interface processing method is provided, where the method is applied in a graphics rendering architecture, and the method may include:
acquiring a browser event monitored by an operating system;
according to the configured browser event set, performing event type verification on the browser event; the browser event set comprises event types corresponding to all browser events;
if the browser event is a first type event, carrying out graphic drawing processing on the browser event; the first type event is a browser interface drawing event processed by the graph drawing framework;
if the browser event is a second type event, sending the browser event to a browser kernel so that the browser kernel processes the browser event; the first type of event is different from the second type of event;
and displaying the event processing result on the browser interface.
In an optional implementation, if the browser event is a first type event, performing a graph drawing process on the browser event, including:
and if the browser interface drawing event is a graph drawing event processed by the graph drawing framework, performing graph drawing processing on the browser interface drawing event by adopting a preset graph drawing frame.
In an optional implementation, if the browser event is a first type event, performing a graph drawing process on the browser event, including:
if the browser interface drawing event is not the graph drawing event processed by the graph drawing framework, calling the graph drawing information in the basic graph drawing framework stored by the browser, and performing graph drawing processing on the browser interface drawing event.
In an alternative implementation, sending the browser event to a browser kernel includes:
sending the browser event to an abstraction layer of the browser;
and sending the browser event to the browser kernel through the abstraction layer.
In an optional implementation, before sending the browser event to an abstraction layer of the browser, the method further includes:
establishing a coupling connection with the abstract layer; the coupling connection is for coupling with the abstraction layer event handling function.
In an alternative implementation, the second type of event is a browser interface element typesetting layout event, a mouse event, or a keyboard event.
In a second aspect, a browser interface processing apparatus is provided, which may include: the device comprises an acquisition unit, a verification unit, a processing unit and a display unit;
the acquisition unit is used for acquiring a browser event of a browser architecture monitored by an operating system;
the verification unit is used for verifying the event type of the browser event according to the configured browser event set; the browser event set comprises event types corresponding to all browser events;
the processing unit is used for carrying out graphic drawing processing on the browser event if the browser event is a first type event; the first type event is a browser interface drawing event processed by the graph drawing framework;
if the browser event is a second type event, sending the browser event to a browser kernel so that the browser kernel processes the browser event; the first type of event is different from the second type of event;
and the display unit is used for displaying the event processing result on the browser interface.
In an optional implementation, the processing unit is specifically configured to perform, if the browser interface drawing event is a graph drawing event handled by the graph drawing framework itself, a preset graph drawing frame to perform graph drawing processing on the browser interface drawing event.
In an optional implementation, the processing unit is further specifically configured to, if the browser interface drawing event is not a graph drawing event handled by the graph drawing framework itself, invoke graph drawing information in a basic graph drawing frame stored in the browser, and perform graph drawing processing on the browser interface drawing event.
In an optional implementation, the processing unit is further specifically configured to send the browser event to an abstraction layer of the browser;
and sending the browser event to the browser kernel through the abstraction layer.
In an alternative implementation, the apparatus further comprises a setup unit;
the establishing unit is used for establishing coupling connection with the abstract layer; the coupling connection is for coupling with the abstraction layer event handling function.
In an alternative implementation, the second type of event is a browser interface element typesetting layout event, a mouse event, or a keyboard event.
In a third aspect, an electronic device is provided, which includes a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory complete communication with each other through the communication bus;
a memory for storing a computer program;
a processor adapted to perform the method steps of any of the above first aspects when executing a program stored in the memory.
In a fourth aspect, a computer-readable storage medium is provided, having stored therein a computer program which, when executed by a processor, performs the method steps of any of the above first aspects.
According to the browser interface processing method provided by the embodiment of the invention, after a browser event monitored by an operating system is obtained, event type verification is carried out on the browser event according to a configured browser event set; if the browser event is a first type event, performing graph drawing processing on the browser event; if the browser event is the second type of event, the browser event is sent to a browser kernel so that the browser kernel can process the browser event; and displaying the event processing result on the browser interface. If the browser event is a browser interface drawing event, processing the browser interface drawing event; if the browser event is not a browser interface drawing event, sending the browser event to a browser kernel so as to process the browser event; and displaying the event processing result on the browser interface. The method can separate the processing of the browser kernel event from the processing of the browser interface graphic drawing event, simplify the design process of an interface designer, and improve the user experience.
Drawings
Fig. 1 is a schematic view of a browser architecture applied to a browser interface processing method according to an embodiment of the present invention;
fig. 2 is a schematic diagram of a graph drawing architecture according to an embodiment of the present invention;
fig. 3 is a schematic flowchart of a browser interface processing method according to an embodiment of the present invention;
fig. 4 is a schematic diagram illustrating a browser interface drawing event processing result according to an embodiment of the present invention;
fig. 5 is a schematic diagram of a browser event processing result except a browser interface drawing event according to an embodiment of the present invention;
fig. 6 is a schematic structural diagram of a browser interface processing apparatus according to an embodiment of the present invention;
fig. 7 is a flowchart of an electronic device according to an embodiment of the present invention.
Detailed Description
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 only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present application without any creative effort belong to the protection scope of the present application.
The browser interface processing method provided by the embodiment of the invention can be applied to the browser architecture shown in fig. 1. The target browser architecture may include: the System comprises a chrome project architecture, a graph drawing architecture created by the application, a graph design framework (Window System) stored by a browser and a browser Kernel (Kernel).
Among them, the chrome project architecture may include a rendering engine layer Blink and an abstraction layer Ozone of the browser.
The graph drawing framework is used for drawing a user-defined graph or a complex graph; which may include Qt-based graphics rendering framework, Gtk-based graphics rendering framework, DUILib-based graphics rendering framework, or the like.
The Window System is used for drawing a basic graph drawing frame for drawing a basic graph or a conventional graph, such as drawing a triangle, drawing a straight line, drawing a point and the like.
Kernel, for processing other events than graph drawing events.
The graphic rendering framework is coupled with an event handling function of an abstraction layer Ozone in the Chromium project framework, wherein the coupling connection can enable the graphic rendering framework to inherit the event handling function of the abstraction layer Ozone or a part of the event handling function containing the abstraction layer Ozone. As shown in fig. 2, taking the graphics rendering architecture as Gtk graphics rendering architecture as an example, the graphics rendering architecture may include:
a graphic drawing Window (Gtk Window) coupled with an abstraction Window (Platform Window) in the Ozone;
a browser Event set (Event Source Gtk) coupled with an abstract Event set (Platform Event Source) in Ozone; the browser event set comprises event types corresponding to the browser events, and the event types in the browser event set are more than the event types of the abstract event set. For example, the event types in the browser event set include browser interface drawing events which can be processed by the graphic drawing framework and events which cannot be processed by the graphic drawing framework, such as browser interface element typesetting and layout events, mouse events, keyboard events and the like, while the abstract event set only includes events which cannot be processed by the graphic drawing framework.
Window management (Window manager gtk) coupled to a drawing Surface manager (Surface Factory Ozone) in Ozone;
a Platform dependent component manager (Ozone Platform Gtk) coupled to the Platform dependent component manager (Ozone Platform) in the Ozone;
it should be noted that the graphics rendering architecture may also be built in the Ozone, and the event processing function in the Ozone is used to complete the rendering of the browser interface event.
The browser architecture does not require an Interface designer to understand the concepts and functions of the various components of the User Interface (UI) in the browser of the chrome architecture. For the browser interface drawing event, the graphic drawing framework can realize the processing of the browser interface drawing event; for the event which can not be processed by the graph drawing framework, the event can be sent to the browser kernel through the Ozone, so that the event can be processed by the browser kernel, the design process of an interface designer is simplified, and the user experience is improved.
The preferred embodiments of the present application will be described below with reference to the accompanying drawings of the specification, it being understood that the preferred embodiments described herein are merely for illustrating and explaining the present invention and are not intended to limit the present invention, and that the embodiments and features of the embodiments in the present application may be combined with each other without conflict.
Fig. 3 is a flowchart illustrating a browser interface processing method according to an embodiment of the present application. The execution subject of the method is the graph drawing architecture created by the application, and as shown in fig. 3, the method may include:
step 310, obtaining a browser event monitored by an operating system.
Browser events may include browser mouse events, keyboard events, drag and drop events, and browser interface drawing events.
A mouse event refers to an event that is triggered when a mouse button is pressed on an interface element of a browser, when a mouse pointer is moved onto an interface element, or when a mouse button is released on an interface element.
A keyboard event is an event triggered when a user presses a key or when the user releases a key.
Drag and drop events refer to events that are triggered when an element is dragged, when a drag operation begins, when an element is being dragged on an active drag and drop target, and when an element has been dragged to a target area.
The interface drawing event refers to an event triggered when a graph is required to be drawn in a browser interface, namely a drawing event of an element icon in the interface.
And step 320, processing the browser event.
The graph drawing framework can detect the Event type of the browser Event according to the configured browser Event set (Event Source Gtk).
If the browser event is a first type event, performing graph drawing processing on the browser event; the first type of event is a browser interface drawing event handled by the graphics drawing architecture.
If the browser event is the second type of event, the browser event is sent to a browser kernel so as to be processed; the second type of event is an event different from the first type of event, namely a browser event which cannot be processed by the graph drawing architecture.
(1) And if the browser event is a second type of event, such as a browser interface element typesetting layout event, a mouse event or a keyboard event, sending the browser event to a browser kernel so that the browser kernel processes the browser event.
In specific implementation, if the graph drawing architecture is built in an abstraction layer Ozone of the browser, the graph drawing architecture can directly send a browser event to a browser kernel, and the browser event is processed through the browser kernel.
If the graph drawing architecture is externally arranged on the Ozone of the abstract layer, a browser event needs to be sent to the Ozone of the abstract layer, the browser event is sent to a browser kernel through the abstract layer, and the browser event is processed through the browser kernel.
(2) And if the browser event is the first type of event, performing graph drawing processing on the browser event.
In specific implementation, if the browser interface drawing event is a graph drawing event that can be processed by the graph drawing framework, a preset graph drawing frame, such as a graph drawing frame based on Qt or a graph drawing frame based on Gtk, is used to perform graph drawing processing on the browser interface drawing event;
and if the browser interface drawing event is not the interface drawing event processed by the graph drawing framework, calling the graph drawing information in the basic graph drawing framework stored by the browser to process the browser interface drawing event.
The graph drawing information in the basic graph drawing frame comprises a drawing function of the basic graph and corresponding drawing data.
The graphic drawing framework can send the browser interface design event to an abstract layer of the browser, and the abstract layer calls the stored graphic drawing framework to process the browser interface drawing event.
Therefore, based on the Ozone layer, the graph drawing framework can separate the browser event processed by the browser kernel from the browser interface graph drawing event processed by the graph drawing framework, and realize the interaction between the browser kernel and the browser interface design.
Step 330, displaying the event processing result on the browser interface.
The display of the processing results of the graphical rendering architecture browser events may be as shown in fig. 4, a "save" graphic, a "back" graphic, a "forward" graphic, a "favorite" graphic, etc. of a toolbar on the browser interface.
For the browser kernel to process the browser event, the display of the processing result of the browser interface element typesetting layout event can be as shown in the contents of typesetting layout 1-typesetting layout 3 in the browser interface shown in fig. 5.
Corresponding to the foregoing method, an embodiment of the present invention further provides a browser interface processing apparatus, as shown in fig. 6, where the browser interface processing apparatus includes: an acquisition unit 610, a verification unit 620, a processing unit 630, and a display unit 640;
an obtaining unit 610, configured to obtain a browser event monitored by an operating system;
a verifying unit 620, configured to perform event type verification on a browser event according to a configured browser event set; the browser event set comprises event types corresponding to all browser events;
a processing unit 630, configured to perform graph drawing processing on the browser event if the browser event is a first type event; the first type event is a browser interface drawing event processed by the graph drawing framework;
if the browser event is a second type event, sending the browser event to a browser kernel so that the browser kernel processes the browser event; the first type of event is different from the second type of event;
and a display unit 640 for displaying the event processing result on the browser interface.
In an optional implementation, the processing unit 630 is specifically configured to perform, if the browser interface drawing event is a graph drawing event handled by the graph drawing framework itself, a preset graph drawing frame to perform graph drawing processing on the browser interface drawing event.
In an optional implementation, the processing unit 630 is further specifically configured to, if the browser interface drawing event is not a graph drawing event processed by the graph drawing framework itself, invoke graph drawing information in a basic graph drawing frame stored in the browser, and perform graph drawing processing on the browser interface drawing event.
In an alternative implementation, the processing unit 630 is further specifically configured to send the browser event to an abstraction layer of the browser;
and sending the browser event to the browser kernel through the abstraction layer.
In an alternative implementation, the apparatus further comprises a establishing unit 650;
a establishing unit 650, configured to establish a coupling connection with the abstraction layer; the coupling connection is for coupling with the abstraction layer event handling function.
In an alternative implementation, the second type of event is a browser interface element typesetting layout event, a mouse event, or a keyboard event.
The functions of the functional units of the browser interface processing apparatus provided in the above embodiment of the present invention may be implemented by the above method steps, and therefore, detailed working processes and beneficial effects of the units in the browser interface processing apparatus provided in the embodiment of the present invention are not described herein again.
An embodiment of the present invention further provides an electronic device, as shown in fig. 7, including a processor 710, a communication interface 720, a memory 730, and a communication bus 740, where the processor 710, the communication interface 720, and the memory 730 complete mutual communication through the communication bus 740.
A memory 730 for storing a computer program;
the processor 710, when executing the program stored in the memory 730, implements the following steps:
acquiring a browser event monitored by an operating system;
according to the configured browser event set, performing event type verification on the browser event; the browser event set comprises event types corresponding to all browser events;
if the browser event is a first type event, carrying out graphic drawing processing on the browser event; the first type event is a browser interface drawing event processed by the graph drawing framework;
if the browser event is a second type event, sending the browser event to a browser kernel so that the browser kernel processes the browser event; the first type of event is different from the second type of event;
and displaying the event processing result on the browser interface.
In an optional implementation, if the browser event is a first type event, performing a graph drawing process on the browser event, including:
and if the browser interface drawing event is a graph drawing event processed by the graph drawing framework, performing graph drawing processing on the browser interface drawing event by adopting a preset graph drawing frame.
In an optional implementation, if the browser event is a first type event, performing a graph drawing process on the browser event, including:
if the browser interface drawing event is not the graph drawing event processed by the graph drawing framework, calling the graph drawing information in the basic graph drawing framework stored by the browser, and performing graph drawing processing on the browser interface drawing event.
In an alternative implementation, sending the browser event to a browser kernel includes:
sending the browser event to an abstraction layer of the browser;
and sending the browser event to the browser kernel through the abstraction layer.
In an optional implementation, before sending the browser event to an abstraction layer of the browser, the method further includes:
establishing a coupling connection with the abstract layer; the coupling connection is for coupling with the abstraction layer event handling function.
In an alternative implementation, the second type of event is a browser interface element typesetting layout event, a mouse event, or a keyboard event.
The aforementioned communication bus 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 electronic equipment and other equipment.
The Memory may include a Random Access Memory (RAM) or a Non-Volatile Memory (NVM), 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, including a Central Processing Unit (CPU), a Network Processor (NP), and the like; but also Digital Signal Processors (DSPs), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) or other Programmable logic devices, discrete Gate or transistor logic devices, discrete hardware components.
Since the implementation and the beneficial effects of the problem solving of each device of the electronic device in the above embodiment can be realized by referring to each step in the embodiment shown in fig. 3, detailed working processes and beneficial effects of the electronic device provided by the embodiment of the present invention are not described herein again.
In another embodiment of the present invention, a computer-readable storage medium is further provided, which stores instructions that, when executed on a computer, cause the computer to execute the browser interface processing method described in any one of the above embodiments.
In yet another embodiment of the present invention, there is also provided a computer program product containing instructions which, when run on a computer, cause the computer to perform the browser interface processing method described in any of the above embodiments.
As will be appreciated by one of skill in the art, the embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, embodiments of the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, embodiments of the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
Embodiments of the present application are described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
While preferred embodiments of the present application have been described, additional variations and modifications in those embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. Therefore, it is intended that the appended claims be interpreted as including the preferred embodiment and all changes and modifications that fall within the true scope of the embodiments of the present application.
It is apparent that those skilled in the art can make various changes and modifications to the embodiments of the present application without departing from the spirit and scope of the embodiments of the present application. Thus, if such modifications and variations of the embodiments of the present application fall within the scope of the claims of the embodiments of the present application and their equivalents, the embodiments of the present application are also intended to include such modifications and variations.

Claims (10)

1. A browser interface processing method, which is characterized in that the method is applied in a graphic drawing architecture, and the method comprises the following steps:
acquiring a browser event monitored by an operating system;
according to the configured browser event set, performing event type verification on the browser event; the browser event set comprises event types corresponding to all browser events;
if the browser event is a first type event, carrying out graphic drawing processing on the browser event; the first type event is a browser interface drawing event processed by the graph drawing framework;
if the browser event is a second type event, sending the browser event to a browser kernel so that the browser kernel processes the browser event; the first type of event is different from the second type of event;
and displaying the event processing result on the browser interface.
2. The method of claim 1, wherein if the browser event is a first type of event, performing a graph drawing process on the browser event comprises:
and if the browser interface drawing event is a graph drawing event processed by the graph drawing framework, performing graph drawing processing on the browser interface drawing event by adopting a preset graph drawing frame.
3. The method according to claim 1 or 2, wherein if the browser event is a first type event, performing a graphic rendering process on the browser event includes:
if the browser interface drawing event is not the graph drawing event processed by the graph drawing framework, calling the graph drawing information in the basic graph drawing framework stored by the browser, and performing graph drawing processing on the browser interface drawing event.
4. The method of claim 1, wherein sending the browser event to a browser kernel comprises:
sending the browser event to an abstraction layer of the browser;
and sending the browser event to the browser kernel through the abstraction layer.
5. The method of claim 4, wherein prior to sending the browser event to an abstraction layer of the browser, the method further comprises:
establishing a coupling connection with the abstract layer; the coupling connection is for coupling with the abstraction layer event handling function.
6. The method of claim 1, wherein the second type of event is a browser interface element typographical layout event, a mouse event, or a keyboard event.
7. A browser interface processing apparatus, characterized in that the apparatus comprises: the device comprises an acquisition unit, a verification unit, a processing unit and a display unit;
the acquisition unit is used for acquiring browser events monitored by an operating system;
the verification unit is used for verifying the event type of the browser event according to the configured browser event set; the browser event set comprises event types corresponding to all browser events;
the processing unit is used for carrying out graphic drawing processing on the browser event if the browser event is a first type event; the first type event is a browser interface drawing event processed by the graph drawing framework;
if the browser event is a second type event, sending the browser event to a browser kernel so that the browser kernel processes the browser event; the first type of event is different from the second type of event;
and the display unit is used for displaying the event processing result on the browser interface.
8. The apparatus according to claim 7, wherein the processing unit is specifically configured to perform, if the browser interface drawing event is a graphics drawing event handled by the graphics drawing framework itself, graphics drawing processing on the browser interface drawing event by using a preset graphics drawing frame.
9. An electronic device, characterized in that the electronic device comprises a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory are communicated with each other through the communication bus;
a memory for storing a computer program;
a processor for implementing the method steps of any of claims 1-6 when executing a program stored on a memory.
10. A computer-readable storage medium, characterized in that a computer program is stored in the computer-readable storage medium, which computer program, when being executed by a processor, carries out the method steps of any one of claims 1 to 6.
CN202011062447.3A 2020-09-30 2020-09-30 Browser interface processing method and device Active CN112114800B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202011062447.3A CN112114800B (en) 2020-09-30 2020-09-30 Browser interface processing method and device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202011062447.3A CN112114800B (en) 2020-09-30 2020-09-30 Browser interface processing method and device

Publications (2)

Publication Number Publication Date
CN112114800A true CN112114800A (en) 2020-12-22
CN112114800B CN112114800B (en) 2021-06-29

Family

ID=73797363

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202011062447.3A Active CN112114800B (en) 2020-09-30 2020-09-30 Browser interface processing method and device

Country Status (1)

Country Link
CN (1) CN112114800B (en)

Citations (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103279518A (en) * 2013-05-27 2013-09-04 中山爱科数字科技股份有限公司 Browser
CN103458035A (en) * 2013-09-05 2013-12-18 深圳市共进电子股份有限公司 Client configuration interface implementation method based on WEB server
CN104808913A (en) * 2014-01-23 2015-07-29 腾讯科技(深圳)有限公司 Event responding method and device
CN105095220A (en) * 2014-04-24 2015-11-25 华为技术有限公司 Browser implementation method, terminal and virtualized agent device
CN105488041A (en) * 2014-09-15 2016-04-13 北京畅游天下网络技术有限公司 Browser interface multi-language display method
US20160335736A1 (en) * 2012-07-31 2016-11-17 Intel Corporation Hybrid rendering systems and methods
CN108595177A (en) * 2018-04-28 2018-09-28 广东电网有限责任公司 interface development method and device
US20190340512A1 (en) * 2018-05-07 2019-11-07 Sauce Labs Inc. Analytics for an automated application testing platform
CN111339458A (en) * 2018-12-18 2020-06-26 阿里巴巴集团控股有限公司 Page presenting method and device

Patent Citations (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20160335736A1 (en) * 2012-07-31 2016-11-17 Intel Corporation Hybrid rendering systems and methods
CN103279518A (en) * 2013-05-27 2013-09-04 中山爱科数字科技股份有限公司 Browser
CN103458035A (en) * 2013-09-05 2013-12-18 深圳市共进电子股份有限公司 Client configuration interface implementation method based on WEB server
CN104808913A (en) * 2014-01-23 2015-07-29 腾讯科技(深圳)有限公司 Event responding method and device
CN105095220A (en) * 2014-04-24 2015-11-25 华为技术有限公司 Browser implementation method, terminal and virtualized agent device
CN105488041A (en) * 2014-09-15 2016-04-13 北京畅游天下网络技术有限公司 Browser interface multi-language display method
CN108595177A (en) * 2018-04-28 2018-09-28 广东电网有限责任公司 interface development method and device
US20190340512A1 (en) * 2018-05-07 2019-11-07 Sauce Labs Inc. Analytics for an automated application testing platform
CN111339458A (en) * 2018-12-18 2020-06-26 阿里巴巴集团控股有限公司 Page presenting method and device

Also Published As

Publication number Publication date
CN112114800B (en) 2021-06-29

Similar Documents

Publication Publication Date Title
AU2016286308B2 (en) Robotic process automation
EP2605129A2 (en) Method of rendering a user interface
CN104199734A (en) Android smart terminal based application multi-run management method and system
US11681507B2 (en) Composable context menus
US9665463B2 (en) In-process wrapped execution engine(s) for tooling a dynamic program across a process boundary
CN107368996B (en) Method/system for problem handling/supervision of field project, storage medium, terminal
CN103593171A (en) Multi-zone screenshot method and device
CN111782651A (en) Visual editing method, device and equipment for data association relation and storage medium
CN112114800B (en) Browser interface processing method and device
US20170115866A1 (en) Method, device and terminal apparatus for recognizing multi-finger sliding gesture
WO2018205392A1 (en) Control response area display control method, electronic apparatus, and storage medium
US8719704B2 (en) Seamless integration of additional functionality into enterprise software without customization or apparent alteration of same
WO2023173726A1 (en) Interaction method and apparatus, and storage medium
US20180143747A1 (en) User interface device and method for displaying screen of user interface device
CN112764729B (en) Application software development method, device, computer equipment and readable storage medium
CN114416264A (en) Message display method and device
CN113902841A (en) Image drawing method and device, electronic equipment and readable storage medium
CN111949510B (en) Test processing method, device, electronic equipment and readable storage medium
CN111198899B (en) Development system and method for entity rendering in application program
CN107450913B (en) ExtJS-based window component access control method
CN111008012A (en) Prototype design method, prototype design device, electronic product and storage medium
CN106293304B (en) Interface operation method and device
CN108459847B (en) Object calling method and device and terminal equipment
CN112486368B (en) Application program management method and device
US11372743B2 (en) Computer devices and computer implemented methods

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