CN105354013A

CN105354013A - Application interface rendering method and apparatus

Info

Publication number: CN105354013A
Application number: CN201410406745.8A
Authority: CN
Inventors: 康彬; 洪小龙; 高嘉峻; 黄金涌; 张津; 倪顺坚; 徐焕杰
Original assignee: Alibaba Group Holding Ltd
Current assignee: Alibaba Group Holding Ltd
Priority date: 2014-08-18
Filing date: 2014-08-18
Publication date: 2016-02-24
Anticipated expiration: 2034-08-18
Also published as: CN105354013B

Abstract

The application discloses an application interface rendering method and apparatus. An SDK package is arranged in a client of an application. The SDK package comprises a rendering engine. A first correspondence between component information defined in interface data and a native component in a current terminal device is stored in the rendering apparatus. The method comprises: completing the following operations through the rendering engine: when a request of displaying a specified interface of the application is received, requesting for interface data of the specified interface of the application from a server; after the interface data returned by the server are received, analyzing the interface data to obtain the component information defined in the interface data; according to the first correspondence, mapping the component information defined in the interface data into the native component in the current terminal device; and rendering the native component. Through the application interface rendering method and apparatus, users can be enabled to use latest functions of applications more timely, and various defects of a hybird scheme are avoided.

Description

Application interface rendering intent and device

Technical field

The application relates to application interface Rendering field, particularly relates to application interface rendering intent and device.

Background technology

The essence of mobile terminal application (App) is exactly the set at numerous interface, therefore, in traditional mobile terminal App development technique, for a mobile terminal App product, uses generally need through following process from exploitation to final user:

The first step: by complete for interface module development and testing all in App, and GUI code is packaged into one and complete satisfiedly issues the App installation kit required;

Second step: App installation kit is published to various channel, such as, application commodity shop (Appstore) etc.), download and install App for user;

3rd step: App, to a certain channel down load application installation kit, is installed on oneself mobile terminal, brings into use App by user.

Such development procedure determines existing App exploitation and runs into following problem to I haven't seen you for ages: no matter be New function exploitation, or bug repairs, or implementation adjusting and optimizing, all needing to be upgraded to this process of new edition through issuing redaction from App to subscriber terminal equipment, could finally allow user use.Such as, for the App installed in terminal device, when there being redaction to issue, the lastest imformation of redaction generally can be pushed to the channels such as Appstore by server, user needs manually to enter the concrete renewal interface of Appstore, triggers the renewal of application, accordingly, server can be sent to terminal device data such as the codes after renewal, completes the processes such as the upgrading of App.Before user manually performs renewal, although user can continue to use this App, the latest function of App cannot be used.

On the other hand, there is a kind of Hybird development mode, the principle of this mode is, the interface data of application is kept at server end, and the API of movement is mapped to JavaScript by the webview in system and connects for HTML5 by client.Under this mode, if developer needs the interface data of more new opplication, then only need to carry out upgrading at server end, do not need the code revising client, therefore, no longer exist and issue the processes such as redaction to client, user can use the function after renewal in time.

If Hybird technology can be applied in the App performance history of mobile terminal, then foregoing problems can be solved, but, the App of Hybird technological development is used generally to write with HTML5 and JavaScript, this language directly cannot be moved the primary code call in terminal, therefore, and must by means of browser kernel (such as webkit), and changed by webview, could run in the terminal.That is, if use Hybird development mode in the terminal, then need to carry out representing of interface by means of the browser installed in mobile terminal, browser kernel webkit in this meeting heavy dependence mobile phone operating system, and webkit is a general browser kernel, rise in conventional P C browser technology, carry the web technology on too many conventional P C, and this wherein has quite a few and be not suitable for mobile terminal, make the core of whole technical scheme seem extremely heavy, also therefore cruelly spill some problems.Such as:

First, all JavaScript need just can be mapped in the native layer of movement by the transfer of webview, therefore, developer needs to define for the transformational relation between JavaScript and webview and between webview and native, and cost of development is higher;

Secondly, be subject to some safety rules restriction that PC browser technology is intrinsic, to the various service of this locality and resource access limited, comprise local file system or network cross-domain etc., such as, if certain application needs the camera function called in mobile terminal device, then may there is situations such as cannot calling;

Moreover, the use of the new features respectively provided is limited to the support of webkit kernel, and webkit wants the compatible thing inherited too many due to it, General development can be slower, this just causes hybird scheme that various new technology on mobile terminal cannot be used in time to improve Product Experience, such as, it just can not use distinctive various sensor technologies etc. on mobile terminal smoothly.

Visible, how allowing user use the latest function of App more in time, avoid again the various defects of hybird scheme simultaneously, is the technical matters solved in the urgent need to those skilled in the art.

Summary of the invention

This application provides application interface rendering intent and device, user can be allowed to use the latest function of App more in time, avoid again the various defects of hybird scheme simultaneously.

This application provides following scheme:

A kind of application interface rendering intent, SDK bag is provided with in the client of application, described SDK comprises a render engine, the first corresponding relation between the primary assembly in the module information defined in interface data and present terminal equipment is preserved in described render engine, described method comprises, and completes following operation by described render engine:

When receiving the request at the appointment interface showing described application, to the interface data at the described appointment interface of this application of server request;

After receiving the interface data that server returns, described interface data is resolved, obtains the module information defined in described interface data;

According to described first corresponding relation, the module information defined is mapped as the primary assembly in present terminal equipment in described interface data;

Described primary assembly is played up, for the described appointment interface of displaying.

A kind of application interface rendering intent, is characterized in that, comprising:

Receive the request at the displaying appointment interface that client sends;

The interface data at described appointment interface is returned to described client, so that after the render engine comprised in integrated in described client SDK bag receives the interface data that server returns, described interface data is resolved, obtain the module information defined in described interface data, according to the first corresponding relation preserved in advance, the module information defined in described interface data is mapped as the primary assembly in present terminal equipment, and described primary assembly is played up, for the described appointment interface of displaying; Wherein, the interface data of described application is kept at the server end of application, and described first corresponding relation is the corresponding relation between the primary assembly in the module information and present terminal equipment defined in interface data.

A kind of application interface rendering device, SDK bag is provided with in described device, described SDK comprises described render engine, and preserve the first corresponding relation between the primary assembly in the module information defined in interface data and present terminal equipment in described render engine, described render engine comprises:

Request of data unit, for when receiving the request at the appointment interface showing described application, to the interface data at the described appointment interface of this application of server request;

Data Analysis unit, after receiving interface data that server returns, resolves described interface data, obtains the module information defined in described interface data;

Assembly map unit, for according to described first corresponding relation, is mapped as the primary assembly in present terminal equipment by the module information defined in described interface data;

Rendering unit, for playing up described primary assembly, for the described appointment interface of displaying.

A kind of application interface rendering device, is characterized in that, comprising:

Request reception unit, the request at interface is specified in the displaying sent for receiving client;

Data return unit, for returning the interface data at described appointment interface to described client, so that after the render engine comprised in integrated in described client SDK bag receives the interface data that server returns, described interface data is resolved, obtain the module information defined in described interface data, according to the first corresponding relation preserved in advance, the module information defined in described interface data is mapped as the primary assembly in present terminal equipment, and described primary assembly is played up, for the described appointment interface of displaying; Wherein, the interface data of described application is kept at the server end of application, and described first corresponding relation is the corresponding relation between the primary assembly in the module information and present terminal equipment defined in interface data.

According to the specific embodiment that the application provides, this application discloses following technique effect:

Pass through the embodiment of the present application, the assembly defined in interface data can be mapped directly to the primary assembly in mobile terminal due to Dynative, therefore, the primary code that can directly call in mobile terminal device is played up interface, and be no longer dependent on Webkit kernel and the Webview of browser, that is, use the interface data that the data layouts such as JSON are write, can as the native applications in mobile terminal in be performed, therefore, for the various New function etc. used in mobile terminal, all there is good adaptability, user can be allowed to use the latest function of App more in time, avoid again the various defects of hybird scheme simultaneously.

Certainly, the arbitrary product implementing the application might not need to reach above-described all advantages simultaneously.

Accompanying drawing explanation

In order to be illustrated more clearly in the embodiment of the present application or technical scheme of the prior art, be briefly described to the accompanying drawing used required in embodiment below, apparently, accompanying drawing in the following describes is only some embodiments of the application, for those of ordinary skill in the art, under the prerequisite not paying creative work, other accompanying drawing can also be obtained according to these accompanying drawings.

Fig. 1 is the interface schematic diagram that the embodiment of the present application provides;

Fig. 2 is the process flow diagram of the method that the embodiment of the present application provides;

Fig. 3-1 is the logical tree structure schematic diagram that the embodiment of the present application provides;

Fig. 3-2 is physics tree construction schematic diagram that the embodiment of the present application provides;

Fig. 3-3 is another physics tree construction schematic diagram that the embodiment of the present application provides;

Fig. 4 is the GUI code schematic diagram in Hybird scheme;

Fig. 5 is another GUI code schematic diagram in Hybird scheme

Fig. 6 is Hybird system architecture schematic diagram;

Fig. 7 is the schematic diagram of the GUI code in the scheme that provides of the embodiment of the present application;

Fig. 8 is the system architecture schematic diagram that the embodiment of the present application provides;

Fig. 9 is the other method process flow diagram that the embodiment of the present application provides;

Figure 10 is the rendering device schematic diagram that the embodiment of the present application provides;

Figure 11 is the server-side device schematic diagram that the embodiment of the present application provides.

Embodiment

Below in conjunction with the accompanying drawing in the embodiment of the present application, be clearly and completely described the technical scheme in the embodiment of the present application, obviously, described embodiment is only some embodiments of the present application, instead of whole embodiments.Based on the embodiment in the application, the every other embodiment that those of ordinary skill in the art obtain, all belongs to the scope of the application's protection.

In the embodiment of the present application, provide a kind of novel render engine (being referred to as Dynative), provide Dynative agreement simultaneously, developer can develop oneself application according to Dynative agreement, write interface data, after having developed, this interface data is only needed to be kept at server end, and application client in this Dynative render engine integrated, this interface data just can be mapped in concrete mobile terminal and run by Dynative, and realizes corresponding function.For the ease of understanding, first Dynative agreement is introduced below.

Due to the basic composition element that assembly is user interface (UI), therefore, in Dynative agreement, define multiple assembly, developer can carry out writing of interface data according to the module information defined in Dynative agreement.Wherein, so-called assembly, refers to a block that can represent on mobile terminal screen.

Such as, in Dynative agreement, define figure chip module, text component, list element, panel assembly etc., and the type declaration, input list etc. of various assembly are defined.Such as, the type declaration of figure chip module is as shown in table 1:

Table 1

Attribute

Type

Title

Whether essential

Type

String

Image

Y

Input list is as shown in table 2:

Table 2

Like this, developer is when writing the interface data of oneself, and just can define according to above-mentioned agreement the figure chip module oneself needed, such as, in certain example, code can be as follows:

Visible, in above-mentioned interface data code, define the assembly that type is " image ", like this, Dynative according to the type name information, will be identified as a figure chip module, the follow-up primary assembly that just can be mapped as in concrete mobile terminal.Certainly, the formal definition dynamic interaction information of also jump script function by reference in above-mentioned figure chip module, script function can also be mapped to the primary api function in concrete mobile terminal by Dynative, and call, about this, follow-uply have detailed introduction.

And for example, in agreement, also define text component, wherein, about type declaration as shown in the following Table 3:

Table 3

Attribute	Type	Title	Whether essential
				Type	String	Text	Y

Input list as shown in the following Table 4:

Table 2

Visible, in above-mentioned interface data code, define the assembly that type is " text ", like this, Dynative according to the type name information, can be identified as a text component, the follow-up primary assembly that just can be mapped as in concrete mobile terminal.

About other assemblies such as list element and panel assembly, also corresponding type declaration and input list information is all given in agreement, in a word, framework user can according to the module information defined in this agreement, carry out writing of interface data, operationally, Dynative maps according to the corresponding relation in the module information of preserving in advance and mobile terminal between primary assembly again.

Wherein, in concrete application interface, may need to possess certain interaction capabilities when some assembly represents in interface, such as dynamically pulling data coordinates list element display data, basic logic, arithmetical operation, relational calculus are carried out to data, on-the-fly modify the attribute of view elements, etc.For this reason, the embodiment of the present application has also defined the custom script that can run on framework based on Dynative, allows framework user to embed script in interface, and is performed by Analysis on Framework.

That is, Dynative script in Dynative framework, like JavaScript script in browser, in time not having script, Dynative framework can only show the static page, and ability does not provide front end mutual.Such as in a commodity page, according to interface data, some commodity need to beat " preferential price mark ", what have does not need, this time, the simple Dynative page cannot be accomplished dynamically to judge which has preferential price, must have script to perform this logic, and change view.The commodity page provides collection function for another example, and user clicks " collection " button collecting commodities, and the word of button and background all need to change over collecting state, and this interactive function also needs script to perform.

For this reason, except said modules information, also define some other information in agreement, comprising:

Built-in variable, comprises client.userid (user id), client.sid (identify label), client.ttid (client ttid), client.version (client release) etc.

Way of reference information, comprise ui element and quote that ($ layout starts, element id point separates, such as $ layout.banner.url), ($ variable starts in variable reference, or directly use " $ variable name " to quote, such as $ variable.varname), data referencing (search by data referencing, general with $ context, $ response, $ args starts, according to json structure lookup data, such as { context:{data:{items:[{a:1}, b:1}] } } }), ($ function starts in function reference, functional based method is searched, function only supports that one deck is searched, such as $ function.method1) etc.

Expression formula, comprises binary arithmetic operator expression formula, relational expression, logical expression etc.

Built-in basic script function, such as, string connecting moves, isempty sentences empty action, order performs an action, condition performs an action, circulating performs an action, setup of attribute action, assembly update action, prompt action (representing rear automatic disappearance), alert action, logs in and check action (if do not logged in, can trigger clients log in), long-range API Calls action etc.Developer can use these basic script function to define some dynamic interaction contents etc., and basic script function can be used to assemble self-defining function.

Like this, Dynative script can be realized based on following basic procedure:

First, the fundamental element related in definition script, comprises operational symbol, statement, function etc., is the definition of each fundamental element grammer, namely agreement.

Like this, framework user just can adopt general certain data layout (such as, JSON) to realize the scripting definition of above-mentioned fundamental element.

Dynative framework is responsible for resolving these JSON and is defined, and function object when example changes into concrete relevant operation, the logic in function object is operationally performed according to agreement.

Needs illustrate, except defining various grammers in script etc. in the protocol, also need to preserve the corresponding relation between the various script function in script and the primary api function in concrete mobile terminal in advance, so that Dynative framework is when resolving script, the mapping from JSON data to primary api function can be completed, to this, hereinafter have detailed introduction, first the script definition mode in Dynative agreement is introduced below.

First, in Dynative agreement, a agreement is both defined for each fundamental element, at least one type field is all contained in every a agreement, it show that protocol type, Dynative resolver needs the primary api function object resolved to according to the value of this field in concrete mobile terminal.Dissimilar agreement also can comprise field exclusive separately, is used for quoting data required separately.Be introduced respectively below.

(1) assignment

Protocol type is setdata, var is quoting of variable or view elements attribute etc.; Value is constant, another variable reference, view elements attribute are quoted, a function call etc.

(2) value

Protocol type is that getdata, type field can be omitted; Value is constant, another variable reference, view elements attribute are quoted, a function call etc.

(3) binary arithmetical operation

Protocol type is the one in add, sub, mul, div, respectively representative add, subtract, multiplication and division.Can only carry out binary arithmetical operation to numeral, the value of operand can be constant, variable etc., also can another binary arithmetical operation of nested definition, using its rreturn value as operand.

(4) relational calculus

Protocol type is the one in eq, ne, gt, ge, lt, le, representative equals, is not equal to, is greater than, is more than or equal to, is less than, is less than or equal to respectively, eq and ne can compare computing to numeral, character string, Boolean, and other relational calculuses can only for numeral.The value of operand can be constant, variable reference etc., also can another binary arithmetical operation of nested definition or other functions, using its rreturn value as operand.

(5) logical operation

Protocol type is the one in and, or, not, respectively representative with or, non-, when type is not, operand only has one.Logical operation only carries out computing for Boolean type.Operand can be constant, variable reference etc., or another logical operation nested, relational calculus, using its rreturn value as operand.If relate to the logical operation of two or more condition, nested logical operation computing can only be carried out at present.

Relational calculus and logical operation are generally used for condition judgment statement.

(6) sequential statement

Protocol type is call.Can store other arbitrary function lists in funcs field, order performs.

(7) conditional statement

Protocol type is condition, by performing the function call in test, if for returning results as true, performs the function in then, the function in no execution else.

(8) loop statement

In addition, in agreement, also define other build-in functions, similar with above-mentioned basic definition, by a type keyword definition type, provide the function of some practicalities, such as string-concatenation, sentence sky, remote interface calls etc.

In a word, based on above-mentioned Dynative agreement, framework user can carry out the exploitation of applying, and defines the interface data of this application, and, can be define in units of assembly.Concrete, so-called interface data can comprise the content-data of interface layout's data and each assembly, can define the information such as the coordinate of each assembly, size in interface layout's data; Content-data then can comprise two kinds, and one is the static data content for static component (such as, some simple text component etc.) defines, and it can define the content of concrete display in assembly; Another kind is the data content for dynamic assembly definition, and this dynamic assembly can have various ways according to the difference of triggering mode.Such as, just need to obtain the assembly of particular content data (such as by calling the modes such as network interface when can be included in view initialization, the picture shown in interface, video etc., general when definition interfaces data, only may point out picture, the network address at video place, and quoted, instead of directly in interface data, provide picture, the concrete data of video or data stream itself), or, the assembly be triggered when being view elements binding data (such as, some data lists, may need to read data from certain database table), moreover, can also be the assembly that is triggered according to the dynamic interaction action of user (such as, some buttons etc.).For this dynamic assembly, for the content-data of its definition can be the dynamic script defined according to Dynative script agreement in interface data.

Interface layout's pattern data can be regarded as about interface layout's data and static data content, therefore, various interface description language (such as xml, json, html, xhtml, html5 etc.) can be selected according to actual needs to be described, and about dynamic script data, then various script (such as JavaScript, lua, json etc.) can be selected as required to describe interaction logic.Such as, under dynative implementation, all data (comprising interface layout's pattern data and interaction scripts data) mutual between client and server can adopt json format organization.

In addition, for the ease of carrying out the renewal of data, interface layout's data and content-data can carry out independence and define and preserve.Certainly, during for the ease of subsequent solves, by being associated with on same assembly for interface layout's data of same component definition and content-data, when writing interface data, can also definitions component id, same assembly has identical id.Like this, when in follow-up redaction, if only need to upgrade certain partial content data, then interface layout's data can be constant, directly upgrades this part content-data, if need to upgrade certain part interface topology data, also be then only need to upgrade this part interface layout's data, content-data can be constant, like this, can avoid causing the significantly amendment to interface data, reduce the workload of the work such as edition upgrading, renewal.

Visible by the above, when specific implementation, in order to allow the various data of the Dynative complete resolution interface of energy, the interface data that server end issues needs all information needed when comprising traditional native interface development, mainly comprise interface layout information and interface-data content information, data content information also comprises static information and dynamic logic information.Such as, in the example of a certain specific implementation, the data structure that Dynative service end issues can be as follows:

Wherein, the layout information at whole interface is housed in layout, be used for describing this interface and comprise which assembly, the position of each assembly in interface, size etc., this partial data can be resolved the genuine interface element being mapped to each movement by Dynative resolver.

Such as, the concrete data structure of layout can be:

House interface static data in Context, if the data that certain assembly is shown do not need to adjust network interface to obtain in addition, just can directly leave in here by static data, Dynative can from getting here when using interface data.

Such as, the concrete data structure of Context can be:

Contain the script function that this interface uses in function, the function of script function comprises calls that certain network interface obtains interface data, response user clicking operation jumps to other interfaces etc.

Such as, the concrete data structure of function can be:

It should be noted that, the assembly described in the embodiment of the present application can comprise atom component and container assemblies two kinds.Wherein, so-called atom component refers to minimum assembly, is generally used for representing the content of certain particular form, and as text component is used for showing text message, figure chip module is used for representing picture etc.; So-called container assemblies is used to a kind of particular components of Management Unit, is responsible for, comprises parsing, layout, drafting etc. to the life cycle of all sub-components of its management.In order to solve the multiplexing problem of layout definition, in the embodiment of the present application, developer can also be allowed in interface data to define composite component, and so-called composite component is the various assemblies using atom component and container assemblies to be assembled into, and general practical business of following is closely connected.In actual applications, as long as define a composite component, can quote Anywhere in interface, and not need to re-define identical interface layout in each place.

Such as, in the example of practical application, composite component can be defined by lib, and concrete data structure can be as follows:

In the above example, define the composite component of a fourfoldimage by name, the function of this composite component is, often capable display two atom component, and define the type etc. of first atom component at eighth row to the 13rd row, define the type of second atom component at the 14th to the 19th row, two kinds are figure chip module; Therefore, in layout, just can use this composite component, wherein, respectively employ once this composite component at the 31st row and the 45th row, and specify the picture address of concrete display, final display effect can be as shown in Figure 1.

It should be noted that, when there is composite component, the partial data structure of the interface data that server end issues can be as follows:

In addition, system component (comprising atom component and container assemblies) is all belonged to above about the text component introduced, figure chip module etc., when defining these assemblies, all need to specify its type typonym, such as, the 5th row in previous example, the 10th provisional capital specify type name information respectively.But, when using composite component, in order to distinguish with atom component, employ ref as key word, as the 31st row in previous example and the 45th row.For Dynative resolver, when resolving interface data information, if find type key word, then can determine to which define a system component (comprising atom component and container assemblies), if find ref key word, then determine to it use a composite component, then according to the composite component title after ref, corresponding composite component information is found in libs, and according to the atom component information defined in composite component information, carry out the operations such as the follow-up mapping to primary assembly.

After having defined interface data with upper type, can server end be kept at, follow-up when needs represent this interface, Dynative just can be used to carry out parsing to interface data and to play up.Wherein, specifically when resolving interface data, a groundwork of Dynative is exactly the primary assembly be mapped as by the various assemblies defined in interface data in mobile terminal, when there is dynamic script, various fundamental elements in dynamic script are mapped to the primary API in mobile terminal, and primary api function is defined as the content-data of this assembly, when being triggered with the execution event of convenient dynamic script, use primary code to call this primary API.In order to complete this mapping, also need to preserve the corresponding relation between each module information in agreement and the primary assembly in concrete mobile terminal in advance, also needing in addition to preserve in advance in agreement is the corresponding relation between the primary api function in the type value of the various fundamental elements of dynamic script definition and mobile terminal.

Therefore, during specific implementation, SDK can be provided to wrap for the developer of mobile terminal App, Dynative render engine (processing logic that this engine is can be nothing to do with) can be comprised in this SDK bag, and the module information in interface data and the corresponding relation between the primary assembly in terminal device, when there is dynamic script in interface data, (above-mentioned two kinds of correspondence relationship information are with relevant for the corresponding relation also comprising between the type value of the various fundamental elements defined in script and the primary api function in mobile terminal, such as, same function understands corresponding different primary assemblies in different).In other words, the Main Function of this render engine is exactly, according to the corresponding relation preserved in SDK, by the module information defined in interface data, primary assembly in mapping in current mobile terminal, the dynamic script defined in interface data is mapped to the primary api function in current mobile terminal, and calls the primary code in current mobile terminal, displaying is played up to primary assembly.That is, for webkit, Dynative is a kind of render engine of lightweight, mainly serves the intermediation between interface data and primary code, no longer needs the transfer of Webview.

As mentioned before, above-mentioned two kinds of corresponding relations, to relevant, such as, are text component equally, and in Android, corresponding primary assembly is textview, and in iOS, corresponding primary assembly is lable, etc.Therefore, in order to realize correct conversion, can provide different SDK bags for different mobile terminals respectively, in different SDK wraps, aforementioned corresponding relation is different.Such as, for Android, the corresponding relation between the primary assembly in the module information in interface data and terminal device can be as shown in table 5:

Table 5

The component type title defined in agreement

Primary assembly

text	TextView
		Image	ImageView
list	ListView
		……	……

For iOS, this corresponding relation can be as shown in table 6:

Table 6

The component type title defined in agreement	Primary assembly
		Text	UILable
Image	UIImageView
		list	UITableView
……	……

For Android, the corresponding relation between the primary api function in the type value of the various fundamental elements of dynamic script in interface data definition and mobile terminal, can be as shown in table 7:

Table 7

The type value of fundamental element	Primary api function
		tips	Toast
alert	AlertDialog
		……	……

For iOS, this corresponding relation can be as shown in table 8:

Table 8

The type value of fundamental element

Primary api function

tips	UIAlertView
		alert	UIActionSheet
……	……

Remarks: only list two or three examples in above assembly and API and carry out principle of specification, in fact can comprise the mapping logic of multiple assembly and API in SDK.

Wherein, in order to directly call the primary code in mobile terminal, when for certain mobile terminal exploitation SDK bag, SDK bag can be use the code speech that in this mobile terminal device, native applications uses to develop.Such as, for iOS, its primary App uses ObjectC language development, the SDK bag then provided for iOS also can use ObjectC language development, and the primary App of Android generally develops with Java language, therefore, the SDK bag provided for Android also can be develop with Java language.In a word, for the SDK bag developed for different mobile terminal, the language used separately may be different, and the module information of preserving separately and the corresponding relation between primary assembly also may be different, but the logic that realizes of Dynative kernel is identical.

Like this, App developer can write the interface data of App according to certain form, but, do not need this interface data code to be bundled in installation kit, but only preserve in the server.When needing its App to be published in certain concrete mobile terminal, can be that the SDK bag of this mobile terminal exploitation is integrated in the client installation kit of App by the embodiment of the present application.Such as, when issuing to Android, can SDK corresponding for Android bag being integrated in App, when issuing to iOS, can SDK corresponding for iOS bag being integrated in App, etc.Certainly, corresponding different, only need in the server to preserve with a interface data, accordingly, Dynative kernel in different SDK bags, can carry out from interface data to primary assembly according to the corresponding relation preserved separately, the mapping of primary api function, and Dynative kernel directly can also carry out and carry out mutual, primary code in calling, directly carry out playing up of primary assembly to represent, and do not need the transfer through similar webview, implement flexibly convenient.

Visible, in the embodiment of the present application, for mobile terminal App, because all interface datas are all only be kept at server end, therefore, when needing the operation such as upgrading, bug reparation carrying out App, directly the interface data that server is preserved is modified, upgrade information etc. need not be issued again to terminal device, therefore, the version after user can be made to use renewal more timely.On the other hand, owing to being integrated with the SDK bag of the embodiment of the present application in client, Dynative kernel wherein uses the language development identical with native applications, therefore, both the primary assembly in interface data can being mapped to, the primary codes implement that can also directly call plays up displaying to primary assembly, therefore, no longer need the webkit kernel depending on browser, also no longer need to carry out transfer by webview, so, the various service of access this locality that can be more flexible and resource, comprise local file system or network cross-domain etc., such as, if certain application needs the camera function called in mobile terminal device, then may directly define in interface data, API during Dynative kernel can be mapped to, and utilize this API to call, etc..In addition, the various characteristics on mobile terminal can also be used smoothly, comprise sensor technology etc.

Below the specific implementation that Dynative carries out in displaying interface process is introduced in detail.

Embodiment one

See Fig. 2, the embodiment of the present application one provide firstly a kind of application interface rendering intent, and this embodiment one is mainly introduced from the scheme of angle to the embodiment of the present application of client.Wherein, developer preserves in the server for the interface data of application provided, SDK bag is provided with in the client of application, under preferred implementation, described SDK bag can be use the code speech that in current mobile terminal equipment, native applications uses to develop, this SDK comprises a render engine, and the corresponding relation between primary assembly in the module information defined in interface data and present terminal equipment, concrete, the method can complete following steps by this render engine:

S201: when receiving the request at the appointment interface showing application, to the interface data at the described appointment interface of this application of server request;

So-called appointment interface can be the main interface of application, or other sub-interfaces, etc.When receiving the request shown and specify interface, not following installation kit due to interface data and downloading to terminal device together, therefore, can first to the interface data at this interface of server request.Concrete definition mode about interface data is introduced in the preceding article.

S202: after receiving the interface data that server returns, described interface data is resolved, obtains the module information defined in described interface data;

Due to cannot directly by terminal device identification with the interface data of the language definitions such as json, therefore, after receiving the interface data that server returns, Dynative kernel just can be resolved this interface data, and can be mapped directly to the primary assembly in present terminal equipment.That is, the Main Function of Dynative kernel is exactly the assembly defined in the interface data that will describe with language such as json, convert the primary assembly in mobile terminal to, so as to carry out interface play up displaying.In order to complete this conversion, first can resolve interface data, obtaining the module information of each assembly wherein defined.Such as, concrete module information can be the type name information of finger assembly, specifically can comprise the typonyms such as previously described text, image.

S203: according to corresponding relation, is mapped to the primary assembly in present terminal equipment by the module information defined in described interface data;

Specifically when mapping, Dynative kernel can first according to the type name information of assembly each in interface data, the assembly defined in interface data is converted to the logic module of native layer, in other words, from interface data, namely extract the typonym of each assembly, the corresponding logic module of each typonym; Further, due to the corresponding relation between also saving in component type title and mobile terminal in SDK bag primary assembly in advance, therefore, this corresponding relation can be utilized logic module to be converted to primary assembly in mobile terminal.Such as, when parsing that in interface data, containing type name is called the assembly of text, if the mobile terminal at current place is Android, then according to table 5, this assembly can be mapped as textview assembly, if the mobile terminal at current place is iOS, then according to table 6, this assembly can be mapped as lable assembly.

S204: the primary code calling present terminal equipment is played up described primary assembly, for the described appointment interface of displaying.

After logic module being converted to the primary assembly in present terminal equipment, just can play up this primary assembly, because primary assembly is the composition component of user interface, therefore, after showing primary assembly, just can show the appointment interface to.

Specifically when carrying out showing interface, can first according to the typonym of assembly each in interface data and separately between the information such as nest relation, formation logic is set.Described logic tree comprises multiple first node, and the module information of the corresponding use interface description language definition of each first node, is mainly used to the static content data storing each assembly in interface, and for information such as script function.In addition, the information of each first node can also comprise the coordinate information defined in interface layout's data.Also namely, the interface data that server returns can be represented with tree form data structure, in logic tree, contain the information that whole interface is all, comprise pattern, layout, interaction scripts etc.Afterwards, according to the information of each first node, imposition layout can be carried out to logic tree, determine coordinate when each first node shows on screen; In addition, after, each first node in logic tree can just be traveled through, and according to the information of each first node, and the corresponding relation between each logic module and primary assembly, logic tree is converted to physics tree.Described physics tree comprises multiple Section Point, the corresponding primary assembly of each Section Point, and the information of each Section Point is included in coordinate information when screen shows and content information.Last each Section Point just physics can set is plotted on screen.Wherein, Section Point and first node one_to_one corresponding, script function can only operate first node, and the operating result of script function can be transparent to corresponding Section Point by first node, and is finally presented on screen.

Such as, suppose that certain section of code in certain interface data is:

There is defined two text component, be respectively txt1 and txt2, then the corresponding logic tree generated as shown in figure 3-1, if in android system, after converting physics tree to, as shown in figure 3-2, if in iOS system, after converting physics tree to, as shown in Fig. 3-3.

If interface layout's data and content-data independently define, then specifically when formation logic is set, can first resolve interface layout's data (being also aforementioned layout data), determine each first node in logic tree, and the coordinate information of each first node, certainly, the assembly id that each first node is corresponding can also be determined simultaneously, then, according to the content-data searching each assembly in assembly id to aforementioned Content data and function data, and being tied on corresponding first node, formation logic is set.

As mentioned before, it is the content-data of each component definition in interface data, comprise static content data and dynamic content data, wherein, when formation logic is set, for static content, can directly extract from the interface data that server end returns, for dynamic content, can be obtained by the dynamic script function in interface data.

Wherein, if only comprise static content data in certain interface data, then the treatment scheme of Dynative can be:

Step 1: resolve layout data, extract the typonym of each assembly wherein defined, determine the title of each logic node, and according to the nest relation in layout data, determine the set membership between each logic node, and then formation logic tree (being equivalent to the dom tree in html);

Step 2: traversal logic tree, and by the data binding in corresponding Content on logic tree, now on logic tree, information is just complete;

Step 3: according to the coordinate information in each node and content information, carries out imposition layout to logic tree;

Step 4: traversal logic tree, according to the corresponding relation preserved in table 5 or table 6, the assembly defined in interface data is mapped as the primary assembly in concrete terminal device, generates corresponding physical node, such physics tree generates (being equivalent to the render tree in html);

Step 5: upper for physics tree each node is plotted on screen.

If except static content data in certain interface data, also comprise dynamic content data, and script needs just triggering when view initialization that this part dynamic data is corresponding, then the treatment scheme of Dynative can be:

Step 1: resolve layout data, formation logic tree (corresponding abovementioned steps 1 and step 2);

Step 2: according to the information in logic tree, carries out preliminary placement to logic tree;

Step 3: traversal logic tree, according to the information in each first node, generates corresponding Section Point, creates out corresponding physics tree;

In the logic tree generated by first three step, contain all components defined in interface data, just wherein members does not also have binding data, only defines the layout information such as coordinate, size;

Step 4: according to the corresponding relation preserved in table 7 or table 8, the script function defined is mapped as primary api function in mobile terminal in interface data, and obtain content-data corresponding to dynamic assembly by calling this api function;

Step 5: the content-data got is tied on first node corresponding to logic tree;

Step 6: according to the information of supplementing in the logic tree of data, again again to logic tree layout;

Step 7: by the lastest imformation in logic tree synchronously in physics tree;

Step 8: upper for physics tree each Section Point is plotted on screen.

In addition, the dynamic script that the dynamic assembly defined in interface data is corresponding may need to be triggered by other events, such as, during view binding data, or during by operations such as user click, etc.But the parsing of script can disposablely complete, also namely start at Dynative framework, when an initialization Dynative page, define script if found that there is, so just disposablely can complete all parsings.And concrete execution, then to wait until that view elements triggers particular event, when such as user clicks certain button, just can occur.

Such as, be below the Dynative script example used in business: the function that it realizes is exactly by judging whether the value imported in parameter is true, changes the show or hide of certain view elements.Its integrated use basic function such as condition judgment, assignment operation.In conjunction with this part of example, continue introduction below again and how to resolve, perform this section of script.

Be made up of the definition of a series of function object in each section of Dynative script, this series of functions is often in nest relation (especially with under this structured data format of JSON).Just such as above in filterWapFinalPrice this section of script, main body is a condition judgment statement, judges that statement itself have invoked one section of eq function, and according to judged result, in then, else branch, have invoked setdata function respectively again.

When such one section of script imports Dynative resolver into, resolver also can be resolved from level to level.When resolving each time, first resolver extracts type field, if the value in type field is registered, namely be defined in the protocol, so according to the corresponding relation preserved in table 7 or table 8, example dissolves the function object mapped with it again, and parses the content in other fields.If the value finding type is not register in agreement, so this section of script will be abandoned.In time resolving what a function object, it can also be put in a public function object pool by resolver, identifies it with its id, facilitates that other of other Dynative frameworks are local uses these function objects.This id is exactly filterWapFinalPrice in the examples described above, only has the id of ground floor function to be significant, because they are an entirety, the function quoted separately in then or else is nonsensical.

As mentioned before, the execution of script is generally triggered by event, event refer to define in Dynative framework, specific time occurrence.Time view elements in the such as page is initialized, when view elements binding data, or time user clicks button etc.Above-mentioned this section of filterWapFinalPrice script is by calling $ function.filterWapFinalPrice to trigger after view elements binding data, and Dynative framework can find according to id the function object that this section of script is corresponding.No matter be but any event, the flow process triggering script execution is the same, in event, first define the function needing to call, and invoked function is specified by the above-mentioned id mentioned; Then the parameter required for function is defined.Dynative framework, before triggering is called, first can set parameter, and the variable that these parameters finally can be started by $ args in script goes to quote.And then Dynative framework searches function by id, if function exists, function so will be allowed to trigger and perform, the flow process of execution then can be carried out according to the flow process that protocol conventions is good.

Above the Dynative framework that the embodiment of the present application provides being described in detail, in order to better embody its advantage relative to Hybird framework, being introduced below by the example in a practical application.

In order to realize certain function, under Hybird framework, need preparation two to overlap code, wherein a set of is HTML code, and as shown in Figure 4, another set of is Java code, as shown in Figure 5.Operationally, cooperatively interacting of two cover codes is needed.Such as, 5th row of Fig. 4 and the 10th row, define two functions with html language, be respectively javacalljs () and javacalljswithargs (arg), if this two functions will be loaded, then need to have been come by Java code, see the 38th row in Fig. 5 and the 40th row, in Java code, need the loadUrl method calling webview to load this two functions, and the 38th row before this, also needs java code to be registered in Webview.Visible, for Hybird framework, as shown in Figure 6, the code using HTML to write, needs the execution of the native layer completion code that could be arrived by the transfer of JavaScript, Webview to its framework.

And in order to realize identical function, utilize the scheme that the embodiment of the present application provides, then only need to prepare a set of code (such as, the data of JSON form), as shown in Figure 7, wherein do not exist and register in Webview, and call the processes such as method in Webview, operationally, Dynative kernel just can identify the assembly wherein defined, and the primary assembly be mapped as in mobile terminal, afterwards by calling primary code, just can representing interface be realized.Visible, for Dynative framework, its Organization Chart as shown in Figure 8, the interface data using JSON etc. to write is kept at server end, client reads interface data from server end, and afterwards, Dynativecore just directly can be mapped as the primary assembly of Native layer, primary api function etc., and then just can run in the terminal, and show on screen.

In a word, pass through the embodiment of the present application, be no longer dependent on Webkit kernel and the Webview of browser, use the interface data that the data layouts such as JSON are write, can as the native applications in mobile terminal in be performed, therefore, for the various New function etc. used in mobile terminal, all there is good adaptability.

Finally it should be noted that, the application described in the embodiment of the present application can be the App in mobile terminal device, and accordingly, so-called present terminal equipment can be mobile terminal device.

Embodiment two

Previous embodiment one introduces from the angle of client the technical scheme that the embodiment of the present application provides, and for server end, is mainly used in the interface data preserving application, and returns to client when receiving and showing request.This embodiment two is mainly introduced from the technical scheme of angle to the application of server end.

See Fig. 9, this embodiment two provides a kind of application interface and plays up methods of exhibiting, and preserve the interface data of described application at the server end of application, the method specifically can comprise the following steps:

S901: the request receiving the displaying appointment interface that client sends;

S902: the interface data returning to described appointment interface to described client, so that after in the SDK bag be provided with in described client, the render engine that comprises receives the interface data that server returns, described interface data is resolved, obtain the module information defined in described interface data, according to the first corresponding relation preserved in advance, the module information defined in described interface data is mapped as the primary assembly in present terminal equipment, and described primary assembly is played up, for the described appointment interface of displaying; Wherein, described first corresponding relation is the corresponding relation between primary assembly in the module information and present terminal equipment defined in interface data.

This embodiment two is compared with previous embodiment one, and be only different in description angle, the concrete details that realizes see the introduction in embodiment one, can repeat no more here.

Corresponding with the application interface rendering intent that the embodiment of the present application one provides, the embodiment of the present application additionally provides a kind of rendering device, wherein, SDK bag is provided with in the client of application, described SDK comprises described rendering device, preserve the first corresponding relation between the primary assembly in the module information defined in interface data and present terminal equipment in described render engine, see Figure 10, described rendering device comprises:

Request of data unit 1001, for when receiving the request at the appointment interface showing described application, to the interface data at the described appointment interface of this application of server request;

Data Analysis unit 1002, after receiving interface data that server returns, resolves described interface data, obtains the module information defined in described interface data;

Assembly map unit 1003, for according to described first corresponding relation, is mapped as the primary assembly in present terminal equipment by the module information defined in described interface data;

Rendering unit 1004, for playing up described primary assembly, for the described appointment interface of displaying.

Wherein, described interface data comprises the type name information of each assembly, described Data Analysis unit 1002 specifically for:

By resolving described interface data, from described interface data, extracting the type name information of each assembly, according to name type information, the module information defined in described interface data being converted into logic module;

Accordingly, described assembly map unit 1003 specifically may be used for

According to described first corresponding relation, described logic module is mapped as the primary assembly in present terminal equipment.

Now, rendering unit 1004 specifically can comprise:

Logic tree generates subelement, for the nest relation formation logic tree in described interface data according to described logic module and each logic module, described logic tree comprises multiple first node, the corresponding described logic module of each first node, it is the layout information of corresponding component definition and data content information that the information of each first node comprises in described interface data;

Physics tree generates subelement, and for traveling through each node in logic tree, the primary assembly corresponding according to each logic module, is converted to physics tree by described logic tree; Described physics tree comprises multiple Section Point, the corresponding described primary assembly of each Section Point, and the information of each Section Point is included in layout information when screen shows and data content information;

Draw subelement, be plotted to screen for each Section Point set by physics.

Wherein, described interface data comprises the topology data of each assembly and the content-data of each assembly, the assembly id that same assembly is corresponding identical; Described logic tree generates subelement and can comprise:

Node determination subelement, for resolving described topology data, determines each node in logic tree, and the layout information of assembly corresponding to each node, assembly id and internodal set membership information;

Data binding subelement, for the assembly id corresponding according to each node, and the content-data defined for each assembly id in interface data obtains the content-data of each assembly, and is tied on corresponding node, and formation logic is set.

If the content-data for certain component definition in interface data is static content data, then described data binding subelement specifically may be used for:

The assembly id corresponding according to each node, extracts the content-data of this assembly from described content-data.

In addition, the second corresponding relation between the primary api function in the fundamental element defined in dynamic script and mobile terminal can also be preserved in described rendering device, each fundamental element comprises at least one type value, now, if the content-data for certain component definition in interface data is dynamic data, described data binding subelement specifically can comprise:

Script obtains subelement, for according to the script function id comprised in each logic node, obtains the dynamic script that this assembly is corresponding from described content-data;

Fundamental element type value obtains subelement, for extracting the type value of each fundamental element from described dynamic script;

Function Mapping subelement, for the type value according to each extracted fundamental element, and described second corresponding relation, described script function is mapped as the primary api function in current mobile terminal;

Function call subelement, for obtaining the content-data of this assembly by calling described primary api function.

Wherein, described fundamental element comprises the element for expressing computing/logical relation, or function, or statement.

During specific implementation, described assembly can comprise atom component and composite component, now, can in advance for using atom component to set the first keyword, for using composite component to set the second key word, described Data Analysis unit 1002 specifically can comprise:

Atom component acquisition of information subelement, for by the first key word, obtains the module information of atom component;

Composite component acquisition of information subelement, for by the second keyword, determine that corresponding assembly is composite component, and according to the composite component title that described second keyword is quoted, in composite component information, search the atom component that this composite component comprises, and obtain the module information of this atom component.

Under preferred implementation, described SDK bag uses the code speech that in current mobile terminal equipment platform, native applications uses to develop.

Corresponding with the application interface rendering intent that the embodiment of the present application two provides, the embodiment of the present application additionally provides a kind of application interface rendering device, and see Figure 11, this device specifically can comprise:

Request reception unit 1101, the request at interface is specified in the displaying sent for receiving client;

Data return unit 1102, for returning the interface data at described appointment interface to described client, so that after in the SDK bag be provided with in described client, the render engine that comprises receives the interface data that server returns, described interface data is resolved, obtain the module information defined in described interface data, according to the first corresponding relation preserved in advance, the module information defined in described interface data is mapped as the primary assembly in present terminal equipment, and described primary assembly is played up, for the described appointment interface of displaying; Wherein, described first corresponding relation is the corresponding relation between the primary assembly in the module information and present terminal equipment defined in interface data, and wherein, the interface data of application is kept at the server end of application.

In a word, pass through the embodiment of the present application, the assembly defined in interface data can be mapped directly to the primary assembly in mobile terminal due to Dynative, therefore, the primary code that can directly call in mobile terminal device is played up interface, and be no longer dependent on Webkit kernel and the Webview of browser, that is, use the interface data that the data layouts such as JSON are write, can as the native applications in mobile terminal in be performed, therefore, for the various New function etc. used in mobile terminal, all there is good adaptability.

As seen through the above description of the embodiments, those skilled in the art can be well understood to the mode that the application can add required common hardware by software and realizes.Based on such understanding, the technical scheme of the application can embody with the form of software product the part that prior art contributes in essence in other words, this computer software product can be stored in storage medium, as ROM/RAM, magnetic disc, CD etc., comprising some instructions in order to make a computer equipment (can be personal computer, server, or the network equipment etc.) perform the method described in some part of each embodiment of the application or embodiment.

Each embodiment in this instructions all adopts the mode of going forward one by one to describe, between each embodiment identical similar part mutually see, what each embodiment stressed is the difference with other embodiments.Especially, for system or system embodiment, because it is substantially similar to embodiment of the method, so describe fairly simple, relevant part illustrates see the part of embodiment of the method.System described above and system embodiment are only schematic, the wherein said unit illustrated as separating component or can may not be and physically separates, parts as unit display can be or may not be physical location, namely can be positioned at a place, or also can be distributed in multiple network element.Some or all of module wherein can be selected according to the actual needs to realize the object of the present embodiment scheme.Those of ordinary skill in the art, when not paying creative work, are namely appreciated that and implement.

The application interface rendering intent above the application provided and device, be described in detail, apply specific case herein to set forth the principle of the application and embodiment, the explanation of above embodiment is just for helping method and the core concept thereof of understanding the application; Meanwhile, for one of ordinary skill in the art, according to the thought of the application, all will change in specific embodiments and applications.In sum, this description should not be construed as the restriction to the application.

Claims

1. an application interface rendering intent, it is characterized in that, SDK bag is provided with in the client of application, described SDK comprises a render engine, the first corresponding relation between the primary assembly in the module information defined in interface data and present terminal equipment is preserved in described render engine, described method comprises, and completes following operation by described render engine:

2. method according to claim 1, is characterized in that, described interface data comprises the type name information of each assembly, and the module information defined in the described interface data of described acquisition, comprising:

Described according to described first corresponding relation, the module information defined in described interface data is mapped as the primary assembly in present terminal equipment, comprises:

3. method according to claim 2, is characterized in that, describedly plays up described primary assembly, comprising:

The nest relation formation logic tree in described interface data according to described logic module and each logic module, described logic tree comprises multiple first node, the corresponding described logic module of each first node, it is the layout information of corresponding component definition and data content information that the information of each first node comprises in described interface data;

Each node in traversal logic tree, the primary assembly corresponding according to each logic module, is converted to physics tree by described logic tree; Described physics tree comprises multiple Section Point, the corresponding described primary assembly of each Section Point, and the information of each Section Point is included in layout information when screen shows and data content information;

Each Section Point set by physics is plotted on screen.

4. method according to claim 3, is characterized in that, described interface data comprises the topology data of each assembly and the content-data of each assembly, the assembly id that same assembly is corresponding identical; Described according to described logic module and each logic module nest relation formation logic tree in described interface data, comprising:

Described topology data is resolved, determines each first node in logic tree, and the set membership information between the layout information of assembly corresponding to each first node, assembly id and first node;

The assembly id corresponding according to each first node, and the content-data defined for each assembly id in interface data obtains the content-data of each assembly, and be tied on corresponding node, formation logic is set.

5. method according to claim 4, it is characterized in that, if the content-data for certain component definition in interface data is static content data, the then described assembly id corresponding according to each first node, and the content-data defined for each assembly id in interface data obtains the content-data of each assembly, comprising:

The assembly id corresponding according to each first node, extracts the content-data of this assembly from described content-data.

6. method according to claim 4, it is characterized in that, described interface data comprises and utilizes preset script function to be the dynamic content data of certain component definition, described preset script function is expressed by least one fundamental element, each fundamental element comprises at least one type value, also preserves the second corresponding relation between the primary api function in the type value of the fundamental element defined in script function and mobile terminal in described render engine; The described assembly id corresponding according to each first node, and the content-data defined for each assembly id in interface data obtains the content-data of each assembly, comprising:

The assembly id corresponding according to each first node, obtains the dynamic script that this assembly is corresponding from described content-data;

The type value of each fundamental element is extracted from described dynamic script;

According to the type value of each extracted fundamental element, and described second corresponding relation, described script function is mapped as the primary api function in current mobile terminal;

Described primary api function being defined as the content-data of this assembly, when being triggered with the execution event of the described dynamic script of box lunch, carrying out the displaying at interface by calling described primary api function.

7. method according to claim 6, is characterized in that, described fundamental element comprises the element for expressing computing/logical relation, or function, or statement.

8. the method according to any one of claim 1 to 7, it is characterized in that, described assembly comprises atom component and composite component, in advance for using atom component to set the first keyword, the second key word is set for using composite component, the module information defined in the described interface data of described acquisition, comprising:

By the first key word, obtain the module information of atom component;

By the second keyword, determine that corresponding assembly is composite component, and according to the composite component title that described second keyword is quoted, in composite component information, search the atom component that this composite component comprises, and obtain the module information of this atom component.

9. the method according to any one of claim 1 to 7, is characterized in that, described SDK bag uses the code speech that in current mobile terminal equipment platform, native applications uses to develop.

10. the method according to any one of claim 1 to 7, is characterized in that, described in be applied as App in mobile terminal device, described present terminal equipment is mobile terminal device.

11. 1 kinds of application interface rendering intents, is characterized in that, comprising:

Receive the request at the displaying appointment interface that client sends;

12. 1 kinds of application interface rendering devices, it is characterized in that, SDK bag is provided with in described device, described SDK comprises described render engine, preserve the first corresponding relation between the primary assembly in the module information defined in interface data and present terminal equipment in described render engine, described render engine comprises:

13. devices according to claim 12, is characterized in that, described interface data comprises the type name information of each assembly, described Data Analysis unit specifically for:

Described assembly map unit specifically for

14. devices according to claim 13, is characterized in that, described rendering unit comprises:

Draw subelement, be plotted to screen for each Section Point set by physics.

15. devices according to claim 14, is characterized in that, described interface data comprises the topology data of each assembly and the content-data of each assembly, the assembly id that same assembly is corresponding identical; Described logic tree generates subelement and comprises:

16. devices according to claim 15, is characterized in that, if for the content-data of certain component definition is static content data in interface data, then described data binding subelement specifically for:

17. devices according to claim 15, it is characterized in that, described interface data comprises and utilizes preset script function to be the dynamic content data of certain component definition, described preset script function is expressed by least one fundamental element, each fundamental element comprises at least one type value, also preserves the second corresponding relation between the primary api function in the type value of the fundamental element defined in script function and mobile terminal in described render engine; Described data binding subelement specifically comprises:

18. devices according to claim 17, is characterized in that, described fundamental element comprises the element for expressing computing/logical relation, or function, or statement.

19. according to claim 12 to the device described in 18 any one, it is characterized in that, described assembly comprises atom component and composite component, in advance for using atom component to set the first keyword, for using composite component to set the second key word, described Data Analysis unit specifically comprises:

20., according to claim 12 to the device described in 18 any one, is characterized in that, described SDK bag uses the code speech that in current mobile terminal equipment platform, native applications uses to develop.

21., according to claim 12 to the device described in 18 any one, is characterized in that, described in be applied as App in mobile terminal device, described present terminal equipment is mobile terminal device.

22. 1 kinds of application interface rendering devices, is characterized in that, comprising: