Skip to content

Instantly share code, notes, and snippets.

@kitsunet
Last active October 19, 2016 12:26
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save kitsunet/6373523b03017ec57f56b0e2d29e1f68 to your computer and use it in GitHub Desktop.
Save kitsunet/6373523b03017ec57f56b0e2d29e1f68 to your computer and use it in GitHub Desktop.
Using custom editors in Neos
define(
[
'emberjs',
'Library/jquery-with-dependencies',
'Content/Inspector/Editors/ImageEditor'
],
function (Ember, $, ImageEditor) {
return ImageEditor.extend({
categorization: [],
_initializeUploader: function () {
// This example extends the default ImageEditor from Neos, but has no functionality yet
// do some special stuff here or override other functions
// or just extend some basic object and build a fully custom editor
}
});
});
'Vendor.Package:NodeType':
properties:
someProperty:
ui:
inspector:
# Note: This uses the mapping "key" from Settings.yaml
editor: 'Vendor.Package/Js/MyCustomEditor'
TYPO3:
Neos:
userInterface:
requireJsPathMapping:
'Vendor.Package/Js': 'resource://Vendor.Package/Public/JavaScript'
@kitsunet
Copy link
Author

This is the bare minimum to configure a custom editor, obviously you need to fill in other stuff in the configuration and actually add functionality to your custom editor.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment