Like my development environments, things change. Since my next project is to extend a product written in Java and, since I used to develop Eclipse rich clients in my webMethods days, I figured I'd install Eclipse on my MacBook Pro.
We use SVN so, I also installed the most excellent Subclipse Eclipse plug-in. All was going well until, I tried to synchronize to the repository. When I did, I got the following error:
While creating an Eclipse TableView using Eclipse 3.2, oddly, only one of two defined table column titles was showing up. My table should have showed "Type" and "Name" columns but only the "Type" column header text would appear:
If you you’re a Perforce customer and an Eclipse user, you should use the Perforce plugin for Eclipse. It makes the job managing check-ins and check-outs easy, allowing you to stay nearly fulltime in your environment. Unfortunately, renaming an Eclipse plugin project isn’t supported very nicely.
OReilly recently reports that JBuilder is open-sourcing their IDE. Is this more proof of IDE commoditization?
It makes me wonder; does open-sourcing force commodization? You might argue this as a tactic used by second or third place competitors to grab market share, forcing the commoditization process. It's hard to argue that this can't at least be partially successful.
Introduction M/VC may be more familiar as "MVC," or Model-View-Controller the design pattern used in the Smalltalk environment [KP88] and cemented as the "Observer" pattern in Design Patterns [GHJV95] by the Gang Of Four. In real life, subconsciously plowing along with M, then V, then C often leads to MV with little or no decoupled C. Call this M/VC. With controller code woven deeply into your view, it becomes nearly impossible to later switch the view out.
NetBeans vs. Eclipse. This used to be a flashy debate but is losing luster with the rapid adoption and growth Eclipse as a platform for developing rich client applications. Perhaps this will explain why.
This is the blog-workout sequel to my carefree "Eating the Eclipse 3.1M5 RCP Donut" post. Presented here are four simple recipes for using the new 3.1M5 capabilities to create, configure, and export a Rich Client Platform (RCP) application out of one or more plug-ins. It can all be done graphically and completely avoids messing with plugin.xml or hand-editing a .properties file. Thanks, Eclipse RCP team for giving us this exquisite feature!