Hi Sam,
I just discovered this projet from the HN post today. I have been exploring this kind of work (reactive django components) since few months now and I use django reactor: https://github.com/edelvalle/reactor (version 2.2 though, not the last one) on a big project.
Tetra looks quite similar in usage but there are a few differences:
js integration looks really clean in tetra,
inlined templates/css/js shoudl be tested before saying anything about it :)
blocks ! That is a great feature !
I will definitely take some time to read your code and try to see if we can port some of the features of Tetra to reactor too.
In reactor we built an app store (similar to vuex) and a router (similar to vue-router). They are not published yet but will be at some point.
I have a few questions:
any plan to integrate websockets communications ?
do jinja works here ? If not do you plan to use it ? Using reactor we realized it was absolutely necessary for snappy reactions on big templates.
is there an easy way for siblings components to communicate ?
Anyway it's great to see all those new "frameworks" extending django to ease the frontend creation.
Congrats !
Hi Sam, I just discovered this projet from the HN post today. I have been exploring this kind of work (reactive django components) since few months now and I use django reactor: https://github.com/edelvalle/reactor (version 2.2 though, not the last one) on a big project.
Tetra looks quite similar in usage but there are a few differences:
I will definitely take some time to read your code and try to see if we can port some of the features of Tetra to reactor too. In reactor we built an app store (similar to vuex) and a router (similar to vue-router). They are not published yet but will be at some point.
I have a few questions:
Anyway it's great to see all those new "frameworks" extending django to ease the frontend creation. Congrats !