Thread: I'd like to do this but am totally new to working with a GUI

I don't like the way Java IDE's handle input and output. It shows at the bottom in an output window which is fine for programs that only work with output. But when you write code to do input, you will see the cursor placed at the wrong spot in the window which looks quite bad.

So someone suggested to me awhile back that what I could do is make a window (GUI) that would be used to show the output of my program. I would also use this window to handle user input in case I wrote a program for that.

I'm thinking along the simple lines of a window that would have two text boxes in it.

The top text box would be used for user input (like if I asked the user to enter an integer he would enter it there).

The bottom box would be used to show the results of the final program.

Or maybe I could design two windows. One to be used if the program only works with output, and the other window to be used if input and output are used.

But I have no experience in making a GUI.

I was thinking maybe I could go on YouTube and get the basic code to draw a window, and figure out how to add a text box. Then I imagine I would need to place all this code in a method which would also be used in every program I write. I would be using over and over.

So am I on the right track here and can you start me out?

Originally Posted by John Joe

There are no text box in JAVA GUI. It is called JTextField.

Who cares what they're called? It's the same thing.

I will take this opportunity to say that of all the forums I have used over my entire computer life, programming forums are the worst by far. For whatever reason programmers seem to be the most sarcastic and nasty and otherwise less than helpful people across the internet.

JTextField or TextBox. Same thing. Doesn't matter what you call it. Car? Vehicle?

You did not help me in giving me any useful info concerning my question.

Perhaps you programmers who populate forums should learn a few things also. Like NOT making assumptions. NOT making the FALSE assumption that the reader knows what you are referring to. That assumption is almost always FALSE. If I was to tell someone who wants to learn how to play guitar that he needs to develop an economical picking hand he would not have a clue as to what I meant.

Should I assume that my student knows how to tune his guitar? Should I assume that he knows the three types of augmented sixth chords? Should I assume that he knows how to hold his pick? Should I tell him to do research on Google to solve these problems?

I don't think so. That would be very poor advice and even worse teaching. In effect I have done nothing for him.

The same holds true for all you programmers out there.

Get a clue.

I asked a specific question. Who cares what the text box is called. It's still a text box no matter how you look at it.