Blaze Components + Incremental DOM

[alexandesigner]

@mitar What are the benefits we would have if it were rendered in Incremental DOM?

[mitar]

What you mean by incremental DOM? VirtualDOM?

[rclai]

I think he's talking about this: https://github.com/google/incremental-dom

[alexandesigner]

First of all i'd like to compliment you on the great job with Blaze Components... So nice!

That's right, Here is an excellent article

I believe it is a good approach and I would like to try on the Blaze Components, i'm curious to know where Incremental DOM would fit..

[mitar]

I think this would be better opened against Blaze, because it is something which is independent from this package and could be implemented at the Blaze level. But if you want, you can also try to do it directly at this level.

I see three options how you could integrate it. One is to hook into animations hooks, but I doubt this will really work because at that level you have concrete DOM elements already ready to be inserted.

Another would be to implement an alternative DOM backend, but I also do not think this is the right way, because it seems it just handles how you append data and events to an existing DOM elements.

So I think you want to override materializer. If incremental DOM has good API, this might be relatively straightforward to do.

[alexandesigner]

You're right. The direct implementation in the Blaze would be more appropriate.

In a way, my question was made precisely because Blaze Components is treading the path that I believe to be the future of Blaze ... I'm already thinking about how we can improve the approach of the DOM in the Blaze.

So if I want to do some experiments directly on the blaze the path would be override materializer?

I'm going to do some experiments and then return with news, will be if the staff of the MDG would that matter?

[mitar]

So if I want to do some experiments directly on the blaze the path would be override materializer?

I would say in both cases this would be the path.

This could simply be an extra Meteor package which overrides default materializer for Blaze. So people who would like to try it out would just add your package.

[mitar]

@allanalexandre: If there is any internal Blaze API change needed for you to make it work at all (or better), feel free to make them in your fork of Blaze and then we will integrate them with official Blaze.

[alexandesigner]

All right, during those days i'm going to start the experiments, first of all i need to understand better how it works the Blaze and its API.

I will work initially with the idea of the package.

Thanks @mitar

[mitar]

Closing in favor for meteor/blaze#45.