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

📅 News and updates: November 28, 2016 #169

Open
Reinmar opened this issue Nov 28, 2016 · 0 comments
Open

📅 News and updates: November 28, 2016 #169

Reinmar opened this issue Nov 28, 2016 · 0 comments

Comments

@Reinmar
Copy link
Member

Reinmar commented Nov 28, 2016

During the last ~five weeks we released the fourth developer preview and focused on iteration 5 which involved us in the following topics:

  • We've set up continuous integration for CKEditor 5 packages. Not only does it look great (we love green badges ;>), but it also significantly sped up our review process.
  • We have added custom copy/cut support for the clipboard feature. It is important to have full control over what gets to the clipboard when dealing with rich content (like e.g. widgets) and browser quirks.
  • First version of the image feature has landed. It adds image rendering and widget API to the previously implemented fake selection support. We will continue working on this feature and the widget system as there are many levels on which it needs to integrate with other features.
  • We finished a huge UI library refactoring. In general, the refactoring allowed us to remove more than a thousand lines of code, which is a great improvement at this stage. It also significantly simplified the code.
  • We are also constantly working on developing a set of JSDoc plugins which will allow us to write CKEditor 5 API documentation in a simpler and more maintainable way. For instance, we added links and type references validation as well as better support for ES6 classes and modules. In CKEditor 4 we use JSDuck, which is an amazing tool but no longer supported and it is written in Ruby + ExtJS what did not allow us to take over this project. Unfortunately, we have not found a JavaScript API documentation generator which would fit our heavy use case well. We have checked a couple of available generators and decided that JSDoc is still the best one and that we should be able to make necessary adjustments through plugins. Not without troubles, but we managed to achieve satisfying results and we are now reformatting our API docs to the new format. We will share our solution with the JSDoc community once it stabilizes.
@Reinmar Reinmar changed the title 📅 News and Updates: November 28, 2016 📅 News and updates: November 28, 2016 Feb 7, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant