Академический Документы
Профессиональный Документы
Культура Документы
Contents:
Introduction to UI elements
Putting data on the screen: Context binding
Controlling the behaviour of UI elements using context
binding
Using a basic composite UI element
Group UI Element
TextView UI Element
Label UI Element
InputField UI Element
SAP AG 2005, Title of Presentation / Speaker Name / ‹#›
How are UI elements arranged?
BusinessGraphics,
GeoMap
e.g. DateNavigator,
Table, Tree
BI Application Frame
OfficeControl
e.g.
TransparentContainer, MessageArea
Tray
1. Choose Change
from the context
menu of a view
1. Choose Change
from the context
menu of a view
Context
Root Node
Application Coding
Implementation
UI Layout
Standard Context
Hook
Root Node
Methods
Instance
Methods
Actions
Navigation
Plugs
Implementation
UI Layout
Standard Context
Hook
Root Node
Methods
Instance
Updates
Methods
Actions
Navigation
Plugs
1) Declare context
attribute
SAP AG 2005, Title of Presentation / Speaker Name / ‹#›
Putting data on the screen (2)
2) Create UI element
on layout 1) Declare context
attribute
SAP AG 2005, Title of Presentation / Speaker Name / ‹#›
Putting data on the screen (3)
3) Bind UI element
to context attribute
2) Create UI element
on layout 1) Declare context
attribute
SAP AG 2005, Title of Presentation / Speaker Name / ‹#›
Putting data on the screen (4)
3) Bind UI element
to context attribute
2) Create UI element
on layout 1) Declare context
attribute
SAP AG 2005, Title of Presentation / Speaker Name / ‹#›
Putting data on the screen (5)
The order of attributes within a node has no influence on the order in which
the data they hold is displayed.
2.The corresponding
input field will
always be open for
input.
UI element appearance
Available Properties
Possible UI Events
Rendered tree
UI element
hierarchical representation of
a Table UI element
hierarchical representation of
a Table UI element
SAP AG 2005, Title of Presentation / Speaker Name / ‹#›
Binding a Table UI element to the context
BOOKID
CUSTOMID
CLASS
PASSNAME
CARRID
View layout
CONNID
The Table UI element must have its
FLDATE
dataSource property bound to a context
PRICE node of cardinality 0..n or 1..n
BOOKID
Each context attribute is a
CUSTOMID potential candidate for
becoming a TableColumn.
CLASS
PASSNAME
CARRID
CONNID
PRICE
CLASS
PASSNAME
FLDATE
View layout
PRICE
row
Context Root
FLIGHTS (c=0..n) FLIGHTS
BOOKINGS (c=0..n) CARRID ..n
BOOKID CARRID
CONNID
2
CARRID
CONNID 1
CUSTOMID
CONNID
CLASS
FLDATE
PASSNAME
CARRID
Runtime data View layout
CONNID
BOOKID
CUSTOMID
CLASS
PASSNAME