How to start editing a Jframe by hand and continue the final adjustments by the Netbeans "dashboard"?

Asked

Viewed 372 times

0

I was able to write the code or generate a new javaswing file + JFrame, but would like to do writing the code and continue editing with the "dashboard" without adding a "new file.

  • You want to know how to create a jframe without using the netbeans editor]?

  • I don’t understand your question. I don’t understand what you’re trying to do. I could explain it better?

  • Colleague Articuno explained well what I wanted to ask: "From what I understand, you intend to create Jframe from scratch and continue editing using the netbeans Gui-Uilder tool,(...)"

1 answer

2


From what I understand, you intend to create the JFrame from scratch at hand and continue editing using the tool Gui-Builder netbeans, and this may not be as simple as netbeans creates a file .form, with xml data, where it stores all the configuration needed for it to render the screen. Creating at hand, the tool will not know how to render, so it will not open a class created by you.

Not to mention that the screen creator has a feature when creating screens, which is the fact that he uses one of the most complicated layout managers to maintain, which is the Grouplayout, and you might want to choose to merge managers or use others that optimize coding, and the tool won’t know how to handle them.

The screen creation tool is a facilitator for those who do not want to waste time creating designer in "command line", this is quite exhausting when you have deadlines and a complicated business rule to develop, then you need to decide if you want to hack this step and use the tool or if you want to venture out and do it manually.

In the case of window Builder, which is the similar but eclipse-compatible tool, it can already identify hand-created screens. A counter to this tool is that it is not as automated as the one in netbeans, it leaves everything else to the programmer’s control.

Still, it might be a good alternative, because this netbeans tool will hold you back when you need to maintain your screen, because with the amount of code it creates, it’s almost impossible to maintain a more complex interface, and the window Builder gives you more freedom between programming using the drag 'n drop of the tool and manually tamper with the code of the screen design, besides making it possible to see the rendering of the interface in real time, without "soiling" too much the code and without creating extra files.

  • Exactly, I thought this --> "From what I understand, you intend to create Jframe from scratch and continue editing using the netbeans Gui-Uilder tool,"

  • @LUIZ less badly, so the answer was right :D

  • In the future I will search more about windows Builder. Thanks for the help!

Browser other questions tagged

You are not signed in. Login or sign up in order to post.