(Github Comment Enhancer) Integrate into GitHubs new own buttons

[rugk]

You probably already read it: GitHub enhanced it's Markdown commenting system

With your userscript we now have duplicated buttons with the same function, so this is not really good. So you might want to adjust your userscript to fit to the new GitHub update.

[jerone]

Thanks for the heads-up. This requires a complete overhaul of GCE. Not sure what I'm going to do next...

Do you think the new toolbar is sufficient or do you miss something that GCE provides?

[rugk]

What's still missing by default in GitHubs buttons is:

• the easy code syntax selection
• the snippets
• the emoticons (although this had some performance issues ((Github Comment Enhancer) Clicking on the smiley button takes quite long #87) anyway)
• underline
• strikethough

And you cannot use GitHubs new toolbar when editing a wiki site.

[jerone]

Thank you for your input!

For me the missing features I use are:

• strikethrough
• link popup
• clear
• comment reply

[thomaslevesque]

The feature I miss from Github's toolbar is the keyboard shortcuts. Only a few commands have shortcuts:

• Ctrl + I: italic
• Ctrl + B: bold
• Ctrl + K: link (which is annoying, because I'm used to this shortcut being for "code", like in GCE and StackOverflow)

[PhiLhoSoft]

Actually, I would just disable entirely GitHub's toolbar and rely only on the one your create... 😁 If it is in the power of GM.

A major annoyance with the new feature is conflicting key shortcuts: when I use Ctrl+K (the most common for me), eg. around 'with', I get

[`with` ](url)

which is a pain... At least, Undo (Ctrl+Z) leaves only the wanted code markup...

[jerone]

I'm kind of leaning towards separating the reply feature out of GCE and making that a separate userscript. That part still works and can work with GitHub's new toolbar.

For making GCE working again I'm still not sure what do yet...

1. I can extend GitHub's toolbar with the missing features.
2. I can replace GitHub's toolbar with GCE features.
3. Remove GitHub's toolbar and keep things as is.

Option 2 & 3 relatively aren't very much work. Option 1 is probably more work. Then there's the choice to follow GitHub's new buttons design or not...

[rugk]

Now the buttons really look broken:

[jerone]

Even the reply button isn't working anymore :(

[jerone]

Looks like they moved away from glyph fonts and are using SVG now for all icons.

[joeytwiddle]

I don't know why they didn't just install your userscript on their site! ❤️

[Trubbel]

First of all, thank you for making my (and everyone else) life easier with this userscript. Have been using it for quite some time now.

Anyway, me personally would prefer option 3, as that's the one I'm (we?) most used to. It also looks generally better with the buttons above the textare rather than in the tabs.