blocks|key|2978101|text|由于关于什么是“最佳实践”似乎存在一些争论，我将给出我发现的最适合我的方法，以及我的推理：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2978102|2978103|每个窗口都应该扩展JFrame或JDialog+(取决于窗口类型)。这使得控制窗口的属性变得很容易，而不需要每次都指定特定的对象。不过，这是更一般的情况，因为我知道这两种方法都可以做到。--|ordered-list-item|2978104|2978105|2978106|+main()方法应该在单独的类中。这增加了在其他地方使用窗口类的可能性，因为它们不绑定到特定的实现。从技术上讲，这没有什么不同，但应用程序启动代码不属于窗口。|offset|length|style|CODE|2978107|2978108|2978109|侦听器应该在匿名内部类中。您的顶级类不应实现任何侦听器。这可以防止诸如从任何地方调用侦听器方法之类的黑客攻击，而不是从它们所附加到的对象。|2978110|2978111|下面是一个简单的应用程序，其中包含一个框架来演示这些实践：|2978112|public+class+Main+{
++++public+static+void+main(String[]+args)+{
++++++++final+String+text+=+args[0];
++++++++SwingUtilities.invokeLater(new+Runnable()+{
++++++++++++@Override
++++++++++++public+void+run()+{
++++++++++++++++final+MyWindow+wnd+=+new+MyWindow(text);
++++++++++++++++wnd.setVisible(true);
++++++++++++}
++++++++});
++++}
}

public+class+MyWindow+extends+JFrame+{
++++public+MyWindow(String+text)+{
++++++++super("My+Window");

++++++++setDefaultCloseOperation(WindowConstants.DO_NOTHING_ON_CLOSE);
++++++++addWindowListener(new+WindowAdapter()+{
++++++++++++@Override
++++++++++++public+void+windowClosing(WindowEvent+e)+{
++++++++++++++++MyWindow.this.setVisible(false);
++++++++++++++++MyWindow.this.dispose();
++++++++++++}
++++++++});

++++++++final+JButton+btn+=+new+JButton(text);
++++++++btn.addActionListener(new+ActionListener()+{
++++++++++++@Override
++++++++++++public+void+actionPerformed(ActionEvent+e)+{
++++++++++++++++JOptionPane.showMessageDialog(MyWindow.this,+"Button+Pressed",+"Hey",+JOptionPane.INFORMATION_MESSAGE);
++++++++++++}
++++++++});

++++++++setLayout(new+FlowLayout());
++++++++add(btn);
++++++++pack();
++++}
}|code-block|syntax|javascript|2978113|entityMap^0|0|0|0|0|0|1|6|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|11|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|12|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|13|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|14|8|@]|9|@]|A|$]]|$1|G|3|-4|5|6|7|15|8|@]|9|@]|A|$]]|$1|H|3|I|5|E|7|16|8|@$J|17|K|18|L|M]]|9|@]|A|$]]|$1|N|3|-4|5|6|7|19|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|1A|8|@]|9|@]|A|$]]|$1|P|3|Q|5|E|7|1B|8|@]|9|@]|A|$]]|$1|R|3|-4|5|6|7|1C|8|@]|9|@]|A|$]]|$1|S|3|T|5|6|7|1D|8|@]|9|@]|A|$]]|$1|U|3|V|5|W|7|1E|8|@]|9|@]|A|$X|Y]]|$1|Z|3|-4|5|6|7|1F|8|@]|9|@]|A|$]]]|10|$]]

Since there seems to be some argument about what constitutes "best practices", I'll give you what I have found works best for me, and my reasoning:

1.
Each window should extend either JFrame or JDialog (depending on the type of window). This makes it easy to control the properties of the window without specifying a specific object every time. This is more of the general case, though, as I have been known to do it both ways.

2.
The <code>main()</code> method should be in a separate class. This increases the likelihood of being able to use your window classes elsewhere, as they are not tied to specific implementations. Technically it doesn't make a difference, but application startup code just doesn't belong in a window.

3.
Listeners should be in anonymous inner classes. Your top-level class should not implement any listeners. This prevents hacks like calling the listener methods from anywhere except the object to which they are attached.

Here is a simple application with a single frame to demonstrate these practices:

<pre><code>public class Main {
 public static void main(String[] args) {
 final String text = args[0];
 SwingUtilities.invokeLater(new Runnable() {
 @Override
 public void run() {
 final MyWindow wnd = new MyWindow(text);
 wnd.setVisible(true);
 }
 });
 }
}

public class MyWindow extends JFrame {
 public MyWindow(String text) {
 super("My Window");

 setDefaultCloseOperation(WindowConstants.DO_NOTHING_ON_CLOSE);
 addWindowListener(new WindowAdapter() {
 @Override
 public void windowClosing(WindowEvent e) {
 MyWindow.this.setVisible(false);
 MyWindow.this.dispose();
 }
 });

 final JButton btn = new JButton(text);
 btn.addActionListener(new ActionListener() {
 @Override
 public void actionPerformed(ActionEvent e) {
 JOptionPane.showMessageDialog(MyWindow.this, "Button Pressed", "Hey", JOptionPane.INFORMATION_MESSAGE);
 }
 });

 setLayout(new FlowLayout());
 add(btn);
 pack();
 }
}
</code></pre>

blocks|key|3191896|text|我同意all+of+Jonathan's+points的观点。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3191897|3191898|blockquote|3191899|3191900|3191901|每个窗口都应该扩展JFrame或JDialog...|ordered-list-item|3191902|+main()方法应该在单独的class...|3191903|Listeners中应该在匿名内部类中...|3191904|3191905|我还想补充以下几点：|3191906|3191907|明智地使用了GridBagLayout+(GBL)。是一个强大的布局管理器，很难学习，但相当powerful.|3191908|Consider手工编写所有的用户界面。我个人并不喜欢由可视化编辑器生成的代码。但是，尽管如此，我已经有几年没有使用可视化编辑器了(2000年左右)。在这一点上，它们可能更好。|3191909|明智地使用了JPanels。查看您的ui，确定哪些组件应在屏幕大小更改时具有相同的行为，然后在JPanel上将这些组件组合在一起。考虑在JPanels中使用JPanels来获得正确的大小调整行为。|3191910|3191911|在让组件处理事件方面，我通常会采取与Jonathan略有不同的方法，但我相信他的方法比我的方法更简洁。|3191912|另外，还要学习MVC和分层架构的使用。最好不要把UI和业务逻辑混在一起。|3191913|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/a/5474531/53897^0|3|O|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|1C|8|@]|9|@$A|1D|B|1E|1|1F]]|C|$]]|$1|D|3|-4|5|6|7|1G|8|@]|9|@]|C|$]]|$1|E|3|-4|5|F|7|1H|8|@]|9|@]|C|$]]|$1|G|3|-4|5|6|7|1I|8|@]|9|@]|C|$]]|$1|H|3|-4|5|6|7|1J|8|@]|9|@]|C|$]]|$1|I|3|J|5|K|7|1K|8|@]|9|@]|C|$]]|$1|L|3|M|5|K|7|1L|8|@]|9|@]|C|$]]|$1|N|3|O|5|K|7|1M|8|@]|9|@]|C|$]]|$1|P|3|-4|5|6|7|1N|8|@]|9|@]|C|$]]|$1|Q|3|R|5|6|7|1O|8|@]|9|@]|C|$]]|$1|S|3|-4|5|6|7|1P|8|@]|9|@]|C|$]]|$1|T|3|U|5|K|7|1Q|8|@]|9|@]|C|$]]|$1|V|3|W|5|K|7|1R|8|@]|9|@]|C|$]]|$1|X|3|Y|5|K|7|1S|8|@]|9|@]|C|$]]|$1|Z|3|-4|5|6|7|1T|8|@]|9|@]|C|$]]|$1|10|3|11|5|6|7|1U|8|@]|9|@]|C|$]]|$1|12|3|13|5|6|7|1V|8|@]|9|@]|C|$]]|$1|14|3|-4|5|6|7|1W|8|@]|9|@]|C|$]]]|15|$16|$5|17|18|19|C|$1A|1B]]]]

I agree with <a href="https://stackoverflow.com/a/5474531/53897">all of Jonathan's points</a>.

<blockquote>
 <ol>
 <li>Each window should extend either JFrame or JDialog...</li>
 <li>The main() method should be in a separate class...</li>
 <li>Listeners should be in anonymous inner classes...</li>
 </ol>
</blockquote>

I would also like to add the following:

<ol start="4">
<li>Use GridBagLayout (GBL) judiciously. GBL is a powerful Layout Manager, difficult to learn, but quite powerful.</li>
<li>Consider hand coding all your UI. I'm personally not a fan of the code that is produced by visual editors. But, with that said I have not used a visual editor in several years (2000ish). They might be better at this point.</li>
<li>Use JPanels judiciously. Look at your ui and determine which components should behave the same as the screen size changes and then group those components together on a JPanel. Consider using JPanels inside of JPanels to get your correct resizing behavior.</li>
</ol>

I normally take a slightly different approach on having my components handle events then Jonathan does, but I believe his approach is a bit cleaner then mine.

Also, really study the use of MVC and Layered Architecture. It is truly best not to be mixing UI and Business Logic together.

As a contrast to <a href="https://stackoverflow.com/questions/90813/best-practices-principles-for-gui-design">this wiki</a>, I am looking for the proper way to implement Swing GUI controls from a coding standpoint.

I have been on a quest to learn Java and its GUI tools but I find internet tutorial after internet tutorial that throws everything in <code>main</code> and I know this isn't right.

I've also tried RAD systems like Netbeans and other "visual" editors but by the time I get to coding I've got a heap of code that I don't know half of what it does, so I'm intent on learning to hand code swing, and I know the basic controls and layout, but want to do it the right way.

Is there a model or standard I'm missing?

example questions...

do I extend JFrame and create my own frame object? (I would assume yes)

do I encapsulate the main menu inside that frame object? or do I create its own? etc...

How to I separate "View" logic from "Application" logic?

Basically, I'm looking for what the industry standard is, on how to organize GUI code.

Java/Swing GUI best practices (from a code standpoint)

Java

与形成对比的是，我正在从编码的角度寻找实现Swing控件的合适方法。我一直在寻求学习Java和它的图形用户界面工具，但是我发现互联网教程一个接一个地使用main，我知道这是不正确的。我也尝试过像Netbeans和其他“可视化”编辑器这样的RAD系统，但是当我开始编码的时候，我已经有了一堆代码，我不知道它做了什么，所以我...

问Java/Swing GUI最佳实践(从代码的角度)
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Java/Swing GUI最佳实践(从代码的角度)EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Java/Swing GUI最佳实践(从代码的角度)
EN