Closed d1manson closed 8 years ago
I have started implementing a tile-element which will hopefully encapsulate most of the gorriest details relating to the DOM of the tiles in the tilewall. This is quite a big job though as there are a lot of fiddly things in T.Tool
and the T.groupOver
that rely on various aspects of the exiting structure.
The next step could be to improve and standardise all the events.
Part of that second step might be to separate the loading and post-processing of tets and pos etc. and make them on demand only.
The tile element is now live.
Have made scrollable-area, file-drop and floating-info into elements, though they will have to wait for the other stuff before going live. The "other stuff" in question is the file-organizer element, which currently does all the basic interaction stuff, but it doesn't yet trigger any events. The event model is going to be significantly updated so as to allow better post-processing (to include eeg and dir) and temporal masking...this is quite a big task.
Finally, this is basically done.
Although the codebase has undergone multiple restructurings in the past, it is still rather unwieldy and adding plots and other features is a painful process...even though the end result may look painless.
With some work it should be possible to improve upon this situation. Ideally it should get to the point where it only takes a few hours to add a completely new plot type and have it work seamlessly with everything else.