-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
evaluate mol* for replacement #375
Comments
After some eval, I think it might be a reasonably small few days of focused time project to try to wedge the mol* canvas into the viewer. as a basic starting point for eval / comparison. we won't automatically get all of our same features back. But there seems to be a clear path for us to be able to render the same meshes and pdb sphere collections that we show now.
As previously discussed, we can also go the other direction and ask: what exactly do we want from their codebase for the simularium viewer? |
There were some blockers with this, with respect to using the mol* codebase to get anything to render. The mol* devs addressed this initial blocker but we never revisited. Current considerations (while we move forward with simularium viewer dev tasks):
|
For reference, prototype code branch is here: https://github.com/simularium/simularium-viewer/tree/feature/molstar-canvas |
What needs to happen?
look at mol* code and determine what it would take to actually replace the simularium-viewer canvas with their canvas and drawing api.
Why should we do this?
To eval the size of effort
When does this need to get done?
within the next couple of simularium dev mtgs
The text was updated successfully, but these errors were encountered: