Thanks for the update @eviltrout . Topics are now rendering much faster. I can only imagine how much work was involved, especially considering your efforts to support legacy code.
I do appreciate that code injected client side via the Admin panel isn’t your focus right now, but it would save client side devs a lot of time if you could show how the following deprecated event (or equivalent) is now being generated and how we should hook into it.
var topicView = require('discourse/views/topic').default; //get a reference to the topic view
topicView.reopen({ //access view object
didInsertElement : function(){
this._super();
Ember.run.scheduleOnce('afterRender', this, this.afterRenderEvent);
},
afterRenderEvent : function(){ //after view has been rendered do this:
//console.dir(this); //Use this to to get a good overview of what's available
console.dir("Category ID: " + this._controller.model.category.id + " - Category Name: " + this._controller.model.category.name);
}
});
It’s only a token example, but help with this, coupled to the new API document should be sufficient to get to grips with the new topic architecture.
A final question. Is the new virtual DOM architecture limited to topics only, or are there plans to expands its use elsewhere?