Currently the Boilerplate is an example widget, meaning there are a couple of things included that might not be necessary. We should ask the user a couple of questions:
Are you going to use a template? (default: true)
If not, remove the dependency, do not copy the template folder
Are you going to use jQuery in your widget? (default: true)
If not, remove the dependency, do not copy the jquery included in the lib folder
<file path="WidgetName/widget/" />
is unnecessary in package.xml for Mendix 6, removing it will solve a couple of problems when zipping the src folder with Windows zip. Unfortunately, this will break backwards compatibility with Mendix 5. So we might ask the user for compatibility (whether or not it needs to work in 5 as well) and based on that edit the package.xml file
We might have to include the widget.js file in the generator itself and use it as a jade template (like we do with _package.json), this makes it easy to omit unnecessary lines in the code
JelteMX
commented
7 years ago
Currently the Boilerplate is an example widget, meaning there are a couple of things included that might not be necessary. We should ask the user a couple of questions:
If not, remove the dependency, do not copy the template folder
If not, remove the dependency, do not copy the jquery included in the lib folder
<file path="WidgetName/widget/" />is unnecessary in package.xml for Mendix 6, removing it will solve a couple of problems when zipping the src folder with Windows zip. Unfortunately, this will break backwards compatibility with Mendix 5. So we might ask the user for compatibility (whether or not it needs to work in 5 as well) and based on that edit the package.xml fileWe might have to include the widget.js file in the generator itself and use it as a jade template (like we do with _package.json), this makes it easy to omit unnecessary lines in the code