Hi guys I am new here.Just used biojs. I have encountered some problems recently. is about how to do two sequence alignment by javascript. For example, mapping CDS to DNA. I tried some NW or SW algorithm on github. but it do not work. i konw in python it can be very easy to solve by use biopython. Can someone give some advice? Thank you!
@rkpattnaik780 I added a few comments to your PR
I'm asking it because I forgot it :) It's been a long time since I didn't add anything new.
Hey @IbrahimTanyalcin!
@yochannah will be able to provide you with a better help.
Till then you can check out https://edu.biojs.net/ as most of the tutorials are here only. (It'll soon be updated with our new gsoc project :D)
@yochannah will be able to provide you with a better help.
Till then you can check out https://edu.biojs.net/ as most of the tutorials are here only. (It'll soon be updated with our new gsoc project :D)
@IbrahimTanyalcin - this is probably the tutorial you're looking for https://edu.biojs.net/details/package_json/ - look at the snippets section. https://www.npmjs.com/package/mplexviz-ngraph has a good example
@yochannah ok, I pushed a new version , hopefully it'll get picked up. Just one question, I am guessing that the sniper field in package.json is for local development ? Because I presume you are internally converting
require statements like require("lexicon-mono-seq") into a valid url such as https://cdn.jsdelivr.net/npm/lexicon-mono-seq@1.2.4/lexiconMonoSeq.v0.17.3.js or whatever the main field of package.json is pointing at. Or am I completely wrong with my assumption (which means a build is rendered at your backend servers first)
this is actually kind of in flux at the minute! we've found that sometimes building components successfully can be really tricky (large packages often time out, for example, or poorly defined dependencies) so we're trying to encourage people to include build versions of their files. This will also make it possible for people to implement components using a CDN link and copy/pasting a couple of lines of code rather than having to buid a package (anyone who knows a little HTML can copy/paste and tweak a component config, whereas there is a lot more knowhow required to build an npm component).
right now we try to build / prepare components where possible, but we're working on a more user friendly spec for BioJS 3.0
Ok sure, I asked it because jsdelivr caches everything with access-control-allow-origin as "*" including package.json as well. This means Everything can be fetched/xmlhttped as text/plain,
require statement replaced and rendered at client side within an iframe via script tag. This would greatly reduce complexity you need to deal on backend => you don't need to watch versions anymore and offload everything to client. I find it reasonable.
Hey guys, I have sent a PR(biojs/generator-biojs-webcomponents#8) to update the README of our current Yeoman generator. Please review it and let me know if there are any suggestions.
:smiley:
Hey guys, I sent a PR(biojs/generator-biojs-webcomponents#9) to fix an issue(https://github.com/biojs/generator-biojs-webcomponents/issues/6). Any suggestions are welcome.
"get() returned more than one Snippet -- it returned 8!"
while actually there is a single snippet file?
@DennisSchwartz https://biojs.net/#/component/lexicon-mono-seq , there is only 1 snippet here: https://github.com/IbrahimTanyalcin/lexicon-mono-seq/blob/master/snippets/snippet-1.js
which is an iife,
also the version is still 1.2.2 however i already published 1.2.6 over the course of 2 weeks.
NICE ONE @DennisSchwartz !!
hmmm, we have about 2 days - is it worth applying for http://2019.biohackathon.org/proposals ? @Nikhil-Vats @sarthak-sehgal @DennisSchwartz I don't think I could go this year but would be willing to help write a proposal for one of you to go