Component Solution Services REC02F Manual de usuario Pagina 8

  • Descarga
  • Añadir a mis manuales
  • Imprimir
  • Pagina
    / 78
  • Tabla de contenidos
  • MARCADORES
  • Valorado. / 5. Basado en revisión del cliente
Vista de pagina 7
Basic Concepts Brio 2002
Copyright © 2002, Brio Software Page 6
Flattening the Chart
Sometimes you can influence the data’s interpretation by the way in which it is
presented visually to the user. A basic charting concept to leverage is to realize
the visual difference between a 2-D and 3-D graphical presentation. While 3-D
mode is the default for Brio charts, certain analysis tasks can be performed by
first creating a 3-D chart, then flattening the chart to 2-D to create a layering
effect.
The human mind will interpret the flattened result in a far different manner. You
can create inferences about the data in 2-D that aren’t easily seen (if at all) in 3-D.
Last year’s tips cookbook showed how you can use this difference to create
spotlighting in charts and to show portions of the whole in multiple categories at
once.
Embedding Requirements
Charts and pivots intended for embedding should be designed differently than
items intended for direct manipulation. The unique requirements of each type of
embedding need to be accounted for in your design.
Embedding in an EIS section
Items to be embedded in an EIS section need to use short descriptions to provide
meaningful information in a smaller display. Charts should not use auto-sizing,
since your EIS item’s size should control the scaling of the chart elements. Users
will not be able to change the size of items drilled to in embedded live pivots, so
label length is of key importance in these pivots. You may want to use a
combination of computed items in your data model along with pre-defined drill
paths to keep the display readable.
Embedding in a Report section
Items used for SmartReport embedding in a Report section will probably be
designed with exactly the opposite characteristics in mind. Realize that a chart or
pivot embedded into a Report will become context-sensitive. It will only display
the information that pertains to the report grouping within which the item is
embedded. Thus, you will want to create a “global” pivot or chart with many
more elements than you would display in a directly displayed item. Don’t worry
about what the raw chart or pivot looks like. Design for what it will narrow
down to when embedded in your report.
Scripting Requirements
Do you plan to use an EIS section to control what gets displayed? If so, you may
need to design things a bit differently to support your scripting requirements.
For example, it is easy in a chart or pivot to display only the top 5 items. But if
you want the user to select how many items will display, you may want to
provide a simple EIS screen to automate the process. To pull this off, you will
need to create a Table section and build your chart or pivot off that Table section.
Vista de pagina 7
1 2 3 4 5 6 7 8 9 10 11 12 13 ... 77 78

Comentarios a estos manuales

Sin comentarios