Already leading the field of web-based editor controls Telerik has strengthened their position, adding a host of new features and today announcing the release of version 4.0.
Spanning from practical to nifty to "thank God they fixed that", Telerik has clearly listened to input from their customer base and from their spiffy new partner, one Microsoft Corporation. This release adds a little bit of new love for developers, authors, designers, and content managers.
The full set of new features include:
Accessibility - Section "508" compliant content
Four ways to paste from Word
Enhanced tools and dialogs
Fully compatible with .NET 2.0
Superior table management
Improved application of styles
New Undo/Redo mechanism
Code indentation in HTML mode
Support for .NET 2.0 Themes mechanism
Help 2.0 documentation
Ready-to-use VS.NET projects in C# and VB.NET
The section 508 compliance facilitation will surely be a big plus for US-based Microsoft CMS customers. Many of the other features are just positive steps forward across the board. The new undo/redo mechanism is welcome for all, as the previous one had some frustrating flaws. Overall this is a strong update to the tool and certainly merits a full version rev. New Licensing With the new release comes an updated licensing scheme, the Single Developer model. The editor SD License comes home with you for USD 349. That allows one developer to use the editor for an unlimited number projects and domains. Previously the editor was licensed by domain and IP, which was obviously a bit more tedious to manage.
With the above said, if you are a Microsoft CMS customer, remember that the Telerik editor plugs right into the MCMS framework and is FREE for those with a valid MCMS license. Learn more. | View demos. Editor's Note: Due to feedback from Telerik, the title of this article has been changed from "Telerik Editor for Microsoft CMS Updated" to "Telerik Updates Web Editor Control". Their MCMS editor, while based on roughly the same code is following a different release schedule. Please see the article's inline comments and Mark Harrison's blog entry for additional details.