10 comments

[ 3.2 ms ] story [ 29.6 ms ] thread
Cool demo [0]. The highlights around the text editor and the ambiguity of the buttons' functions (what does a button labelled "ಠ.ಠ" intuitively mean?) ruin parts of the demo for me though. Maybe consider using a different color / scheme for the active box highlighting + more standard buttons.

[0] http://bevacqua.github.io/woofmark/

Yeah that demo was just a leftover from the old "not gonna open-source this" days, so I didn't really care at all. Revamped it a bit now :)
Great, looks a lot better!
Cool, slightly OT, I currently use Voog Wysiwyg since some years, should I use woofmark instead? Any other wysiwyg editor? (Markdown stored is fine with me)
I found it interesting that the project's only dependencies are also written by the author: https://github.com/bevacqua/woofmark/blob/1ffb31db3008c3c018...

Is it a case of NIH, or is it justified?

I'd suspect, just going with what's more known. In addition, you can remove any limitations you encounter a lot easier.

it is partially NIH, but that doesn't mean its unjustified.

This is something I built in house for Stompflow.com and I work in small modules, which is why you see a bunch of modules in there. They're all quite smallish and reusable, which is kind of the point.

Most people wouldn't have bothered and they would've just created a single module with everything clumped together. By writing smaller pieces I get to reuse them across other stuff that I write, open-source or not

Edit for context: this wasn't originally going to be open source

(comment deleted)