221–226 of 226 posts
It'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.
Thank god for tiling window managers. Xmonad, we salute you. You are the best.
Earlier quoted context omitted.
The video highlighted an annoying feature of Squeak Smalltalk, where you get tiny little views of individual methods in their own window, which seems like a good idea until you actually try to do something complicated using it. It's pretty to watch though. The cool things there, in my opinion, were the code navigation pieces. Those are the things I actually think work better with tabbed files. In other news, yikes! I…
Those bubbles would have been a nightmare if they didn't relate to each other in such a clean way They have some great grouping features - snapping, colouring, pushing, connections with lines, naming groups.
Reminds me of Smalltalk...
The original version of eclipse was written in smalltalk…
Earlier quoted context omitted.
That might be the correct way to write that code if the situation is not recoverable. Say you have public int doubleFooBarBazQux(Foo foo) { return foo.bar().baz().qux() * 2; } That might throw a NPE, but what's the alternative?
I typed this into Eclipse, and it's super-awesome-excellent auto-code-writer decided that it should be: public int doubleFooBarBazQux(Foo foo) throws NullPointerException { try { return foo.bar().baz().qux() * 2; } catch(NullPointerException e){ throw new NullPointerException(e.getMessage()); } } If only there was a right-click option for "improve quality"...
Earlier 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…
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…
That 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.
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…