Live data from Hacker News

Trix: A rich text editor for everyday writing

github.com

61–70 of 137 posts

Re: Trix: A rich text editor for everyday writing

#62
post #5

Please tell me this is a humane alternative to TinyMCE, CKEditor, etc?

Going from the README, the main difference is the architecture. It creates a layer of indirection between user actions and the DOM. This has two advantages: * For developers of Trix itself, it eases the pain of cross-browser development - as the README says, contenteditable is inconsistent across browsers. * For developers using Trix, you get a clean API (Trix.editor) so you can edit the document programmatically wit…

'contenteditable is inconsistent across browsers'.

We (the Guardian) created Scribe to tackle this:

https://github.com/guardian/scribe

(I can't take any credit personally though alas!)

Re: Trix: A rich text editor for everyday writing

#64
post #17

Interesting naming. The WYSIWYG rich text editor in Google Docs is named Kix. The engine behind Google Sheets is named Trix.

Is there an open source alternative to Kix? I've been looking for WYSIWYG which has the look and feel of a document processor.

http://etherpad.org/

Re: Trix: A rich text editor for everyday writing

#68
post #67

I really like this. If only it supported ie 9 and below I would use it. Looks like we are stuck with CK unless anyone can offer other viable, preferably pretty, solutions?

It seems like it uses polyfills to solve this problem, no?

From the documentation:

> Eventually we expect all browsers to implement these standards. In the meantime, Trix includes polyfills for missing functionality.

Re: Trix: A rich text editor for everyday writing

#69
post #9

How does this compare to Prosemirror? ( http://prosemirror.net/ )

From the document model standpoint, Prosemirror has a tree of nodes, while Trix has an array of blocks with a stack of block-level formatting. Mathematically equivalent, practically not so much.

Re: Trix: A rich text editor for everyday writing

#70

One thing this gets right that heaps of other WYSIWYG's get wrong is lists. You can create a proper multi-level list here with order and unordered lists nested inside each other correctly. This sort of stuff is actually important for creating accessible documents as things like flowcharts need a plain text version and nesting lists is a reasonable way of displaying these.

Absolutely. I do note though that headers (h1, h2, etc.) are not supported (unless there's a way to customize the format bar past what I saw in the demo). Switching from ul/ol/li to h1, h2 and back has been a MAJOR headache for us when we tried to offer text-editing features based on an older library called wysihtml5. Medium also dodges that altogether. Text editing is still extremely complicated.
Post reply on HN