CN1369828A - Method for processing user-defined event and network page - Google Patents
Method for processing user-defined event and network page Download PDFInfo
- Publication number
- CN1369828A CN1369828A CN 01104601 CN01104601A CN1369828A CN 1369828 A CN1369828 A CN 1369828A CN 01104601 CN01104601 CN 01104601 CN 01104601 A CN01104601 A CN 01104601A CN 1369828 A CN1369828 A CN 1369828A
- Authority
- CN
- China
- Prior art keywords
- incident
- event
- chained list
- content
- empty
- 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
Links
Images
Abstract
A method for treating user-defined event of network page incldues following steps. An event generatino module is used to obtain message about occurrence of user-defined event from a network page. The message of user-defined event obtained is sent to the management module of registering even to carry out registration treatment that includes registration treatment; registering or unregistering user-defined event. The registered user-defined event it inserted into the network page through an event transmission module.
Description
The present invention relates to a kind of disposal route of User Defined incident, the control and the sending method of the User Defined event queue (queue) of especially relevant webpage.
In webpage design, at present the Document Object Model (DOMs) of standard generally be used in describe all objects in the webpage between relation.This document object pattern is one cross-platform and stride the interface of language, can allow program and script (programs and scripts) the dynamically content and the kenel (content and styles) of access and updating file.The specifications of this pattern comprise two partly: core and HTML.Core DOM is provided for the file interface of any structure, and HTML DOM provides additional interfaces, makes HTML have the preferable picture of watching.Though this model can provide the function of coming accessing web page by as scripts such as JavaCript, partly obtaining and disposal route of standard Event only is provided, for example, make a reference variable, when being written into, webpage has the function of compression grammer.If run into netpage user's customized event, then lack corresponding flexible support and management, and some is needed the independently developed interactive application type webpage of user, often in operating process, occur making customer satisfaction system phenomenon.For example, the user comprises ListControl＜Select one of exploitation〉during the interactive webpage of object, the developer can increase (being AddItem) to ListBox as required, this moment is at this operation, the DOM model of standard only provides the support of separate threads (independent thread), that is to say, when the user adds one in List, could accept the processing of the project that increases newly when the task of must wait until this separate threads is finished, can occur a. like this needs full page to upgrade again; B. the local appearance of the page is blank for a long time, the similar false effect of shutting down.
In view of the above, the disposal route that the purpose of this invention is to provide a kind of User Defined event queue (queue) of relevant webpage.This method is used a timer (Timer) in the DOM mode standard, utilize this timer timing controlled look-at-me to simulate a new thread, when the user does some operation in webpage, when for example going up one that increases in the example among the List, can realize the operation of multithreading, the part that promptly increases newly can appear on the webpage synchronously, and does not pause in the operation.
Another object of the present invention provides a kind of control and sending method of User Defined event queue, and it adopts the event queue form, and expansion is to the support of variety of event, and the permission user is to the various different event of different element definitions.
The invention provides a kind of control and sending method of User Defined event queue.This method comprises the following steps: to utilize an incident generation module to obtain the information that a User Defined incident occurs in a webpage; This User Defined event information of obtaining is delivered to an event registration administration module carry out location registration process, comprising interpolation (register) or deletion (unregister) location registration process this User Defined incident; This User Defined incident through location registration process is inserted in this webpage via an incident sending module.
For allow above-mentioned and other purpose of the present invention, feature, with advantage can be clearer, a preferred embodiment cited below particularly, and conjunction with figs. elaborate:
Fig. 1 shows functional module group figure of the present invention and operating process thereof;
Fig. 2 shows User Defined event structure synoptic diagram of the present invention;
Fig. 3 shows the flow process of event registration management of the present invention;
Fig. 4 shows the flow process of deletion event of the present invention;
Fig. 5 shows the flow process that incident of the present invention generates; And
Fig. 6 shows the slotting flow process of sending out of incident of the present invention.
With reference to figure 1, it is represented according to the present invention the User Defined event handling flow process of webpage.In Fig. 1, the user is a self-defined incident on a page 101, at first this information is transmitted out by this page 101, obtain this information (Getmessage) (step S1) by an incident generation module 102 provided by the present invention, and resulting information is delivered an event registration administration module 103 carry out location registration process (step S3), comprising interpolation (register) or deletion (unregister) location registration process to this incident, Hou is by an incident sending module 104, obtain this new events Get message, and should insert in this page 101 (step S5) by user-defined new events through registration.
With reference to figure 2, it shows User Defined event structure synoptic diagram of the present invention.In Fig. 2, relevant self-defined description and list structure comprise: the A. event description, and wherein, this self-defined structure comprises: an incident receives pointer to object, an event name, an event handling function; B. incident bag (event packet), it comprises an event name, source (Source) object name, an event response method; C. register chained list; And D. event queue.Above-mentioned relevant User Defined event structure will cooperate each flow process of the present invention in describing down.
The incident management flow process
This flow process comprises the operation of deletion two aspects of User Defined register of event and User Defined incident, will be described in down respectively.
1. the User Defined event registration is managed (Register) flow process
With reference to figure 3, it shows the flow process of event registration management of the present invention.As shown in Figure 3, at first, event description form according to Fig. 2 is filled in event description table (step 301), read first (step 302) of the event registration chained list of having set up shown in Fig. 2, judge whether this reads a content is empty (step 303), if, then the registered events with user's redetermination inserts in this chained list (step 304), last layer is returned in operation, if this reads a content not for empty in this chained list, then read the content (step 305) of this item in this chained list, judge in the current customized event that will register and this chained list this incident title that reads whether identical (step 306), if it is identical, show that then the current customized event of registering has existed in chained list, so choose the pointer (step 307) of next event item in this chained list, so that read the next item down content, if pairing incident title is inequality in the current customized event that will register and the chained list, pairing reception object chained list is (for example in Fig. 2 then to read it, reception object 1 shown in Fig. 2 corresponding to event name 1, receive object 2, to receiving object N) (step 308), judge whether this chained list content is empty (step 309), if, then the customized event that will need register at present inserts in the chained list (step 310), program is returned last layer, if be not empty, then read the content (step 311) of this item in this reception object chained list, judge that whether the content read is same target (step 312) with the customized event that will register, if then program is returned last layer; If not, then read the next item down pointer (step 313) in this accepting object chained list.
2. the User Defined incident is deleted (Unregister) flow process
With reference to figure 4, it shows the flow process of deletion event of the present invention.As shown in Figure 4, at first, read first (step 401) in the event registration chained list, judge whether this reads a content is empty (step 402), if, then program is returned last layer, if not, then read this content (step 403), whether the title of judging this incident title and User Defined incident in this chained list identical (step 404), if it is different, then read the next item down content (step 405) of this chained list,, then read content (step 406) corresponding in the pairing object chained list of this chained list if identical, judge whether this reads a content is empty (step 407), if then program is returned last layer, if be not empty, then get the content (step 408) in this object chained list, determine resulting object whether with the user to delete to as if same target (step 409), if then it is removed (step 410), if not, then get the next item down pointer (step 411) in this chained list.
The incident product process
With reference to figure 5, it shows the flow process that incident of the present invention generates.As shown in Figure 5, at first, look for the incident title (step 501) that will send, promptly in this event registration chained list, compare the incident title in regular turn, whether find the incident title (step 502) that will send with decision, if do not find, then withdraw from this operation (step 503),, then from its object chained list, seek corresponding contents of object (step 504) if find, whether decision finds (step 505), if not, then withdraw from this operation (step 503), if find, then content relevant in this object chained list is generated incident bag (step 506) as shown in Figure 2, and this incident bag is added in this event queue (step 507).
The incident transmission flow
With reference to figure 6, it shows the flow process that incident of the present invention sends.As shown in Figure 6, at first, set the time interval (such as being 0.3 second) (step 601) of a timer (Timer), wait for the transmission (step 602) of an incident, the event items (step 603) that from this event queue, finds this desire to send, judge whether this content is empty (step 604), if be empty, then return last layer program (step 602), to wait for next transmission incident,, then from the incident bag of this desire transmission incident, take out the response function (this response function is specified when registering customized event in advance by the developer) (step 605) of this incident bag if be not empty, determine whether this incident bag is empty (step 606), if then return last layer program (step 602), in order to the transmission incident of waiting for that Hou is continuous, if be not empty, then use this response function to respond this customized event (step 607).
Though the present invention discloses as above with a preferred embodiment, yet it is not in order to limiting the present invention, and any one of ordinary skilled in the art can carry out various modifications and variations under situation without departing from the spirit or scope of the invention.
Claims (7)
1. the disposal route of the User Defined incident of a webpage, this method comprises the following steps:
Utilize an incident generation module in a webpage, to obtain the information that a User Defined incident occurs;
This User Defined event information of obtaining is delivered to an event registration administration module carry out location registration process, comprising interpolation (register) or deletion (unregister) location registration process this User Defined incident;
This User Defined incident through location registration process is inserted in this webpage via an incident sending module.
2. disposal route as claimed in claim 1, wherein, this User Defined incident comprises that the customized event structure, of a relevant event description is used to send the required incident bag of this incident, a registration chained list, reaches an event queue, wherein, this customized event structure comprises that this incident receives pointer to object, this incident title, reaches this event handling function; This incident comprises this incident title, this source object oriented, reaches this event response method.
3. disposal route as claimed in claim 1, wherein, the interpolation location registration process step of this User Defined incident comprises the following steps:
Fill in an event description table that is used to register according to this customized event structure;
Read a default event registration chained list first;
Judge whether this reads a content is empty;
If, then this user is utilized the defined registered events of wanting of this event description table to insert in this chained list, finish and add location registration process and make operation return the last layer program,, then read the content of this item in this chained list if this reads a content not for empty in this chained list;
Relatively whether this incident title that reads is identical in this customized event that will register and this chained list;
If it is identical, show that then this customized event that will register exists in chained list, so choose the pointer of next event item in this chained list, so that read the next item down content, if pairing incident title is inequality in customized event that this will be registered and the chained list, then read the pairing reception object of this customized event that will register chained list;
Judge whether this chained list content is empty;
If, then this customized event that will register is inserted in this reception object chained list, finish and add location registration process and make program return last layer, if be not empty, then read the content of this item in this reception object chained list;
Judge that whether the content read is same target with the customized event that will register; And
If then program is returned last layer, if not, then read the next item down pointer in this accepting object chained list.
4. disposal route as claimed in claim 1, wherein, the deletion location registration process step of this User Defined incident comprises the following steps:
Read first in the event registration chained list;
Judge whether this reads a content is empty;
If then program is returned last layer, if not, then read this content;
Judge whether this incident title is identical with the title of User Defined incident in this chained list;
If different, then read the next item down content of this chained list, if identical, then read in the pairing object chained list of this chained list corresponding content;
Judge whether this reads a content is empty;
If then program is returned last layer,, then get the content in this object chained list if be not empty;
Determine resulting object whether with the user to delete to as if same target; And
If, then it is removed, if not, the next item down pointer in this chained list then got.
5. disposal route as claimed in claim 1, wherein, the described step of utilizing an incident generation module to obtain a User Defined incident in a webpage also comprises the following steps:
Look for an incident title that will send;
In this event registration chained list, compare the incident title in regular turn, whether find the incident title that will send with decision;
If do not find, then withdraw from this operation, if find, then from its object chained list, seek corresponding contents of object;
Whether decision is found;
If not, then withdraw from this operation,, then content relevant in this object chained list is generated an incident bag if find;
This incident bag is added in this event queue, finish obtaining of this customized event.
6. disposal route as claimed in claim 1, wherein, the processing that this incident sends comprises the following steps:
Set the time interval of a timer (Timer);
Wait for the transmission of an incident;
The event items that from this event queue, finds this desire to send;
Judge whether this content is empty;
If be empty, then return last layer program (step 602), to wait for next transmission incident,, then from the incident bag of this desire transmission incident, take out the response function of this incident bag if be not empty;
Determine whether this incident bag is empty; And
If, then return the last layer program, with the transmission incident of waiting for that Hou is continuous,, then use this response function to respond this customized event if be not empty, thus this customized event is inserted in this webpage.
7. disposal route as claimed in claim 6, wherein, this response function is predetermined in advance when this customized event of registration.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN 01104601 CN1205570C (en) | 2001-02-15 | 2001-02-15 | Method for processing user-defined event and network page |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN 01104601 CN1205570C (en) | 2001-02-15 | 2001-02-15 | Method for processing user-defined event and network page |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN1369828A true CN1369828A (en) | 2002-09-18 |
| CN1205570C CN1205570C (en) | 2005-06-08 |
Family
ID=4653971
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN 01104601 Expired - Fee Related CN1205570C (en) | 2001-02-15 | 2001-02-15 | Method for processing user-defined event and network page |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN1205570C (en) |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN100424630C (en) * | 2004-03-26 | 2008-10-08 | 宏碁股份有限公司 | Operation method of web page speech interface |
| CN100465886C (en) * | 2006-05-26 | 2009-03-04 | 华为技术有限公司 | Extendable file model and method for managing file model |
| WO2011076011A1 (en) * | 2009-12-22 | 2011-06-30 | 中兴通讯股份有限公司 | Method, system for defining message in machine-to-machine platform, and machine-to-machine platform |
| CN105468344A (en) * | 2014-08-26 | 2016-04-06 | 腾讯科技（深圳）有限公司 | Floating layer setting method and device, and electronic equipment |
-
2001
- 2001-02-15 CN CN 01104601 patent/CN1205570C/en not_active Expired - Fee Related
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN100424630C (en) * | 2004-03-26 | 2008-10-08 | 宏碁股份有限公司 | Operation method of web page speech interface |
| CN100465886C (en) * | 2006-05-26 | 2009-03-04 | 华为技术有限公司 | Extendable file model and method for managing file model |
| WO2011076011A1 (en) * | 2009-12-22 | 2011-06-30 | 中兴通讯股份有限公司 | Method, system for defining message in machine-to-machine platform, and machine-to-machine platform |
| CN105468344A (en) * | 2014-08-26 | 2016-04-06 | 腾讯科技（深圳）有限公司 | Floating layer setting method and device, and electronic equipment |
| CN105468344B (en) * | 2014-08-26 | 2019-08-06 | 腾讯科技（深圳）有限公司 | A kind of float layer setting method, device and electronic equipment |
Also Published As
| Publication number | Publication date |
|---|---|
| CN1205570C (en) | 2005-06-08 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101364236B (en) | Data processing apparatus and processing method of WEB page | |
| US6973619B1 (en) | Method for generating display control information and computer | |
| AU2008206688B2 (en) | Method and system for creating IT-oriented server-based web applications | |
| US6430591B1 (en) | System and method for rendering electronic images | |
| US6961737B2 (en) | Serving signals | |
| US6950866B1 (en) | XML-based integrated services parsing | |
| US20020120679A1 (en) | Methods and apparatus for communicating changes between a user interface and an executing application using property paths | |
| EP1403778A1 (en) | Adaptive multimedia integration language (AMIL) for adaptive multimedia applications and presentations | |
| US20040230900A1 (en) | Declarative mechanism for defining a hierarchy of objects | |
| WO2003036548A1 (en) | System and method for portal page layout | |
| CN111639278B (en) | Webpage loading method and device | |
| JP2003526960A (en) | Apparatus and method for executing an interactive TV application on a set top unit | |
| US20030167320A1 (en) | Registration service for registering plug-in applications with a management console | |
| CN106101751A (en) | Player based on Android operation system and embedded broadcasting box | |
| US8421806B2 (en) | Method of optimizing rendering of a multimedia scene, and the corresponding program, signal, data carrier, terminal and reception method | |
| AU2006291331B2 (en) | Script markup | |
| CN106649299B (en) | Method and device for lazy loading of webpage block | |
| CN1205570C (en) | Method for processing user-defined event and network page | |
| CN111737618A (en) | Vector diagram display method and device for Web end and computer equipment | |
| US6286025B1 (en) | Method and system of process identification by user defined process variables | |
| US6697859B1 (en) | Apparatus, method, program, and information processing system for prioritized data transfer to a network terminal | |
| CN103257855A (en) | MVC (model view controller) based processing system, MVC based processing method and application in facial beautifying software | |
| CN112597423A (en) | Webpage content display method, terminal and server | |
| WO2002075596A2 (en) | Method and system for literal data access | |
| US8776118B1 (en) | Using web based information to select television programs |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| C17 | Cessation of patent right | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20050608 Termination date: 20110215 |