Timeline for Swing Component Resizer Class
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 29, 2016 at 13:40 | answer | added | Vogel612 | timeline score: 3 | |
| Oct 12, 2015 at 19:49 | history | tweeted | twitter.com/StackCodeReview/status/653658776436887552 | ||
| Sep 23, 2015 at 18:17 | history | edited | Mathieu Guindon | CC BY-SA 3.0 |
deleted 31 characters in body
|
| Sep 23, 2015 at 18:16 | history | post merged (destination) | |||
| Sep 23, 2015 at 18:04 | comment | added | durron597 |
Also, if you want a LayoutManager that respects the sizes of the child components and supports auto resizing, you want GroupLayout
|
|
| Sep 23, 2015 at 13:44 | review | First posts | |||
| Sep 23, 2015 at 14:16 | |||||
| Sep 23, 2015 at 13:40 | history | asked | Patrick Wallace | CC BY-SA 3.0 | |
| Sep 23, 2015 at 11:23 | comment | added | Dragan Bozanovic | There are many similar configs already built in the existing layout managers. For example, GridBagConstraints weightx and weighty. | |
| Sep 23, 2015 at 11:23 | comment | added | MadProgrammer | As a "crude" "conceptional" example | |
| Sep 23, 2015 at 11:18 | comment | added | MadProgrammer |
It would have more appropriate to start with a LayoutManager based class. You would then need to determine the "base" (or normal) ratio, maybe based on the preferredSize of the component, then from this you could calculate the required size need to facilitate the requirements of the actual physical layout (as the ratio would only be a small part). If you're after a review, it would better to post the code on codereview instead
|