You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 20 Next »

 

This document relates to the "Lower the Entry Barrier" initiative, codenamed "Ramp".

Some concepts which will be implemented in 5.4 have become children of page Concepts 5.4

Here I will go into more detail about some of the concepts. These will probably be broken into individual documents.

Concepts to cover:

  • Template & Resource Loading Cascade
  • Inplace editing of Templates & Resources: Access filesystem
  • Config By File: Configuration & Bootstrap improvements
    • Work with config more like templates & resources.
    • JCR Document View or JSON. Autoloading. Autoexporting
    • Maybe it works like code in that it creates a dynamic configuration every time - not a permanent change to the configuration tree.
  • Better Javascript handling.
  • ConfigTree improvements. Extends insight. Template Extender tool.
  • Enable frontend developers to create apps & fields with templates.

References

STK 2.0 Workshop

http://wiki.magnolia-cms.com/download/attachments/42270723/stk-remarks-vpro.pdf


Inplace editing of Templates & Resources: Access filesystem

What if nothing was stored in repository?: Not templates or resources?

  • Templates and resources do not get stored in repository.
    • Admincentral apps load the files from filesystem for display.
    • inplace editing - edits the files directly. (In exploded War)

That does not work for JARS, the files cannot be written to.


ConfigByFile - Autowrite to File on ConfigTree edits.

If writes to the configTree were automatically written back to the ConfigFile - that would solve problem of loosing changes made in adminCentral.
But how would the system know to which file to write?
And how would it know when to write given the likely situation that some configuration is defined by File, but some is loaded from Bootstraps?

Proposals for Consideration: (How to find file)

  • Filename is written as a property to the root node of the configuration it represents. So on change, it can walk down the tree till it finds the filename (or flag).
  • Unlike bootstraps, ConfigFiles always start at a specific level. There is a separate file for each app, each dialog, and the basic "config" node for a module. As this is set - its easy for the system to generate the filepath of the file and check if it exists.
  • All files are scanned to find matching file.

Questions

If a user makes a ConfigTree change to a node that is not created by ConfigByFile, does system create a file for this manual change?

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


  • No labels