CN101887376A - Widget engine and method for uploading scripts or plugins by using same - Google Patents
Widget engine and method for uploading scripts or plugins by using same Download PDFInfo
- Publication number
- CN101887376A CN101887376A CN2010102233385A CN201010223338A CN101887376A CN 101887376 A CN101887376 A CN 101887376A CN 2010102233385 A CN2010102233385 A CN 2010102233385A CN 201010223338 A CN201010223338 A CN 201010223338A CN 101887376 A CN101887376 A CN 101887376A
- Authority
- CN
- China
- Prior art keywords
- widget
- script plug
- plug
- script
- attribute
- 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
- 238000013515 script Methods 0.000 title claims abstract description 163
- 238000000034 method Methods 0.000 title claims abstract description 32
- 238000011068 loading method Methods 0.000 claims description 45
- 230000006870 function Effects 0.000 description 33
- 238000010586 diagram Methods 0.000 description 2
- 230000000694 effects Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
Images
Landscapes
- Stored Programmes (AREA)
Abstract
The invention discloses a Widget engine and a method for uploading scripts or plugins by using the same. The method comprises the following steps of: acquiring the preset attributes of scripts or plugins to be uploaded in a Widget packet by using the Widget engine; and uploading the scripts or the plugins to a browser engine according to the preset attributes of the scripts or the plugins. In the Widget engine and the method for uploading scripts or plugins by using the same, plugin interfaces can be directly invoked through the Widget engine so that the scripts or the plugins can be uploaded in advance, thereby improving user experience without making declaration in the scripts.
Description
Technical Field
The invention relates to a technology for loading a script plug-in by a browser, in particular to a method for loading the script plug-in by a Widget engine and the Widget engine.
Background
Widget is a Web applet based on the internet, and can generally realize a certain function; the presentation may be in the form of a video, map, news or mini-game, etc. The mobile Widget runs on the mobile terminal, has the characteristics of small size, portability, openness, interactivity and the like, and is very suitable for mobile internet application.
The loading method of the script plug-in of the hypertext language is plug-and-play, and the plug-in needing to be loaded can be determined by executing keywords (< object > or < embed >) in the hypertext file or the script file through a browser engine. Referring to fig. 1, the process of loading the plug-in by the browser includes:
step S10, when opening a URL, the browser engine executes a Web Resource corresponding to the URL (Uniform Resource Locator); firstly, starting and initializing a browser engine by a browser, and then calling the browser engine to open a URL (uniform resource locator);
step S11, checking whether the tag is an object tag or an embedded tag; the browser engine checks whether the keyword in the hypertext file or the script file is < object > or < embed >; if yes, go to step S12, otherwise end;
step S12, loading plug-ins required by < object > or < embed > tags; the browser engine loads the plug-ins required by the < object > or < embed > tags.
The browser plug-in loading mode is carried out during script running, and a user can be in a waiting state in the loading process, so that the user experience is influenced.
Disclosure of Invention
The invention mainly aims to provide a method for loading a script plug-in by a Widget engine and the Widget engine, which can improve user experience.
The invention provides a method for loading script plug-ins by a Widget engine, which comprises the following steps:
the method comprises the steps that a Widget engine obtains attributes which are pre-configured by script plug-ins needing to be loaded in a Widget package;
and loading the script plug-in into a browser engine according to the attribute preset by the script plug-in.
Preferably, the step of the Widget engine obtaining the attribute pre-configured by the script plug-in stored in the Widget package further includes the following steps:
and searching the needed script plug-in by the Widget engine, and storing the needed script plug-in the Widget package.
Preferably, the pre-configuring specifically includes:
and adding keywords in the configuration file of the Widget package, and identifying script plug-ins needing to be loaded through the attributes of the configuration keywords.
Preferably, the pre-configuring further specifically includes:
adding extension keywords in a configuration file of the Widget package, and setting the name and the path of the script plug-in the attribute; or,
and adding standard keywords in the configuration file of the Widget package, and setting the name of the script plug-in the attribute.
Preferably, the step of loading the script plug-in into the browser engine according to the attribute preconfigured by the script plug-in specifically includes:
the method comprises the steps that a Widget engine reads keywords of a configuration file of a Widget package to obtain attributes of script plug-ins needing to be loaded;
acquiring an interface function of the script plug-in according to the attribute, and calling the interface function to acquire an entry function operated by the script plug-in;
and calling the entry function, and loading the script plug-in into a browser engine.
The invention also provides a Widget engine, comprising:
the acquisition module is used for acquiring the attribute which is configured in advance by the script plug-in needing to be loaded in the Widget package;
and the loading module is used for loading the script plug-in into the browser engine according to the attribute preset by the script plug-in.
Preferably, the apparatus further comprises:
and the storage module is used for searching the needed script plug-in and storing the needed script plug-in the Widget package.
Preferably, the pre-configuring specifically includes:
and adding keywords in the configuration file of the Widget package, and identifying script plug-ins needing to be loaded through the attributes of the configuration keywords.
Preferably, the pre-configuring further specifically includes:
adding extension keywords in a configuration file of the Widget package, and setting the name and the path of the script plug-in the attribute; or,
and adding standard keywords in the configuration file of the Widget package, and setting the name of the script plug-in the attribute.
Preferably, the loading module is specifically configured to:
reading keywords of a configuration file of the Widget package to obtain the attribute of the script plug-in needing to be loaded;
acquiring an interface function of the script plug-in according to the attribute, and calling the interface function to acquire an entry function operated by the script plug-in;
and calling the entry function, and loading the script plug-in into a browser engine.
The method for loading the script plug-in by the Widget engine and the Widget engine can directly call the plug-in interface through the Widget engine, load the script plug-in advance, and do not need to declare in the script, thereby improving the user experience.
Drawings
FIG. 1 is a flowchart illustrating steps of loading a plug-in by a browser in the prior art;
FIG. 2 is a flowchart illustrating steps of an embodiment of a method for loading a script plug-in by a Widget engine according to the present invention;
FIG. 3 is a flowchart illustrating steps of another embodiment of a method for loading a script plug-in by a Widget engine according to the present invention;
FIG. 4 is a flowchart illustrating steps of loading a script plug-in according to another embodiment of the method for loading a script plug-in by a Widget engine of the present invention;
fig. 5 is a schematic structural diagram of an embodiment of a Widget engine of the present invention;
fig. 6 is a schematic structural diagram of another embodiment of the Widget engine of the present invention.
The implementation, functional features and advantages of the objects of the present invention will be further explained with reference to the accompanying drawings.
Detailed Description
The invention can load the script plug-in advance, does not need to declare the loaded plug-in the script, directly uses the plug-in interface and can improve the user experience. The script plug-in may be a plug-in that does not require a window operation and conforms to the NETSCAPE plug-in specification.
The browser engine referred to below may be used to process Web hypertext on a mobile terminal; the Widget engine can be positioned above the browser engine and is used for operating the browser engine; NETSCAPE plug-in standard is Web hypertext plug-in specification proposed by network view company; < object >, which is a hypertext language keyword; < embed >, which is a hypertext language keyword; the Widget package can be a folder or a compressed package of a folder.
Referring to fig. 2, an embodiment of a method for loading a script plug-in by a Widget engine according to the present invention is provided, where the method includes:
step S20, the Widget engine acquires the attribute pre-configured by the script plug-in needing to be loaded in the Widget package;
and step S21, loading the script plug-in into the browser engine according to the attribute preset by the script plug-in.
As shown in step S20, the properties of the script plug-in can be pre-configured to determine the script plug-in that needs to be loaded. In this embodiment, the method may be applied to a mobile terminal, and the mobile terminal may provide services provided by the mobile terminal itself to the mobile Widget for access through a script plug-in mode. The mobile terminal classifies script plug-ins according to the types of services, such as multimedia playing plug-ins, hardware device plug-ins, network plug-ins, telephone plug-ins, file operation plug-ins, database service plug-ins, and the like. The mobile Widget can analyze the Widget package according to the requirement, extract the attribute of the script plug-in the configuration file and determine the plug-in needing to be loaded. In the Widget package, a corresponding script plug-in may be stored in advance. The attributes include the name, type, path, version number of the script plug-in, and/or the URL of the update plug-in, etc.
The mobile terminal may be a handheld intelligent electronic device such as a mobile phone and a Personal Digital Assistant (PDA).
As shown in step S21, the Widget engine may call a plug-in interface of the script plug-in according to the pre-configured attributes (such as name, path, etc.), and load the script plug-in to be loaded into the browser engine.
According to the method for loading the script plug-in by the Widget engine, the plug-in interface can be directly called by the Widget engine, the script plug-in is loaded in advance, and the statement in the script is not needed, so that the user experience is improved. Meanwhile, due to the fact that resources of the mobile terminal are limited, the method has a more remarkable effect when used in the mobile terminal.
Referring to fig. 3, another embodiment of the method for loading a script plug-in by a Widget engine according to the present invention is provided, where the method further includes, before step S20:
and S200, searching the needed script plug-in by the Widget engine, and storing the needed script plug-in the Widget package.
In step S200, in this embodiment, the Widget engine may search for a needed script plug-in from script plug-ins provided by the mobile terminal, and store the needed script plug-in into the Widget package as a standby. The searching can be to search for a needed (including version updating) script plug-in the mobile terminal, and save the attribute (including name, path, type and the like) of the script plug-in to the configuration file of the Widget package through pre-configuration; the searching may also be performed outside the mobile terminal, for example, by searching for a required script plug-in through a network, downloading and storing the script plug-in into the Widget package according to a network path (for example, a URL), and storing the attribute of the script plug-in into a configuration file of the Widget package through pre-configuration.
In this embodiment, the pre-configuring may specifically include:
and step A, adding keywords in the configuration file of the Widget package, and identifying script plug-ins to be loaded through the attributes of the configuration keywords. The keywords comprise standard keywords and extended keywords; and aiming at the standard keyword, the Widget engine has corresponding configuration in advance. And corresponding keywords can be selected and added for configuration according to the attribute (type attribute) of the script plug-in which needs to be loaded. The types of the script plug-ins comprise standard script plug-ins and extended script plug-ins; the standard script plug-in may be provided by a service operator of the mobile terminal and the extended script plug-in may be provided by a third party. The pre-configuration can be completed by a Widget system tool, or other tools other than Widget.
In this embodiment, the step a may specifically include:
step A1, adding extension keywords in the configuration file of the Widget package, and setting the name and path of the script plug-in the attribute; or,
step A2, adding standard keywords in the configuration file of the Widget package, and setting the name of the script plug-in the attribute.
The step a1 may specifically be: xml, adding keyword < NETSCAPELIB >, setting name of script plug-in name attribute of < lib > sub item, and setting path of script plug-in path attribute.
The step a2 may specifically be: xml, add keyword < standby > in the configuration file config of the Widget package, and set the name of the script plug-in the name attribute of the < lib > sub-item.
Referring to fig. 4, in this embodiment, the step S21 specifically includes:
step S210, the Widget engine reads the key words of the configuration file of the Widget package to obtain the attribute of the script plug-in needing to be loaded;
step S211, obtaining an interface function of the script plug-in according to the attribute, and calling the interface function to obtain an entry function operated by the script plug-in;
step S212, calling the entry function, and loading the script plug-in into the browser engine.
In step S210, in this embodiment, the Widget engine of the mobile terminal reads the configuration file config.xml of the mobile Widget, and obtains the corresponding attribute of the script plug-in to be loaded according to the keyword < NETSCAPELIB > and < standardliib >, so as to conveniently read the script plug-in to be loaded.
In step S211, in this embodiment, the Widget engine of the mobile terminal may find the script plug-in that needs to be loaded according to the attribute of the script plug-in that needs to be loaded, which is obtained in step S210, by using the interface function provided by the operating system of the mobile terminal. And opening the script plug-in to be loaded to obtain an interface function provided by the script plug-in to the outside. The interface function includes: initializing the interface function of the plug-in, obtaining the interface function of the plug-in entry function, closing the interface function of the plug-in, and the like. The interface function is an export interface function specified by the script plug-in.
The Widget engine constructs a data type variable defined by a browser engine, and calls the initialization plug-in interface function as a parameter to initialize the script plug-in; the Widget engine calls the interface function for obtaining the plug-in entry function to obtain the entry function operated by the script plug-in.
In step S212, in this embodiment, the Widget engine of the mobile terminal may call an entry function run by the script plug-in, and embed the plug-in the browser engine.
After receiving the mobile Widget closing message, the Widget engine can check whether an interface function of the closing plug-in of the script plug-in exists, and if so, the Widget engine calls the interface function of the closing plug-in to unload the plug-in; the Widget engine may then shut itself down.
Referring to fig. 5, an embodiment of the Widget engine 30 of the present invention is provided, which includes an obtaining module 31 and a loading module 32; the obtaining module 31 is configured to obtain an attribute preconfigured by a script plug-in to be loaded in the Widget package; the loading module 32 is configured to load the script plug-in into the browser engine according to the attribute preconfigured by the script plug-in.
The obtaining module 31 may obtain the configured attributes of the script plug-in advance, and determine the script plug-in to be loaded. The loading module 32 may call a plug-in interface of the script plug-in according to the configured attributes (such as name, type, path, and the like), and load the script plug-in to be loaded into the browser engine.
The Widget engine 30 of this embodiment may directly call a plug-in interface, load a script plug-in advance, and need not to make a statement in a script, thereby improving user experience. Meanwhile, because the resources of the mobile terminal are limited, the Widget engine 30 is used in the mobile terminal, which has a more significant effect.
Referring to fig. 6, another embodiment of the Widget engine 30 of the present invention is provided, where the Widget engine 30 further includes a storage module 33, which is configured to search for a needed script plug-in and store the needed script plug-in a Widget package. The searching can be to search for a needed (including version updating) script plug-in the mobile terminal, and save the attribute (including name, path, type and the like) of the script plug-in to the configuration file of the Widget package through pre-configuration; the searching may also be performed outside the mobile terminal, for example, by searching for a required script plug-in through a network, downloading and storing the script plug-in into the Widget package according to a network path (for example, a URL), and storing the attribute of the script plug-in into a configuration file of the Widget package through pre-configuration.
In this embodiment, the pre-configuring may specifically include adding a keyword to a configuration file of the Widget package, and identifying a script plug-in to be loaded by configuring an attribute of the keyword.
In this embodiment, the pre-configuring may further specifically include: adding extension keywords in a configuration file of the Widget package, and setting the name and the path of the script plug-in the attribute; or, adding a standard keyword in a configuration file of the Widget package, and setting the name of the script plug-in the attribute.
In this embodiment, the loading module 32 may be specifically configured to: reading keywords of a configuration file of the Widget package to obtain the attribute of the script plug-in needing to be loaded; acquiring an interface function of the script plug-in according to the attribute, and calling the interface function to acquire an entry function operated by the script plug-in; and calling the entry function, and loading the script plug-in into the browser engine.
The above description is only a preferred embodiment of the present invention, and not intended to limit the scope of the present invention, and all modifications of equivalent structures and equivalent processes, which are made by using the contents of the present specification and the accompanying drawings, or directly or indirectly applied to other related technical fields, are included in the scope of the present invention.
Claims (10)
1. A method for loading script plug-in by Widget engine is characterized by comprising the following steps:
the method comprises the steps that a Widget engine obtains attributes which are pre-configured by script plug-ins needing to be loaded in a Widget package;
and loading the script plug-in into a browser engine according to the attribute preset by the script plug-in.
2. The method for loading the script plug-in by the Widget engine according to claim 1, wherein the step of obtaining the pre-configured attribute of the script plug-in stored in the Widget package by the Widget engine further comprises the steps of:
and searching the needed script plug-in by the Widget engine, and storing the needed script plug-in the Widget package.
3. The method for loading the script plug-in by the Widget engine according to claim 1 or 2, wherein the pre-configuring specifically comprises:
and adding keywords in the configuration file of the Widget package, and identifying script plug-ins needing to be loaded through the attributes of the configuration keywords.
4. The method for loading the script plug-in by the Widget engine according to claim 3, wherein the pre-configuring further specifically comprises:
adding extension keywords in a configuration file of the Widget package, and setting the name and the path of the script plug-in the attribute; or,
and adding standard keywords in the configuration file of the Widget package, and setting the name of the script plug-in the attribute.
5. The method for loading the script plug-in by the Widget engine according to claim 3, wherein the step of loading the script plug-in into the browser engine according to the attribute pre-configured by the script plug-in specifically comprises:
the method comprises the steps that a Widget engine reads keywords of a configuration file of a Widget package to obtain attributes of script plug-ins needing to be loaded;
acquiring an interface function of the script plug-in according to the attribute, and calling the interface function to acquire an entry function operated by the script plug-in;
and calling the entry function, and loading the script plug-in into a browser engine.
6. A Widget engine, comprising:
the acquisition module is used for acquiring the attribute which is configured in advance by the script plug-in needing to be loaded in the Widget package;
and the loading module is used for loading the script plug-in into the browser engine according to the attribute preset by the script plug-in.
7. The Widget engine according to claim 6, further comprising:
and the storage module is used for searching the needed script plug-in and storing the needed script plug-in the Widget package.
8. The Widget engine according to claim 6 or 7, wherein the pre-configuring specifically includes:
and adding keywords in the configuration file of the Widget package, and identifying script plug-ins needing to be loaded through the attributes of the configuration keywords.
9. The Widget engine according to claim 8, wherein the pre-configuring further specifically includes:
adding extension keywords in a configuration file of the Widget package, and setting the name and the path of the script plug-in the attribute; or,
and adding standard keywords in the configuration file of the Widget package, and setting the name of the script plug-in the attribute.
10. The Widget engine according to claim 8, wherein the loading module is specifically configured to:
reading keywords of a configuration file of the Widget package to obtain the attribute of the script plug-in needing to be loaded;
acquiring an interface function of the script plug-in according to the attribute, and calling the interface function to acquire an entry function operated by the script plug-in;
and calling the entry function, and loading the script plug-in into a browser engine.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201010223338.5A CN101887376B (en) | 2010-07-09 | 2010-07-09 | The method of Widget engine loading scripts plug-in unit and Widget engine |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201010223338.5A CN101887376B (en) | 2010-07-09 | 2010-07-09 | The method of Widget engine loading scripts plug-in unit and Widget engine |
Publications (2)
Publication Number | Publication Date |
---|---|
CN101887376A true CN101887376A (en) | 2010-11-17 |
CN101887376B CN101887376B (en) | 2015-09-16 |
Family
ID=43073306
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN201010223338.5A Active CN101887376B (en) | 2010-07-09 | 2010-07-09 | The method of Widget engine loading scripts plug-in unit and Widget engine |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN101887376B (en) |
Cited By (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN102081633A (en) * | 2009-11-27 | 2011-06-01 | 阿里巴巴集团控股有限公司 | JavaScript file management method, device and system |
CN102207873A (en) * | 2011-06-15 | 2011-10-05 | 中国联合网络通信集团有限公司 | Realizing method of JavaScript extended object based on Android platform, and binding interface structure |
CN102546811A (en) * | 2012-01-17 | 2012-07-04 | 百度在线网络技术(北京)有限公司 | Method and device for arranging browser plugin on mobile terminal |
WO2012155698A1 (en) * | 2011-06-30 | 2012-11-22 | 中兴通讯股份有限公司 | Browser engine based method for dynamically loading widget and mobile terminal |
CN102880456A (en) * | 2012-07-31 | 2013-01-16 | 北京奇虎科技有限公司 | Method and device for creating plug-in |
CN103365907A (en) * | 2012-04-06 | 2013-10-23 | 腾讯科技(深圳)有限公司 | Method, system and server for displaying payment page |
CN103839156A (en) * | 2014-03-20 | 2014-06-04 | 上海讯联数据服务有限公司 | Method for displaying checkout counter page based on page skip payment in online payment |
CN104049986A (en) * | 2013-03-14 | 2014-09-17 | 腾讯科技(深圳)有限公司 | Plugin loading method and device |
CN104423986A (en) * | 2013-09-02 | 2015-03-18 | 北京亿阳信通科技有限公司 | Method and device for embedding script into application system |
CN105446709A (en) * | 2014-07-29 | 2016-03-30 | 阿里巴巴集团控股有限公司 | Method and device for processing Java application |
WO2017020459A1 (en) * | 2015-07-31 | 2017-02-09 | 百度在线网络技术(北京)有限公司 | Method and apparatus for configuring plugin package for host |
Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101505409A (en) * | 2009-03-13 | 2009-08-12 | 中兴通讯股份有限公司 | Method for playing mobile multimedia broadcast program through browser and terminal thereof |
CN101667115A (en) * | 2008-09-02 | 2010-03-10 | 中国移动通信集团公司 | Terminal, system and method for deploying client application |
-
2010
- 2010-07-09 CN CN201010223338.5A patent/CN101887376B/en active Active
Patent Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101667115A (en) * | 2008-09-02 | 2010-03-10 | 中国移动通信集团公司 | Terminal, system and method for deploying client application |
CN101505409A (en) * | 2009-03-13 | 2009-08-12 | 中兴通讯股份有限公司 | Method for playing mobile multimedia broadcast program through browser and terminal thereof |
Non-Patent Citations (2)
Title |
---|
黄金雪: "《Widget引擎编程应用》", 《电脑知识与技术》 * |
黎莹等: "《基于XML_Glue的Widget的开发与研究》", 《计算机技术与发展》 * |
Cited By (18)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN102081633A (en) * | 2009-11-27 | 2011-06-01 | 阿里巴巴集团控股有限公司 | JavaScript file management method, device and system |
CN102207873A (en) * | 2011-06-15 | 2011-10-05 | 中国联合网络通信集团有限公司 | Realizing method of JavaScript extended object based on Android platform, and binding interface structure |
CN102207873B (en) * | 2011-06-15 | 2013-10-23 | 中国联合网络通信集团有限公司 | Realizing method of JavaScript extended object based on Android platform, and binding interface structure |
CN102323887B (en) * | 2011-06-30 | 2017-02-08 | 中兴通讯股份有限公司 | Browser engine-based method for dynamically loading Widget and mobile terminal |
WO2012155698A1 (en) * | 2011-06-30 | 2012-11-22 | 中兴通讯股份有限公司 | Browser engine based method for dynamically loading widget and mobile terminal |
CN102546811A (en) * | 2012-01-17 | 2012-07-04 | 百度在线网络技术(北京)有限公司 | Method and device for arranging browser plugin on mobile terminal |
CN103365907A (en) * | 2012-04-06 | 2013-10-23 | 腾讯科技(深圳)有限公司 | Method, system and server for displaying payment page |
CN103365907B (en) * | 2012-04-06 | 2017-06-30 | 腾讯科技(深圳)有限公司 | Display pays method, system and the server of the page |
CN102880456A (en) * | 2012-07-31 | 2013-01-16 | 北京奇虎科技有限公司 | Method and device for creating plug-in |
CN102880456B (en) * | 2012-07-31 | 2016-08-31 | 北京奇虎科技有限公司 | Plug-in loading method and system |
CN104049986A (en) * | 2013-03-14 | 2014-09-17 | 腾讯科技(深圳)有限公司 | Plugin loading method and device |
CN104049986B (en) * | 2013-03-14 | 2018-12-18 | 腾讯科技(深圳)有限公司 | plug-in loading method and device |
CN104423986A (en) * | 2013-09-02 | 2015-03-18 | 北京亿阳信通科技有限公司 | Method and device for embedding script into application system |
CN104423986B (en) * | 2013-09-02 | 2018-12-14 | 山东亿阳信通信息技术有限公司 | A kind of method and apparatus that application system embeds script |
CN103839156A (en) * | 2014-03-20 | 2014-06-04 | 上海讯联数据服务有限公司 | Method for displaying checkout counter page based on page skip payment in online payment |
CN105446709A (en) * | 2014-07-29 | 2016-03-30 | 阿里巴巴集团控股有限公司 | Method and device for processing Java application |
CN105446709B (en) * | 2014-07-29 | 2019-06-21 | 阿里巴巴集团控股有限公司 | A kind of Java application processing method and device |
WO2017020459A1 (en) * | 2015-07-31 | 2017-02-09 | 百度在线网络技术(北京)有限公司 | Method and apparatus for configuring plugin package for host |
Also Published As
Publication number | Publication date |
---|---|
CN101887376B (en) | 2015-09-16 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN101887376B (en) | The method of Widget engine loading scripts plug-in unit and Widget engine | |
US8620995B2 (en) | Method, computer program, transcoding server and computer system for modifying a digital document | |
US9262311B1 (en) | Network page test system and methods | |
CN107864173A (en) | Terminal page caching method, system and readable storage medium storing program for executing | |
CN106790206B (en) | The message parsing method and device of operation system | |
US10284686B2 (en) | Server, client, system and method for preloading browsed page in browser | |
CN108319662A (en) | Page processing method, device, electronic equipment and readable storage medium storing program for executing | |
CN105260318A (en) | Automatic testing method and device based on web pages | |
US8990929B2 (en) | Auditing application activities | |
CN105094777B (en) | Realize the method and device for applying screenshotss | |
CN110928767A (en) | Webpage analysis method, device, equipment and storage medium | |
US20130290898A1 (en) | Method for presenting prompt message, terminal and server | |
US20050160414A1 (en) | System and method for dynamically adding features to software applications | |
CN106201610A (en) | Web application accesses the method and device of the primary function of terminal | |
CN112154420A (en) | Automatic intelligent cloud service testing tool | |
CN112636966A (en) | Application batch deployment method based on remote debugging protocol | |
CN113064685A (en) | H5 page loading method and device | |
CN113946602A (en) | Data searching method, device, equipment and medium | |
CN111949491A (en) | SQL extraction method and device for MyBatis application program | |
CN108920246B (en) | Form draft component sharing method and device, terminal device and readable storage medium | |
CN112351094B (en) | Webpage pushing method and device, electronic equipment and storage medium | |
CN107888451A (en) | The method of testing and device of a kind of Web server | |
CN109492144A (en) | Association relationship analysis method, device and the storage medium of software systems | |
CN109144841B (en) | Method and device for identifying advertisement application, computer equipment and storage medium | |
CN110348226A (en) | A kind of scan method of project file, device, electronic equipment and storage medium |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
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 |