Splitting up the NuGet packages

[GregoryHouseMDParticipant]

First I’d like to point out that you guys are doing an excellent job 🙂

I got the splitting idea from the angularjs packages. You can install the whole AngularJs, or you can install the Core package and the elements you need.

Obviously, having a package for every widget is stupid, that is just too much, but maybe bundle them by feature type (inputs, tables and stats etc.).

Splitting up the themes would also be great because now I have some 900 files I need to commit to the server when there is a new version, and I only use the bootstrap theme and two or three widgets. Removing them from the solution once they’re added can solve this, but if I do a restore on the packages, all the files get downloaded again.

It is excellent the way it is now, don’t get me wrong, I’m just throwing this idea out there.

Cheers,
House

[DimitarParticipant]

Hello House,

Thank you for your feedback. Please note that you can also use only the file jqx-all.js which contains all widgets.

Best Regards,
Dimitar

jQWidgets team
http://www.jqwidgets.com/

[GregoryHouseMDParticipant]

Hi Dimitar,

The idea is not to add a 3 MB script to the site when I’m only using some 300KB, and also not to clutter the solution with +300 files, when I’m using around ten.

Regards,
House

[adminKeymaster]

Hi Gregory,

Themes are already in different files and you can use the theme file which you prefer. It is not necessary to copy all theme files.
Most of the javascript scripts depend one from another. We have a bundle called jqx-all.js and jqxchart.js which combines all chart files, but for all other widgets it is not reasonable to create small bundle packages which will lead to unnecessary confusion among people. If you wish, you can bundle files, by using bundle config or by concatenation of files.

Best Regards,
Peter Stoev

jQWidgets Team
http://www.jqwidgets.com

[Author]

Posts