Craig Or

John de Michele wrote:Craig:

Definitely start small. I know there is a temptation to do a few code examples and feel like you can code a huge project. Avoid this temptation like the plague. You'll end up frustrated, or worse, you'll give up on programming. The fact that you're asking this question is good, but it illustrates how far you have to go. My suggestion would be to find a small project that interests you, and work on it until you complete it. Maybe it'll be a card game, or a text-based RSS reader. Once you've gotten a few, smaller projects under your belt, then is the time to attempt to tackle something bigger.

John.

Well, I appreciate the thoughts John (and everyone). I'm actually trying to read first before I drive in so although I could use the card game as a project, I was really hoping to get the "book smarts" first. But I'll give it a try I have a couple of things I want to build but they really are small (1 main form and one sub form with some buttons that calculate entires).

Craig

So I'm a total newbie to Java. In fact, outside of the infamous "Hello World" app, I haven't written a single line of code. Right now I am reading. So I'm starting to get the concepts of objects, classes. polymorphism, inheritance, messaging, and OOP as some level of understanding. What I don't understand is this:

In the world of OOP how do you structure an application? Do I start my "public static void main(String[] args) {" blah blah blah and then put all my objects in that? I want to build a desk top application. Do I start by building my GUI and then put all my objects, etc in that?

I'm not really looking for an answer here in the forums but if someone could point me to a web site, tutorial, book, what ever that does a good job of explaining how to structurally lay out the code, that would be much appreciated.

Can you tell how much of a greenhorn I am? LOL