From: giddy on
hi,

I'm a really good C# programmer and I've been programming for quite
sometime with MS stuff.

I've decided I need to know a little JAVA, i think i've already put a
post in this forum for books but now i need help with NetBeans

Firstly, I had quite some trouble installing it and now If i open
desktop application projects I get reference problems,

Also, New Project-->Java Desktop Application _does_not_exist on my
netbeans, its not there! I have NetBeans 6.1

Also, there are some other reference problems again from time to time,
what exactly is wrong? I can see that NetBeans itself has packages
starting with the word org and some more packages under
\platform8\modules\ext

i've installed the latest JDK so how do i end up having reference
problems? Is there something wrong with netbeans or JDK?

Thanks so much
Gideon
From: giddy on
[July-20-2008 11:55:37 PM]
Very precisely when i open a GUI project i got:

Problem: The project uses a class library called "swing-app-
framework", but this class library was not found.
Solution: Click Resolve to open the Library Manager and create a new
class library called "swing-app-

[July-20-2008 12:20:42 PM]
JEEZ! I finally got it!

I check tools->Plugins->Installed-> and Just activated GUI builder!!
UGH!

Already started to NOT like Java little!


Hope this helps someone.

Gideon
From: Mark Space on
giddy wrote:

> Firstly, I had quite some trouble installing it and now If i open
> desktop application projects I get reference problems,

I'm pretty sure Desktop Applications are still experimental. You want
the regular old Java Application.

What sorts of missing references do you get? Most times you can solve
them by adding a .jar file as a library to the project. If you are
using build scripts, NetBeans may not pick up the location of the .jar
or the need for it.

>
> Also, New Project-->Java Desktop Application _does_not_exist on my
> netbeans, its not there! I have NetBeans 6.1

It's there on mine, but I never use it. Use Java Application.

However, there could be other issue because of the problems you had
during installation.

>
> Also, there are some other reference problems again from time to time,
> what exactly is wrong? I can see that NetBeans itself has packages

We'll need to see what the actual error message is to diagnose this further.
From: Arne Vajhøj on
giddy wrote:
> Firstly, I had quite some trouble installing it and now If i open
> desktop application projects I get reference problems,

Please provide more information than just "reference problems" !

> Also, New Project-->Java Desktop Application _does_not_exist on my
> netbeans, its not there! I have NetBeans 6.1

It is in mine.

> Also, there are some other reference problems again from time to time,
> what exactly is wrong? I can see that NetBeans itself has packages
> starting with the word org and some more packages under
> \platform8\modules\ext

Again: much more details is needed to troubleshoot.

Arne
From: Lew on
giddy wrote:
>> Firstly, I had quite some trouble installing it and now If i open
>> desktop application projects I get reference problems,

Arne Vajhøj wrote:
> Please provide more information than just "reference problems" !

giddy wrote:
>> Also, New Project-->Java Desktop Application _does_not_exist on my
>> netbeans, its not there! I have NetBeans 6.1

Arne Vajhøj wrote:
> It is in mine.

Like the other respondents who have NB 6.1, I see that option in my installation.

Arne Vajhøj wrote:
> Again: much more details is needed to troubleshoot.

giddy wrote:
>> JEEZ! I finally got it!
>>
>> I check tools->Plugins->Installed-> and Just activated GUI builder!!
>> UGH!

Hmm, a simple, straightforward activation procedure in the IDE. I can see how
that disgusted you.

Given that the rest of us didn't have to do that step, though, I wonder if
there might have been some procedural error in the installation of NetBeans at
the start.

RedGrittyBrick:
> NetBeans != Java. I write Java using Eclipse. I would not blame the Java
> language for any problems I had using the Eclipse IDE.

If the IDEs are too much trouble, and they won't be later, I promise, then
just work with the command line. That's a good way to learn Java anyway.

One should make it a rule when first learning any new discipline, such as Java
programming, not to judge the subject emotionally until one has actually
learned it. Most of the time the problem will turn out to have been
unfamiliarity with the tools, not a flaw in the tools themselves. Blaming the
tools for what's really due to one's own lack of knowledge will impede the
acquisition of that knowledge.

--
Lew