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.
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:
changed the title
How do you define a bio-core? For me code that should go inside is something like a "GenericParser" which all components can inherit. Why do you have the sequence class as core?Aug 3, 2014
During the BioJS 2.0 hackathon we created biojs-model. Currently it is somewhat empty and there isn't a widespread use. So maybe we don't need to specify schemes in a JS package that one needs to install.
However in my humbled opinion agreeing on a common format for the same data is something worthwhile to achieve.
Have you already created data schemes that you would consider fit for a global model definition?