...

If a user makes a ConfigTree change to a node that is created by ConfigByFile, but by another module - it's not correct that this change be written to the file of another module. If anything it should just be written to the "project module". As the project module has super dependencies, its always loaded last and so its ConfigFiles would be applied last, mimicking the manual change.

Javafree Template

What would the file structure be for a component template stored in a directory. 
templateName.xml could be the template definition that ties everything together.

But if everything follows conventions, is this file actually necessary? If the directory holds a template script, a dialog configuration, a model, resources - then we dont need an xml file to redundantly point to all of these things again. Less boilerplate. Less chance to write something wrong.

• Dir: myYoutubePlayer
  
  • myYoutubePlayer.ftl
  • myYoutubePlayerDialog.xml
  • myYoutubePlayerModel.js
  • resources
    
    • whatever.css
    • whatever.png
    • whatever.svg
    • whatever.js
    • whatever_en.properties
    • libs
      
      • superyoutube
      • parquetteLayout