🚀 go-pugleaf

Oooops, I guess I used just the wrong word to mention
that I would be better to stick to the suggestion to always
store reference in a variable even though you do not
need to do so.

Thanks Hartmut!

And yes, it is really worth using projects when working with
JBuilder since JBuilder uses a project to add its .class files
to the classpath when running the project. (To be precise,
JBuilder adds the 'class' folder of the project to the classpath
when running the project).

Regards,

Marcel



Hartmut wrote:

> Mike,
>
> against the two previous postings,
> it's not necessary in your main method to save the reference of the new
> object in a variable.
> I tried your code, and it works fine!
> You simply made a typical JBuilder newbie mistake:
> JBuilder doesn't know that it shall execute the main method of this class.
>
> I took this way to use your class - not that this would be the way I would
> recommend also for you to work with JBuilder:
> 1) I created a new project
> 2) In this project I created a new application named "uebung_3". JBuilder
> also allows (leads) me to create a frame by this.
> 3) Now i Have an application clas with main method and a JFrame class. Look
> at the code and figure it out - will help you very much!
> 4) Since I wanted to try your class, a combination of main method and frame,
> I deleted the generated Frame, and I replaced the code of the application
> class by your code.
> My class uebung_3 is simply your code, only additional 1 package command at
> the top.
>
> Compiles and executes - all ok.
>
> In fact JBuilder gives you great help, but everything must be in a project,
> and you should let it generate application and frame like I showed you.
>
> Finally: Please follow that advice to call your class Java-typical: Uebung3.
>
> Hope this helps you to get a Java crack.
>
> Regards,
> Hartmut