Earlier quoted context omitted.
Because not declaring the type of variables makes code not work with bubbles?
The demo is relying heavily on code navigation features that are only available to static language IDEs such as "Open Declaration", "Find All References", code completion, navigating object hierarchies, code outlines, inline docs, and other fancy code traversal techniques.
New IDE: code bubbles
181–190 of 226 posts
Re: New IDE: code bubbles
#182What I like about Bubbles is that it manages to visualize the program more like how I think graphically. I've never been a text programmer. I see the code in a visual way in my head, far from typing on a keyboard. About the opposite of Emacs/Vim. I seldom remembers the names of classes and methods, but where they are in a code landscape where the code almost have different kind of colours and textures. Negative space and beautifulness of code is important to me, and it has nothing to do with the text itself. The less I need to use a keyboard the better.
Re: New IDE: code bubbles
#183Earlier quoted context omitted.
This was my exact impression; I hate leaving the keyboard when I'm writing or reading code. To simulate some of the functionality of codebubble in vim, I :vsp the same file and scroll up/down to the method I want. I have, however, come to realize that navigation through a large project with keys alone is suboptimal. One typo in a nav command and you have to press at least four or five more keys. With the mouse, you'r…
This is exactly why I love the "Open File in Project" functionality that exists in some editors/IDEs (e.g., SlickEdit). It lets you type the filename, and does a "fuzzy search" match on it. Practically, this means that whatever file you think of, you can type any part of its name at any time to get to it. Once I got used to working this way, I stopped using the project tree-view: it's just much slower.
Agreed. The keyboard shortcut in Eclipse (at least in C/C++ mode, not sure if that changes for other languages) is Ctrl-Shift-R.
Re: New IDE: code bubbles
#184Earlier quoted context omitted.
I apologize if people thought I was hostile. I thought I was just making an argument by pointing out several examples of things text editors like Emacs don't normally do that IDE's do well. You've proven me wrong, at least for the case of C/C++. I would still argue that Emacs itself is not an IDE. It's just an editor with a turing-complete scripting engine. However, you could definitely convince me that Emacs+CEDET i…
Where you went wrong was in realizing that Emacs isn't a text-editor. Emacs is a text-based IDE.
Emacs is a scripting environment shell that comes with an editor. It's probably closer in philosophy to one of the old single-user operating systems that microcomputers used to come with.
Re: New IDE: code bubbles
#185It's odd that it's so rare in software to find window widgets that push each other out of the way instead of overlapping. I'm thinking of the gazillion pallettes in Adobe CS that always occlude each other. You'd think they'd have figured that out by now.
That's why I prefer Wmii, Ion2 and similar window managers. They really manage my windows, ensuring that they don't overlap and use the screen effectively.
In contrast, most other window managers just enable you to fiddle with the windows yourself, and that's all they do for you. You keep moving and resizing them, one by one, steadily. That's very annoying.
(In fact, I don't even have a desktop image, because most of the time, the desktop isn't visible anyway. I don't want to look at my desktop, I want to use that space for the application I'm working with!)
Re: New IDE: code bubbles
#186Earlier quoted context omitted.
One extremely annoying bit watching the video is that for an IDE manipulating text files it requires that your hand never leave the mouse. Every single operation it looks like requires that you right click, click to activate, click to drop down, click to open. Even the 'insta-search' box requires a click. Someone should buy a one button mouse and install it on their computer or just take the mouse away completely. A…
The plan9 folks would disagree quite vehemently. We are used to keyboard operations being more efficient for most tasks, but the keyboard operation for "go to the file over there, the one 3 links over semi-related to this one" may be slower than just clicking.
Yes, but there is a big difference between typing part of the file or function name and typing a full path. Search-based semi-global matching is a really fast way to navigate.
Re: New IDE: code bubbles
#187Earlier quoted context omitted.
This was my exact impression; I hate leaving the keyboard when I'm writing or reading code. To simulate some of the functionality of codebubble in vim, I :vsp the same file and scroll up/down to the method I want. I have, however, come to realize that navigation through a large project with keys alone is suboptimal. One typo in a nav command and you have to press at least four or five more keys. With the mouse, you'r…
This is exactly why I love the "Open File in Project" functionality that exists in some editors/IDEs (e.g., SlickEdit). It lets you type the filename, and does a "fuzzy search" match on it. Practically, this means that whatever file you think of, you can type any part of its name at any time to get to it. Once I got used to working this way, I stopped using the project tree-view: it's just much slower.
For those of you using Visual Studio, there is an addon called StudioTools that adds this functionality: http://submain.com/products/studiotools.aspx
Highly recommended, they both have a smart open file that lets you start typing a filename, and smart goto, which lets you start typing a class or method name. Makes navigation so much faster!
Re: New IDE: code bubbles
#188Earlier quoted context omitted.
Emacs is a text editor in the same way the space shuttle is a vehicle.
Yes, it's equally hard to operate.
Really?
I can see grandma not using it, but anyone on this site ought to be able to figure out the basics in short order.
Of course, no one ever truly masters it - I'm always learning cool new things. But that's part of what makes it so great.
Re: New IDE: code bubbles
#189Earlier quoted context omitted.
This was my exact impression; I hate leaving the keyboard when I'm writing or reading code. To simulate some of the functionality of codebubble in vim, I :vsp the same file and scroll up/down to the method I want. I have, however, come to realize that navigation through a large project with keys alone is suboptimal. One typo in a nav command and you have to press at least four or five more keys. With the mouse, you'r…
This is exactly why I love the "Open File in Project" functionality that exists in some editors/IDEs (e.g., SlickEdit). It lets you type the filename, and does a "fuzzy search" match on it. Practically, this means that whatever file you think of, you can type any part of its name at any time to get to it. Once I got used to working this way, I stopped using the project tree-view: it's just much slower.
Vim has a good plugin for this, FuzzyFileFinder. See http://stackoverflow.com/questions/1894614/vim-fuzzyfinder-u... for instructions on how to set it up.
Re: New IDE: code bubbles
#190That is a very interesting approach - instead of just presenting files , this IDE is already abstracting out some of the semantic structure for you and presenting code based on its relationships . It's meeting you halfway. And it keeps track of things the way you work - by explicitly acknowledging the task structure of the work, it's again meeting you halfway. This is a really promising start. Very cool.
Programming hasn't been about files for a long time now. That's the reason that we have IDEs in the first place, and why I cringe when people talk about writing code in a text editor. Any IDE worth its salt will do all the things in that video, except for the little draggable bubbles.
Meh .. by the time Eclipse boots up, and by the time you load your project in Eclipse, I'm already in-the-flow with tickets read / 5 files open / the project running on my localhost.
Besides, it's not like it's a primitive environment ... when I want some API discovery/learning or when I want to do some debugging (or both) ... I open up an interactive shell.
I have Textmate-like snippets setup in my Emacs, and for CRUD-stuff I bet I'm ten times more efficient than you (and adding new snippets is a piece of cake ... not to mention that we share them company wide because they are text-files in our SVN).
When wanting "rename" refactoring, commands with grep/find/sed are already hardwired in my brain.
And nothing beats editors like Vim/Emacs on pure text-editing efficiency. Also, good luck using your favorite IDE when trying out a new language ;)
So you can cringe all you want, some of us are quite happy with just text-editors.