|
|
# Importand Hints for testing on Stage Server
|
|
|
|
|
|
## https://stage.d2sphere.com
|
|
|
|
|
|
|
|
|
### General hint
|
|
|
Using the light theme over the dark theme is highly
|
|
|
recommended at this stage, as all new developments happen first in the
|
|
|
light theme and will be adopted to the dark theme only randomly.
|
|
|
|
|
|
Beside several improvements (e.g. mysterious text shadow on piecharts
|
|
|
was removed, table columns and orders), the most interesting feature
|
|
|
introduced by Okjin are the extended filters.
|
|
|
|
|
|
### The shortest story ever:
|
|
|
Just try it out
|
|
|
|
|
|
### The short story
|
|
|
The extended filters are an extension to the general search box. Both
|
|
|
work in conjunction to each other, so pre filtering by an advanced
|
|
|
filter for e.g. online devices and then use the general searchbox for
|
|
|
additional search criteria is one feature. Extended filters can be
|
|
|
configured in a special filter configuration dialog. Resetting one of
|
|
|
them can be done directly in the filter bar by simply hitting the cross
|
|
|
symbol of the filter tag. An alternative way is the use of the trash
|
|
|
icon on the upper right corner of the configuration dialog. Ressetting
|
|
|
them all in one bunch can be done by the lower reset button in the same
|
|
|
dialog. Sophisticated input options (e.g. min and max values for numbers
|
|
|
or lists of strings for string based filter) are a plus. Currently
|
|
|
active filters are marked by a different caption color in the tab bar
|
|
|
area of the dialog.
|
|
|
|
|
|
### The long story aka outlook:
|
|
|
Several additional filters may be developed, e.g. compound filters for
|
|
|
defining several features of a query in just one settings pane (user
|
|
|
accounts with its several flags are a possible match). Another filter
|
|
|
will simply reduce the maximum number of visible rows in a table (e.g.
|
|
|
first 100 of 1.000.000 results). The filters will be extended to work
|
|
|
together with the backing database to not only filter the values as late
|
|
|
as the are available in the table but queriying them already filtered
|
|
|
from the database (this makes it possible to limit the data transfer
|
|
|
volume from database to frontend and speed up page rendring).
|
|
|
In a next stage it will be possible also to define some of the filters
|
|
|
as "permanent", so that they are active and visible always on a page
|
|
|
(e.g. trips or events). Without this feature the amount of data to be
|
|
|
shown in the table would exceed any healthy limit. Another future option
|
|
|
will be the possibility to define limits from programmer side to the
|
|
|
input fields (e.g. interval between start and end may not exceed 1 day)
|
|
|
to further reduce misuse by defining to large query intervals. |
|
|
\ No newline at end of file |