Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
You're absolutely right. I dislike extra buttons being added to my browser, and the context menu item and shortcut key are good enough for me, but... I can certainly understand that other people would like a button. I should have added one long ago.
I'll try to get this implemented soon-ish.
Some might dislike extra context menus or shortcuts ;)
There are a lot of addons that provide optional buttons, e.g. one for almost every menu item. This way it would be very unobstrusive.
Another (more difficult) option would be to place a button/link next to every textfield on the page (maybe combined with whitelist and blacklist for where it should not appear).
Am 29.10.2012 um 04:12 schrieb Adam Pritchard firstname.lastname@example.org:
Yes. And the browsers themselves also make it pretty easy to manage which buttons are showing in the chrome. I might just leverage that rather than creating a new option.
I really don't want to do that. If I start modifying web pages, it'll introduce a whole new level of code complexity (and testing, and support...). Plus, it's pretty difficult to know where Markdown Here will work and not work (and to what degree) without trying. So... yeah, probably not going to put buttons in the page.