I hardly use the resource perspective, just stick to the Java persepctive as it does everything I need when editing (I also use the debug perspective for debugging). I suppose the resource perspective is there as a filesystem-only view of the project without any language specific stuff. As you say it doesn't do any Java stuff.
A library in Eclipse is just a collection of jars and classes that you can use in multiple projects. They're useful for defining libraries of related stuff, so when you create a new project you can just reference a library instead of importing all the jars individually, handy if you create a lot of projects. E.g. I might define a library named "common" that inculdes junit.jar and ant.jar.
I'm not sure about the different ways to add a project to version control, I only know the one way. Do you have an example of a way that doesn't work?
WRT creating a new perspective, just show the views that you want and dock them where you want and do Window -> Save Perspective As to create a perspective that you can switch to when you want.
After downloading the JDK and Eclipse and setting the CLASSPATH and JAVA_HOME vars, all I had to do to get Eclipse running was type./eclipse.
You don't even have to set CLASSPATH and JAVA_HOME. As long as there is a usable java executable in the path, Eclipse will Just Work (tm). I have no idea how it could be difficult to set up, just unzip the downloaded archive and go. No install. Nothing. Zilch. Nada.
Eclipse is real fussy about existing/new directories, and yes I have generated projects to encompass collections of.java files I had previously maintained with a text editor and compiled with javac, but I can never remember from one time to the next how to do it.
Once you've defined a project and copied over your source files, just go to Project -> Properties -> Source and include/exlclude your source directories as required. Choose a build directory (or not) and Eclipse will build your project in the background when you click OK. Fussy? Hardly.
When I was starting with Eclipse I had little problem figuring out stuff. Now it's like second nature.
E.g. how many ways are there to create a new project and connect it to a CVS repository? And why does only ONE of those many ways work correctly?
Well, creating a new project is as simple as File -> New -> Project or File -> Import to import an existing one. Connecting to CVS is as simple as (right click on project) -> Team -> Share project, etc.
The way how classpathes and libraries work is a compete mess. Why can't it be simple as saying: put this *.jar into classpath?
Copy the Jar into your lib directory (or not) and choose Project -> Properties -> Libraries -> Add Jars/External Jars. Is that not simple enough? You can even define "Libraries" or buches of Jars to save time importing them to multiple projects.
As I mentioned in the other post: why does every plugin need its own perspective?
A perspective is simply a configuration of views (dockable UI elements). Perspectives provide an easy way to switch to different layouts. Since you can't fit everything on screen at once, perspectives seem like an easy and logical way to manage the problem. If you don't like the built in perspectives or the ones that come with your plugins, you can easily define your own. I tend to do most things within the Java perspective, switching to the debug perspective for debugging.
Most of the stuff simply should be done in the "navigator" where you see "files". Ther eis no special "java package view" needed, but I'm forced to use it often because a lot of commands are only there.
Not sure I agree with this but you *can* do everything from the Resource perspective if you configure it with views you need.
Basically the only 2 perspectives beyond "navigator" making sense are CVS/version control and debugging.
I would say the Java perspective is more useful than the Resource perspective since it has all the Java refactoring stuff in addition to being able to create/delete java files.
I wan't all commands I can do on a Java "class" in the "file navigator"
I find you can do pretty much everything you need from the Java perspective, e.g. you can create, rename, repackage and delete Java classes. If you need more flexibility there's a bash shell.
Eclipse does very little in terms of creating filesystems, you can configure your project however you want, or create a project from any existing code, no matters how it is structured in terms of files. The only files it creates are.project and.classpath.
I use an Ant build for building and packaging deliverables. Eclipse compiles my code as I work (the Eclipse build Just Works (tm)) and the hot code replacement means I don't have to repackage using the Ant script until I release to test. Whichever way you look it's a win-win situation.
I had problems because my main Java directory was defined as a "folder" instead of a "source folder".
Sorry but this is sooo easy to figure out, you go Project -> Properties -> Source -> Add folder, and if you really couldn't figure this out you could always try reading the fucking manual.
you don't get any kind of useful error message
Yeah, probably because it's NOT AN ERROR.
As if Eclipse doesn't make things easy anough already, asshats have to come along complaining it's too hard to use. It's about the most easy and intuitive Java IDE ever.
There's also a trend to employing developers with more than one language, certainly in the UK - it's no longer good enough to "just" be a C++ whizz, you need C and Java or Perl and 10 other core skills. Perhaps the higher level jobs are fewer and further between, but there are a wealth of jobs for people with intermediate skills in a few areas.
If you don't have to pay highway taxes, vehicle registration, licensing permits, emissions testing, or anything else, then stay off the highways.
Agreed that cycling on highways is a bad idea, but on other roads... A few counter arguments - many cyclists also own cars (I do) and so pay the aforementioned taxes. Not sure about the US but here in the UK "road tax" doesn't actually pay for roads, which are usually maintained by local authorities, at their expense. Emissions testing a bicicyle? Is farting considered hazardous to the environment now? Licensing and registration don't really apply to bicycles. As a cyclist, I've heard these arguments before, but really there are many good reasons to cycle such as health, congestion, pollution, etc.
Slashdot Mirror
Uhhh - he meant that only an American company would spend this much to not look like they're from the country they are from.
There's an saying that goes "if you can't do it, teach it" and you sound bitter about people who work in IT ...
I'm with you. Do what interests you not what someone else wants you to do. If you need calculus later on, go and buy a book and learn it.
Most humour is based on truth.
I hardly use the resource perspective, just stick to the Java persepctive as it does everything I need when editing (I also use the debug perspective for debugging). I suppose the resource perspective is there as a filesystem-only view of the project without any language specific stuff. As you say it doesn't do any Java stuff.
A library in Eclipse is just a collection of jars and classes that you can use in multiple projects. They're useful for defining libraries of related stuff, so when you create a new project you can just reference a library instead of importing all the jars individually, handy if you create a lot of projects. E.g. I might define a library named "common" that inculdes junit.jar and ant.jar.
I'm not sure about the different ways to add a project to version control, I only know the one way. Do you have an example of a way that doesn't work?
WRT creating a new perspective, just show the views that you want and dock them where you want and do Window -> Save Perspective As to create a perspective that you can switch to when you want.
ROFL! Where are my mod points when I need them?
I just re-read that post and it sounds very harsh. Please don't take offence I'm just having a bad day :-/
Eclipse does very little in terms of creating filesystems, you can configure your project however you want, or create a project from any existing code, no matters how it is structured in terms of files. The only files it creates are .project and .classpath.
I use an Ant build for building and packaging deliverables. Eclipse compiles my code as I work (the Eclipse build Just Works (tm)) and the hot code replacement means I don't have to repackage using the Ant script until I release to test. Whichever way you look it's a win-win situation.
There's also a trend to employing developers with more than one language, certainly in the UK - it's no longer good enough to "just" be a C++ whizz, you need C and Java or Perl and 10 other core skills. Perhaps the higher level jobs are fewer and further between, but there are a wealth of jobs for people with intermediate skills in a few areas.
Common problems include casting errors, off-by-one errors, and array index errors. Just because code compiles does not mean it will work.
So you never did anything mildly stupid when you were 18? At 18 he may be legally an adult, but emotionally still immature. Give the kid a break.
What he did was wrong but it doesn't justify being thrown in jail. To call it a felony is just ridiculous.