Appearently this does not include class- and data-attributes.
Personally I am fond of creating elements from markup rather than manually enriching them with ManiaScript. For that the data-attributes are great. To individualize instances, class- and data-attributes should be merged on the resulting instance frame.
Envision a framemodel 'button_with_icon' having a quad for the background, a quad as shadow, a label for the text and a quad as icon. It makes sense to bundle this in a framemodel, if you want to re-use that, as it consists of quite some code you don't want to duplicate.
Normally I would need to get the frame, get the label, set the text. Get the background, set a background color, e.g. considering a normal or primary button. Get the icon, set a style/substyle or image. Either manually for each occurance or I'd have to introduce some data structure for that. Either in ManiaScript or with a element referenced via naming convention which will then be deleted xD
The following could be completely sufficient in combination with some BWI_Init() to set the provided values.
Code: Select all
<frameinstance modelid="button_with_icon" data-bwi-style="Icons128x128_1" data-bwi-substyle="Create" data-bwi-label="awesum!" />
Although I don't see to big of an audience for that