Instead of a form, now links are used that immeadiately apply a selected
filter. To construct the link, the type's renderTagCloudLink() method is
reused.
Still to do:
* make it possible to apply multiple filters (this might need some
adjustments on the renderTagCloudLink() method signature)
* do ensure that one selected filter does not collapse all filter
possibilities. Cloud currently does this by implementing it's own
SearchConfig in SearchCloud, but that seems to be limited to handling
a single schema and field. I think it would make more sense to be able
enable/disable the dynamic filter handling for the standard
SearchConfig
* Improve styling. This is currently just a very quick rendering on top
of <details>
This allows users to set custom CSS classes on aggregations potentially
restyling them differently for different use cases.
This makes startScope and finishScope part of the public API of the
Aggregation class. It should no longer be called within render() but is
instead called outside.
This might potentially break plugins implementing their own
aggregations. Needs to be checked
This restyles the input entry form to make data entry more comfortable,
by enlarging most of the input fields. It also uses more modern CSS to
achieve the same layout as before.
This has only been tested with the dokuwiki template. Adjustements may
be neeed for other templates.
To avoid confusion with the Lookup type, the three different ways of
accessing a schema have now the following names:
* page data - for revisioned struct data attached to a page
* serial data - for an unrevisioned list of struct data attached to a
page
* global data - for an unrevisioned list of struct data not attached to
any page (formaly known as lookup schema)
The editor mechanism used for serial and global data is now called
AggregationEditor
Some reference to lookup schemas is still in the bureaucracy support
part.
The restructuring of the entry label↔input html in #304 has caused the
css for struct fields in bureaucracy forms to break. This commit should fix
this and hence fix#307.
Since `div.field` are now the only elements inside the fieldsets (beside
the legend), we can just hide them explicitly.
This bug occurred, because the star had a lower specifity than the more
explicitly defined display-states for div.field and its descendants.
Quix-80
Multiple inputs within a single label in invalid HTML. This bug can not
only occur in multi-fields but also in plugin-provided single fields
which may contain multiple input-fields which are then only combined by
javascript.
Thus, we provide an id which every type can assign to the edit-field
best suited. For multi-types this is usually the new-input-template.
Fixes#292
Implement the list aggregation known from the dokuwiki data plugin. This
feature is useful when an entire table would be to much boilerplate.
Usually one would select only a few columns.
Enable the option sepbyheader to behave analogous to the data plugin.
Report any options that are not valid for a list aggregation as error.
Show that error during the render phase of a page. That way the error is visible
always when the page is rendered, not only after the initial save when it is
parsed.
See #90 and see SPR-710
`$this->data['cols']` holds the number of cols defined in the syntax,
which may be different from the displayed cols because the `*` might be
used which counts only as 1 in data['cols'] or there might be columns
defined in the syntax which are not part of the schemas and are hence not
displayed.
Fixes#217 and fixes SPR-711
This is not terribly useful on it's own, but will be used by other
plugins defining their own types and making use of this.
The default color will never be saved.
This type makes use of <input type="color"> which is not supported in
some older browsers (a simple text input will be displayed by those).
* master:
output the key not value for unknown option in ConfigParser
media fields need unique IDs. fixes#152
fixed references to old Integer type
removed Integer type
Version upped
fixed problem with multicolumns and made the param name clearer
added missing schema file
when Page uses titles, sorting should use title #146
Decimal type needs to type cast for order and compare #146
make sure pages are assigned in tests
give types a way to influence sorting
add slight shadow for aggregation images
Fixed multi fields for inline editor
test wildcard adding in Search
