I just finished the client GUI and found the major Layout settings are difficult to settle components. For example, it is a painstaking to fix components in FlowLayout. GridLayout makes all its children components the same size, sometimes it looks strange since components� sizes should be different from each other. When you resize the window, sometimes components in GridBagLayout could shrink becoming a dot or disappear.
So I decided to use null Layout and setBounds method to do it.
The advantage is that it can fix all components� positions precisely and provide exact size of each component. It also has some weaknesses. Each component must use setBounds method. If you resize the window, all components� sizes don�t change accordingly so I use �setResizable(false)�.
But I heard using pixels to fix components would cause disorder when transplanting the program into another OS. My OS is Windows 2000, so I installed the Cygwin software to mimic Unix Box and test my client GUI on it. I found the program displays the same appearance as in Windows2000. Does it mean that I can safely use setBounds method, which uses pixels to fix all components, or it could be trouble when I run it in pure Unix Box?
Thanks in advance! Regards, Ailsa Cape [ August 23, 2005: Message edited by: Ailsa Cape ]
The Cygwin utilities do not mimic the low level Unix graphics drivers, so you cannot rely on them to give you a true Unix GUI.
This is dangerous as component sizes can differ on different platforms. Take a look at the following three screen dumps from the discussion of this topic in The Sun Certified Java Developer Exam with J2SE 5, Second Edition, all of which were generated by the same source code - only the look and feel was changed. In particular take a look at the button sizes.
what kind of Layout the three screen snapshots above uses.
They were created using the combination of multiple layouts. We used a FlowLayout with left alignment for the data entry field, and FlowLayout with right alignment for the three buttons. These were then combined in a BorderLayout.
Do you mean even if each component uses setBounds method, its size can also differ on different platforms?
Yes. Take a look at the physical button sizes in each of those three graphics - they are physically different sizes.
In this situation, all components will be disorder or simply change zoom scales?
In general the "zoom scale" as you put it will change. Worst case scenario - say you had used the look and feel that created the second diagram. The buttons are physically very small in that (32x20 pixels). If someone then used a different look and feel - say the third option where the buttons are nearly twice the size (61x28 pixels) - you might find that one button obscures another button, rendering your GUI useless.
Combining layouts is a very powerful method way of designing a GUI that can handle different platforms / look and feels / resizing correctly. Here is the code that created those samples:Regards, Andrew
Thanks a lot! I notice many methods in Swing package using pixels to fix size or location, such as JFrame's setSize/setLocation, JTable's setColumnsWidth/setRowHeight and many setBounds methods. Should we all avoid using these methods?
Thanks in advance! Regards, Ailsa Cape [ August 26, 2005: Message edited by: Ailsa Cape ]
There are many reasons why these methods exist, including that prior to having layout managers, graphical components needed to be set in explicit locations (the problems with doing this was one of the major reasons for the development of layout managers). So if you are working with any old code that uses explicit positioning then you will want to be able to explicitly position your new components. Also many programmers from other languages are used to explicitly setting positions. And if you know that your application is only going to be run on one particular platform and cannot have its look and feel changed then you might take this particular shortcut.
In general though, it is better to set minimum, maximum, and default sizes only where necessary, not set explicit bounds if you can avoid it, and let the layout manager do the work necessary to ensure a good GUI.
I have just recently started working on the UI elements, and I discovered that the GUI does not size down as well as it sizes up. For example, I found some of my elements disappearing when I grabbed the window frame and made it smaller than its starting size. This was only in the 1 window I have completed, the server window, so I don't know if this is a general problem with Swing components or not.
Anyway, if this is what you are running into, my solution was to create each element at its minimum permissable size, in terms of logical units (like number of characters for text edit fields), then create the window and make it visible, then set the size of the window to twice the minimum size (because the minimum size is kind of tiny). I also added code to prevent the window from getting any smaller than its initial size.
All of the world's problems can be solved in a garden - Geoff Lawton. Tiny ad:
RavenDB is an Open Source NoSQL Database that’s fully transactional (ACID) across your database