Thanks for the tips. Currently I already have my own component defined which uses a computed property in the model:
var Meeting = DS.Model.extend({
city: DS.attr('string'),
weekday: DS.attr('string'),
start: DS.attr('string'),
finish: DS.attr('string'),
address: DS.attr('string'),
record: function() {
var html = '';
html += '<td>' + this.get('city') + '</td>';
html += '<td>' + this.get('weekday') + '</td>';
html += '<td><span class="whitespace-nowrap">' + this.get('start') + '-' + this.get('finish') + '</span></td>';
html += '<td>' + this.get('address') + '</td>';
return new Ember.Handlebars.SafeString(html);
}.property('city', 'weekday', 'start', 'finish', 'address')
});
In my template:
<tbody class="hover-cursor">
{{#each meeting in listMeetings}}
{{#link-to 'meetings.show' meeting tagName="tr" }}
{{meeting.record}}
{{/link-to}}
{{/each}}
</tbody>
This seems to help a little bit but not alot, and besides it’s a very awkward and inelegant solution which is not very maintainable.