Make Fiori Run Like Never Before
One of the major challenges of software development is managing complexity. A common way of reducing some of the complexity of a codebase is to separate the code into different files based on what the code does. In this way, you could have a file that contains your utility functions, a file for each of your classes etc.
Advanced Data Binding in SAP Fiori Apps
SAP UI5 has a very convenient and robust mechanism for doing two-way binding of your data from you data layer (the model) to your presentation layer (the view). By using data binding you are effectively separating the concerns of your application. In an ideal world you want your model code to only be responsible for your data and your presentation code to only be responsible for the way the data is displayed.
Extending SAP Fiori Applications with Web IDE
In this blog post I wish to demonstrate the ability of SAP Web IDE to extend existing Fiori applications. None of the code of the original application is altered, the new application merely adds, modifies and/or hides features of the original app.
Decoupling SAPUI5 Controllers
Building web applications using the MVC architecture helps with separating concerns and keeping the application modular. In an ideal application every module has only a single responsibility. Model View Controller architecture advocates breaking an application up into three groups that are logically separated.
See SAP Fiori in Action
At the recent SAP TechEd in Las Vegas, SAP announced the availability of a demo that can be easily accessed.