|Oracle Fusion Middleware Data Visualization Tools Tag Reference for Oracle ADF Faces
11g Release 1 (18.104.22.168.0)
UIComponent class: oracle.adf.view.faces.bi.component.timeline.UITimelineOverview
Component type: oracle.dss.adf.timeline.TimelineOverview
The TimelineOverview component provides a macro view of all the events from all TimelineSeries in the Timeline. Users can scroll through the timeline using the TimelineOverview. The TimelineOverview component must be placed inside of a Timeline component.
The TimelineOverview component can have the following children: <dvt:timeAxis>.
A time axis must be specified on the TimelineOverview component. An application can specify the time axis by adding the
<dvt:timeAxis> tag to timelineOverview. See the documentation for
<dvt:timeAxis> for details.
The items that appear on the TimelineOverview component can be customized with a
<dvt:marker> by using the overviewItem facet on
<dvt:timelineItem>. See the documentation for
<dvt:timelineItem> for details.
Items in the timelineOverview component can be selected if the selection feature is enabled in the timeline component. See the selection feature in
<dvt:timeline> for details.
Apply Request Values
|Event delivered to describe an attribute change. Attribute change events are not delivered for any programmatic change to a property. They are only delivered when a renderer changes a property without the application's specific request. An example of an attribute change events might include the width of a column that supported client-side resizing.|
|attributeChangeListener||javax.el.MethodExpression||Only EL||a method reference to an attribute change listener. Attribute change events are not delivered for any programmatic change to a property. They are only delivered when a renderer changes a property without the application's specific request. An example of an attribute change events might include the width of a column that supported client-side resizing.|
|binding||String||Only EL||an EL reference that will store the component instance on a bean. This can be used to give programmatic access to a component from a backing bean, or to move creation of the component to a backing bean.|
|id||String||Yes||the identifier for the component|
|inlineStyle||String||Yes||the CSS styles to use for this component. This is intended for basic style changes. The inlineStyle is a set of CSS styles that are applied to the root DOM element of the component. Be aware that because of browser CSS precedence rules, CSS rendered on a DOM element takes precedence over external stylesheets like the skin file. Therefore skins will not be able to override what you set on this attribute. If the inlineStyle's CSS properties do not affect the DOM element you want affected, then you will have to create a skin and use the skinning keys which are meant to target particular DOM elements, like ::label or ::icon-style.|
|partialTriggers||String||Yes||the IDs of the components that should trigger a partial update. This component will listen on the trigger components. If one of the trigger components receives an event that will cause it to update in some way, this component will request to be updated too. Identifiers are relative to the source component, and must account for NamingContainers. If your component is already inside of a naming container, you can use a single colon to start the search from the root, or multiple colons to move up through the NamingContainers - "::" will search from the parent naming container, ":::" will search from the grandparent naming container, etc.|
|rendered||boolean||Yes||specifies whether the component is rendered. The default value is true.|
|styleClass||String||Yes||a CSS style class to use for this component. The style class can be defined in your page or in a skinning CSS file, for example, or you can use one of our public style classes, like 'AFInstructionText'.|
|visible||boolean||Yes||the visibility of the component. If it is "false", the component will be hidden on the client. Unlike "rendered", this does not affect the lifecycle on the server - the component may have its bindings executed, etc. - and the visibility of the component can be toggled on and off on the client, or toggled with PPR. When "rendered" is false, the component will not in any way be rendered, and cannot be made visible on the client. The default value is true.|