Community
Participate
Working Groups
We talked about the possibility using the concept of scroll spy today at the UX call with Szymon, Susan, Mark and McQ. I would like to do some investigation on this to see how doable it is in Orion. McQ drew a draft on the white board: 1.We spy on the scroll event in the browser 2.If the view port is intersecting with any section, we pin the sectional tool bar some where in the top of the page. 3.The sectional tool bar should also indicate how many items were selected. ETC...
I drew a cut and paste mockup of this here: http://wiki.eclipse.org/Image:Orion-scrollspysectionheader.png We should have Anton comment on styling the sectional header. Does it look different when pinned than when it's inline? In the mockup I just pasted the current section styling at the top, but I'm not sure it stands out enough from the scrolled content. We may need additional affordance for this state?
meant to cc: anton. Note that the idea of showing selection count (and probably full item count) is something he's played with already in the plugins page. So having a nice, pretty, standard rendering of all that would be great.
(In reply to comment #2) > meant to cc: anton. > Note that the idea of showing selection count (and probably full item count) is > something he's played with already in the plugins page. So having a nice, > pretty, standard rendering of all that would be great. Yes. I will be tweaking on the underlying logic first. Some points I can think about for now. 1.We should listen to browser's scroll event but should we extend this any other DIV(with scroll bar)containing sections? 2.We should be able to register sections/explorers that are interested to be spied. And maybe with importance. E.g In navigator page, if both file navigator and favorites are hit by view-port and their local tool bars are hidden we may want to pin the file navigator's. Or we should not even register the favorite section. 3.APIs like, provide the section main DIV and tool bar DIV from a section, for hit test. 4. Animations ? see this: http://www.wduffy.co.uk/blog/keep-element-in-view-while-scrolling-using-jquery/
(In reply to comment #3) > 2.We should be able to register sections/explorers that are interested to be > spied. And maybe with importance. There is already css class called sectionAnchor that was meant for sections navigating and spying. I wonder if we can use it here. I like the navigation from your example. I think thought we were rather talking about a floating section toolbar that sticks to the top of the page as long as you see the section.
(In reply to comment #4) > (In reply to comment #3) > > > 2.We should be able to register sections/explorers that are interested to be > > spied. And maybe with importance. > > There is already css class called sectionAnchor that was meant for sections > navigating and spying. I wonder if we can use it here. > > I like the navigation from your example. I think thought we were rather talking > about a floating section toolbar that sticks to the top of the page as long as > you see the section. Yes, I also thought we were talking about a floating section toolbar, like the one on http://twitter.github.com/bootstrap/javascript.html (the second bar that floats up and pins to the top banner). But the example is an interesting idea, too, I think it could be used to address the other issue we have, which is having an "outliner" that lets you navigate all the sections on a page.
(In reply to comment #5) > But the example is an interesting idea, too, I think it could be used to address > the other issue we have, which is having an "outliner" that lets you navigate > all the sections on a page. I agree. I was already looking at it. I would like to continue working on the section navigation thing. This may somehow overlap this task
(In reply to comment #6) > (In reply to comment #5) > > But the example is an interesting idea, too, I think it could be used to address > > the other issue we have, which is having an "outliner" that lets you navigate > > all the sections on a page. > > I agree. I was already looking at it. I would like to continue working on the > section navigation thing. This may somehow overlap this task Szymon, can you open a separate bug as a blocking one for this? My focus will be on be on tweaking the underlying stuff: scroll event interacting with the current view port, intersecting with interested sections, make some initial UI work while scrolling. Then we can integrate your outliner.
(In reply to comment #4) > (In reply to comment #3) > > > 2.We should be able to register sections/explorers that are interested to be > > spied. And maybe with importance. > > There is already css class called sectionAnchor that was meant for sections > navigating and spying. I wonder if we can use it here. > > I like the navigation from your example. I think thought we were rather talking > about a floating section toolbar that sticks to the top of the page as long as > you see the section. Lemme look. My original point was to filter out some non important sections from spying.(e.g fav list is parallel to file navigator. Will be funny to spy both when they are very long)
There are already some view port intersecting stuff in the traversing model. Like when you arrow down to the next row, it checks if the next row intersects with a rectagle(view port +- orion tool bar and footer). We may want o surface those as a util function.
See also bug 380703.
Talked to Simon, we are not going to do this for 0.5.
Closing as part of a mass clean up of inactive bugs. Please reopen if this problem still occurs or is relevant to you. For more details see: https://dev.eclipse.org/mhonarc/lists/orion-dev/msg03444.html
