react-chat-ui
TOAST UI Editor
react-chat-ui | TOAST UI Editor | |
---|---|---|
9 | 18 | |
62 | 16,774 | |
- | 0.4% | |
9.0 | 0.0 | |
3 months ago | 22 days ago | |
TypeScript | TypeScript | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
react-chat-ui
-
The Benefits of Outsourcing Chat Messaging Development for Resource-Constrained Startups
Here is a tutorial for building chat messaging functionality, one for React and one for React Native. Additionally, you can use MinChat as your outsourced Chat SDK.
-
The Dos and Don'ts of Designing Chat Messaging UIs for Your App
If you need a free opensource Chat UIKit have a look at React Chat UI and React Native Chat UI libraries. You can also read the tutorial on Building a React Native Chat App for a step by step guide on how to create a chat application. Thank you for following this guide, and we hope that you found it helpful in designing your chat messaging UIs for your app.
Need a free opensource Chat UIKit? have a look at the React Chat UI and React Native Chat UI libraries.
-
What's your Startup OS stack?
Im currently running https://minchat.io and I use Asana to keep track of tasks and tickets and use notion to document everything else.
-
Building a React Native Chat App: A Comprehensive Guide
Additionally, by using a chat API such as MinChat, you can add advanced features and functionalities to your chat feature, such as multimedia file sending, online/offline, and read receipts. The possibilities are endless, so don't stop here! Explore the MinChat chat api documentation to learn about even more ways to enhance your react native chat app.
- react-chat-ui - Build your own chat UI with React components in a few minutes.
- A free open-source React Chat UIKit
-
Developer tool Feedback
I am excited to announce the launch of my startup https://minchat.io that lets you easily build chat messaging functionality into your app or website. As a developer-focused community, I would love to get your feedback. If you're interested in trying it out and providing your honest thoughts, please let me know. I would greatly appreciate your input.
-
Opensource React UI library
I created an opensource UI library for react to create web chat messaging and open to anyone contributing to it https://github.com/MinChatHQ/react-chat-ui
TOAST UI Editor
-
UX Case Study: Markdown Heading
A step in that direction can be seen in TOAST UI editor:
-
I'm making a GlowUI text editor to get back into coding
If you need a WYSIWYG markdown editor you can try Toast UI Editor or simply use Markdown Live add-on for Visual Studio Code
-
Is there a way to edit callouts in preview mode
- Toast UI Editor: https://ui.toast.com/tui-editor
-
Ask HN: Any good out of the box WYSIWYG and MD JavaScript libs?
https://github.com/nhn/tui.editor Might be close to what you are after.
- Using external Editor
-
Ask HN: Help me pick a front-end framework
Can you elaborate a bit more on this part, please?
> I'm thinking of building a text-annotation based app _alone in my spare time_. The core usage loop is about viewing and interacting with "visual markup" applied to a body of text. So lots of tooltips/hoverbars I guess.
Or show us a mockup... doesn't have to be anything fancy, just like a pen and paper sketch or a simple Figma.
I'm asking because it kinda sounds like you're wanting to do something like an online IDE or Google Docs, where you're manipulating a body of text in the style of a rich text editor. If that's the case, it's possible the HTML DOM model isn't quite the right fit for you... you may find it better to abstract over a Canvas or WebGL object instead of trying to shoehorn that experience into the raw DOM. That way you have full control over rendering, outside of the normal layout/styling/rendering loop. It might also make a good case for a single-page app (at least the majority of the editor itself would be, and the other stuff -- marketing, blog, etc. -- can be routed to individual pages).
In that case, it wouldn't be so much a question of "framework" in the sense of React, Vue, etc., which traditionally work on the DOM. It might be more a question of "engine", like whether to use something like PixiJS to manipulate the graphics layer vs rolling your own. State management can be done with something like Redux (even without React), or if you choose to use a frontend framework for the rest of it, you can maybe use their state solution with your rendering engine.
In addition to choosing a low-level graphics lib, you can also look at some existing rich text markup solutions. A CMS I used had a good blog post on this: https://www.datocms.com/docs/structured-text/dast#datocms-ab... along with their open-source editor: https://github.com/datocms/structured-text
A more widespread one is the toast UI editor: https://ui.toast.com/tui-editor
I know you're not just working in Markdown, but these give you an idea of what it's like to work with complex text trees in JS.
Once you have the actual text editor part figured out, choosing the wrapper around it (again, just for marketing pages, etc.) is relatively trivial compared to the difficulty of your editor app. I really like Next.js myself (if you choose React), but I don't think you could really go wrong with any of the major choices today... React/Vue/Svelte/etc. And it looks to me like the complexity of your site wouldn't really be around that anyway, but the editor portion.
Lastly: I don't think ANY JS tool or package is going to be maintained in 10 years. Frankly, 2 years is a long time in the JS ecosystem :( I'm not defending this phenomenon, I hate it too, but that's the reality of it. If long-term maintenance is a goal of yours, you might want to consider writing abstraction layers over third-party tools you use, so you can easily swap them out when future things come out (because they will). The web itself is changing too fast for libraries to keep up; instead, people just write new ones every few years. An example of this is the pathway from the Canvas to WebGL to workers to WASM (and how to juggle heavy computational vs rendering loops around)... a lot of the old Canvas-based renderers, which were super powerful in their time, are now too slow vs the modern alternatives. Nobody is going to port the old stuff over, they just make new libs. It's likely that trend will continue in the JS world (that whatever you write today will be obsoleted by a new web API in a few years).
Lastly, as an aside, TypeScript is a superset of JS... if you find a JS project/lib/plugin that you want to use, there will often be types for it made by the community (https://github.com/DefinitelyTyped/DefinitelyTyped) , or you can write your own types for it. I don't really have an opinion about TypeScript vs writing in some other language and compiling to JS, but it would probably be easier to find help (especially frontend) in the future if you stick with TypeScript instead of convoluting your stack with multiple languages. Sounds like most of your app will be clientside anyway with limited backend needs.
---------
Tech aside... have you considered partnering with a frontend dev for this? I know you said "alone", but just having someone set up the basic skeleton of such an app with you for the first month or two could be super helpful. Or a UX person to help you with some of the interactions before you start serious coding. They don't have to be with you the whole journey, but maybe they can help jumpstart your project so you can then work on adding features & polish in your spare time, instead of figuring out basic architecture? Unless, of course, that's the part you actually enjoy. In that case, don't let anyone rob of you that :)
Have fun! Sounds like a cool project.
-
Is there any *real* WYSIWYG markdown editor besides Typora?
I think the Toast UI Editor can achieve what you want, and it does a pretty good job at that. Is built upon ProseMirror. Won't be a lot else out there since it's actually quite a hard thing to achieve once you get into the detail.
-
Stick - Shareable Git-powered notebooks
Ideas to add: - add markdown editor that works via plain JS - ability from UI to rollback to previous note version (git checkout) - Ability to create directories for notes
-
TOAST UI Editor VS ink - a user suggested alternative
2 projects | 7 May 2022
-
Implement ToastUI Editor with Next.JS (w/ TypeScript)
To make it as brief as possible, this post will only deal with some of the issues that you might encounter while implementing ToastUI Editor inside Next.JS projects.
What are some alternatives?
Quasar Framework - Quasar Framework - Build high-performance VueJS user interfaces in record time
quill - Quill is a modern WYSIWYG editor built for compatibility and extensibility.
chat-ui-kit-react - Build your own chat UI with React components in few minutes. Chat UI Kit from chatscope is an open source UI toolkit for developing web chat applications.
daisyui - πΌ πΌ πΌ πΌ πΌ βThe most popular, free and open-source Tailwind CSS component library
react-native-chat-ui - Build your own chat UI with React Native components in a few minutes. Chat UI Kit from minchat.io is an open source UI toolkit for developing mobile chat applications.
TinyMCE - The world's #1 JavaScript library for rich text editing. Available for React, Vue and Angular
ContentTools - A JS library for building WYSIWYG editors for HTML content.
SimpleMDE - A simple, beautiful, and embeddable JavaScript Markdown editor. Delightful editing for beginners and experts alike. Features built-in autosaving and spell checking.
CodeMirror - In-browser code editor (version 5, legacy)
fullcalendar - Full-sized drag & drop event calendar in JavaScript
React PDF viewer - A React component to view a PDF document
ckeditor-releases - Official distribution releases of CKEditor 4.