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
How do you define a bio-core? #11
Comments
Is a bio-core even necessary? What would bio-core look like without parser and sequence methods? |
Well it was more because what I was seeing at the Bionode core wasn't that important for every component. Btw here 's the example of how an optional, generic reader one could extend could look like. |
During the BioJS 2.0 hackathon we created However in my humbled opinion agreeing on a common format for the same data is something worthwhile to achieve. |
I think we should let models/schemas evolve naturally and only worry about that when it becomes a real issue for collaboration/integration among modules. Right now, this hasn't been a problem for |
Seb: Why do you have the sequence class as core?
Seb: Something that I am imagining that should go inside this core could be a "GenericParser" which all parsers can inherit. After all they receive text and output an object. On the other side that might change too: arrays of binary data could be needed or with the upcoming ES6 Harmony browsers might finally support more structures.
Bruno: I think bio core should have helpers or util functions that are reused by most of the other bio modules.
The Sequence methods fit that description, although the reason why I have them in core is more historical than anything else. The first bionode module started as a way to provide those functions client side to the Afra project, while also being available for server side usage.
They should probably be moved to a specific bionode-sequence module, but then the bionode module would be empty since I don't have helper functions for now. In that case, the bionode module could become instead of the "core" module the "meta" module that links the other modules together in some kind of framework.
The text was updated successfully, but these errors were encountered: