beat.editor issueshttps://gitlab.idiap.ch/beat/beat.editor/-/issues2018-09-21T19:19:04Zhttps://gitlab.idiap.ch/beat/beat.editor/-/issues/94Add flask (& nose?) tests2018-09-21T19:19:04ZJaden DIEFENBAUGHAdd flask (& nose?) testsVia nose if possible
Also will need to mock a BEAT prefix, use beat.examplesVia nose if possible
Also will need to mock a BEAT prefix, use beat.examplesJS & Python Testinghttps://gitlab.idiap.ch/beat/beat.editor/-/issues/90Separate cloning & versioning functionality in list views2018-05-18T14:29:39ZJaden DIEFENBAUGHSeparate cloning & versioning functionality in list viewsRight now there's only a "clone" button that does double duty.
There should be a "clone" button that requires a new object name and pins the version to "1"
There should be a "new version" button that pins the name and ups the version b...Right now there's only a "clone" button that does double duty.
There should be a "clone" button that requires a new object name and pins the version to "1"
There should be a "new version" button that pins the name and ups the version by onehttps://gitlab.idiap.ch/beat/beat.editor/-/issues/86Update plotterparameter schema & editor2018-04-17T09:23:28ZJaden DIEFENBAUGHUpdate plotterparameter schema & editorflavio's changes in beat/beat.core#49flavio's changes in beat/beat.core#49https://gitlab.idiap.ch/beat/beat.editor/-/issues/85update to new major/minor versions of deps2018-05-30T14:09:09ZJaden DIEFENBAUGHupdate to new major/minor versions of depsThe API might be changing
- d3
- react-popperThe API might be changing
- d3
- react-popperhttps://gitlab.idiap.ch/beat/beat.editor/-/issues/67Fuzzy search box2018-03-16T15:03:16ZJaden DIEFENBAUGHFuzzy search boxSearch through names/descriptionsSearch through names/descriptionshttps://gitlab.idiap.ch/beat/beat.editor/-/issues/66Upgrade to webpack 42018-03-08T15:55:25ZJaden DIEFENBAUGHUpgrade to webpack 4I've put this off long enough, waiting for everything to stabilize. There's apparently huge build performance gains as well as better default settings for the complicated stuff, so I should do this soonish.I've put this off long enough, waiting for everything to stabilize. There's apparently huge build performance gains as well as better default settings for the complicated stuff, so I should do this soonish.https://gitlab.idiap.ch/beat/beat.editor/-/issues/63Safely create/cast objects using the respective editor's `getValidObject` func2018-03-09T15:40:14ZJaden DIEFENBAUGHSafely create/cast objects using the respective editor's `getValidObject` funcInspired by all the work I have to do to handle malformed objects.
Instead of trusting the objects, use the editor getObject funcs to cast objs in `selectors.jsx`.Inspired by all the work I have to do to handle malformed objects.
Instead of trusting the objects, use the editor getObject funcs to cast objs in `selectors.jsx`.https://gitlab.idiap.ch/beat/beat.editor/-/issues/57"potentially unsaved changes" remark2018-03-20T15:27:38ZJaden DIEFENBAUGH"potentially unsaved changes" remarkActually checking if the server element is different than the local element is too expensive. Just have a flag "potential_changes_made" that turns on when the user edits something, and turns off when they save/write to serverActually checking if the server element is different than the local element is too expensive. Just have a flag "potential_changes_made" that turns on when the user edits something, and turns off when they save/write to serverhttps://gitlab.idiap.ch/beat/beat.editor/-/issues/51Assigning a protocol for an experiment's datasets doesn't always assign the d...2018-03-13T13:21:59ZJaden DIEFENBAUGHAssigning a protocol for an experiment's datasets doesn't always assign the datasets properlyThis is an issue with the `user/user/fisherface/1/atnt` experiment. After pulling it from a local BEAT instance, it using the `atnt/3` database. Because the current version of `beat.cmdline` only supports `atnt/5`, I pulled that db tried...This is an issue with the `user/user/fisherface/1/atnt` experiment. After pulling it from a local BEAT instance, it using the `atnt/3` database. Because the current version of `beat.cmdline` only supports `atnt/5`, I pulled that db tried to update all the experiment's datasets by selecting the `idiap_test_eyepos (atnt/5)` protocol option. It flipped the dev/test datasets when assigning
![image](/uploads/d3911ac58df31633c60fdf8d7d05150f/image.png)