Download the PHP package mhsdesign/liveinspectordomchange without Composer

[!WARNING]
This package is deprecated!

While declarative syntax is cool, the matter is simply too complex to have a seemingles simple framework like this.

Its recommended to create a custom / well suited implemenation with the library https://github.com/mhsdesign/MhsDesign.LiveInspectorJsEvents instead of relying on this opinionated package.

For a tutorial to use the recommended library see: https://github.com/mhsdesign/MhsDesign.LiveInspectorJsEvents#tutorial-for-a-self-made-implementation

This package will likely be not declared compatible with Neos 8 as there are only very little usages left.

Edit your Neos Site with more* live feedback!

*Neos features already a great inline editor: www.neos.io

Neos CMS Plugin for live inspector editing:

MhsDesign.LiveInspectorDomChange

(the most non-advertising name - but thats what happening)

Install this package via composer:

Demo Video: thanks, @Sebobo for https://github.com/Sebobo/Shel.Neos.ColorPicker

Usage

Activate live inspector editing in your Fusion component:

This Fusion will allow to change the class:

The EEL Helper Editable.attributes will return an array of attributes which need to be applied via Fusion @apply or as AFX spread on the HTML element that should be updated live.

(Those spreads work exacly like in Js World: <p {... {'key': 'value'} }></p> will be rendered as <p key="value"></p>)

The EEL Helper will render those attributes only in the backend into your markup.

Multiple Editable.attributes on one HTML element:

just add two spreads on the same HTML element. <div {...Editable.attributes()} {...Editable.attributes()}></div>

you can also concat them beforehand via: Array.concat(Editable.attributes(), Editable.attributes()) and apply this as a spread to your HTML element.

note that multiple editable attributes on one HTML element must come from the same node!

API:

EEL Helper

• node (NodeInterface): The current node which has the property.
• propName (string): Name of the property - must be the same name as in the CR (Yaml declaration) and belong to the node otherwise an exception is thrown.
• changerFunction (string) Name of the function to execute. (Key of the Js liveChangeFunctions object)
• changerArguments (mixed) Additional arguments for the JavaScript function. Can be of any type as long as they can be Json encoded. Note: if null is provided it will be converted in JavaScript to an empty array to allow nested default parameters.

JavaScript 'Changer' functions

All functions must be 'registered' on the global object liveChangeFunctions.

Predefined functions:

• changeClass
  • changerArguments: none
  • example: ${Editable.attributes(node, 'height', 'changeClass')}
• changeStyle
  • changerArguments: string and a valid property of HTMLElement.style
  • example: ${Editable.attributes(node, 'color', 'changeStyle', 'color')}
• changeText
  • changerArguments: none
  • example: ${Editable.attributes(node, 'color', 'changeStyle', 'color')}
• clientEval
  • changerArguments: string, which will evaluated via JavaScript eval*. el, propName, newVal, oldVal are usable.
  • example: ${Editable.attributes(node, 'color', 'clientEval', 'el.textContent = newVal; console.log(oldVal);')}

* yes I'm evil for using eval.

Create a custom JavaScript 'Changer' function

Add this to your JavaScript in the backend iframe.

Use it like:

FAQ:

I dont want to pollute my Fusion:

see #1

Limitations:

• It doesnt work for images, as 'Redux Cr node' doesnt know about an image uri. (it would probably work to use an endpoint but then complex server operations like responsive images via Fusion wont work easily. reloadIfChanged: true is a better option.)
• It doenst work yet for toggling HTML elements. But you could build yourself a Fusion Vendor:Toogle Object, which will accept a condition and in the backend sets the style to display:none and for live toggling implements a JS helper. Or use a custom web component and use el.customFunction() on the web component in a customChanger.
• You cant have two nodes controlling one HTML element.

Internal workings:

The live updates are evaluated via the nodes contextPath. that means that as long as you specify the right node as parameter to the Editable.attributes, it will work.

for more information look at the tests ;) ./Tests/JavaScript/ ./Tests/Unit/

Test:

run the phpunit tests from your flow root:

run the JavaScript jest test in the location ./Tests/JavaScript

MhsDesign.LiveInspectorJsEvents

this Package relies on the Package MhsDesign.LiveInspectorJsEvents https://github.com/mhsdesign/MhsDesign.LiveInspectorJsEvents. Which sends the JavaScript events to the iframe.