Forgot your password?
typodupeerror
Google Java Open Source Software

Google Donates Windowbuilder, Codepro To Eclipse 150

Posted by timothy
from the spreading-it-around dept.
h00manist writes "Google is donating Windowbuilder Pro and Codepro Profiler to the Eclipse project. 'Google acquired the software when it bought Instantiations, relaunching the Java graphical user interface building tool Windowbuilder Pro shortly after. Now the outfit has decided to donate both Windowbuilder Pro and the code analysis tool Codepro to the open source Eclipse project. Although Google has announced its intention to donate the software, it needs go through a rigorous filtering process to ensure that no intellectual property rights will be breached. Once those formalities are dealt with, it is likely that both Windowbuilder Pro and Codepro will tip up in the Indigo release of Eclipse sometime in June 2011.'"
This discussion has been archived. No new comments can be posted.

Google Donates Windowbuilder, Codepro To Eclipse

Comments Filter:
  • by TheCybernator (996224) on Monday December 20, 2010 @05:01AM (#34613758) Homepage
    am more interested in CodePro. And what more it has to offer compared to YourKit
    • by xtracto (837672)

      A bit sad: [theinquirer.net]

      A Google employee got in touch with The INQUIRER to clarify that Google's donation to the Eclipse project does not include the Codepro Analytix software which it had acquired through Instantiations. The donation only includes Codepro Profiler and Windowbuilder Pro.

  • Of the market by using Smalltalk. Its great to Instantiations still in business, and focused on Smalltalk. I find it very perplexing that Google bought the Java tools from them while leaving the Smalltalk business and dev folks behind that used Smalltalk to create these Java tools. When folks finally get to the real world of Smalltalk and its power, and Java is realized for its weaknesses maybe we'll all get back to the real work of creating real tools for real people with real problems to solve.
  • Ha (Score:2, Insightful)

    by ledow (319597)

    It's Java. That's where my interest ends, especially after Google's own fight with Oracle.

    Now if you do integrate a couple of decent C profiling tools, I'd be interested.

  • by seanyboy (587819) on Monday December 20, 2010 @06:10AM (#34613990)

    This seems great, but it pisses me off that the lawyers have to get involved. It seems shockingly bad to me that we accept that there has to be lawyers too. That's how deeply they've embedded themselves into software licensing.

  • Fantastic news (Score:4, Interesting)

    by Andy Smith (55346) on Monday December 20, 2010 @06:11AM (#34613994) Homepage

    Love Java. Love Eclipse. Sounds like my IDE of choice is going to get a lot stronger.

  • Hidden motive? (Score:5, Interesting)

    by Compaqt (1758360) on Monday December 20, 2010 @06:33AM (#34614078) Homepage

    There's another aspect to this.

    Oracle's fighting with Google over how they screwed over Sun. Sun's Netbeans Java IDE heretofore had the most innovative free Java GUI designer, the so-called Matisse [google.com]. Matisse gave Netbeans a major edge vs. Eclipse, the other popular free IDE. And Sun sold services based on Netbeans.

    Now, granted, Google's done a lot of stuff out of the goodness of their hearts. But when you have a chance to stick to someone (Oracle) who's suing you, and also get PR points in the process, why not?

    • Re:Hidden motive? (Score:5, Informative)

      by icebraining (1313345) on Monday December 20, 2010 @07:18AM (#34614206) Homepage

      Google's internal Java IDE is Eclipse, so improving it is in their direct interest.

      • by Compaqt (1758360)

        Is it really? I didn't know that.

        Don't get me wrong. I applaud the move.

        But this is also going to definitely decrease Matisse's uniqueness.

    • by mjwx (966435)

      Now, granted, Google's done a lot of stuff out of the goodness of their hearts. But when you have a chance to stick to someone (Oracle) who's suing you, and also get PR points in the process, why not?

      Now stabbing your enemies in the stomach is not the definition of evil.

      Not being sarcastic, Google and Oracle are embroiled in a serious fight and this is far from the dirtiest trick in the book.

    • by tangent3 (449222)

      I don't think so.

      In my opinion, I think Google bought Instantiations for the GWT Designer, easily the best Google Widget Toolkit plugin around for Eclipse, better than Google's own plugin. GWT Designer was available only under a paid proprietary license, and Google wanted it free for all developers to use, so they acquired Instantiations to make GWT Designer free.

      Of course, Instantiations owned a lot more than just GWT Designer, and Google doesn't really want to maintain the products other than GWT Designer

    • by ADRA (37398)

      I always thought that the commonly assumed reason for buying them was that they made great a great GWT IDE, and a great GWT IDE means better GWT adoption which means more GWT mindshare. The company was probably available for sale cheaper than building a group would have been, so the reasons are pretty self-evident.

      Oh, I could also see them using the team to build out the next generation of Android GUI development tools, because the current iteration of the tool is quite lacking in comparison to the builders

    • by Eskarel (565631)

      Which would make sense, except that Oracle are big users of Eclipse and have also donated a tonne of software to the Eclipse foundation. It's possible that Oracle will switch to netbeans now that they own it, but it'd be a fairly major cultural change for software they didn't find worthwhile to begin with.

  • by assertation (1255714) on Monday December 20, 2010 @07:40AM (#34614274)

    I've been a Java developer for 11 years and I don't use development tools written in Java. While I am gaga over server side Java, I'm not a fan of interpreted code for client applications. I've always had fast machines and Jbuilder/Ecliples/Netbeans and all of the other Java IDEs have lasted for about 15 min with me whenever I have tried a new version. I can't think of anything else more irritating than having to wait for a menu on my development tool to come up. Coworkers always rave to me how _____ has improved and is fast. It has never been true.

    I've stuck to Visual Slickedit all of this time. It is written in compiled code, is fast and has a ton of Java support. It also has a ton of support for many other languages so I can use it for everything and not have to learn a new tool.

    • You're not running McAfee are you. I run jBuilder on my work machine and Eclipse on my PS3 and laptop. My work machine almost dies every time I start jBuilder and then everything (right click context menus, drop down menus, compiling, debugging, etc...) is insanely slow the first time it's used. I don't have the same problems with my PS3 or laptop.
      • I see where you are going.

        Every place I have ever worked and expect to work has antivirus software. The last place the antivirus software slowed down everything! I had to get more RAM just so I could DO work at 3:30 when it ran everyday.

        Yet, I've also used development tools written in Java on my Linux box, even smaller ones like JEdit and the interface is slower.....every time.

        Some things I am willing to put with a slowdown for. Just clicking on a menu option for main work tool is not one of them.

        The Ja

    • My guess is you use Windows and have anti virus software.

      My desktop machine has 1/3 the ram (1gig) of my work machine and the processor is almost half the speed and yet Netbeans and Eclipse run better. The only difference is my dekstop at home runs Ubuntu and my work machine is XP with McAfee loaded on there as well.
      • My guess is you use Windows and have anti virus software.

        I'll admit that's been the setup for most (not all) of the times I personally have done professional Java work.

        Thing is, you only can give Eclipse so much cover for running like a one-legged dog in that kind of environment, because most things don't. Actually I can't think of anything that runs as badly as Eclipse in that environment.

        • I'm not sure if Eclipse has gotten better or it's because I've given up on attempting to use too many plugins but I do know Eclipse used to have some really awful default settings which means it would come to a crawl if you start adding in some big plugins. In fact I think it used to use just the default memory settings for Java which I believe means it only had 64 megs to play with.

          You had to fix it by other modifying the ini file or startup command on your icon. While that may seem fairly minor I thoug
    • While I am gaga over server side Java, I'm not a fan of interpreted code for client applications.

      Me neither! Fortunately, I can sleep soundly, secure in the knowledge that it hasn't been interpreted for well over a decade (JIT was introduced in 1997 with 1.1).

      • Correct if I am wrong, but only non-GUI code is compiled with JIT.

        • by siride (974284)
          There's no difference between GUI code and non-GUI code. What would that even mean?
        • by radish (98371)

          Consider yourself corrected :) Unless you intentionally disable hotspot everything is a candidate for JIT and post-JIT optimizations.

          • Then why do Java GUI apps perform so poorly?

            • by ADRA (37398)

              The application is as good as its programmer, and GUI programming of ANYTHING takes a baseline of ability. Java is usually used on Web and server platforms, so there are few Java GUI specialists. When a Java programmer is tasked to write a GUI app, it is more often than not a weak knowledge area for the individual. For those that can develop good GUI's in Java, I'm sure they do a great job. Its kind of sad that two of the most popular Java applications (Eclipse, Azareus/Vuze) are written in SWT but that's a

    • by olau (314197)

      I think it has more to do with shoddy GUI implementations than anything else. Much of Emacs is written in Emacs Lisp, not exactly a speed demon, and it runs fast enough.

      And Visual Studio seems pretty slow to me too, the few times I've had to endure its presence. :)

      • I started off with EMACS in school way back in the 20th century. I had to go on a 12 step program to break away from it. I never had any experiences with EMACS being slow...even NTEmacs for Windows. Given the crappy hardware of the era I can't see how it would be slow now.

    • by ADRA (37398)

      Eclipse has an iterative compiler. I NEVER wait for a compile unless I've structurally changed a file that is literally used by 100's of classes. That alone is worth its weight in gold.

  • Oracle will be anxiously anticipating their handout in the coming weeks.

    • Netbeans developers claim that fowl play is at the heart of the latest Eclipse GUI code and existing steps in that direction may have been responsible for Eclipse's legendary slowness [blogspot.com]. The developers' claims stem from their exploratory search of the donated code, where a new GUI code a class called "Beak" was found to contain methods such as doPeck(), doSquark(), doScratch(). Further suspicions were raised when an existing Eclipse non-GUI class called Headless was found to be extending Thread class while ov

  • by Yuioup (452151)

    I see that WindowBuilder Pro can be used to create GWT GUIs.

    Serious question: Does anybody out there use GWT? I went searched for good showcases and didn't find any good examples. If anything the examples tell me to stay away from GWT.

    • by wandazulu (265281)

      I use GWT. It's a pretty nice toolkit for web pages that is all Java; it compiles the Java to Javascript so there are some classes that you can't use (AWT, Swing, etc.). I've found the performance to be good (certainly better than the big Flex apps I'm using it to replace) and being able to stick with one language through everything is a big plus. You can still use CSS to format the output, so you don't have to stick with a single look or have to dive into the html/javascript to change it.

      It's definitely an

Man must shape his tools lest they shape him. -- Arthur R. Miller

Working...