Skip to content
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

Update of SBMLDocuments on file changes (reload new version) #165

Open
matthiaskoenig opened this issue Aug 11, 2016 · 1 comment
Open
Labels

Comments

@matthiaskoenig
Copy link
Owner

There should be a concept/method of updating SBMLDocuments with keeping the layout information/Cytoscape information.
Part of the solution is the current layout export/import, but there should be a default method to update models from revision to revision.
This could also integrate with #110 .
An essential part of model development is a rapid iteration of model versions. This should be supported.
A solution could be to base a model on another model, i.e. if models with high similarity (based on model differences) are found in the Network2Document mapper they should be suggested as input.
When a core model is selected information is transferred as far as possible based on node_id mapping, i.e.

  • layout
  • background elements and annotations
  • visual style

Differences could be highlighted.

@matthiaskoenig matthiaskoenig added this to the 0.4.0 milestone Aug 11, 2016
@matthiaskoenig matthiaskoenig modified the milestone: 0.4.0 Aug 30, 2016
@matthiaskoenig matthiaskoenig changed the title Update of SBMLDocuments & Support of model iteration/versions Update of SBMLDocuments Oct 4, 2017
@matthiaskoenig
Copy link
Owner Author

No model iteration information displayed.
But the source files should be monitored and a reload offered on observed changes.

@matthiaskoenig matthiaskoenig changed the title Update of SBMLDocuments Update of SBMLDocuments on file changes (reload new version) Oct 4, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant