plugin_event issueshttps://gitlab.in2p3.fr/tev/plugin_event/-/issues2018-05-18T05:04:30+02:00https://gitlab.in2p3.fr/tev/plugin_event/-/issues/1Rename database fields2018-05-18T05:04:30+02:00LE GAC RenaudRename database fields* In order to keep consistency with the others data table and to avoid ambiguities, rename the database fields in the following ways:
```
objects.reference --> objects.object
objects.serial_number --> objects.reference
obj...* In order to keep consistency with the others data table and to avoid ambiguities, rename the database fields in the following ways:
```
objects.reference --> objects.object
objects.serial_number --> objects.reference
objects.batch_number (decide to keep it or not)
events.data --> events.model (to avoid confusion with history.data)
```https://gitlab.in2p3.fr/tev/plugin_event/-/issues/25Add a the table blobs or materials2018-05-18T05:04:30+02:00LE GAC RenaudAdd a the table blobs or materials* link a series of file or URL to an event.
* The `blobs` table has four fields: `id`, `id_events`, `file name` or `path` and `blob`.
* No foreign key in the table `history`.
* Require to develop callback on record insert, delete or...* link a series of file or URL to an event.
* The `blobs` table has four fields: `id`, `id_events`, `file name` or `path` and `blob`.
* No foreign key in the table `history`.
* Require to develop callback on record insert, delete or update.
* Add the entry `Add material` in the `HistoryContextMenu`.
* Tune the component `RowHistoryData` to display a list of hyperlink to download file, follow URL, *etc*.
* It might be usefull to have a dedicated node which allows to see the material for event and to filter them.
* ...https://gitlab.in2p3.fr/tev/plugin_event/-/issues/27Add link in list to edit event2018-05-18T05:04:30+02:00LE GAC RenaudAdd link in list to edit event* In a list the column `id` should be a link
* Clicking on the link open a form allowing to edit the event
* This technique is used in limbra* In a list the column `id` should be a link
* Clicking on the link open a form allowing to edit the event
* This technique is used in limbrahttps://gitlab.in2p3.fr/tev/plugin_event/-/issues/28New interface to create list2018-05-18T05:04:30+02:00LE GAC RenaudNew interface to create listCreate a list is still complicated. To ease this process create a new interface.
* When a source is displayed, customized it like a spreadsheet and save it:
- Hide/show column via the grid interface
- Tune the size of the colu...Create a list is still complicated. To ease this process create a new interface.
* When a source is displayed, customized it like a spreadsheet and save it:
- Hide/show column via the grid interface
- Tune the size of the column via the grid interface
- Entry in a context menu to Add / delete columns
- Entry in a context menu to Add a `computed column`
- Entry in a context menu to define `sorter`
- Entry in a context menu to define the `query`
- Entry in a context menu to define `protection`
- Entry in a context menu to `Save as...`
* When a list is displayed is it also possible to customize, duplicate or save it:
- On top of the previous case, add an entry in the context menu `Save..`
* Remove the viewport node `Configure lists`
* Rename the viewport node `Lists` → `My lists`https://gitlab.in2p3.fr/tev/plugin_event/-/issues/29Bug in UserDataMultiDefault2018-05-18T05:04:30+02:00LE GAC RenaudBug in UserDataMultiDefault* `plugin_dbui 0.9.8.2`
* The following sequence is not working:
- Open the `History` table
- Create a new event `Budget xFR` (OK)
- Open and existing event `Budget xFR` (OK)
- Create a new event `Budget xFR` -- faile...* `plugin_dbui 0.9.8.2`
* The following sequence is not working:
- Open the `History` table
- Create a new event `Budget xFR` (OK)
- Open and existing event `Budget xFR` (OK)
- Create a new event `Budget xFR` -- failed since the data block is empty
* The issue is located in the widget `UserDataMultiDefault`https://gitlab.in2p3.fr/tev/plugin_event/-/issues/30Bugs...2018-05-18T05:04:29+02:00LE GAC RenaudBugs...Series of bugs appears during the preparation of the EAP in September 2017. They are related to the *user data block* in the form as well as in the grid.
In the form
* Update an entry in the history grid (for an vent with a non-empty da...Series of bugs appears during the preparation of the EAP in September 2017. They are related to the *user data block* in the form as well as in the grid.
In the form
* Update an entry in the history grid (for an vent with a non-empty data block)
* Move to the tab *event*. In most of the case the data block is empty
* Close the form an reopen it, then the data block is OK
In the grid
* Select an event
* Expand several data blocks
* It is working fine but after several iteration the data block is not displayed properly and the form is corrupted
* The only possibility is to restart the application
Other instabilities appears when filtering the history tables and playing with list, ....