Fan product selector

Employer: Web-IT Solutions

I continued to develop the product selector and working with new features like creating a Node.JS microservice to create images for PDF-files from the interactive frontend diagrams and the current set point in the diagrams. I also developed a configurator for some of the products which should have selectable options. For the configurator there was also a need for another microservice with .NET to handle API-calls to get data from Windows DLL-files used in the final calculations for the selected configuration.

At first the Node.JS microservice was used to generate the diagram-images for better backward compability with old browsers but some years later (2020) it was decided to not support old browsers (Internet Explorer) and the diagrams was instead gathered with HTML5/Canvas into the PDF-files. Instead the Node.JS service was rewritten to use Headless Chrome to gather the diagram images and share the same code-files to save static images for each product which then could be used with an automatic/data-creation of their physical product catalog in print.

Site:
fsp.ostberg.com

I continued to develop the product selector and working with new features like creating a Node.JS microservice to create images for PDF-files from the interactive frontend diagrams and the current set point in the diagrams. I also developed a configurator for some of the products which should have selectable options. For the configurator there was also a need for another microservice with .NET to handle API-calls to get data from Windows DLL-files used in the final calculations for the selected configuration.

At first the Node.JS microservice was used to generate the diagram-images for better backward compability with old browsers but some years later (2020) it was decided to not support old browsers (Internet Explorer) and the diagrams was instead gathered with HTML5/Canvas into the PDF-files. Instead the Node.JS service was rewritten to use Headless Chrome to gather the diagram images and share the same code-files to save static images for each product which then could be used with an automatic/data-creation of their physical product catalog in print.

Here are some screenshots from the configurator (requires registration of an account and logged in):