Latest @
Forum Controls
Spotlight Features
The Rich Engineering Heritage Behind Dependency Injection
Andrew McVeigh takes us on a tour of the rich heritage behind dependency injection, what it represents, and tells us why its here to stay.
Java, the OLPC, and community responsibility
The "One Laptop Per Child" project has a great device ready to ship, but there's no Java on there. Let's think about working together to put Java on OLPC!
Eclipse 3.2 M4 reproduces many features of Swing and IntelliJ IDEA
URL: Eclipse 3.2 M4 - Old and Already Implemented
At 2:45 AM on Dec 23, 2005, Alex Tkachman
wrote:
Is it really so new, then?
78 replies so far (
Post your own)
Re: Eclipse 3.2 M4 reproduces many features of Swing and IntelliJ IDEA
Pretty interesting!It would be pretty cool though if you could list some features that are present in other ides and Swing which are still not present in Eclipse and SWT.
Re: Eclipse 3.2 M4 reproduces many features of Swing and IntelliJ IDEA
I think most 'new' features introduced by new IDEs releases are only new for this specific IDE, because they were already implemented in some other IDE.AFAIK no one claimed that these new Eclipse features are world-novelties.
Re: Eclipse 3.2 M4 reproduces many features of Swing and IntelliJ IDEA
> It would be pretty cool though if you could list some features that are present in other ides and Swing which are still not present in Eclipse and SWT.You mean like supporting indexed properties? Ok, I've heard that it's the Eclipse VE team that is responsible for this, but even so this missing feature means many visual JavaBeans don't work in Eclipse...
There was a big discussion here at JL about a year ago where someone said that two-way parsing of source code is the best way. A few said that it would be impossible to re-parse some custom made GUI code. I guess the latter group was right since they haven't even been able to reparse simple:
setProperty(new String[] {"Hello"}); String[] prop = getProperty();Here's the RFE:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=49718
Cheers,
MiG Java Calendar Component, MiG Layout for Swing/SWT (Vote -> JDK)
Re: Eclipse 3.2 M4 reproduces many features of Swing and IntelliJ IDEA
This guy clearly has too much time on his hands.The only case he proves with this comparsion is that he doesn't know anything about Eclipse.
And for me I just proven to be an idiot for actually reading it, but this is not about me
Re: Eclipse 3.2 M4 reproduces many features of Swing and IntelliJ IDEA
I agree.Most interesting part for me is to see how different ideas invented and implemented firstly in IntelliJ IDEA n after 2-3 years become "new" in other Java IDEs. It is not against some specific IDE. It is even not against any Java IDE at all. Just curious.
alex(dot)tkachman(at)jetbrains(dot)com
Re: Eclipse 3.2 M4 reproduces many features of Swing and IntelliJ IDEA
I don't think he has too much free time. At least list of his projects is very impressive. I also can say that his participation in the IntelliJ Comunity is always very smart..
alex(dot)tkachman(at)jetbrains(dot)com
Re: Eclipse 3.2 M4 reproduces many features of Swing and IntelliJ IDEA
It is very interesting. I got many new ideas from the list.I never notice for these feature before. Good job!
Re: Eclipse 3.2 M4 reproduces many features of Swing and IntelliJ IDEA
This is a comparison at two different levels:- at IDE level between the Eclipse Java IDE and IntelliJ IDEA
- at widget set level between Swing and SWT with JFace
Still I think that it is incomplete: why only milestone 4 compared and not the other 3 milestones too?
In fact what's the point of comparing a product version at a random stage of development with stable versions of other products and technologies?
Re: Eclipse 3.2 M4 reproduces many features of Swing and IntelliJ IDEA
It would be great if somebody will do more detailed comparison. Most probably we will find that a lot of fetures were borrowed from IntelliJ IDEA . All information about features of IntelliJ IDEA is available herealex(dot)tkachman(at)jetbrains(dot)com
Re: Eclipse 3.2 M4 reproduces many features of Swing and IntelliJ IDEA
Look, I have nothing against IntelliJ IDEA. It's a great tool which raised the Java IDE standard quite a lot. But it has weaknesses: its license, price and modularity.However in order to be able to fully compare IntelliJ IDEA with Eclipse and show off its superiority you should think again.
Eclipse helps you a lot in developing good quality plugin based Java desktop applications because it's such a highly modular platform. And a lot of effort goes into developing the platform itself to suit all other kind of applications besides a Java IDE. A lot of effort goes into developing the EMF and GEF projects. The Eclipse Visual Editor is an application of these technologies (call it the top of the iceberg).
And there are, at the very heart of the GUI, the SWT and JFace plugins which proved that you can have really fast Java GUI applications (and forced Sun to improve Swing's speed). The best SWT showcase I think is Azureus, SourceForge.net's constant top 10 project (this month it's in second place).
If Eclipse would be just a Java IDE like IntelliJ IDEA then I think that it would be feature wise above IntelliJ IDEA - all this with an open source license.
So, yes, if you want to put it that way, Eclipse IDE vs. IntelliJ IDEA 1:1 and Eclipse RCP+GEF+EMF vs. IntelliJ IDEA 3:0
Re: Eclipse 3.2 M4 reproduces many features of Swing and IntelliJ IDEA
> You mean like supporting indexed properties? Ok, I've> heard that it's the Eclipse VE team that is
> responsible for this, but even so this missing
> feature means many visual JavaBeans don't work in
> Eclipse...
Just interesting, what kind of indexed properties support do you want? SWT/Swing Designer can now understand them and apply to bean. You can also see them in property table and navigate to the line where you set them. If property is not set and you click on this property, Designer will generate setXXX(null) statement for you. More user friendly editing support is limited to array of String's.
So, I just try to understand, what means "support indexed properties".
> There was a big discussion here at JL about a year
> ago where someone said that two-way parsing of
> source code is the best way. A few said that it would
> be impossible to re-parse some custom made GUI code.
> I guess the latter group was right since they haven't
> even been able to reparse simple:
>
>
> setProperty(new String[] {"Hello"}); > String[] prop = getProperty(); >What do you want from this code? I don't understand without context. getProperty() can return anything.
>
> Here's the RFE:
>
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=49718
I see only String[] here, so at least partly indexed properties are supported in Eclipse.
SWT/Swing/ GWT Designer - SWT/Swing/GWT GUI designer for Eclipse
Re: Eclipse 3.2 M4 reproduces many features of Swing and IntelliJ IDEA
It's great you now support array properties in SwingDesigner! The support wasn't there a while ago (when we tested it) and neither did it work in Eclipse's VE. When I asked at EclipseZone why it didn't work I got pointed to the bug linked above, so I thought I'd monitor it to see if there was a changed.Since the RFE is there in the Eclipse database the conclusion is not far fetched that it is the base platform itself that lacks the functionality.
Do you mean that it's the responsibility for the GUI plugin to parse and create the code for properties and that isn't supported by the base platform? Or have you just added the indexed properties part around the base platform?
In any way, if you say it's working now we will do a new test suite to see if our beans work with Eclipse. Even if it is just your SwingDesigner that can handle it that's fine since it's a very good product. If would of course be good if all Eclipse GUI editors supported indexed properties...
Can you just quickly say where the border between the GUI plugin and base eclipse platform is? I mean do you (IDE plugin) for instance have to parse/create all source code for the properties or just some of it?
Cheers,
MiG Java Calendar Component, MiG Layout for Swing/SWT (Vote -> JDK)
Re: Eclipse 3.2 M4 reproduces many features of Swing and IntelliJ IDEA
> It's great you now support array properties in> SwingDesigner! The support wasn't there a while ago
> (when we tested it) and neither did it work in
> Eclipse's VE.
String[] support for Java beans was implemented 06.01.2005, i.e. almost 1 year ago.
> Do you mean that it's the responsibility for the GUI
> plugin to parse and create the code for properties
> and that isn't supported by the base platform? Or
> have you just added the indexed properties part
> around the base platform?
Hm... Problem is that Swing Designer is not based on VE.
Initially when I started SWT Designer there was no open source VE. Later, when we started to work on Swing Designer we decided that we want keep independence and have faster development.
SWT/Swing/ GWT Designer - SWT/Swing/GWT GUI designer for Eclipse
Re: Eclipse 3.2 M4 reproduces many features of Swing and IntelliJ IDEA
> String[] support for Java beans was implemented 06.01.2005, i.e. almost 1 year ago.Ok, the example used String[], but actually it should be able to support any type. For instance:
setRows(new MyRowDef[] {1, 2, 3}); MyRowDef[] myRows = getRows();Do you support this in SwingDesigner as well?
Then I guess it's VE that lacks indexed properties support, but since one need a visual editor to use visual JavaBeans that shortcoming affects the whole Eclipse platform. Or is there a replacement for VE (other than SwingDesigner) that everybody, or most, are using?
I should also mention that non-Eclipse based Java IDEs (netBeans, JFormDesigner, JBuilder) support indexed properties (and not only String[]) out of the box.
Cheers,
MiG Java Calendar Component, MiG Layout for Swing/SWT (Vote -> JDK)