@krausest Hi Stefan, tagging you here to keep you in the loop.
The requirements to create a demo app are a bit painful for neo, similar to the real world app.
We have to use bootstrap as well as an exactly defined dom markup.
This means: we can not use high level components like Neo.table.Container, but need to stick to Neo.component.Base.
I started the development inside a fork:
https://github.com/neomjs/js-framework-benchmark/tree/master/frameworks/keyed/neomjs/apps/neoapp
but am now moving it into the main neo repo, to faster work on the app and framework in parallel.
For a "real" table comparison, I would definitely go for buffered rendering (not possible here).
The demo is also missing mass table cell updates, which is a point where the vdom engine really shines.
E.g.: https://github.com/neomjs/neo/tree/dev/examples/tablePerformance
This would be a nice addition to the requirements.
@krausest Hi Stefan, tagging you here to keep you in the loop.
The requirements to create a demo app are a bit painful for neo, similar to the real world app. We have to use bootstrap as well as an exactly defined dom markup.
This means: we can not use high level components like
Neo.table.Container, but need to stick toNeo.component.Base.I started the development inside a fork: https://github.com/neomjs/js-framework-benchmark/tree/master/frameworks/keyed/neomjs/apps/neoapp
but am now moving it into the main neo repo, to faster work on the app and framework in parallel.
For a "real" table comparison, I would definitely go for buffered rendering (not possible here).
The demo is also missing mass table cell updates, which is a point where the vdom engine really shines.
E.g.: https://github.com/neomjs/neo/tree/dev/examples/tablePerformance
This would be a nice addition to the requirements.