summaryrefslogtreecommitdiffstats
path: root/documentation/layout/layout-csslayout.asciidoc
blob: d6a50157ce45ee95f4df9470a5b50481e11382f5 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
a> 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173
---
title: CssLayout
order: 12
layout: page
---

[[layout.csslayout]]
= CssLayout

ifdef::web[]
[.sampler]
image:{live-demo-image}[alt="Live Demo", link="http://demo.vaadin.com/sampler/#ui/layout/css-layout"]
endif::web[]

[classname]#CssLayout# allows strong control over styling of the components
contained inside the layout. The components are contained in a simple DOM
structure consisting of [literal]#++<div>++# elements. By default, the contained
components are laid out horizontally and wrap naturally when they reach the
width of the layout, but you can control this and most other behaviour with CSS.
You can also inject custom CSS for each contained component. As
[classname]#CssLayout# has a very simple DOM structure and no dynamic rendering
logic, relying purely on the built-in rendering logic of the browsers, it is the
fastest of the layout components.

The basic use of [classname]#CssLayout# is just like with any other layout
component:


[source, java]
----
CssLayout layout = new CssLayout();

// Component with a layout-managed caption and icon
TextField tf = new TextField("A TextField");
tf.setIcon(new ThemeResource("icons/user.png"));
layout.addComponent(tf);

// Labels are 100% wide by default so must unset width
Label label = new Label("A Label");
label.setWidth(Sizeable.SIZE_UNDEFINED, 0);
layout.addComponent(label);

layout.addComponent(new Button("A Button"));
----

The result is shown in <<figure.layout.csslayout.basic>>. Notice that the
default spacing and alignment of the layout is quite crude and CSS styling is
nearly always needed.

[[figure.layout.csslayout.basic]]
.Basic Use of [classname]#CssLayout#
image::img/csslayout-basic.png[width=60%, scaledwidth=100%]

The [literal]#++display++# attribute of [classname]#CssLayout# is
[literal]#++inline-block++# by default, so the components are laid out
horizontally following another. [classname]#CssLayout# has 100% width by
default. If the components reach the width of the layout, they are wrapped to
the next "line" just as text would be. If you add a component with 100% width,
it will take an entire line by wrapping before and after the component.

[[layout.csslayout.injection]]
== CSS Injection

Overriding the [methodname]#getCss()# method allows injecting custom CSS for
each component. The CSS returned by the method is inserted in the
[parameter]#style# attribute of the [literal]#++<div>++# element of the
component, so it will override any style definitions made in CSS files.


[source, java]
----
CssLayout layout = new CssLayout() {
    @Override
    protected String getCss(Component c) {
        if (c instanceof Label) {
            // Color the boxes with random colors
            int rgb = (int) (Math.random()*(1<<24));
            return "background: #" + Integer.toHexString(rgb);
        }
        return null;
    }
};
layout.setWidth("400px"); // Causes to wrap the contents

// Add boxes of various sizes
for (int i=0; i<40; i++) {
    Label box = new Label("&nbsp;", ContentMode.HTML);
    box.addStyleName("flowbox");
    box.setWidth((float) Math.random()*50,
                 Sizeable.UNITS_PIXELS);
    box.setHeight((float) Math.random()*50,
                  Sizeable.UNITS_PIXELS);
    layout.addComponent(box);
}
----

The style name added to the components allows making common styling in a CSS
file:


[source, css]
----
.v-label-flowbox {
  border: thin black solid;
}
----

<<figure.layout.csslayout.getcss>> shows the rendered result.

[[figure.layout.csslayout.getcss]]
.Use of [methodname]#getCss()# and line wrap
image::img/csslayout-getcss.png[width=60%, scaledwidth=100%]


[[layout.csslayout.compatibility]]
== Browser Compatibility

The strength of the [classname]#CssLayout# is also its weakness. Much of the
logic behind the other layout components is there to give nice default behavior
and to handle the differences in different browsers. With [classname]#CssLayout#,
you may need to make use of the browser-specific style classes in the root
element of the application to write browser specific CSS rules.
// TODO: ... described in <<advanced.browserinfo>>
Some features in the other layouts are not even solvable in pure CSS, at least
in all browsers.

[[layout.csslayout.css]]
== Styling with CSS

[source, css]
----
.v-csslayout {}
.v-csslayout-margin {}
.v-csslayout-container {}
----

The [classname]#CssLayout# component has [literal]#++v-csslayout++# root style.
The margin element with [literal]#++v-csslayout-margin++# style is always
enabled. The components are contained in an element with
[literal]#++v-csslayout-container++# style.

For example, we could style the basic [classname]#CssLayout# example shown
earlier as follows:

[source, css]
----
/* Have the caption right of the text box, bottom-aligned */
.csslayoutexample .mylayout .v-csslayout-container {
    direction: rtl;
    line-height: 24px;
    vertical-align: bottom;
}

/* Have some space before and after the caption */
.csslayoutexample .mylayout .v-csslayout-container .v-caption {
    padding-left:  3px;
    padding-right: 10px;
}
----

The example would now be rendered as shown in
<<figure.layout.csslayout.styling>>.

[[figure.layout.csslayout.styling]]
.Styling [classname]#CssLayout#
image::img/csslayout-styling.png[width=50%, scaledwidth=70%]

Captions and icons that are managed by the layout are contained in an element
with [literal]#++v-caption++# style. These caption elements are contained flat
at the same level as the actual component elements. This may cause problems with
wrapping in [literal]#++inline-block++# mode, as wrapping can occur between the
caption and its corresponding component element just as well as between
components. Such use case is therefore not feasible.