That's not the part I'm worrying about... it's the "not understanding part of the specification" bit I'm worrying about. I can do quite a bit of this thing, construct necessary classes, doing about 25% of the gui... There's the JPanel's paintComponent, which I've no idea about. There's something about a custom class called Document and a method used to associate a JPanel (or its subclass) with an instance of Document which I also have no idea about. other than that. It's cool.
Actually... nothing for me is "cool" with this piece of work.
oh dear, I just haven't understood a sentence in this post.
oh dear, I just haven't understood a sentence in this post.
I have since made progress on my Java work. Still don't know what the "Document" is. But at least my thing is drawing random rectangles all over the place.
I have since made progress on my Java work. Still don't know what the "Document" is. But at least my thing is drawing random rectangles all over the place.
You can ignore me when I talk about java.
Oh i see, I will do exactly that.
(oh wait, I still have to read it to see whether it is java-related or not? )
I have since made progress on my Java work. Still don't know what the "Document" is. But at least my thing is drawing random rectangles all over the place.
You can ignore me when I talk about java.
My computer woes are greater than yours. gcc is getting very angry with me because I'm using pointers without understanding what the hell I'm doing with them in my thrilling program to compute a basis for the kernel of a matrix over a finite field of a prime number of integers.
Dude, talk to Bjourne, he uses Kcc which is a billion times better than gcc at doing matrices stuff. Besides, compscis don't get taught C++. And I hate pointers.