Replies: 3 comments 1 reply
-
I don't know, I have a feeling a canvas renderer could be a bad idea. I'm not sure how you approach considering using canvas or 3d.js in your project. If I were to decide for or against it, I would start with "what immediate existing problems and missing features would they solve" instead of "By using those techs, what can we do in the project". If a simple WYSWIG editor and drag and drop are the only core features, then maybe it's an overkill? |
Beta Was this translation helpful? Give feedback.
-
I don't think Canvas is the way to go forward, specially with so much work that has gone into the DOM for links and variables, which would have to be redone. We can still use this discussion as a place to talk about what features we might want V4 to have. |
Beta Was this translation helpful? Give feedback.
-
Closing this in favor of #2879 |
Beta Was this translation helpful? Give feedback.
-
Today there was a little discussion about a new approach to rendering documents, namely utilizing d3.js in conjunction with Codemirror to output an HTML canvas rather than styled DOM. Please correct me if I misunderstood that.
It might not ever happen, and we can't be sure what the final outcome is, but it's good to drop that info in one spot. Any change to the renderer is likely to be delayed to a "version 4" since we don't want to screw up existing brews.
Benefits of something like d3.js:
Cons:
Beta Was this translation helpful? Give feedback.
All reactions