-
Notifications
You must be signed in to change notification settings - Fork 4
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
Compatibility with JBrowse2 #63
Comments
Not yet but integration is underway! |
Is JBrowse2 now integrable with Tripal 3? |
Sorry, not yet. I've been away on leave for 2 months and unable to work on it but it is high on my priority list now that I'm back! |
Hi, thanks for this great extension. Any update on jbrowse2 and tripal3 compatibility? |
Hi @CFGrote, thanks for checking in :-) My colleague is still working on it but progress was a bit slow due to other grant deadlines and work on Tripal 4. We're hoping to get back to it soon. That said, we are also happy to collaborate with anyone who has some developer time and needs this sooner! |
hi @laceysanderson, thanks for getting back. i'd be tempted to help out on this. but actually, i have much more need for tighter integration into tripal, along the lines of #8 and #9 (but not sure these are relevant any more). what would be a good place to get started? |
Nice! #9 would be very relevant for both JBrowse 1 + JBrowse 2 eventually so that's where I would start with those priorities. #8 will likely change a lot between the two JBrowse versions but maybe I'm being too idealistic wanting native integration -an iFrame would still provide a lot of functionality and there would be less change between JBrowse versions. For both, you would want to start with the Tripal v3 documentation on custom fields and I'll provide more specific helpful hints in the individual issues. |
Does the Tripal-JBrowse module work with JBrowse2?
I have noticed, for instance, that the JBrowse2 installation does not create a bin folder which is required by Tripal JBrowse Management.
The text was updated successfully, but these errors were encountered: