[cheesewheels99]

cewy

[Mike0001]

*Monty Python Moment brought on by Spamalot*

"We're Knights of the Round Table
We dance whene'er we're able
We do routines and chorus scenes
With footwork impeccable

We dine well here in Camelot
We eat ham and jam and Spam a lot

We're Knights of the Round Table
Our shows are formidable
But many times we're given rhymes
That are quite unsingable

We're opera-mad in Camelot
We sing from the diaphragm a lo-o-o-o-t

In war we're tough and able
Quite indefatigable
Between our quests, we sequin vests
And impersonate Clark Gable

It's a busy life in Camelot
I have to push the pram a lot"

[Mike0001]

Originally Posted by Cew27

im not sure there a few ide's i used net beans but i am using jcreator as the book im using uses that but i may switch over depending
i cant remember does netbeans have an interface editor

By interface do you mean GUI?

http://www.netbeans.org/features/java/swing.html

[Cew27]

what the hell ? how am i spamming cheese this is my thread and it is a useful one to help ME with computer problems not do your good Charlotte polls!

[ComputerGuy]

Cew what book are you learning from? Is it any good?


CG

[Cew27]

i am learning from a book, it is brilliant and easy to understand i havent had any problem up until the packages
add me on msn if you want to discuss this
Cew27@violentvomit.net

[Mike0001]

With packages, you run into access and privacy issues for the first time. With everything in the same folder, everything has access by default to everything else, exactly what you don't want in OOP.

Think about this when you are programming: if I change one class file, how many other class files must I re-compile to get my program working? If it is more than a few, then your project is too tightly bound and will be difficult to maintain.

If your book uses things like

a.b=x;

x=a.b;

outside the "a" class, throw it away! Always:

a.setB(x);

x=a.getB();

or changing the data structure for a will screw up everything else.

interfaces are very important in isolating classes too. If one class A needs access to another class B, try to do that via an interface that B implements, that way when you change A only that interface is recompiled, not B. Then A + that interface is portable to another application.

[dr john]

I didn't really like Java, despite coming top of the class in it at uni. But when they told us to try out the Eclipse IDE (to test it for use as the default for the coming year), I spent two hours trying to get the hang of it, and by the end of the day had done twice as much successful coding compared to if I'd stayed in the text editor we were using! (We used TextPad, which can be linked to the Java compiler). Hated NetBeans, as did everyone else in the class. Those who tried Eclipse just loved using it. It rocks!

[Cew27]

what is so good about eclipse??

[Mike0001]

Netbeans, Eclipse, Textpad, I have tried them all but mostly used Textpad. (That way I was forced to understand the language.) Netbeans is on v6 now and looking good though.

Funny, but I was more productive with Textpad than others who used IDEs! My colleagues who used Eclipse wished they could use Netbeans...