Matthias,

We are working to document Builder properties, it’s been on our backlog for a while and it looks like it’s going to be front and center very soon.

In the meantime, you can have a property of type “template”, and that will present the merge field picker, e.g.

var myProp = {
    id: “foo”,
    type: “template”,
    location: “attribute”,
    label: “Foo!”
};

The location property here should be set to attribute as well, as type “template” can also be used to store the resultant template as the body of your XML node, which is probably not what you want here.

Now, in your Component’s Runtime, in order for your variables to be converted, you will need need to process them through skuid.utils.merge, which takes a string of text that may contain merges, and inserts content into the merges based on the context you have available. For instance, if your Component relies on a Model, and you want to merge in some data from the first row in this Model, then you might have something like this:

skuid.componentType.register(‘mypack__mycomponent’,function(element,xmlDef,component){
   // Get a reference to the requested Skuid Model
   var model = skuid.model.getModel(xmlDef.attr(‘model’));
   // Get its first row
   var row = model.getFirstRow();
   // Merge foo in context of our row and model
   var foo = skuid.utils.merge(‘row’,xmlDef.attr(‘foo’),{createFields:true},model,row);
   element.append(foo);
});