Links

Introduction

Over the weekend I’ve been tinkering around to create a small SAPUI5 “getting started” app which is based on the new SAPUI5 tutorials (released with 1.30). It is a bit more than a “Hello-World” but not as detailed as the “Walkthrough” tutorial.

The app has just one page and uses a JSON model and was build with the SAP Web IDE.

I am sure you have built lots of Sales Orders, Employees, Invoices and whatever apps. Business apps can be tedious, so I thought a more fun and “useful” example application would make it easier for you get started.

😉

So why not Juck Norris and some nerdy jokes? And yes! There is an API for that! And when you hear API – yes I use the HCP destination service as a proxy.

See the app in action.

Go to the app’s repository.

The app structure

If you look at the repository you will think “WHAAAT??? So many files for such a small app???”.

But that was intentional! The app is indeed small, but has a very good structure:

  • component based
  • view & controller folders
  • app descriptor for routing
  • not found view
  • translations
  • styles

Head over to the app’s repository, explore the source code and find information about how to deploy it to your SAP Web IDE.

It gives you a good starting point if you want to extend it. I must admit there are no tests for this small app.

Pictures

The app:

/wp-content/uploads/2015/09/jucknorrisjokes_image_798049.png

The folder structure:

/wp-content/uploads/2015/09/app_structure_798071.png

Start the app:

/wp-content/uploads/2015/09/qrcode_798072.png

Summary

So happy SAPUI5 coding and enjoy the Juck Norris Jokes! 😆

Background Info: The idea for this app is based on the fact that our Jenkins CI somehow also has a “Chuck Norris Jokes plugin”.

To report this post you need to login first.

5 Comments

You must be Logged on to comment or reply to a post.

  1. Pavel Duchac

    Hi Denise,

    This is a great learning app! I had no idea you could switch off authentication and share your app.

    Do you need to have “neo-app.json” if you are using destination service and define it in manifest.json?

    Cheers,

    Pavel

    (0) 
    1. Denise Nepraunig Post author

      Hi Pavel.

      Thank you!

      The neo-app.json is indeed needed to make the destination “known” to your app. After that I put the final destination URL into the manifest.json where I can easily access it.

      As you see the i18n model is also there and is automatically instanciated, this also works for OData models. Hm, good idea to test it with a JSON Model.

      Cheers,

      Denise

      (0) 

Leave a Reply