quill
quill copied to clipboard
slab
Status of quill
Hi,
Sorry about posting this here, but I was whecking out quill js and evaluating whether we are going to use it in our project. But even though I see a lot of checkins still occuring, it seems to be a while since a new version has been released.
Also, he blog's latest post dates back from september 2017, so I was wondering whether this library is still actively maintained (the number of checkins confirm that, but it appears sstrange that there has been no releases for quite a while...)
If anyone could direct me to some more info on "the status of quill", I'd be very thankful. Again - apologies for abusing the issues tracker for this question.
Most likely everyone that wants to use 2.0 features is depending on latest dev release directly. We're using ngx-quill, which depends on latest stable 1.x release so benefit from none of the 2.0 dev branch features :\
Would be great if a 2.0 release were made in the not too distant future; has been a long time since a new release has been published...
The table support in 2.0 is amazing and it would be great if this could be rolled out as prod release.
Yes well, since we always try to stick to releases that we pull in through npm for any third party library, it made us doubt to going down this path, because the latest release is 14 months old.
It looks as if quilljs is really good, and would love to incorporate it into our UI, but the fact that there are new releases nor new blogposts made us doubt about whether this is the best choice we can make...
I'm here for the same reasons. If 2.0 is close to stable, I would rather just start using it now, but v1 also looks good enough for my needs. Is there any project road map available for 2.0 and documentation for how to upgrade from v1 to v2?
There's a (WIP) guide on the develop branch: https://github.com/quilljs/quill/blob/develop/docs/guides/upgrading-to-2-0.md
Yet if you look at the recent commits, in the last 7 days there haven't been any commits in last month only one commit was made.
I wonder if we are ever going to see 2.0 released
I've been using v1 for a couple of years, but I'm also considering jumping ship to another editor. Not because v2 is taking a while, but because of the lack of public communication around it, which gives pause for thought over the future of the project. @jhchen are there any updates about progress or the project in general you can share with us to assuage these concearns?
jumping ship to another editor.
@RobAley what would that other editor happen to be? Last time I checked, QuillJS was the only one capable of producing consistent content across different browsers, rest of them were flawed by design. It was a while ago though.
I've not chosen one yet, I'm still hoping quill v2 can pull it out of the bag, so to speak. However cross browser support isnt a worry for me as it's for an electron based app, so there's quite a number of alternatives to choose from. Would rather stick with Quill if i can be more confident of it's future.
On Sun, 2 Jun 2019, at 12:28 PM, arggh wrote:
jumping ship to another editor.
@RobAley https://github.com/RobAley what would that other editor happen to be? Last time I checked, QuillJS was the only one capable of producing consistent content across different browsers, rest of them were flawed by design. It was a while ago though.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/quilljs/quill/issues/2619?email_source=notifications&email_token=ABMPXAA7JRTHLM5OKIS2IILPYOVD5A5CNFSM4HNNX2CKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWXTRAA#issuecomment-498022528, or mute the thread https://github.com/notifications/unsubscribe-auth/ABMPXAEKWVTH5JK6J77CAY3PYOVD5ANCNFSM4HNNX2CA.
For what it's worth, I've recently had a couple of pull requests reviewed and merged pretty quickly recently, so I think this is still under pretty active development.
Yes - that’s the confusing part - There are MANY commits, but no releases being tagged. Even the most recent 1.x release is quite old, which makes me wonder if there ar no bugs there that are worth a new release. I know we can pull in from github master, but we follow the policy of only pulling in releases...
Yeah, I'd love to see a blog post about the evolving philosophy behind the 2.0 design, and a rough timeline of the progress... My product is heavily dependent upon Quill, and there are some limitations of the 1.0 architecture that I'm keen to solve.
Even the absence of a maintainer's comment on this one-month-old issue is a bad sign… The current status speaks for itself: few recent commits, lots of open issues and PRs, no new releases. I understand open-source is hard to maintain, but at least communication should be the top priority.
It does look as though contributions have slowed in graphs/contributors, but that could simply mean that @jhchen needs more maintainers to keep it going.
I agree, but as a newcomer checking out quill, I’m just trying tobunderstand the status. If @jhchen would confirm that that’s the case, then at least there would be an update. Currently, I have no clue whether quill IS still active or not.
That none of the maintainers have chimed in here speaks volumes; that, or it's simply easier to ignore the unwashed masses and proceed to use Quill as they see fit, with the community in mind or not.
Saying that, it would be great to hear something definitive as I prefer Quill to, for example, TinyMCE, which I'll have to go back to if this project has been abandoned.
How often does a project have this little communication about a new version for this long and actually see the new version released? I'd be stunned if version 2 ever comes out at this stage.
If we could aggregate whatever issues it has, what breaking changes are involved (I've witnessed very few, but I assume they're there?), etc, then at least someone might feel comfortable picking up the project.
Updated comment:
Regarding Quill in general:
- I think an overview of things the delta format works really poorly with (e.g lists, tables) is something people need to be aware, the project is very well thought out imo so a "you should not use Quill if you need..." style section in the Readme seems like it'd be both useful and very doable.
- You're kind stuck with Quill for rendering this data when you go with it, the Deltas are absolutely not intuitive to interpret from a database, I don't know if this is the case with alternatives
- the codebase is difficult to read through, not helped by it being unnecessarily spread out across multiple packages (unless delta and parchment are being used by other things) is a big pain too when it comes to debugging (although I get why it was done)
- I think the project has possibly suffered a bit from the high github star rating, attracting a lot of people as their first WYSIWYG library experience
Regarding version 1:
- while the documentation omits some of the lower level stuff (e.g. the scroll module is pretty powerful) it is mostly pretty solid and Jason has done a great job responding to issues over the years to the point that I've been able to quickly google solutions straight from him either her or on stack overflow
- most of what else is missing/needed (e.g. not very SSR friendly) is covered in the quill v2 blog post from 2017 tbh
- extending the functionality is hard
- some of the typescript definitions have caused issues for me and seemed to be coming up in search results explicitly connected to the project (https://github.com/quilljs/delta/issues/33)
- if you need basic text editing and won't have to deal with demands for features, it's pretty good! If there's a vagueness as to what you may need from either the editor or the data it generates, you need something with more control
- I would use it on a personal project that has a limited lifespan/scope, I wouldn't on a professional one
- it can probably do whatever that thing you want it to do, but it might be hacky as hell
Regarding version 2:
- Version 2 is basically undocumented (and why should it be, breaking changes are likely to still occur surely?) with very little as far as progress or plans or anything like that
- but at the same time loads of people seem to have just started using it regardless, and the dev version seems like it has loads of room for breaking changes so that sounds like a lot of extra pain
- it looks like very few people have stepped up to help maintain the project, I think this is partially because once you go beyond the stuff in the documentation it gets very confusing but at the same time, why would you want to put out a v2 in any race and deal with a new burst of issues to resolve along with 4 years worth of projects that are stuck on v1?
- Personally I kind of think v1 is good enough and does what it does quite well, there's no need for V2 when newer alternatives have come in but 1 has room for refinements
I regret to have added dependency from dead Quill project into my app earlier. You reading this comment do not repeat my mistake
@Gladskih: I think @jhchen is likely overtasked with how many issues are popping up here, as there are still commits actively happening in this repository.
Yeah Tiptap is great! Envious of all the Vue developers to get to use it... As far as I'm aware it's a fairly straight implementation of ProseMirror (just way more advanced than any of the ones for React)?
Thanks all! It sounds like you're more informed than I am on this. I wondering if QuillJS is still one of top options we have right now when it comes to feature set availability?
I'm looking for something that can hopefully work on React and have modules/plugins available such as:
- Load/Paste Word document (and hopefully keep formatting and things such as tables)
- Compare text versions (for redlining)
- Add comment on the text
- Add custom fields or required inputs within text
... and a few more along these lines of Google Docs behaviors
quill is obviously dead.
The only issue with <p> tag instead of <br> for newlines makes it a pain!
Multi-level lists and other things.... ah...
I'm also looking for an alternative.
Tiptap looks nice at first glance but then it has it's own down sides. For example try to change font-size or text-color..
So I guess you should be really specific on what features you need before choosing the editor.
Oh yeah, all of them have downsides. I even notice Google Docs has some mildly confusing handling of things with tables, presumably to safeguard against bugs. Bizarre that tiptap doesn't allow colors but the inline-level font size thing seems to be a general issue.
Another factor to consider is whether you need a fully open source option; CKEditor or TinyMCE might meet your needs, at the very least you'd be dealing with an editor that roughly meets the standards a user might realistically expect as far as features are concerned.
A huge issue with all of this stuff is how old the search results are for it. I just looked up CKEditor vs TinyMCE and the top result was from 2010! I plan on updating Quill's documentation in this regard a bit whenever I can find the time as it's ~3 years old now (making it much newer than most the results google is giving me right now).
Has anyone tried migrating from Quill to Slate?
I saw this post dated a few years back but it seems similar to our issues. I'm just worried about all of our saved documents being properly rendered via Slate.
https://medium.com/the-lead/why-we-moved-from-quill-to-slate-94f42aa54fec
I don't think Slate has been around long enough to warrant a move tbh, by its own admission it's in beta and I haven't seen much to suggest that it's a drastic improvement. If it were a new project maybe it'd be worth a try, but to undergo the hassle of moving everything over it seems not worth the hassle.
Appreciate the thoughts @padraigfl ! Although not entirely free for my purposes, CKEditor seems to have some neat features I would need to build for other open source editors otherwise. It seemed as close to Google Docs as I could get, and that's essentially what I'd love to build for my project without the work of implementing every little feature, since CKEditor has a lot of it. I'll keep watching this thread in case something else pops up. thanks!
Has anyone tried migrating from Quill to Slate?
I saw this post dated a few years back but it seems similar to our issues. I'm just worried about all of our saved documents being properly rendered via Slate.
https://medium.com/the-lead/why-we-moved-from-quill-to-slate-94f42aa54fec
Judging by its repo, Slate appears to be just as dead.
