Changes between Version 3 and Version 4 of S3/S3Summary


Ignore:
Timestamp:
07/31/14 12:57:44 (7 years ago)
Author:
Dominic König
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • S3/S3Summary

    v3 v4  
    22[[TOC]]
    33
     4A summary page is a single-resource, multi-record view with multiple embedded data presentations ("widgets", e.g. tables, maps, charts) and a common filter form.
     5
     6The general structure of a summary page is:
     7
    48[[Image(summary_structure.png)]]
     9
     10== Sections ==
     11
     12The summary page can be broken up into '''sections''' (optional), each of which containing one or more widgets.
     13
     14Sections are rendered with a tab-style navigation, only one section visible at a time. An additional "common" section is always visible.
     15
     16Number, type and contents of the sections are freely configurable.
     17
     18== Widgets ==
     19
     20'''Widgets''' are presentations of the filtered data, e.g. as tables, maps or charts.
     21
     22The summary framework does not render the widgets itself, but invokes the {{{widget()}}} interface of regular REST method handlers (e.g. S3CRUD, S3Map, S3Report) to generate them.
     23
     24The type and order of widgets is freely configurable.
     25
     26== Filtering ==
     27
     28All widgets can be filtered simultaneously with a common '''filter form'''.
     29
     30The summary framework features lazy-refresh, so that only visible widgets are refreshed immediately after a filter change, while the hidden widgets are scheduled for refresh when they become visible. This reduces the load for server and network to what is really necessary.
     31
     32The summary framework does not render or control the filter form itself, but uses the S3Filter framework to generate the form and apply the filters.
    533== Configuration ==
    634