Timotej Ecimovic

See https://github.com/project-chip/zap/issues/196

There is something we call "renderer API". It is a communication layer between Vue app and the "renderer container". The "renderer container" is a thing that contains chromium engine. We...

I don't see this being done at all. Back to ToDo list.

This is a bit of a larger item.... The problem is the following: currently all the UI for attributes/clusters/commands, etc is mostly hardcoded. The columns are fixed. We have a...

See this part of the "SDK customization" doc: https://github.com/project-chip/zap/blob/master/docs/sdk-integration.md#template-key-zcl This lists the custom "zcl" keys in the `gen-templates.json` file, which contribute additional data tokens to the entities. At the bottom,...

For a good example of how these "extensions" are added to the system, see: `test/gen-template/zigbee/gen-templates.json` It has the "zcl" key which defines the extensions: ``` "zcl": { "cluster": { "testClusterExtension":...

@Mehradml : here is my belief of what kind of APIs we have... 1.) query-package.js has these queries: ``` exports.insertPackageExtension = insertPackageExtension exports.selectPackageExtension = selectPackageExtension exports.selectPackageExtensionByPropertyAndEntity = selectPackageExtensionByPropertyAndEntity exports.deleteSessionPackage =...

At this point, custom ZCL clusters are stored in the XML files. zcl.json file is a top-level SDK file that is read in to read multiple XML files.

We should add a nice description for the users...

In all reality, why not allowing zcl.json to load the custom XML? This way we can simply load multiple XML files through one file.