4 ms·
But to your #2 - that seems to me to be exactly what this IDE is doing. That's the way I see it, anyway.
by Vivtek 17y ago
But to your #2 - that seems to me to be exactly what this IDE is doing. That's the way I see it, anyway.
- viraptor 17y agoIt's better than normal eclipse for sure - you get the arrow link between related methods, etc. What I meant is that in Vim I go to a name in ctags. That's what happens - whether I'm in the same file, or different, or I looked at that tag before. Type in tag name -> go - that's all that happens. With code bubbles, I could have the bubble already open, but just off the screen. Or maybe it's open in another dependency. Or maybe it's not open at all. I have to look at the screen, localise the bubble, make a decision and then do the action (either click existing bubble, or open a new one). Of course it's too early to criticise it, without testing beforehand. But it definitely got my attention, as something I tried to avoid. Having one good way to access stuff == less thinking. Let's say that Vim is stateless, but bubbles are stateful :)
- nitrogen 17y agoIt should be possible to add equivalent keyboard shortcuts to Code Bubbles, so that finding a nearby bubble could be accomplished by ESC,/tagname or something.