Skip to content

Latest commit

 

History

History
67 lines (58 loc) · 4.27 KB

TODOs.md

File metadata and controls

67 lines (58 loc) · 4.27 KB

TODOs

TODO Later...

  • full height and distraction free functionality matching is confusing
  • support gutenberg
    • html block
    • shortcode backwards compat
    • gutenberg block comment + json
  • fewer but better themes
  • update layout on 1-2 column switch
  • load in visual 2col, switch to text, settings is in wrong place
  • drop jQuery dependency, needed now for form switch

Testing

  • test new features
  • browsers
    • Safari - seems ok
    • FireFox (Mac) - seems ok
    • Chrome (Mac) - seems ok
    • FireFox (Win10) - seems ok
    • Chrome (Win10) - seems ok
    • Edge - seems ok
    • IE 11 - Support dropped. Don't test

CD from wordpress

cd wp-content/plugins/HESH-WordPress-Plugin/

Useful Links

Support Gutenberg:

A proper implementation might require a different program altogether. Many of the features that create complexity in the current hesh.js(e.g. inserting media, buttons that wrap text in <em> tags, etc.) do not exist in Gutenberg, and the startup/stop/saving methods will have to be done using Gutenberg EsNext/React/Js/whatever. Learning the Gutenberg API will take time. It is new, incomplete, and not yet well documented. I believe a similar implementation is possible, but I'm not sure when I'll have time to work on it...

Features:

  • Gutenberg Code Editor (with just the current highligher)
    • Listen for switch between Visual Editor and Code Editor to start up.: There is currently no easy/quick way to listen for these button presses because they have no exclusive identifiers.
    • For the same reason, there is no easy way to save the codemirror state back to the textarea input and thus save the work.
    • The "correct" switching implementation would be from extending the Gutenberg API and listen for some event or hook to start and to stop/save.
    • Scrolling will have to work differently. The current textarea scrolls contains the full height of all the text. Codemirror can do this too, but a lack of virtualization causes poor performance, and additional features(search for example) require the editor edges to be present at all times.
    • Maybe just submit a Gutenberg pull request instead of extension/plugin?
    • If it requires redoing large amounts of work, maybe just start over using VS Code's Monaco Editor instead? It is 1000% better. WP Code?
  • Gutenberg Code Editor syntax parser of block-comment+json
    • gutenberg HTML comment syntax
    • highlight xml-like start and stops tags of HTML comments.
    • highlight json as attributes inside tags.
    • <!-- wp:namespace/tag-name {"json":"attributes"} --> content <!-- /wp:namespace/tag-name -->
    • <!-- wp:singletag /-->
  • Shortcode block editing with highlighting
    • Extend the current shortcode block.
    • Use the current HTML+shortcode highlighter.
  • Highlighting 'Edit as HTML' feature of all blocks
    • WP Gutenberg might be planning to implement this natively. TODO: search for an issue.
  • HTML block already works
    • This one uses Emmet and its already GREAT!
    • Extend the current HTML block to follow the same settings and make everything consistent.