Open SteveHawes opened 4 years ago
you are free to have a service like that. Problem is that we always try to avoid external urls (everything should come from servoy itself) this is better for security (CSP) and when people deploy inhouse then getting to external urls is also a problem.
The current service contains the CSS and font files embedded within the NG Service package. This means that it is difficult for the developer to use a different version of the icons (particularly the Pro icons) and we are reliant on Servoy publishing updates to get newer versions.
Using the kit concept could provide Servoy with a number of advantages over the current delivery method:
The .load() method could be modified to accept a parameter indicating the kit id which governs the version, type (SVG or webfont) and even subset of icons to be delivered to the client.
The .spec file becomes something like:
Where the xxxxxxxxxx.js is the kit identifier for the default free icon set and the load method changes to:
In your code the developer would call plugins.fontawesomekit.load(); to use the standard Servoy kit or plugins.fontawesomekit.load('a12b34c56d'); to load the kit with ID a12b34c56d.