Editor.js: Block Tunes API

[neSpecc]

Provide API that allows to build Block Tunes plugins

[rishighan]

Hello @neSpecc, Thanks for your work on editor.js
I have a few questions about Block Tunes:

1. Why does selecting 90% of the text in a block give me a block tunes menu? From the user's perspective it is 90% of the text, not 100%. Shouldn't the user see an inline tools menu unless they select 100% of the text? (at which point they have selected the content of the entire block)
2. The conversion menu is another point of contention. Given the fuzziness around what constitutes a block vs. what constitutes not-a-block, the paradigm of block and inline menus starts to get confusing. Should editor.js offer a static toolbar with both block and inline options? The menu tools can be enabled or disabled based on whether the user is navigation a block or just the contents of a block. Just wanted to get your perspective on this.

[fdev]

Any progress on this? I would love to be able to add custom Block Tunes that apply to all block types.

[neSpecc]

@fdev we have a PR implementing this feature, but it is currently in a freezed state. Upcoming version 2.16 won't contain that, but 2.17 — maybe.

[carakas]

Looking forward to this one

[nsobolev]

Привет, когда релиз? Нужно реализовать эту фичу - https://github.com/codex-team/editor.js/issues/980

[mikekoro]

@fdev we have a PR implementing this feature, but it is currently in a freezed state. Upcoming version 2.16 won't contain that, but 2.17 — maybe.

Currently at 2.17. Seems like it didnt make it did?

[mguenther]

Any news on this?

[gohabereg]

Hi @mguenther

There are two related PRs opened #1075 #1078.

1078 includes Block Tunes API, but it's only on the concept stage. There are still some things to do. Will be merged after it's tested and approved