>>Thanks to all for your advice... I did actually mean IDE, Eclipse appears to
>>be a good start...
[quoted text clipped - 3 lines]
> to come here and ask 'why Eclipse will not [1]?' or
> 'how can I make Eclipse [1]?'.
>>>Thanks to all for your advice... I did actually mean IDE, Eclipse appears to
>>>be a good start...
[quoted text clipped - 6 lines]
> I thought that Gary was the student, not the teacher. Hopefully he is
> not teaching a course when he hasn't "touched Java for a couple of years".
Uggh. I read 'just about to start a course in' as meaning
the OP was teaching it.
> I would recommend using BlueJ in this course, which he said was about
> data structures and algorithms in Java. If the focus is on data
> structures and algorithms you don't want to add the burden of using the
> command line tools.
That is (endlessly) debatable(*). Not what the OP wants, but
that which works best.
So, Dale.. When the OP pops back in to descibe how 'their IDE'
will not compile a packaged class, are you going to jump in
to guide them as to which menu and option of their IDE to tweak?
* Because if you cannot provide that assurance, the approach of
using the tools that the audience are familiar with, will probably
best suit a person who comes to usenet for advice..

Signature
Andrew Thompson
physci.org 1point1c.org javasaver.com lensescapes.com athompson.info
Bigfoot's Choice
Dale King - 23 Jul 2005 13:56 GMT
>>>>Thanks to all for your advice... I did actually mean IDE, Eclipse appears to
>>>>be a good start...
[quoted text clipped - 14 lines]
>>structures and algorithms you don't want to add the burden of using the
>>command line tools.
Uggh. Somehow I left off the part about "If he were teaching the
course...". I was saying that the best tool for a teacher in a course
focussed on data structures and algorithms would be BlueJ.
> That is (endlessly) debatable(*).
It is certainly endlessly debated, but not in my mind debatable ;-)
The argument that always comes up in these debates is the notion that it
is important to learn how to invoke the command line tools. That is not
valid in a course that is about data structures not Java programming.
You don't care in that course if they learn how to invoke the command
line tools you care if they understand how a heap works and how
quicksort works.
> Not what the OP wants, but that which works best.
Well Gary did eventually say he wanted an IDE. But we are talking
hypothetical here since I was referring to the teacher of a course.
> So, Dale.. When the OP pops back in to descibe how 'their IDE'
> will not compile a packaged class, are you going to jump in
[quoted text clipped - 3 lines]
> using the tools that the audience are familiar with, will probably
> best suit a person who comes to usenet for advice..
I assume your response is based on my not clearly saying that I was
referring to the teacher of the course and not the student. If the
teacher cannot handle such questions then they are not qualified to
teach the course.
And that is the reason why I would recommend BlueJ for this. There is
nothing to tweak for this. You simply hit the compile button.
If a student has the expertise to use a different tool then they can,
but then they are responsible for supporting it. I was addressing the
tool a teacher would use as the standard tool for a course.

Signature
Dale King
Andrew Thompson - 23 Jul 2005 15:36 GMT
(IDE/comand line knowledge of Java tools)
> ..That is not
> valid in a course that is about data structures not Java programming.
Good point.
<stubbornly>
My attitude of "don't come here for IDE advice" stands though.
</stubbornly>

Signature
Andrew Thompson
physci.org 1point1c.org javasaver.com lensescapes.com athompson.info
Soon To Be A Major Religion
Thomas Weidenfeller - 25 Jul 2005 09:49 GMT
> So, Dale.. When the OP pops back in to descibe how 'their IDE'
> will not compile a packaged class, are you going to jump in
[quoted text clipped - 3 lines]
> using the tools that the audience are familiar with, will probably
> best suit a person who comes to usenet for advice..
I guess it is known that I am also in the "know your tools" fraction,
and think that it is a good idea to know how the command line tools (and
the classpath) work.
But, I think it is justifiable to recommend BlueJ to students. Last time
I looked at that IDE it was so self-contained that it will really not
come to student's minds to think about packaging, building jars, "making
exes", or other stuff like this. In BlueJ you twiddle with your objects
and source code, and that's it. You don't even get to see a "static void
main(String args[])" if you don't want to.
/Thomas

Signature
The comp.lang.java.gui FAQ:
ftp://ftp.cs.uu.nl/pub/NEWS.ANSWERS/computer-lang/java/gui/faq
http://www.uni-giessen.de/faq/archiv/computer-lang.java.gui.faq/
Tim Tyler - 27 Jul 2005 10:07 GMT
Thomas Weidenfeller <nobody@ericsson.invalid> wrote or quoted:
> But, I think it is justifiable to recommend BlueJ to students. Last time
> I looked at that IDE it was so self-contained that it will really not
> come to student's minds to think about packaging, building jars, "making
> exes", or other stuff like this. In BlueJ you twiddle with your objects
> and source code, and that's it. You don't even get to see a "static void
> main(String args[])" if you don't want to.
It sounds like a good way of learning OOP - but maybe not such a good
way of learning Java.
...and if learning OOP is the goal, why start with a language like
Java in the first place?
Java hasn't yet managed to embrace the idea of making everything an
object - surely a pretty basic OO concept.

Signature
__________
|im |yler http://timtyler.org/ tim@tt1lock.org Remove lock to reply.
Dale King - 27 Jul 2005 13:13 GMT
>> So, Dale.. When the OP pops back in to descibe how 'their IDE'
>> will not compile a packaged class, are you going to jump in to guide
[quoted text clipped - 7 lines]
> and think that it is a good idea to know how the command line tools (and
> the classpath) work.
Well in this case we were talking about a course in data structures and
algorithms. Teaching the command line tools is not a goal of such a
course and not relevant. But let's ignore that and say it is truly a
course on Java programming.
I am in the "know your language then know your tools" faction, because
that is the order that makes sense. You can't know the tools unless (and
until) you know the language. Starting newbies out on an IDE does not
mean that you never teach them the comand line tools. It only means you
teach them the language first so that they will be able to understand
what you are talking about when you teach them the tools.

Signature
Dale King