Closed nathandunn closed 8 years ago
So, this is pretty inconsistent and flaky. I think, related to #1126, we should change the behavior to open and close the side-bar only. It would be a lot cleaner and give the eventual correct behavior:
I did not see the 404 error; instead if I am currently in the Full-screen view and choose to Show Annotator Panel, then the annotator panel shows up again, and the JBrowse list of available tracks remains in the window as such:
Would it be okay if the show annotate / full screen options just opened and closed the annotator panel (i.e., the same as the button at the top)?
Nathan
On Jul 29, 2016, at 1:38 PM, Monica Munoz-Torres notifications@github.com wrote:
I did not see the 404 error; instead if I am currently in the Full-screen view and choose to Show Annotator Panel, then the annotator panel shows up again, and the JBrowse list of available tracks remains in the window as such:
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.
No, I think that dismisses the original intent of having the Full-screen view: to offer the ability to include the JBrowse menu, or remove it.
You can do that already be choosing the native track list from the track menu.
Nathan
On Jul 29, 2016, at 2:01 PM, Monica Munoz-Torres notifications@github.com wrote:
No, I think that dismisses the original intent of having the Full-screen view: to offer the ability to include the JBrowse menu, or remove it.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.
We can fix that either way.
Nathan
On Jul 29, 2016, at 2:01 PM, Monica Munoz-Torres notifications@github.com wrote:
No, I think that dismisses the original intent of having the Full-screen view: to offer the ability to include the JBrowse menu, or remove it.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.
Yes. That's already addressed with the toggle menu to Show JBrowse Track Selector. Unfortunately, at the moment, the Full-screen view is the only way in which we can display the data in the browser without being logged into Apollo.
Talked with NAL/USDA people today and I proposed a solution where full-screen mode would just slide out the annotator panel. They said they would be fine with that, but that users would be confused as to where the track panel went to and how do you get it back. This brings up why doesn't the track panel not have a show-hide button in the first-place, which we could add?
WRT to logged out, jbrowse only view, that shouldn't be affected, but that is an important use-case as well when switching.
To test:
To fix:
@nathandunn This may be a little 'meta' but if you look up this thread, you can see that I had already shared the same objection to your idea that "full screen mode just slide[s] out the Annotator Panel". Your solution was to toggle the JBrowse track list, as it is already possible from the Annotator Panel using the Show JBrowse Track Selector button. Again I add: Unfortunately, at the moment, the Full-screen view is the only way in which we can display the data in the browser without being logged into Apollo. Please keep that in mind as well. As (I think) you mention, this function cannot be lost.
Please keep that in mind as well. As (I think) you mention, this function cannot be lost.
Yeah. That is what I was responding to. We definitely need that functionality as well.
This proposal was just a proposal . . I'm going try and address the stuff in this comment first.
ClientToken was being handled in twice, so it was a string array instead of a string . . which confused java
Tested all functionality. Nearly all steps worked as expected, except:
@nathandunn are you experiencing the same? (is this what you were referring to above in your list 'To test'?
To reproduce, login, go to /apollo/jbrowse/ . . was because it was returning the index.html if you had a valid user, but not a valid organism or client_token.
Fixed.
It is fixed. All other steps in the above testing work. Gets a 💃 !
Clicking on "show annotator panel" in full-screen mode leads to this screen, where the clientToken is obviously not being transformed into a string properly.:
http://icebox.lbl.gov/Apollo-staging/annotator/index?clientToken=[Ljava.lang.String;@6acd68b8&tracklist=1&highlight=0..-1&tracks=DNA,Annotations,Nurse,Forager,Official%20Gene%20Set%20v3.2&nav=1&overview=1