TEMPLATE-BASED DEPLOYMENT OF USER INTERFACE OBJECTS
A system may include reception of a model describing a plurality of user interface elements, modification of a markup language template based on the model, and deployment of the modified template to a runtime environment. Further aspects may include reception of a second model describing a second plurality of user interface elements, transformation of the second model to a metadata model in accordance with a common metadata framework, transformation of the metadata model to a generic runtime model, and transformation of the generic runtime model to a runtime model associated with a runtime environment.
1 . A method comprising:
receiving a model describing a plurality of user interface elements;
modifying a markup language template based on the model; and
deploying the modified template to a runtime environment.
2 . A method according to claim 1 , further comprising:
receiving a second model describing a second plurality of user interface elements;
transforming the second model to a metadata model in accordance with a common metadata framework;
transforming the metadata model to a generic runtime model; and
transforming the generic runtime model to a runtime model associated with a runtime environment.
3 . A method according to claim 1 , wherein modification of the markup language template based on the model comprises:
replacing placeholder fields of the markup language template with data associated with each of the plurality of components.
4 . A method according to claim 1 , wherein the model comprises an eXecutable graphical user interface language (XGL) model.
5 . A method according to claim 1 , wherein the template conforms to the Web Dynpro specification.
6 . A medium storing processor-executable program code, the program code comprising:
code to receive a model describing a plurality of user interface elements;
code to modify a markup language template based on the model; and
code to deploy the modified template to a runtime environment.
7 . A medium according to claim 6 , the program code further comprising:
code to receive a second model describing a second plurality of user interface elements;
code to transform the second model to a metadata model in accordance with a common metadata framework;
code to transform the metadata model to a generic runtime model; and
code to transform the generic runtime model to a runtime model associated with a runtime environment.
8 . A medium according to claim 6 , wherein the code to modify the markup language template based on the model comprises:
code to replace placeholder fields of the markup language template with data associated with each of the plurality of components.
9 . A medium according to claim 6 , wherein the model comprises an executable graphical user interface language (XGL) model.
10 . A medium according to claim 6 , wherein the template conforms to the Web Dynpro specification.
11 . An apparatus comprising:
a deployment module to:
receive a model describing a plurality of user interface elements;
modify a markup language template based on the model; and
deploy the modified template to a runtime environment.
12 . An apparatus according to claim 11 , the deployment module further to:
receive a second model describing a second plurality of user interface elements;
transform the second model to a metadata model in accordance with a common metadata framework;
transform the metadata model to a generic runtime model; and
transform the generic runtime model to a runtime model associated with a runtime environment.
13 . An apparatus according to claim 11 , wherein modification of the markup language template based on the model comprises:
replacing placeholder fields of the markup language template with data associated with each of the plurality of components.
14 . An apparatus according to claim 11 , wherein the model comprises an eXecutable graphical user interface language (XGL) model.
15 . An apparatus according to claim 11 , wherein the template conforms to the Web Dynpro specification.