Closed matthew-blackman closed 5 months ago
We are seeing that font-family: 'Montserrat-Regular', sans-serif !important;
looks good in the CODAP table. @matthew-blackman changed to use that font in the checkbox panel, and it looks good on @matthew-blackman's screen. But on my screen, I see the correct font in the table but the checkbox labels fall back to Arial.
Documentation for the di query parameter: https://codap-server.concord.org/help/work-documents-create-open-save-and-share-documents/use-url-parameters-to-modify-codaps-behavior
Documentation for the API: https://github.com/concord-consortium/codap/wiki/CODAP-Data-Interactive-Plugin-API#example-update-interactive-frame
I'm getting NaN when it tries to position the webview:
I'm experimenting with a wrapper container that has the sim on the left and the selected attributes to the right:
However, this does not let the user collapse or hide the selected attributes (as a separate window). I don't know if this is an acceptable design. It also traps a lot of empty space below the checkboxes.
Pros to keeping the panel docked
Cons to docking the panel
Remembering this makes me lean towards not docking it.
@matthew-blackman and I discussed this problem.
We wanted to test in a self-contained reproducible minimal example to try to help understand if the problem is in our configuration or in the platform, so we started with the exemplar in the documentation: https://github.com/concord-consortium/codap-data-interactives/blob/master/NewRandomNumbers/random-numbers.js
We added one webview:
However, this still shows behind the data interactive:
We feel there may be a bug because using CODAP to create a web view does position it correctly. Options => Display Web Page:
Therefore, @matthew-blackman and I agree we will have to go with plan B which is currently docking to the right side of the window.
Patch for 3/13 pairing work with @samreid, building out the 'docked' view of the data stream controls:
@matthew-blackman and I got to a point where the docked checkbox panel was working properly. We were also overjoyed to eliminate the hack localStorage
protocol which would likely have failed QA on some platforms.
We want to apply this dock pattern to the tool wrapper as well.
I'll take the next steps here...
I removed a lot of the hacks and workarounds, and was also able to refactor the different wrapper logic into individual files. Things are looking more understandable and maintainable here. There is a little bit of repeated boilerplate, but it is worth it. Let's check in with @matthew-blackman next.
This is looking great - nice work! The docked design is much more straightforward IMO, and cleans up the workaround we were using with localStorage. The wrappers for streaming data and tool data both look good. Closing.
Namely, make sure no panels appear behind the simulation.