Compiling Sass Themes
Sass themes must be compiled to CSS understood by browsers. Compilation can be done with the Vaadin Sass Compiler, which you can run in Eclipse, Maven, or it can be run on-the-fly when the application is loaded in the browser. You can also use any other Sass compiler.
Compiling On the Fly
The easiest way to develop Sass themes is to compile them at runtime, when the page is loaded. The Vaadin servlet does this automatically if a compiled theme CSS file is not found from the theme folder. You need to have the SCSS source files placed in the theme folder. The theme is compiled when the styles.css is first requested from the server. If you edit the Sass theme, it is recompiled the next time you reload the page.
The on-the-fly compilation takes a bit time, so it is only available when the Vaadin servlet is in the development mode, as described in "Other Servlet Configuration Parameters". Also, it requires the theme compiler and all its dependencies to be in the class path of the servlet. At least for production, you must compile the theme to CSS, as described next.
|
Note
| If the on-the-fly compilation does not seem to work, ensure that your build script has not generated a pre-compiled CSS file. If a styles.css file is found by the servlet, the compilation is skipped. Disable theme compilation in your local development environment and delete the existing styles.css file to enable on-the-fly compilation. Note that theme compilation should not be disabled for production builds. |
Compiling in Eclipse
If using Eclipse and the Vaadin Plugin for Eclipse, its project wizard creates a Sass theme. It includes command in the toolbar to compile the project theme to CSS. Another command compiles also the widget set.
The WebContent/VAADIN/mytheme/styles.scss and any Sass sources included by it are compiled to styles.css.
Compiling with Maven
To compile the themes with Maven, you need to include the built-in themes as a dependency:
...
<dependencies>
...
<dependency>
<groupId>com.vaadin</groupId>
<artifactId>vaadin-themes</artifactId>
<version>${vaadin.version}</version>
</dependency>
</dependencies>
...This is automatically included at least in the vaadin-archetype-application archetype for Vaadin applications. The actual theme compilation is most conveniently done by the Vaadin Maven Plugin with update-theme and compile-theme goals.
...
<plugin>
<groupId>com.vaadin</groupId>
<artifactId>vaadin-maven-plugin</artifactId>
...
<executions>
<execution>
...
<goals>
<goal>clean</goal>
<goal>resources</goal>
<goal>update-theme</goal>
<goal>update-widgetset</goal>
<goal>compile-theme</goal>
<goal>compile</goal>
</goals>
</execution>
</executions>Once these are in place, the theme is compiled as part of relevant lifecycle phases, such as package.
mvn packageYou can also compile just the theme with the compile-theme goal:
mvn vaadin:compile-themeCompiling in Command-line
You can compile Sass style sheets to CSS either with the Vaadin Sass compiler or the standard one. The styles.css of a custom theme should be the compilation target. When compiled before deployment, the source files do not need to be in the theme folder.
You can run the Vaadin Sass compiler in a theme folder as follows:
java -cp '../../../WEB-INF/lib/*' com.vaadin.sass.SassCompiler styles.scss styles.cssThe -cp parameter should point to the class path where the Vaadin Sass Compiler and theme JARs are located. In the above example, they are assumed to be located in the WEB-INF/lib folder of the web application. If you have loaded the Vaadin libraries using Ivy, as is the case with projects created with the Vaadin Plugin for Eclipse, the Vaadin libraries are stored in Ivy’s local repository. Its folder hierarchy is somewhat scattered, so we recommend that you retrieve the libraries to a single folder. We recommend using an Ant script as is described next.
Compiling with Ant
With Apache Ant, you can easily resolve the dependencies with Ivy and compile the theme with the Theme Compiler included in Vaadin as follows. This build step can be conveniently included in a WAR build script.
Start with the following configuration:
<project xmlns:ivy="antlib:org.apache.ivy.ant"
name="My Project" basedir="../"
default="package-war">
<target name="configure">
<!-- Where project source files are located -->
<property name="src-location" value="src" />
... other project build definitions ...
<!-- Name of the theme -->
<property name="theme" value="mytheme"/>
<!-- Compilation result directory -->
<property name="result" value="build/result"/>
</target>
<!-- Initialize build -->
<target name="init" depends="configure">
<!-- Construct and check classpath -->
<path id="compile.classpath">
<!-- Source code to be compiled -->
<pathelement path="${src-location}" />
<!-- Vaadin libraries and dependencies -->
<fileset dir="${result}/lib">
<include name="*.jar"/>
</fileset>
</path>
<mkdir dir="${result}"/>
</target>You should first resolve all Vaadin libraries to a single directory, which you can use for deployment, but also for theme compilation.
<target name="resolve" depends="init">
<ivy:retrieve
pattern="${result}/lib/[module]-[type]-[artifact]-[revision].[ext]"/>
</target>Then, you can compile the theme as follows:
<!-- Compile theme -->
<target name="compile-theme"
depends="init, resolve">
<delete dir="${result}/VAADIN/themes/${theme}"/>
<mkdir dir="${result}/VAADIN/themes/${theme}"/>
<java classname="com.vaadin.sass.SassCompiler"
fork="true">
<classpath>
<path refid="compile.classpath"/>
</classpath>
<arg value="WebContent/VAADIN/themes/${theme}/styles.scss"/>
<arg value="${result}/VAADIN/themes/${theme}/styles.css"/>
</java>
<!-- Copy theme resources -->
<copy todir="${result}/VAADIN/themes/${theme}">
<fileset dir="WebContent/VAADIN/themes/${theme}">
<exclude name="**/*.scss"/>
</fileset>
</copy>
</target>
</project>