Sublime text html boilerplate
This makes also the ComponentContainer obsolete. Initialisation of the global models (i18n and the new device model) is taken over form the Component by the App View (RootView). The homeIcon definition is done by the SpliApp itself now. This makes the DOM more lean and removes unnecessary complexity. Shell and Component were removedĪs the Shell and also the Component are not really necessary for a ‘normal’ App (here in the sense of a single, independent App), they have been removed. With the updated version of the UI5 boilerplate there are some fundamental changes which I shortly will describe.
#Sublime text html boilerplate how to
You can find an article which describes How to easily add further pages in this external blog post. In the next blog article I want to explain, how you can easily extend the UI5 Boilerplate with further Pages. The result can be seen in the browser (with UI5 Boilerplate Version 0.6.0): The App View is now returning the SplitApp as member of the mobile Shell. And of course you could also use the other view types here. Both JSViews or XMLViews are possible as you can see. We can then define the Master Page(s) which will be on the smaller left side of the screen (here the Menu View) and also the Detail Pages (CoffeeList View and Info View). In the App View we create a SplitApp which will enable the “iPad” like UI Style. Now lets have a look at the App View: (Application UI) Within the component further general tasks could be executed, like loading master data, which can then be used throughout the application. In the Component (Application) we create the App.view (which represents the UI of our Application) and create the i18n model and attach this to the App.View.
This will create and run our Component (Application): Component.js (Application Component) We create an ComponentContainer with name “app” and attach it to the DOM element with the id “root”, which in our case is the body tag. This Component represents our Application. And we specify that we require app.Component. So UI5 will be able to use resources within these folders. These are in the folders app, model and view. In the app.js we define where UI5 resources are located. The index.html links to the JavaScript file app.js: app.js (declare UI5 resources / ‘start’ Application Component) With local options you can define yourself which dedicated UI5 version you want to use. The boilerplate offers here in comments some alternative sources for the UI5 bootstrap (OpenUI5 external, SAPUI5 external, local SAPUI5 from SAP UI5 Toolkit or providing it via local web server). After the meta declaration for IE the UI5 bootstrap script is declared. Let’s have a look at the index.html file first: UI5 view files (XMLViews, JSViews) and the corresponding controllers UI5 model information (like json, xml files) Resource bundles for internationalization (i18n) are stored in this folder UI5 Application Component, which is responsible for general tasks, like initialize core models like i18n UI5 Boilerplate is structured via the following folders: Folder Web App Preview, Apache Tomcat, HANA Cloud Local Runtime UI5 Boilerplate with Eclipse + SAPUI5 Toolkit
Git clone -b eclipseKepler https: //github.
The UI5 Boilerplate also supports SAP and also Non-SAP Development approach, this is reflected in two different git branches:Īny IDE with Git Support ( Sublime Text, Eclipse, IntelliJ,…)Įclipse 4.3 with SAP UI Development Toolkit for HTML5 (SAP UI5 Toolkit)
#Sublime text html boilerplate code
The UI5 SplitApp Boilerplate code is hosted on Github: 6of5/UI5SplitApp-Boilerplate The Boilerplate provides a basic application and file structure, implements some core features (navigation, i18n) and contains example views/controllers for different purposes. The UI5 Boilerplate can be understood as starting point for your own UI5 Development, both for OpenUI5 and SAPUI5 Apps. It is a template/skeleton for Mobile UI5 Apps and follows the “Mobile First” approach, but also works on desktop (Thanks to the great sap.m controls). In this blog I will describe the structure and concepts behind the UI5 SplitApp Boilerplate.