Got to work briefly on this project and really excited to see it reach the public! Congrats to trueadm and the whole team on this.
Facebook open sources Lexical, an extensible text editor library
31–40 of 141 posts
Re: Facebook open sources Lexical, an extensible text editor library
#32The examples shown on the site are code editing. Which puts it in direct competition with the more established Monaco from Microsoft [1]. Competition is welcome, but the description sounds like this is more of a library than a finished product (which Monaco isn't), and if so, some examples showing how to take advantage of that would have been helpful. [1] https://microsoft.github.io/monaco-editor/
By the examples, do you mean the fact we are using Codesandbox embed to show code examples of the editor itself?
Lexical definitely has the foundational requirements capable of building a CodeMirror or Monaco editor, but that wasn't our initial target with this library. That doesn't mean that we don't expect the community to push it that way in the future, we fully expect that. Let's see how things go, competition is healthy! :)
Re: Facebook open sources Lexical, an extensible text editor library
#33Does it work on Android?
It does. If you get the chance to try Lexical out, please do let us know of any issues you face when using Android, as I'm sure there are some we've yet to find yet.
One quirk for you: using my samsung keyboard with swipe typing, spaces aren't added between words. Not sure at all what causes it. The only other place I have seen this happen is url input in the browser (which I believe is intentional).
Re: Facebook open sources Lexical, an extensible text editor library
#34Earlier quoted context omitted.
It does. If you get the chance to try Lexical out, please do let us know of any issues you face when using Android, as I'm sure there are some we've yet to find yet.
One quirk for you: using my samsung keyboard with swipe typing, spaces aren't added between words. Not sure at all what causes it. The only other place I have seen this happen is url input in the browser (which I believe is intentional).
Awesome! Thank you for this. Would you be able to upload a video or maybe add more context in a Github issue? It's really difficult getting Android right.
The combination between browser + keyboard + OS version + keyboard language, it just makes it so much harder than it should be for Android. So any additional context you can provide will be a MASSIVE help. :)
Re: Facebook open sources Lexical, an extensible text editor library
#35[deleted]
Re: Facebook open sources Lexical, an extensible text editor library
#36The examples shown on the site are code editing. Which puts it in direct competition with the more established Monaco from Microsoft [1]. Competition is welcome, but the description sounds like this is more of a library than a finished product (which Monaco isn't), and if so, some examples showing how to take advantage of that would have been helpful. [1] https://microsoft.github.io/monaco-editor/
By the examples, do you mean the fact we are using Codesandbox embed to show code examples of the editor itself? Lexical definitely has the foundational requirements capable of building a CodeMirror or Monaco editor, but that wasn't our initial target with this library. That doesn't mean that we don't expect the community to push it that way in the future, we fully expect that. Let's see how things go, competition is…
My mistake... I thought the code editor was implemented using Lexical.
The real demo is here: https://lexical-playground.vercel.app/
(Edit) I think you should put this demo on the front page and the code sample on some other page. I was expecting to see the demo on the home page.
Re: Facebook open sources Lexical, an extensible text editor library
#37The examples shown on the site are code editing. Which puts it in direct competition with the more established Monaco from Microsoft [1]. Competition is welcome, but the description sounds like this is more of a library than a finished product (which Monaco isn't), and if so, some examples showing how to take advantage of that would have been helpful. [1] https://microsoft.github.io/monaco-editor/
By the examples, do you mean the fact we are using Codesandbox embed to show code examples of the editor itself? Lexical definitely has the foundational requirements capable of building a CodeMirror or Monaco editor, but that wasn't our initial target with this library. That doesn't mean that we don't expect the community to push it that way in the future, we fully expect that. Let's see how things go, competition is…
Having the live editor examples on the home page be live examples of a different editor (of a different kind) is more than a little confusing. I understood Lexical to be a code editor until I came here and saw your comment. The main page even describes Lexical as a "text editor", a term used for plain text like code. I suggest embedding the playground up the top of the main page and describing Lexical with a different term.
Re: Facebook open sources Lexical, an extensible text editor library
#38Earlier quoted context omitted.
One quirk for you: using my samsung keyboard with swipe typing, spaces aren't added between words. Not sure at all what causes it. The only other place I have seen this happen is url input in the browser (which I believe is intentional).
Awesome! Thank you for this. Would you be able to upload a video or maybe add more context in a Github issue? It's really difficult getting Android right. The combination between browser + keyboard + OS version + keyboard language, it just makes it so much harder than it should be for Android. So any additional context you can provide will be a MASSIVE help. :)
Added an issue here: https://github.com/facebook/lexical/issues/1699
And, as a side note, great work on this project. I had previously built a wysiwyg system from Slate and a custom plugin system; Lexical seems like a solid progression and has some interesting ideas like using React components the way it does to facilitate editor plugins. May have to try creating a Preact wrapper so I can use it in my projects.
Re: Facebook open sources Lexical, an extensible text editor library
#39Earlier quoted context omitted.
By the examples, do you mean the fact we are using Codesandbox embed to show code examples of the editor itself? Lexical definitely has the foundational requirements capable of building a CodeMirror or Monaco editor, but that wasn't our initial target with this library. That doesn't mean that we don't expect the community to push it that way in the future, we fully expect that. Let's see how things go, competition is…
Having the live editor examples on the home page be live examples of a different editor (of a different kind) is more than a little confusing. I understood Lexical to be a code editor until I came here and saw your comment. The main page even describes Lexical as a "text editor", a term used for plain text like code. I suggest embedding the playground up the top of the main page and describing Lexical with a differen…
Totally agree. I assumed I was seeing an example of the editor!
Re: Facebook open sources Lexical, an extensible text editor library
#40One of the big frustrations with DraftJS is that Facebook moved on (which is understandable), but the core repo wasn’t given control to the community, so patches and updates couldn’t be pulled in. Obviously it’s open source and could be hard forked, but that’s not ideal. I’d be curious if there are plans internally to make sure Lexical continues to be supported by Facebook and doesn’t end up with the same fate.
I completely understand. I can't guarantee anything, no on can in software. However, we do have a dedicated full-time team working on Lexical. DraftJS never had that, it only had a few part-time maintainers at Facebook.
Agreed there’s no guarantees in software, but that’s helpful context that there’s a dedicated team working on Lexical. Thanks for sharing and also for giving back to the software community by open sourcing the code. Editors are tough and every thoughtful approach like this that’s publicly available to use helps push them forward.