Wordgard: In-browser rich-text editor from the creator of ProseMirror
1–10 of 111 posts
Re: Wordgard: In-browser rich-text editor from the creator of ProseMirror
#2ProseMirror is an excellent project, but it’s always been a bit awkward using it directly in React. I remember that NYT had to rewrite the renderer to make it work for their use-case.
I wonder how Wordgard compares in this aspect!
Re: Wordgard: In-browser rich-text editor from the creator of ProseMirror
#3I can’t believe that we are still trying to solve this. One would think that after so many years (I’ve started doing web almost 20 years ago) we would end up with some solutions baked in browsers
Re: Wordgard: In-browser rich-text editor from the creator of ProseMirror
#4ProseMirror is an excellent project, but it’s always been a bit awkward using it directly in React. I remember that NYT had to rewrite the renderer to make it work for their use-case. I wonder how Wordgard compares in this aspect!
That's due to the React constraints, though
Re: Wordgard: In-browser rich-text editor from the creator of ProseMirror
#5I think most people would love to the know the 'why'. This page discusses differences with prosemirror and is the closest I got to that question: (https://wordgard.net/docs/prosemirror/).
One thing to note is that there is not an upgrade path. Many concepts are shared with prosemirror, but it seems that switching means doing quite some work (correct me if I am wrong). Obsidian is based on Code Mirror so I guess they won't be switching, but tiptap.dev and others do.
@marijn, maybe you could address why wordgard is worth the switching cost?
EDIT: I see many points are addressed in Marijn's personal blog. I submitted (https://marijnhaverbeke.nl/blog/wordgard-0.1.html) to HN for better context.
Re: Wordgard: In-browser rich-text editor from the creator of ProseMirror
#6At Try, I entered x and tapped what I presume is Undo. No effect.
Android Chrome.
Re: Wordgard: In-browser rich-text editor from the creator of ProseMirror
#7The code appears to be unavailable. This includes not just wordgard but all the ProseMirror code as well.
If the motivation for moving off GitHub was "GH is down too much", it might be worth tracking how many 9's of uptime is lost in the self-hosted case.
Re: Wordgard: In-browser rich-text editor from the creator of ProseMirror
#8How do I get text labels on the buttons?
Re: Wordgard: In-browser rich-text editor from the creator of ProseMirror
#9ProseMirror is an excellent project, but it’s always been a bit awkward using it directly in React. I remember that NYT had to rewrite the renderer to make it work for their use-case. I wonder how Wordgard compares in this aspect!
For people who have dealt with react, this part might give some insight into that topic (https://wordgard.net/docs/prosemirror/#h-transactions-and-ch...)? Nevertheless, it would be good if this could be addressed in the docs.
I am not sure if this makes things easier for react interop, but this piece might be of interest too:
> One of the biggest mistake blunders in ProseMirror is that the editor view does not get access to the transaction objects when updating, just the state. Wordgard does not repeat this mistake, and makes updates take transactions, not just a new state.
> This means that things like the DOM update logic and UI plugins can precisely observe what happened, and handle changes in a efficient and more effective way. The weird unexpected DOM redraws that are still a thing in ProseMirror should not occur. Only the precise DOM structure affected by the new transactions will be updated.
Re: Wordgard: In-browser rich-text editor from the creator of ProseMirror
#10Getting that WYSIWYG editor up and running was a major stumbling block that I overcame to get my school newspaper a PHP-Nuke site ~25 years ago.
It is insane that there isn't a web standard implementation for this passed 15 years ago.