Allow specifying an editor config for multiple RDF property names at once #62

flack opened this Issue Jun 15, 2012 · 3 comments


None yet

4 participants

flack commented Jun 15, 2012

Scenario: There are multiple editable properties on an HTML page. About half of them are supposed to accept only plaintext (like a person's or company's name or a blog entry's title) and the other half can also accept HTML-formatted input and images (like the text of a blog post, or the biography of a person).

In the current createjs configuration format, I will have to provide an editor configuration foreach RDF property name, so f.x. one for dcterms:title, one for foaf:name and so on, which leads to much redundancy. It would be much nicer if there was a way to specify one configuration called "Plaintext" and another one called "Richtext" and assign them to the properties of your choosing.

bergie commented Jul 19, 2012

The current idea would be to have a setter API for the editor configurations. Something like:


// Set a editor configuration set called 'foo'
jQuery('body').midgardCreate('configureEditor', 'foo', 'hallo', { ...editor options });

// Set the 'foo' editor to be used by all text properties
jQuery('body').midgardCreate('setEditorForContentType', 'text', 'foo');

// Set the 'foo' editor to be used for all 'dc:title' properties
jQuery('body').midgardCreate('setEditorForProperty', 'dc:title', 'foo');
bfr commented Jul 19, 2012

3..2..1.. implement! ;)

@bergie bergie closed this in 0e1c03c Jul 19, 2012
@bergie bergie added a commit that referenced this issue Jul 25, 2012
@bergie Editor configuration docs, refs #62 7f0d147

I'm trying to work with this - but it doesn't seem to work.

  1. setEditorForContentType seems to have the identical code like setEditorForProperty
  2. basically if I set typeof on any node containing editable data it immediately becomes un-editable
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment