Aurelia KendoUI catalog configuration helper

[adriatic]

This issue is initially referenced (and partially defined in Improving KendoUI bridge installation support issue.

[adriatic]

The page Sample 1 - KendoUI-skeleton-esnext written as a part of the internal KendoUI bridge developers notes book documents the changes the user needs to make in order to add KendoUI components to the basic Aurelia skeleton navigation app.

It is very easy to realize how this page

could be further formalized and the result implemented in the form of a wizard that is hosted on the catalog application

[adriatic]

Here are the key steps in reaching this feature.

1. Do not bother to deal with any actions described in Kendo UI SDK Installation - instead assume the initial situation where it exists in this example, where the kendo-sdk folder is already set up by the user.
2. Note that the content of the kendo-sdk/js folder completely defines the KendoUI "widgets" that the application will use, so the wizard's first question would by "where is the kendo-sdk folder", followed by verification of its content.
3. In order to streamline the process even more, I contacted the Telerik's sales team, got them reasonably excited about the number of bridge downloads, so I am hoping that we will be able to somehow create KendoUI custom "library" - in lieu of the currently used kendo.all.min.js file that is used for testing purposes. If that failes, we will refer the KendoUI pro users to create such kendo.custom.min.js file and put it in the kendo-sdk/js
   I would actually like to use only autocomplete.min.js, button.min.js, chart.min.js and grid.min.js bundled together in all tutorial samples.

[adriatic]

Let's also address the steps 1 - 4 from page Sample 1 - KendoUI-skeleton-esnext

Step 1

It is documented in the summary file that describes the actions that the user needs to do manually

Step 2

This can be achieved in the simplest form by documenting these steps in the above mentioned summary file

Step 3 already explained in 3. above

Step 4

This is where we help users the most, because given the well defined locations of all files in this section we can write the complete set of instructions needed to achieve the effects described in 4.1 - 4.4 - so this would be the final check-list that would drive the user through the process.

[JeroenVinke]

Something else to improve:

au new comes with different environments so finding out where to put the plugin call in the main ts was difficult

Also, it can be confusing that you have to select one installation method for the installation of kendo, and one installation method for t he installation of the bridge. This is based on your setup. But I believe we are already fully aware of this issue (because of the proposal I am writing this in 😄 )