Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 1 year ago.
Improve this question
I would start a J2SE projects for abuntu OS.
I try both Netbeans GUI builder and Eclipse windowbuilder.
Both of them are good, drag&drop, double-click to create event-handler like VisualStudio.
However i have do a research on Netbeans, someone said:
The second major flaw of Matisse is that it just isn't good enough,
you place the components on the grid, Matisse then creates an XML with
the component's attributes, then generates the java code for the
components on the grid. Seems cool, but then you decide you want to
add a button somewhere in the form or resize a component - this
procedure can cause all of the gui to get mixed up throwing the
adjacent components to different places - fixing it can be a pain in
the neck. Even if you managed to place all of the components where
they should be but manually changed some of the generated netbeans
code - you are in a BIG problem, a problem you might not manage to get
out of unless starting all over.
Is that bug still exist on latest netbeans?
What is Pros. and Cons. between Netbeans GUI builder and Eclipse Windowbuilder?
Im using NetBeans since 6.x and never had such problems. Resizing components, adding some new, even working on the generated code etc. is realy easy and had no problem so far. Moreover NB has a visual debugger and an improved GridBagLayout customizer (both since 7.1).
Didn't use Eclipse Windowbuilder so far, but i guess its capable too. Everyone has it's own criteria for a gui builder. Btw. the author of this article seem very eclipse-focused ("on the best IDE out there - eclipse")
I'm sorry i cant give you an answer like "pro / cons of A, pro / cons of B" - as i said i've never used Eclipse Windowbuilder before. And for me there's no need to do so, i can build a gui with netbeans without problems / very easy / fast (even better than with Visual Studio). For my point of view everything works like i want it :-)
If you used both, maybe there are things you prefer or dislike on one IDE, but the other can do better.
Personally, while WindowBuilder is a pretty powerful tool to use within Eclipse, I find it more clunky (and quite honestly, prefer to write Swing GUIs by hand if this were the only optin)
Matisse is a far better option because of the Grid editors like someone mentioned previously, also I prefer the way Matisse handles event handlers over WindowBuilder. Another thing Matisse does well is that it encorporates more properties into GUI element settings where WindowBuilder goes over a very small list of changeable features (leaving you to dive through a mess of auto-generated code to change a simple property).
Eclipse does have a version of matisse available, though the plugin is not for free (look up myeclipse).
I used both Eclipse and Netbeans,
Eclipse -WindowBuilder is a powerful tool, easy to modifying it. But causes more code problems. Long time after you will get Spagetti-Codes to get solve problem.When it get problem you cant open Desing layer.
Netbeans generates codes much easy, and you can change it but more harder, sometimes you can't. But i dont get any (only a few, my mistakes) any code problems...or etc., if you get a problem about a component; you can too easy to get Default Settings any time.
Note: THAT IS ONLY MY IDEA!
Related
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 6 years ago.
Improve this question
I have heard from my peers on more than one occasion that it is "advised" not to do version controlling of your code from within the IDE where you write it. I have seen them developing on Eclipse, IntelliJ IDEA, etc. but doing version control (in my current scenario - Git) from command-line or standalone clients as opposed to using the corresponding plugins readily available for the IDE.
Though I have used version control plugins in Eclipse and never found any issues, I would like to know what is the general norm and why?
I don't think that there's a general norm. The answer to the question is highly subjective.
I personally don't use any IDE integration (not even a GUI tool, except the builtin ones git gui and gitk) because my experience told me that these tools behave different than the command line version and/or don't provide the full functionality available on the command line:
Does NetBeans ignore my Git pre-commit hook?
Can you interact with the index/staging area with TortoiseGit?
Does TortoiseGit actually make Git a lot easier to use like TortoiseSVN?
Another thing is that your knowledge about your versioning tools is bound to your IDE. Maybe you want to set up some version management for other things than the sources you edit with Eclipse (your dotfiles, for example).
Or one day you switch your IDE, drop Eclipse and start using Visual Studio. Then you don't have to learn only Visual Studio but in addition you need to learn the Git integration in VS too.
I think compared with what I've written above, there are no serious advantages that would legitimate the usage of version control tools from inside the IDE.
So, IMO, it's a bad practice to do version control from inside the IDE and it should always be done from the outside.
You should always try to use the right tool for the job, and that is a personal question so there is no "norm" or "good practice".
In my case I prefer to use a ...
GUI, like Sourcetree, for viewing logs, diffs, staging/discarding lots of files, staging/discarding hunks, etc.
CLI for modifying remotes, squashing commits, pushing, cloning, etc.
Also, if you plan to break out of the box a little bit, it wouldn't hurt to know a little bit about the Git internals.
Those plugins and add-ones tend to sometime do things that otherwise you wouldn't do if you were using the native (CLI?) client.
For example, if you were working with an Eclipse + ClearCase plugin, any change in a file, even adding a new line, will initiate a check-out operation (depending on the configuration).
Specifically for Git, you should be aware of its internals to properly work with it. Using the IDE hides those things from you. In normal trivial operations, it will work. But, when you are facing a source control issue (ugly merge, cherry-picking, rebase conflicts) you will have to go to the CLI to resolve, but then you have no idea what were the actual commands that the IDE ran that got you to this situation in the first place (plus you have no experience with the CLI at that point).
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
Questions asking us to recommend or find a tool, library or favorite off-site resource are off-topic for Stack Overflow as they tend to attract opinionated answers and spam. Instead, describe the problem and what has been done so far to solve it.
Closed 9 years ago.
Improve this question
Looking for links to good information for Eclipse beginners. I've been a c# developer for sometime and I feel like I'm swimming in molasses. I'm especially interested in anything like the snippets functionality and how to use it (for example the prop snippet to create a property)
I'd recommend you start with the tutorials on the "Welcome" screen (automatically shown on first launch, or via Help menu).
After that, a lot of stuff can be discovered by poking around. The built-in help is also quite good, and failing that, just google for it.
Set yourself some goal, and do a bit of research; I've found most stuff fairly easily that way.
As for snippets: I'm not terribly familiar with VS, but I gather they are basically code templates that you can insert and then fill in.
In Eclipse, that would be auto-complete (or "Content Assist"), triggered by Ctrl-Space. Just try it, it's fairly clever. It will offer completions of variable names, functions etc., but will also offer common snippets like creating constructors, public methods etc. E.g. type "public ctrl-spc", and it should offer a template for a public method (try ctrl-space several times to cycle through proposals).
You can also create your own auto-complete code snippets. These are called templates in Eclipse, to be found in the prefs under "Java / Editor / Templatest". Templates can be triggerd in auto-complete by typing the (beginning) of the template's name, then auto-completing.
Have fun!
I was also a VS user for a long time and found Eclipse confusing, requires a lot more configuration to get it up and running first off.
Found this very helpful post on a Google search
http://benpryor.com/blog/2006/03/03/top-10-tips-for-new-eclipse-users/
.
I don't use it often but here are a few things that threw me at first.
Workspaces confused me, there is no exact equivalent in VS, I'd say they are a bit like Solutions. I made the mistake of keeping all my projects in one workspace and after a year of work Eclipse could barely open the workspace.
You don't need to hit 'Build' to compile your code, it keeps compiling in the background so there is always an up to date list of bugs, called problems in Eclipse.
When you run your code in debug all the windows jump about some disappear and lots of strange new ones open. These different layouts are called perspectives. There is a tab bar next to the main tool bar which lets you move between open perspectives or you can close them using the Window menu.
Besides the very good Eclipse tutorials and documentation sleske mentioned here are some other good tutorials and introductions:
IBM tutorial for Visual Studio users - you have to register for reading this tutorial but registration is free and you can download a bunch of really good Eclipse materials
Effective Eclipse - Custom Templates - this article shows you Eclipse's "snippets funcionality" in details
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
I am building a desktop application. Our analysis says it would be better built with a RCP. Should I use the eclipse or netbeans platform to build my application . Some of the factors to consider are
Performance
Look and Feel
Popularity among target users (developers/testers)
License (has to be some FOSS)
The application will be having things like text editor, grid views, block diagrams and graph visualizations.
I already have experience with netbeans development, but learning eclipse won't hurt. any other options would be welcome too.
I've used Eclipse to build an RCP text editors, multiple views and graph diagrams (lacking only the block diagrams you mention). The environment was pretty good as well as the support in the community for getting help (it was my first Eclipse RCP experience - nearly all my questions had been answered at one point or another in the eclipse forums. When not - I got great feedback.)
The platform was pretty lightweight and handled memory well generally speaking. Some problems that you might run into, you'll likely run into on any platform you choose.
I would look at Netbeans. Netbeans is based on Swing while Eclipse uses SWT. Sun has put a lot of effort into Netbeans over the past few years and it's quite good.
There are some tutorials on the Netbeans site for plugins and platform.
http://www.netbeans.org/kb/trails/platform.html
This of course is a bit of a religious question. You will find it debated repeatedly on the web. Here are a couple of interesting threads.
http://www.nabble.com/Choosing-Netbeans-platform-or-Eclipse-RCP-td16012394.html
http://www.javalobby.org/java/forums/t103146.html
My vote is for Netbeans. Many of its shortcomings have been corrected in the 5 and 6 releases. The community is smaller, but certainly just as helpful.
Another option is the Swing Application Framework (JSR-296) which provides a very lightweight framework for building Swing applications. It provides some of the basic plumbing such as an Application context to share data and basic status and worker components. It doesn't provide any complex components, so it may be too lightweight for what you need.
I suggest using Eclipse RCP, as far as I can see, it has many useful aspects like action and command mechanism, Eclipse Forms, data binding, etc. You can use GEF and Zest for graph based visualization and visual editors. Also Window builder is a convenient choice for drag and drop ui creation. Also there are many sources for learning Eclipse4 RCP, vogella.de is a good starting point. cheers...
Eclipse RCP is powerfull. I have used it for one of my projects. Yes It has some bugs but it has lots of documents and it is faster than Netbeans RCP I think.
Do you have to choose only between Eclipse and Netbeans?
I heard Spring is good
Eclipse has bugs especialy with the text editors. Netbeans on the other hand sucks RAM worse that Crysis
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
I have a coworker who is looking to switch from InteilliJ Idea to Eclipse, and is concerned about not knowing the Eclipse set of commands.
I was wondering - would anyone have a link to keyboard mappings that can set Eclipse commands to at least sort of match Idea?
Have you made this switch? Any "gotchas", tips, or info we should be aware of?
Thanks!
I went through the experience myself - and result was a series of articles on my blog:
http://virgo47.wordpress.com/2011/01/30/eclipse-vs-intellij-idea/
http://virgo47.wordpress.com/2011/02/22/from-intellij-idea-to-eclipse-2/
http://virgo47.wordpress.com/2011/03/24/from-intellij-idea-to-eclipse-3/
http://virgo47.wordpress.com/2011/02/28/why-to-synchronize-with-svn-in-eclipse/
http://virgo47.wordpress.com/2011/04/10/from-intellij-idea-to-eclipse-4/
http://virgo47.wordpress.com/2011/06/28/from-intellij-idea-to-eclipse-5/
They are all biased towards Idea (obviously) but full of relevant Idea-Eclipse comparisons, keyboard shortcuts, little stories and observations. In generall, they are both very good IDEs, but if IDEA is 100%, Eclipse is 90%, maybe even 95% - with biggest these differences:
different mindset is needed, Projects, Modules, Workspace may mean different things or are not used at all in one or the other IDE, you have/need Perspectives in Eclipse, not in IDEA, etc...
quality of default Maven/SVN support is better in IDEA (it is also built-in), much smoother and less problems + 3way diff in IDEA is just great, generally Eclipse guys are so scared of merging - and now I understand why
IDEA is far more polished, less graphics glitches and much better default colours for highlighting, etc.
free version of IDEA does NOT have so many things as you can have with Eclipse with all possible free plugins - Eclipse plugin ecosystem is just so big!
IDEA is just way smarter in margin cases when it comes to completion, refactorings, and these other little things where IDEA was the top of the class the whole time since 2000
I was lucky I didn't have to convert in the end because we use Maven projects that work just fine in both IDEs. However I still use Eclipse for other projects (xtext).
Get the plugin from here. It seems easier to install than the one in Bartosz' answer, plus no 404s...
For the lazy: direct link to plugin
Drop the plugin jar in eclipse/plugins folder and restart eclipse. Now in preferences dialog under General > Keys you can find "Intellij Idea" key scheme.
If he definitely want to do this:
http://www.jroller.com/ervines/resource/eclipse-intellij-key-bindings.java
In answer to Bartosz, flash builder is a good reason, until jetbrains comes out with a visual mxml editor.
the direct link posted above is outdated, releases are here: http://code.google.com/p/ideakeyscheme/updates/list
Update: Found this one too: http://www.bharathganesh.com/idea-prefs.php , although it's pretty light on the description.
I could list a bunch of tips, gotchas, etc. because I've made the switch several times. I've tried to make the switch to Eclipse several times but couldn't do it and went back to IntelliJ.
First tip:
Intellj "project" -> Eclipse "workspace"
Intellij "module" -> Eclipse "project"
Second tip:
Eclipse has the concept of "Perspectives" which means it reshuffles around your UI when you're doing different things, like for debugging there's the debug perspective. I don't quite get this, I personally prefer the concept of windows, or the tool windows that dock to the bottom or sides.
I am looking into designing new features for Eclipse-based programming tools, from the requirements/ideas perspective. To really do this quickly, I would like to sketch UI elements without having to code things -- my concern is with the concepts and ideas right now, not the possible later realization. Are there any such graphical sketching tools for Eclipse?
(on a side note, I should also note that I find Eclipse a better idea every day, in the way that you can combine partial systems from very many different sources into a single environment. It really is the future of IDEs, especially for embedded systems. It used to pretty horrible pre-Eclipse-3.0, but now it does seem to work)
WireframeSketcher is a tool that helps quickly create wireframes, mockups and prototypes for desktop, web and mobile applications. It comes both as a standalone version and as a plug-in for Eclipse IDEs. It has some distinctive features like storyboards, components, linking and vector PDF export. Among supported IDEs are are Aptana, Flash Builder, Zend Studio and Rational Application Developer.
(source: wireframesketcher.com)
Incidentally, NetBeans is known for having a really good GUI editor (Matisse), but I realize that you weren't asking about NetBeans :)
I've tried the Visual Editor Project before, but in the past it crashed my instance of Eclipse, and I haven't visited it since.
Jigloo is a new one that I'd like to try out soon.
This is really specific to Eclipse: it is the platform of choice for general IDEs today, and I am looking to sketch out extensions to it. The target programming language is more likely to be raw assembler and C than anything else -- OS, driver, system-level debug.