One of my favourite parts in Oracle JET - modular code structuring support. This allows to split application functionality into modules and reusable functions. In this post I will show how you could leverage Oracle JET modular architecture not only by implementing common code functions, but also by managing data maintained in common modules.
Let's jump to the example (download or browse through sample code on GitHub repository - JETModularArchitecture). Sample application is based on JET template. I have created two common modules - dashboardChartHelper and dashboardTableHelper. These modules define data structure to be displayed in the dashboard and provide API to manage this data from consuming module:
Both helper modules are imported into consuming module - dashboard:
Dashboard module defines variables (chart and table data), which are initialized from variables assigned with data structures in helper modules:
There are two wrapper functions, calling API functions from helper modules. API provides data manipulation logic, which changes chart data structure. Wrapper functions are invoked from dashboard UI:
Here is the implementation of API functions - data array changes:
What is great about such structuring - data and data changes logic can be encapsulated in common helper module. As soon as we have observable variable defined in consuming module (dashboard), which points to the method helper method (where data is changed) - changes are automatically visible on UI.
Here is the data coming from helper modules rendered in dashboard module:
Press on Add Group E button, this will call helper module API function to update data array cached in that module. In turn observable variable in dashboard module will be updated and data displayed on UI will be refreshed:
Press on Remove Group E button - chart data will be changed again:
Let's jump to the example (download or browse through sample code on GitHub repository - JETModularArchitecture). Sample application is based on JET template. I have created two common modules - dashboardChartHelper and dashboardTableHelper. These modules define data structure to be displayed in the dashboard and provide API to manage this data from consuming module:
Both helper modules are imported into consuming module - dashboard:
Dashboard module defines variables (chart and table data), which are initialized from variables assigned with data structures in helper modules:
There are two wrapper functions, calling API functions from helper modules. API provides data manipulation logic, which changes chart data structure. Wrapper functions are invoked from dashboard UI:
Here is the implementation of API functions - data array changes:
What is great about such structuring - data and data changes logic can be encapsulated in common helper module. As soon as we have observable variable defined in consuming module (dashboard), which points to the method helper method (where data is changed) - changes are automatically visible on UI.
Here is the data coming from helper modules rendered in dashboard module:
Press on Add Group E button, this will call helper module API function to update data array cached in that module. In turn observable variable in dashboard module will be updated and data displayed on UI will be refreshed:
Press on Remove Group E button - chart data will be changed again:
3 comments:
Hello, how do we run this project? It doesn't seem to be using grunt. Thanks!
This particular sample was built in NetBeans, I dont think it is directly compatible with grunt. If you wish, you can extract source files into your own project and run there.
Regards,
Andrejus
Thank you! Was able to run it that way. Wish you a happy new year!
Regards,
Amitabh
Post a Comment