- This topic has 8 replies, 3 voices, and was last updated 1 year, 8 months ago by
.
-
I think there still may be some confusion or an error here as there are both “smart.element.js” and “smart.elements.js” (difference is the “s”) and in all your documents, your examples for loading all components to use “/source/smart.elements.js” and not “source/modules/smart.elements.js” which does not exists in the current npm package. “smart.elements.js” from what I can tell only exists in the git repo and not the npm package and exists at the root of the source folder and not in the modules. Can you please confirm if this is an issue? Thanks.
Hi rkever,
All examples use the files from source/modules. We do not use source/smart.elements.js or source/smart.element.js in our demos. You can look at them here: https://www.htmlelements.com/demos/grid/overview/. You can download the software from https://www.htmlelements.com/download/ or from npm. The issue is that these are still in github and we will remove them from there as well. The files which should be used are within the source/modules. The styles which should be used are within the source/styles folder. If there is any place on our website where we use something else, we will need to update it.
Best Regards,
Peter StoevSmart UI Team
https://www.htmlelements.com/I think there’s still a disconnect here as your demo docs do indeed call out minified js files at the root of source folder as does your main documentation for downloading and installing. May want to double check this. Not trying to be difficult by any means as I am a big advocate for your framework but my concern here is that when I send folk here, they can easily get confused with incorrect documentation or incorrect npm package structures.
The below screen shots were scraped from the download and install docs page at https://www.htmlelements.com/docs/download-and-installation/ and your demo page https://www.htmlelements.com/demos/framework/event-binding/ for the framework where it’s a single file that includes all components. Thanks.
Appreciate the update. However, still a little concerned as it seems you’re saying there will be no single file that includes all elements in the event you want all available at run time? I can see that file, the “smart.elements.js” file in the git repo at the source/ root folder. In your npm package, that folder only includes other folders. So are you eliminating your single file and then require us to manage all components individual files with DI on our own? I use the single file method for a CMS site that allows any content editors to use any component and I just take the hit during first load. I’m sure I could make my own file but it’s convenient and standard for libs to provide that already.
- You must be logged in to reply to this topic.