Hacker News Reader

Comment by marijn | Hacker News Reader

Nonsense, I've written a much smaller one: `function tinyEditor(element) { element.contentEditable = true }`

That, plus a few crude buttons, is all this does. As several other comments point out, there's good reasons why real WYSIWYG packages are bigger—the user experience of working with a plain contentEditable element is still terrible, the output HTML still a complete mess. If you don't care much about that, you don't need an editor component, since setting an attribute and wiring up some buttons to call `execCommand` is easy enough to do from scratch.

Disclaimer: I work on one of those 'bloated' editors, http://prosemirror.net , and find it a little annoying when someone implies their crude afternoon hack is somehow equivalent and we're crazy for putting in all that effort.

View on HN

The last thing I want for notable developers of high quality WYSIWYG editors is to get upset. Take this with a grain of salt. Continue doing the great things you do with ProseMirror and your other valuable open source contributions. But don't get upset. Try getting inspired, to move with the times, to trust browsers more, to make YOUR projects smaller, lighter, and easier to use.

P.S. Just because something is small, doesn't mean it's a crude afternoon hack :)

> The last thing I want for notable developers of high quality WYSIWYG editors is to get upset.

While I'm certain you have good intentions, the size comparison chart at the top of the README is a bit misleading. It would be fair to list out the trade-offs on going ahead with ContentEditable so that users can know what they are getting if they choose Pell.

To clarify, Pell looks awesome and I don't intend to diss on your project or your hard work, just that the way the project's README is laid out I feel @marijn's response is not totally unwarranted.

I mean, the post you're replying to gives reasons why they didn't take that approach, and this reply seems vaguely insulting.

Do you genuinely believe he has not explored that approach? How is one meant to get inspired by something they have already explored? Please don't be rude and wrong at the same time.

@marijn On prosemirror.net home page, typing "#<space>" in the sample editor seems to break it.

snap

Good point -- I had some CSS attached to H1 nodes that accidentally also matched H1s in the editor. Should be fixed now.

Also note, some of the tooltips appear as "undefined" and there's no way to advance the cursor past a horizontal rule at the end of the document.

What do you mean by tooltips?

There's a solution in the works for the latter problem.

The tooltips that appear when hovering over toolbar items. The ones that are dropdowns, 'Insert' and 'Type' show up as undefined.

Prosemirror's logo reminds me of : https://dribbble.com/shots/2054672-Neg-Owl-4

... more than a little, even. I'll talk to the designer of the logo.

Even as beginner in web tech, I was convinced of the same after glancing at the code. There's probably more project packaging description LoC than logic code, so SNR is quite low.