Menu
▾
▴
#758 special editors needed for magic strings in Autoplot
The Autoplot URI is successful in Autoplot because it provides a compact way for the machine to contain a configuration, but there are also GUIs to create and modify them. There are other magic strings that need editors for the same reason. These function well to contain a state, but when no one knows how to create them, they are not used.
This ticket is to enumerate them and to see that editors are created for the strings. The editor panels which contain them will need to be modified to allow the custom editors to be integrated. There are a few which are already done as examples.
| name | example | locations |
|---|---|---|
| versions in URI templates | $(v,sep,ge=2) | a field which is to be interpretted as a version with ordering |
| URI templates | /tmp/$Y$m$d.dat | file resources, aggregations, but also time formats |
| row,column position | +4em,100%-2em | layout specification relative to parent, also colorbar position |
| font size | 1em+2px | relative or absolute font size, like row column spec but relative to parent font size. |
| render control | fillStyle=outline&backgroundThick=1em | control strings for each renderer |
| granny strings | E=mc!A2!n Τ → Ρ |
strings with format and color control, unicode characters, entities |
| tickValues | +10/4 10,100/3,4,5,6,7,8,9,20,30,40,50,60 |
explicit tick locations |
| macros | Data %{USER_PROPERTIES.version} | grabbing text from metadata |
| operations process strings | |fftPower(512,2,'Hanning') | specifying additional operations to perform to the data |
| jython control parameters | script:/tmp/my.jy?arg1=x&arg2=z | input parameters for Jython scripts |
| time range strings | 2020-10-22 08:00 to 09:00 orbit:rbspa-pp:4005 |
time range strings |
| autoRangeHints | includeZero=T widths=30nT,300nT,3000nT |
autoranging controls |
And this table will track progress.
Last edit: Jeremy Faden 2021-11-11
Many GUIs for these strings have examples in the popups or recent history, to inexpensively satisfy the need for documentation.
All these editors should be a JPanel which can be embedded, have a setValue and getValue method.
I've started adding these editors. These are attached the the PropertyEditor GUI by property name, which might end up being a bad idea.
See Das2 ticket https://github.com/das-developers/das2java/issues/5
See Das2 ticket https://github.com/das-developers/das2java/issues/4