Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

copies of questions from gitter/team #6

Open
adriatic opened this issue Sep 20, 2017 · 1 comment
Open

copies of questions from gitter/team #6

adriatic opened this issue Sep 20, 2017 · 1 comment

Comments

@adriatic
Copy link
Owner

No description provided.

@adriatic
Copy link
Owner Author

@JeroenVinke WOW
I had no idea that you wrote this https://aurelia-ui-toolkits.gitbooks.io/kendo-ui-sdk-installation/content/installation/installing%20kendo/advanced/pro/requirejs.html
Being under the impression how there is nothing on how to use KendoUI with CLI, I put on a heroic hat and went on breaking new ground (not knowing anything about CLI realistically). In addition to wishing to create a really details instructions for that @SaucyJack dude. As I really wanted to make it easy to understand I decided to do it in three steps:
https://adriatic.gitbooks.io/aurelia-cli/content/initial-steps/basic-cli-application.html
https://adriatic.gitbooks.io/aurelia-cli/content/initial-steps/skeleton-typescript.html
https://adriatic.gitbooks.io/aurelia-cli/content/initial-steps/skeleton-typescript-kendoui.html
where the last one (3.) has yet to be written using the information from your response to my today's question.
Even more, I created the alternative (shorter) version of the Contact Manager Tutorial, describing just the salient points of Aurelia CLI in the context of a larger, complete story written by Rob.

Nikolaj Ivancic @adriatic Sep 18 14:31
A few comments on https://adriatic.gitbooks.io/aurelia-cli/content/initial-steps/contact-manager-tutorial.html:
I understand why did you write
Nope, you need to install the package through npm (npm install kendo-ui or whatever) and then add an entry to aurelia.json yourself
at September 18, 2017 10:18 AM. It's because of the statements like

and { "name": "kendo", "path": "../node_modules/@progress/kendo-ui/", "resources": [ "js/kendo.button.js" ] }, Why could I not replace the part of the path node_modules/@progress/kendo-ui/css... with the path that references my manually added folder with the Windows explorer? I am also going to do what you suggested September 18, 2017 10:24 AM and report back here.

Nikolaj Ivancic @adriatic Sep 18 14:39
A question, as well (from this page):
Does line 2 (npm install jquery --save) indicates how the most current bridge works with whatever jquery version gets installed? I understand that the previous limitation on jQuery version was effected by JSPM (not being used here), but I believe that Telerik still wants their users to install the jQuery that ships with KendoUI SDK

Nikolaj Ivancic @adriatic Sep 18 14:48
Oh, and your advice on change to aurelia.json
"jquery",
{
"name": "kendo",
"path": "../node_modules/@progress/kendo-ui/",
"resources": [
"js/kendo.button.js"
]
},
is made to ensure that all single file elements of KendoUI SDK are present in the kendo-ui folder:

I like this a lot - complete control for a nice definition of the SDK subset that one will use (I am trying to load the whole elephant just for being lazy - and to present the crudest case where the access exists for all SDK elements)

Nikolaj Ivancic @adriatic Sep 18 14:54
Last question (I think): If I add KendoSDK widgets (elements) as resources, how do I reference in the application .ts files, when there is no import statement present?

Nikolaj Ivancic @adriatic Sep 18 17:31
@JeroenVinke - I preferred not to create a storm in a teapot, so I am reporting this issue here aurelia-tools/acb-samples#2
Until you tell me what is wrong with this, I will use the simple on-line entry for "text" in aurelia.json

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant