课程配套代码 ± sample.awt.FrameWithPanelSample.java 11.1.6 布局管理器 容器对其中所包含组件的排列方式，包括组件的位置和大小设定，被称为容器的 布局（Layout）。 为了使图形用户界面具有良好的平台无关性，Java 语言提供了布局管理器来管理 容器的布局，而不建议直接设置组件在容器中的位置和尺寸。布局管理器类层次如下： LayoutManager----FlowLayout public FlowLayout(int align, int hgap, int vgap) 显式设定组件的对其方式、组件的水平和垂直间距。 . 课程配套代码 ± sample.awt.layout.FlowLayoutSample.java . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GridLayout(int rows, int cols, int hgap, int vgap) 通过参数指定布局的行数、列数，以及组件间水平间距和垂直间距。 . 课程配套代码 ± sample.awt.layout.GridLayoutSample.java CardLayout 卡片布局的效果如下： • 将多个组件在同一容器区域内交替显示，相当于多张卡片摞在一起，只有最上面 的卡片是可见的。 •

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 5. Wicket as page layout manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . With Wicket we can also apply inheritance to HTML markup in order to build a consistent graphic layout for our applications (we will see markup inheritance in chapter 4.2). • We don’t have to worry page to another. 13 Chapter 5. Wicket as page layout manager Before going ahead with more advanced topics, we will see how to maintain a consistent layout across our site using Wicket and its component-oriented

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 5. Wicket as page layout manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . With Wicket we can also apply inheritance to HTML markup in order to build a consistent graphic layout for our applications (we will see markup inheritance in chapter 4.2). • We don’t have to worry page to another. 14 Chapter 5. Wicket as page layout manager Before going ahead with more advanced topics, we will see how to maintain a consistent layout across our site using Wicket and its component-oriented

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 5. Wicket as page layout manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . With Wicket we can also apply inheritance to HTML markup in order to build a consistent graphic layout for our applications (we will see markup inheritance in chapter 4.2). • We don’t have to worry page to another. 14 Chapter 5. Wicket as page layout manager Before going ahead with more advanced topics, we will see how to maintain a consistent layout across our site using Wicket and its component-oriented

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 5. Wicket as page layout manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . With Wicket we can also apply inheritance to HTML markup in order to build a consistent graphic layout for our applications (we will see markup inheritance in chapter 4.2). • We don’t have to worry page to another. 13 Chapter 5. Wicket as page layout manager Before going ahead with more advanced topics, we will see how to maintain a consistent layout across our site using Wicket and its component-oriented

Repackage with custom Gradle configuration Configuration options Available layouts Using a custom layout Understanding how the Gradle plugin works Publishing artifacts to a Maven repository using Gradle module on GitHub. Chapter 14. Structuring your code Spring Boot does not require any specific code layout to work, however, there are some best practices that help. Using the “default” package When a class the @SpringBootApplication annotation if your main class is in the root package. Here is a typical layout: com +- example +- myproject +- Application.java | +- domain

Repackage with custom Gradle configuration Configuration options Available layouts Using a custom layout Understanding how the Gradle plugin works Publishing artifacts to a Maven repository using Gradle module on GitHub. Chapter 14. Structuring your code Spring Boot does not require any specific code layout to work, however, there are some best practices that help. Using the “default” package When a class annotations that it imports defines that behaviour so you can also use that instead. Here is a typical layout: com +- example +- myproject +- Application.java | +- domain

............................................................................ 232 Using a custom layout ..................................................................................... 232 67.8. Understanding BUILD-SNAPSHOT Spring Boot 33 14. Structuring your code Spring Boot does not require any specific code layout to work, however, there are some best practices that help. 14.1 Using the “default” package When annotations that it imports defines that behaviour so you can also use that instead. Here is a typical layout: com +- example +- myproject +- Application.java | +- domain

............................................................................ 232 Using a custom layout ..................................................................................... 232 67.8. Understanding RELEASE Spring Boot 33 14. Structuring your code Spring Boot does not require any specific code layout to work, however, there are some best practices that help. 14.1 Using the “default” package When annotations that it imports defines that behaviour so you can also use that instead. Here is a typical layout: com +- example +- myproject +- Application.java | +- domain

Repackage with custom Gradle configuration Configuration options Available layouts Using a custom layout Understanding how the Gradle plugin works Publishing artifacts to a Maven repository using Gradle module on GitHub. Chapter 14. Structuring your code Spring Boot does not require any specific code layout to work, however, there are some best practices that help. Using the “default” package When a class annotations that it imports defines that behaviour so you can also use that instead. Here is a typical layout: com +- example +- myproject +- Application.java | +- domain