This news was first posted on EclipseZone. There, you can find an article announcing the move that goes into a little more detail about what Ward will be doing at Eclipse. Please add this article link to your main post.
Re:GPL, the Greedy Programmer's License?
on
Revising the GPL
·
· Score: 1
That's the effect under GPL which is exactly why I can't use GPL'd code in my products. If I want to open up my source code, that should be my choice and not forced on me simply because I want to link in something written under an OSS license. In my opinion it's hypocritical to write a piece of software and call it "free" or "open" when it has these onerous strings attached.
GPL, the Greedy Programmer's License?
on
Revising the GPL
·
· Score: 1
Is it stealing if I embed the Apache web server in a product and make money from it? No, I'm spreading the code around, getting more people to use it. Maybe if I'm successful I'll hire some more programmers and have them work on other OSS projects.
However even if it's allowed by the license most people would object to their code being used and improved but nothing being given back, for example bug fixes. Some licenses just rely on the honor system for that (like PD, BSD, MIT, and ASF) but some make it explicit (like EPL, CPL, MPL, and GPL).
Look, if you really don't want your software to be hoarded then don't hoard it yourself. Let me use it and redistribute it and modify it and mix it with my own code. In return, I'll give you all the fixes and improvements I made to it. Sound fair? Now does it really matter to you if I provide the source to the other parts of my program? Why is that your business? GPL makes it your business, EPL makes it mine.
Fundamental problem won't be addressed
on
Revising the GPL
·
· Score: 2, Informative
GPL intentionally drives a wedge between the open and closed source communities. However it doesn't have to be that way. If your main purpose is to encourage open source, including making the source to any modifications available, then EPL already provides that. Unlike GPL, it does not put restrictions on the other code and licences with which it can be used.
I'm glad that Hubble will be repaired but I fail to comprehend why it has to be by robots. It's in near Earth orbit! If we can't send humans to near Earth orbit then we have no business sending them to, say, Mars.
I have to use regular IE at work and I'm sick of pop-ups. I've tried blocking software but it's too slow. So how about patenting pop-up ads and suing them out of existence?
Since prior art doesn't seem to matter, this should be a cinch. You could call it "Method and process for annoying the heck out of web surfers".
There are several appendixes, including one on SWT and one on JFace. Sample code for these and other sections can be found here. It's not comprehensive, but should be enough to get you started.
Re:Syntax checking as you write the code
on
Eclipse in Action
·
· Score: 1
Another feature I like is that as you are debugging your Java code, you can make minor changes to it and save, and Eclipse (with a 1.4 JVM) will recompile and replace the class while your program is still running. VisualStudio did this with C++ a while back but it was sometimes difficult to get it to work (but handy when it did).
Re:the other book met my needs much better
on
Eclipse in Action
·
· Score: 1
That's a good book too, though it's for Eclipse 2.0 instead of 2.1. It's about 900 pages (vs. 400 for EiA) so it has room for more detail about options, menus, settings, plugins, etc.. There's not really a tutorial section per se, but they have a large exercise section at the end that could be used in a classroom setting (that's where the book originated - from an IBM training course). I think the two books largely complement each other.
In the Eclipse in Action book, Appendix D has an introduction to SWT and Appendix E has an introduction to JFace. They both have stand-alone sample programs, and you can download all the samples for free.
That's not a bad analogy, actually. You can run a shell, read your mail, edit all kinds of files with color coding, and so forth in Eclipse just like you can in Emacs because it's so extensible. Of course the technology is completely different and the license is too, but the effect is similar.
If you're thinking of the Layouts example, it would be a big stretch to call that a GUI editor. Unless your GUI consists only of Buttons named Button 0, Button 1, and so on:).
Slashdot Mirror
This news was first posted on EclipseZone. There, you can find an article announcing the move that goes into a little more detail about what Ward will be doing at Eclipse. Please add this article link to your main post.
Try adding "-Dide.gc=true" to your eclipse.ini file or VM options. This works on all platforms, not just Windows. For more info see: http://www.eclipsezone.com/java/forums/t20967.html
That's the effect under GPL which is exactly why I can't use GPL'd code in my products. If I want to open up my source code, that should be my choice and not forced on me simply because I want to link in something written under an OSS license. In my opinion it's hypocritical to write a piece of software and call it "free" or "open" when it has these onerous strings attached.
Is it stealing if I embed the Apache web server in a product and make money from it? No, I'm spreading the code around, getting more people to use it. Maybe if I'm successful I'll hire some more programmers and have them work on other OSS projects. However even if it's allowed by the license most people would object to their code being used and improved but nothing being given back, for example bug fixes. Some licenses just rely on the honor system for that (like PD, BSD, MIT, and ASF) but some make it explicit (like EPL, CPL, MPL, and GPL). Look, if you really don't want your software to be hoarded then don't hoard it yourself. Let me use it and redistribute it and modify it and mix it with my own code. In return, I'll give you all the fixes and improvements I made to it. Sound fair? Now does it really matter to you if I provide the source to the other parts of my program? Why is that your business? GPL makes it your business, EPL makes it mine.
GPL intentionally drives a wedge between the open and closed source communities. However it doesn't have to be that way. If your main purpose is to encourage open source, including making the source to any modifications available, then EPL already provides that. Unlike GPL, it does not put restrictions on the other code and licences with which it can be used.
I'm glad that Hubble will be repaired but I fail to comprehend why it has to be by robots. It's in near Earth orbit! If we can't send humans to near Earth orbit then we have no business sending them to, say, Mars.
Since prior art doesn't seem to matter, this should be a cinch. You could call it "Method and process for annoying the heck out of web surfers".
There are several appendixes, including one on SWT and one on JFace. Sample code for these and other sections can be found here. It's not comprehensive, but should be enough to get you started.
Another feature I like is that as you are debugging your Java code, you can make minor changes to it and save, and Eclipse (with a 1.4 JVM) will recompile and replace the class while your program is still running. VisualStudio did this with C++ a while back but it was sometimes difficult to get it to work (but handy when it did).
That's a good book too, though it's for Eclipse 2.0 instead of 2.1. It's about 900 pages (vs. 400 for EiA) so it has room for more detail about options, menus, settings, plugins, etc.. There's not really a tutorial section per se, but they have a large exercise section at the end that could be used in a classroom setting (that's where the book originated - from an IBM training course). I think the two books largely complement each other.
In the Eclipse in Action book, Appendix D has an introduction to SWT and Appendix E has an introduction to JFace. They both have stand-alone sample programs, and you can download all the samples for free.
That's not a bad analogy, actually. You can run a shell, read your mail, edit all kinds of files with color coding, and so forth in Eclipse just like you can in Emacs because it's so extensible. Of course the technology is completely different and the license is too, but the effect is similar.
If you're thinking of the Layouts example, it would be a big stretch to call that a GUI editor. Unless your GUI consists only of Buttons named Button 0, Button 1, and so on :).