Open mqtik opened 5 years ago
We haven't started anything for the React.js but when we started this project we thought about it and that's why we designed it to convert everything to HTML. Maybe it's the time to add more to the conversion part and start another project for the web side. But that required a lot of planing and time.
Well, at some point I'll need it, and if not done, I'll have to work it out.
But I'm curious, @ohpax — is this the best way to implement and editor in React Native? can it evolve into a library in terms of consistency and availability of contents across platforms (web & mobile)?
Well this was best we could do, there might be other ways, but I don't think that there is a perfect way. In this way, we use HTML as our final result so if we can support a big range of the syntax we can even have it work with other web based editors, but the perfect scenario would be having our own web based library to match with this project in all scenarios. plus we can straightly show the result from mobile on the web because it is plain HTML.
I totally understand, compatilibity between platforms is a major feature. I'm thinking; maybe we could include a sanitizer of HTML, that would reduce the margin of error.
i'm curious, what other ways do you mean? Besides using directly a WebView
Hi.
Since this editor works with objects in the contents, imports and exports HTML, I get it can be a daunting task to read lots of HTML elements and transport it to native.
However, I find myself in the position of maybe, share how the editor works and replicate it to work with frontend ReactJS.
Any ideas for this in the future?