【Hacker News搬运】Quill v2–富文本编辑器

[hackernews]

Title: Quill v2 – Rich text editor

Quill v2–富文本编辑器

Text:

hn link

Url: https://quilljs.com/

Quill 是一个免费的开源 WYSIWYG（所见即所得）编辑器，专为现代网络设计。它具有模块化架构和表达性 API，可以完全自定义以适应任何需求。Quill 易于上手，支持所有现代浏览器，包括桌面、平板电脑和手机，确保在各个平台上的行为和生成的 HTML 保持一致。

Post by: ulrischa

Comments:

majormunky: At my last job I had built a system where users could enter text into a quill textbox (and style it), and then save it into a database in their delta format. Later, a different team member would pull that into an InDesign plugin where we could easily read what styles had been applied to the text in quill, and style that using the styling in InDesign. This was used when the front desk person would enter in a legal notice for a newspaper, and the production team would be the ones who would get that into InDesign for printing. The quill delta format that it uses made this process so much easier than if we were to have been given HTML like most other editors output / save. Glad to see this is still around, its been a few years since I had heard / used quill.

majormunky: 在我的上一份工作中，我建立了一个系统，用户可以在quill文本框中输入文本（并对其进行样式设置），然后以delta格式将其保存到数据库中。后来，另一个团队成员将其引入InDesign插件，在那里我们可以很容易地读取quill中文本的样式，以及使用InDesign中样式的样式。当前台人员输入报纸的法律通知时，就会使用这种方法，而制作团队则会将其输入InDesign进行打印。它使用的quill-delta格式使这个过程比我们像大多数其他编辑器一样获得HTML输出要容易得多；拯救很高兴看到它仍然存在，我已经有几年没有听说过&#x2022；用过的羽毛笔。

jjcm: Release notes: <a href="https://github.com/quilljs/quill/releases/tag/v2.0.0">https://github.com/quilljs/quill/releases/tag/v2.0.0</a>
Announcement post: <a href="https://slab.com/blog/announcing-quill-2-0/" rel="nofollow">https://slab.com/blog/announcing-quill-2-0/</a><p>I've used quill quite a bit. It's easy to integrate, the json delta format works decently well, and is pretty straightforward, but one thing I find myself doing whenever I use it is asking myself, "Should I just be using prosemirror?".<p>I find Quill to be a great stopgap solution for when I need editing and I need it quick, but in the back of my mind I'm always mentally adding that I'll need a migration plan should that specific feature ever grow in requirements.

jjcm: 发布说明：<a href=“https://；&#x2F；github.com#xx2F；quiljs&#x2F，quill&#x2F”releases&#x2F！tag&#x2F v2.0.0”>https://&#x2F；github.com&#x2F；quilljs&#x2F；套筒；释放；标签&#x2F；v2.0.0</a>公告帖子：<a href=“https://；&#x2F；slab.com&#x2F！blog&#x2F：announcing-juill-2-0&#x2F”rel=“nofollow”>https://&#x2F；slab.com；博客&#x2F；announcing-juill-2-0</a> <p>I；我经常用羽毛笔；很容易集成，json-delta格式工作得很好，而且非常简单，但每当我使用它时，我发现自己在做的一件事是问自己，“；我应该使用prosemirr吗&quot<p> 我发现Quill是一个很好的权宜之计，当我需要编辑并且需要快速编辑时，但在我的脑海中，我；我总是在心里补充说；如果特定功能的需求不断增长，我们将需要一个迁移计划。

crowcroft: Am I crazy for having an obnoxiously strong opinion about how return should be handled by text editors?<p>Plain text return = new line.<p>Rich text return = new paragraph (shift + return = new line if you want).<p>This was a big problem for me with earlier versions, unsure how customizable this behaviour is now.<p>I do appreciate that I probably care too much about this, but I found TipTap worked well.

crowcroft: 我对文本编辑应该如何处理退货有着令人讨厌的强烈意见，我疯了吗<p> 纯文本回车=换行<p> 富文本return=新段落（如果需要，shift+return=新行）<p> 在早期版本中，这对我来说是一个大问题，我不确定这种行为现在有多可定制<p> 我很感激我可能太在乎这个了，但我发现TipTap运行得很好。

blain: This is not obvious from the link but I guess this is posted because of v2 released 3 days ago.<p>I have been working with Quill v1 not long ago and oh boy it is not good. Pain to make tables work with plugins and weird scrolling issues. Hopefully v2 fixes a lot but I'm sticking with TinyMCE as it is superior in term of features.

blain: 从链接中看这并不明显，但我想这是因为3天前发布的v2<p> 不久前我一直在使用Quill v1，天哪，这不好。使用插件和奇怪的滚动问题使表工作很痛苦。希望v2修复了很多，但我；我坚持使用TinyMCE，因为它在功能方面很优越。

toddmorey: Kudos on the docs: I encourage all open source projects to have a "Why Quill"[1] type page so I can quickly understand the philosophy of the project and how it aligns with my goals.<p>Even better when they also have "Why Not Quill" type content so you can quickly learn situations where it may not be the best fit. Every project makes tradeoffs and communicating those directly and clearly helps ensure users have a better experience.<p>[1] <a href="https://quilljs.com/docs/why-quill" rel="nofollow">https://quilljs.com/docs/why-quill</a>

toddmorey: 对文档的赞扬：我鼓励所有开源项目都有一个&quot；为什么被子&quot；[1] 键入页面，这样我就可以快速理解项目的理念以及它如何与我的目标保持一致<p> 当他们也有“；为什么不被子&quot；键入内容，以便您可以快速了解可能不适合的情况。每个项目都会进行权衡，直接而清晰地传达这些权衡有助于确保用户获得更好的体验<p> [1]<a href=“https://；&#x2F；quilljs.com#xx2F；docs#xx2F：为什么quill”rel=“nofollow”>https://&#x2F；quilljs.com&#x2F；docs&#x2F；为什么是quill</a>