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
@scottx611x : Here's one attempt at an IGV wrapper. What's the simplest contract we can require for integrating this or any future visualization into refinery? What still needs to happen here?
How do you want to manage the dependencies? Should I just download then all and put them in a vendor directory? Or should I try a package.json or something like that and leave it to Refinery to pull everything during build?
(Assuming we do want to avoid dependencies on CDNs?)
Extra input from the user: Getting the genome from the user, if it's missing, is pretty adhoc, but it gets the job done? I think that trying to get more user input from inside the refinery space doesn't scale well.
Naming: On the refinery side it needs to know which repo to check out, and what the key js file is, and what the human-readable name for the menu is: we could agree that the same name might be shared across more roles, or the convention could be index.js?
Since there's no compilation here, everything is src... but probably not a pattern to rely on.
I need to write a real refinery.js: There are probably tools that build js from an API spec... but if we only need one method, writing it by hand seems fine for now?
The text was updated successfully, but these errors were encountered:
In my view, part of the contract may be for vis packages to identify themselves as such, rather than maintaining a separate configuration list with all the details. This script does that... but it is unacceptably slow: Perhaps figure out where the package.jsons are stored and parse them directly?
@scottx611x : Here's one attempt at an IGV wrapper. What's the simplest contract we can require for integrating this or any future visualization into refinery? What still needs to happen here?
vendor
directory? Or should I try a package.json or something like that and leave it to Refinery to pull everything during build?index.js
?The text was updated successfully, but these errors were encountered: