jaelelli hanalle moritz

2 views

Skip to first unread message

Divina Milliken

unread,

Aug 3, 2024, 1:44:54 AM8/3/24

to mohacara

The CKEditor team is excited to announce the release of CKEditor 5 version 42.0.0. This version brings significant improvements to the onboarding experience and installation methods, designed to simplify and enhance the integration process for developers. The update includes new installation methods, an upgraded online builder, and comprehensive documentation updates.

The latest version of CKEditor 5 is v42.0.0, which introduces significant improvements to the onboarding experience and installation methods. This update aims to simplify the integration process and enhance the overall user experience.

Back in 2017, when CKEditor 5 was initially launched, webpack was a favored bundler of choice for many and our decision had solid reasoning, but as trends and the JavaScript ecosystem evolved, so did the favored choices.

The ecosystem around CKEditor 5 is complex, and so is the editor itself, with its multiple plugins and extensible APIs. Continuous feedback from the community and customers indicated a need for simpler, yet more versatile methods. Considering this, we decided to focus on standards and allow users to install CKEditor 5 as they install any other library:

The new methods allow for easy installation and integration without bundler or framework-specific dependencies. This change simplifies the setup process and reduces potential integration errors, improving the overall user experience. The new installation methods include:

Legacy installation methods will continue to work to ensure a smooth transition. Support for predefined and custom builds will be maintained until the end of Q1 2025 while DLL methods will be supported until the end of 2025. Detailed information about depreciation timelines can be found in the documentation.

As the new installation methods are a substantial update covering a plethora of use cases, your input is immensely valuable, so do not hesitate to share your experiences, ask questions, and provide feedback to help us refine these changes.

To accompany the new installation methods, we are also introducing a new builder. We wanted to create a smoother experience for creating the desired editor with the possibility to set it up in multiple environments.

Now the new builder provides a centralized, interactive interface where users can select features, configure toolbars, and preview the customization changes in real-time. So you can build your editor and get your code snippets in four easy steps.

The builder provides Vanilla, React, Angular, Vue setups with CDN and npm distributions. This streamlined process enhances user engagement and speeds up editor setup, making it more accessible and efficient for both new and experienced users.

Greenplum uses the Postgresql JDBC (v42.0.0) driver included with Aqua Data Studio, and it works across all versions of Greenplum. Greenplum server releases are frequent, and may sometimes require updating the JDBC driver. Refer to your Greenplum installation documentation for the appropriate PostgreSQL driver requirements.

To update the Aqua Data Studio JDBC drivers for Greenplum you need to overwrite the Aqua Data Studio postgresql.jar file. Below is a listing of the Aqua Data Studio library directory [ADS_INSTALL]\lib\drivers\ ...

The Java class path for the drivers are already configured for ADS in the datastudio.ini for launching ADS with datastudio.exe and in datastudio.bat/.sh and datastudio-bundled.bat/.sh for launching Aqua Data Studio from the command line.

I am working on POC and evaluating platform events feature for our near real time integration. I have create an event and trying to test it with workbench. Some thing like shown in this video =L6OWyCfQD6U ar around 17:14.

I spent a lot of time banging my head against this as well. I finally realized that in the video, the presenter is using (v42.0.0i) instead of the publicly-available (currently v41.0.1). Even though he's hitting API 40, he's on a newer version of Workbench that must do a better job of listening for Platform Events.