You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After that I manually set up different bar plots etc in the HTML.
I was wondering if there is any way to save that manual progress in the HTML (to send it to collaborators, etc.). Setting up views can be time-consuming, and maintaining the interactive aspect is essential for many things (i.e., this is not solved through the svg/png export).
The text was updated successfully, but these errors were encountered:
Hi -- sorry, this functionality is not currently supported in Empress. It would be really useful to have it (I'm aware that manually configuring the barplots, etc. multiple times is a pain point); however, at least speaking personally, I don't have time to address it right now. I hope this situation will change sometime soon.
Regarding #551, I think the plan we had there was using a JSON format (like Emperor uses) to support exporting / importing the Empress settings. So, in the workflow of e.g. sharing an Empress HTML visualization with your collaborators, this would mean that you would also share a small JSON file alongside the HTML file, which could later be loaded in the Empress interface to automatically customize the visualization as it was before. Does this fit your needs?
I imagine it would fit the needs if it was possible to place the json into the empress project folder under a specified name and have it auto-load from there/save to there by clicking a button.
Hello and thank you for maintaining this.
I am creating empress HTMLs, through:
empress tree-plot --tree $tree --feature-metadata $metadata --output-dir empress_results
After that I manually set up different bar plots etc in the HTML.
I was wondering if there is any way to save that manual progress in the HTML (to send it to collaborators, etc.). Setting up views can be time-consuming, and maintaining the interactive aspect is essential for many things (i.e., this is not solved through the svg/png export).
The text was updated successfully, but these errors were encountered: