|
|
| (16 intermediate revisions by 2 users not shown) |
| Line 1: |
Line 1: |
| − | {{Template:Smalltalk_Author|
| + | #REDIRECT [[Small_Talks/2016/June/UI Pattern : Bootstrap and Borderlayout]] |
| − | |author=Sefi Lin, Engineer, Potix Corporation
| |
| − | |date=Jun 2, 2016
| |
| − | |version=ZK 8.0.2
| |
| − | }}
| |
| − | | |
| − | = Introduction =
| |
| − | More and more mobile devices are appearing on the market today, meaning the ability to browse on small screens has now become a necessity. To meet this demand, ZK provides a variety of layout components to help customers build their own user interface, such as TableLayout, VLayout, HLayout or BorderLayout. However, these layouts are not designed for mobile device, which leads to the question- how can we improve our user experience on mobile devices? One of the solutions is to rely on RWD frameworks such as Bootstrap. This article will show how to build a RWD ZK page with BorderLayout and Bootstrap.
| |
| − | | |
| − | = Demo =
| |
| − | Video:
| |
| − | <gflash width="640px" height="480px">UIPattern_bootstrap_borderlayout.swf</gflash>
| |
| − | | |
| − | Screenshot: desktop layout<br/>
| |
| − | [[File:UIPattern_bootstrap_borderlayout-0.png]] | |
| − | | |
| − | <br/>
| |
| − | Screenshot: mobile layout<br/>
| |
| − | [[File:UIPattern_bootstrap_borderlayout-1.png]]
| |
| − | | |
| − | = Prerequisites =
| |
| − | * ZK 8.0.2 or later
| |
| − | * Bootstrap 3 knowledge, read [http://getbootstrap.com/getting-started/ here]
| |
| − | | |
| − | = Idea =
| |
| − | This demo is a simple shopping cart, we expect the page supports RWD, so we need to design two different layout templates, one is for desktop browser written in ZK BorderLayout, another one is for mobile device browser written in Bootstrap, use same MVVM module synchronize data, and using the new feature in ZK 8.0.2 called "MatchMedia" to switch each templates. In your case, you can define more different templates for other device in different screen size.
| |
| − | | |
| − | = Structure =
| |
| − | This image explains two template's relationship, you can see each template's block are mapping to another template's block, the desktop template layout on the right side use ZK Borderlayout, and mobile template layout on the left side follow standard Bootstrap layout rules.
| |
| − | [[File:UIPattern_bootstrap_borderlayout-2.png]]
| |
| − | | |
| − | * More about Bootstrap layout grid system, you can read [http://getbootstrap.com/css/#grid here]
| |
| − | | |
| − | = Main page =
| |
| − | We use a MVVM model to control which template will be displayed. The following are the main zul page source code.
| |
| − | <source lang="xml">
| |
| − | <?meta name="viewport" content="width=device-width, initial-scale=1"?>
| |
| − | <zk>
| |
| − | <div viewModel="@id('vm') @init('org.zkoss.zkshopcart_MVVM')" width="100%" height="100%">
| |
| − | <apply template="@load(vm.layoutTemplate)"/>
| |
| − | </div>
| |
| − | </zk>
| |
| − | </source>
| |
| − | | |
| − | The following are the MVVM java code, it simply displayed desktop layout now, and how to detect which template will be displayed, we will discuss it later in the section '''Media Queries'''.
| |
| − | | |
| − | <source lang="java">
| |
| − | public class zkshopcart_MVVM {
| |
| − | private String _layoutTemplate = "desktop_layout" ;
| |
| − | | |
| − | public String getLayoutTemplate() {
| |
| − | return _layoutTemplate;
| |
| − | }
| |
| − | }
| |
| − | </source>
| |
| − | | |
| − | = Desktop layout template =
| |
| − | This demo desktop layout template we use BorderLayout, without east block, we only use north, west, center and south four blocks. the north is the header, west block is a simple menu tree, center block is main block contains shopping cart items, and the final part south block is the footer.
| |
| − | <source lang="xml">
| |
| − | <template name="desktop_layout">
| |
| − | <borderlayout>
| |
| − | <north>
| |
| − | <apply templateURI="includes/header.zul"/>
| |
| − | </north>
| |
| − | <west width="160px">
| |
| − | <apply templateURI="includes/menu.zul"/>
| |
| − | </west>
| |
| − | <center autoscroll="true">
| |
| − | <apply templateURI="includes/shoplist.zul"/>
| |
| − | </center>
| |
| − | <south>
| |
| − | <apply templateURI="includes/footer.zul"/>
| |
| − | </south>
| |
| − | </borderlayout>
| |
| − | </template>
| |
| − | </source>
| |
| − | | |
| − | = Mobile layout template =
| |
| − | Similar with desktop layout template, the mobile layout template has four blocks too, these blocks follow standard bootstrap rules. The typical layout for mobile is in vretical order, these blocks from top to bottom are header, menu, content and footer normaly, each Divs(North, West, Center and South) are a row, and the xxx_content inside each block is a full width column.
| |
| − | <source lang="xml">
| |
| − | <template name="mobile_layout">
| |
| − | <div sclass="container-fluid">
| |
| − | <div id="north" sclass="north row">
| |
| − | <div id="north_content" sclass="col-xs-12 ">
| |
| − | <apply templateURI="includes/header.zul"/>
| |
| − | </div>
| |
| − | </div>
| |
| − | <div id="west" sclass="west row">
| |
| − | <div id="west_content" sclass="col-xs-12">
| |
| − | <apply templateURI="includes/menu.zul"/>
| |
| − | </div>
| |
| − | </div>
| |
| − | <div id="center" sclass="center row">
| |
| − | <div id="center-content" sclass="col-xs-12">
| |
| − | <apply templateURI="includes/shoplist.zul"/>
| |
| − | </div>
| |
| − | </div>
| |
| − | <div id="south" sclass="south row">
| |
| − | <div id="south-content" sclass="col-xs-12">
| |
| − | <apply templateURI="includes/footer.zul"/>
| |
| − | </div>
| |
| − | </div>
| |
| − | </div>
| |
| − | </template>
| |
| − | </source>
| |
| − | | |
| − | The id is not essentially, but we adding the identity makes the code more readable.
| |
| − | The sclass "container-fluid" at '''line 2''' tell Bootstrap this container is a full width container, "row" at '''line 3, 8, 13, 18''' means this block is a row, and "col-xs-12" at '''line 4, 9, 14, 19''' means this block is a column with full width regularly.
| |
| − | | |
| − | = Media Queries =
| |
| − | We use MatchMedia Queries defined the condition when the template should be switched, in this demo, if screen width greater than 640px will show desktop template, otherwise shows mobile template.
| |
| − | Remember to add '''@NotifyChange("*")''' after MatchMedia Queries to notify ZK update UI.
| |
| − | <source lang="java" high="4,10">
| |
| − | public class zkshopcart_MVVM {
| |
| − | private String _layoutTemplate = "desktop_layout" ;
| |
| − | | |
| − | @MatchMedia("all and (max-width : 640px)")
| |
| − | @NotifyChange("*")
| |
| − | public void getMobileTemplate(){
| |
| − | _layoutTemplate = "mobile_layout";
| |
| − | }
| |
| − | | |
| − | @MatchMedia("all and (min-width : 640px)")
| |
| − | @NotifyChange("*")
| |
| − | public void getDesktopTemplate(){
| |
| − | _layoutTemplate = "desktop_layout";
| |
| − | }
| |
| − | | |
| − | public String getLayoutTemplate() {
| |
| − | return _layoutTemplate;
| |
| − | }
| |
| − | }
| |
| − | </source>
| |
| − | Now your page has RWD and will auto switch template when screen width was changed.
| |
| − | | |
| − | = Some other tips =
| |
| − | Notice, if you want to use RWD feature (MatchMedia, Bootstrap) in your page, you must add a '''meta tag''' on top of the file to describe the viewport, it is essentially.
| |
| − | <source lang="xml" high="1">
| |
| − | <?meta name="viewport" content="width=device-width, initial-scale=1"?>
| |
| − | </source>
| |
| − | | |
| − | * More information of viewport meta, you can read [http://www.w3schools.com/css/css_rwd_viewport.asp here]
| |
| − | | |
| − | If you want to use Bootstrap style component appearance, maybe you need to use some css to override zk's original style, for instance, following css code clear ZK's button appearance, and you can add another Bootstrap button class on this:
| |
| − | <source lang="css">
| |
| − | .z-button.btn{
| |
| − | background-image:inherit
| |
| − | }
| |
| − | .z-button.btn:hover,
| |
| − | .z-button.btn:focus{
| |
| − | background-image:inherit
| |
| − | }
| |
| − | </source>
| |