Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

update the TinyMCE per Block prototype UI to match the Prototype UI style. Also make it keyboard friendly #136

Merged
merged 14 commits into from
Feb 28, 2017

Conversation

youknowriad
Copy link
Contributor

@youknowriad youknowriad commented Feb 24, 2017

closes #83

The idea is when you switch between prototype, you can't see the difference quickly regarding the style. This could ease comparing them technically only.

@youknowriad youknowriad added the [Type] Enhancement A suggestion for improvement. label Feb 24, 2017
@youknowriad youknowriad self-assigned this Feb 24, 2017
@youknowriad youknowriad requested a review from aduth February 24, 2017 12:29
@aduth
Copy link
Member

aduth commented Feb 24, 2017

Should we be relying on or moving styles to the shared shared/index.css stylesheet?

@youknowriad
Copy link
Contributor Author

@aduth working on it

@youknowriad youknowriad force-pushed the update/tiny-mce-per-block-ui branch from 72abde0 to 14565d5 Compare February 24, 2017 15:27
@@ -1,3 +1,4 @@
@import '../../../../shared/index';
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I preferred including this here instead of index.html to keep the npm run dev command working

@youknowriad
Copy link
Contributor Author

youknowriad commented Feb 24, 2017

Updated to use the shared css in 14565d5

@youknowriad youknowriad force-pushed the update/tiny-mce-per-block-ui branch from 882294c to ad82af9 Compare February 25, 2017 17:56
@youknowriad
Copy link
Contributor Author

@aduth Do you think we can merge this. I know how you feel about this approach, but I'm guessing this branch is more evolved than the current prototype. Having it live could encourage some feedback on the pros/cons ?

I'm also planning to write a summary of the technical aspects here : What does this approach mean for UX? What are the UX limits? How does this work? How to write a block? ...

@youknowriad youknowriad changed the title update the TinyMCE per Block prototype UI to match the Prototype UI stype update the TinyMCE per Block prototype UI to match the Prototype UI style. Also make it keyboard friendly Feb 28, 2017
@youknowriad
Copy link
Contributor Author

I'm merging this giant PR to be able to do smaller incremental upgrades later.

@youknowriad youknowriad merged commit 01f2c86 into master Feb 28, 2017
@youknowriad youknowriad deleted the update/tiny-mce-per-block-ui branch February 28, 2017 11:59
nylen pushed a commit that referenced this pull request Mar 16, 2017
…tyle. Also make it keyboard friendly (#136)

* update the TinyMCE per Block prototype UI to match the Prototype UI style
* Adding heading block
* Adding a paragraph block and moving to React
 - preact has some state updating bugs
* Allowing removing/merging components using backspace
* Handling navigation using arrow keys
* Adding a simple quote  block
hypest pushed a commit that referenced this pull request Nov 2, 2018
Implements a basic ENTER interception mechanism.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Type] Enhancement A suggestion for improvement.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Consolidate TinyMCE Prototypes to Gutenberg UI
2 participants