Just to clarify. I'm not very much interested in joinig the current team. As it has been mentioned in this thread, the approach that the current project takes is very different from what I would like to see in the platform. A change in the rich text editing experience can certainly not be achieved by exchanging the provider based RTE.

If we want to improve on the platform I don't think doing some rush exchanging of things will help. That's what DNN has done in the past quite often and it's not the right approach. I do understand that we need a quick solution because the current RadEditor can probably not be upgraded to more recent releases due to licensing issues. It's a shame though that we have that situation in the first place. It's been a while that the Corp announced the separation from Telerik and what happened since then is that Evoq has been given a new RTE while no resources haven been given to the platform side of things. Now it seems to be up to the community to quickly come up with a solution for a component that really makes the heart of a CMS.

With regards to the 250 issues in the current project - most of them are related to way the editor and its configuration is implemented or the file browser dialogs. And that is another reason why I believe it's not right to follow that track. Implementing the editor as downloaded from the CKeditor site literally is one line of code. Extending it in a way that users can link to assets in the platform is what the actual integration should be about - and that is the part that should be done in the core anyway.

That is why possibly changing to another RTE in two years time shouldn't actually be too much of a problem - once we have those dialogs in place in the core.

---

Cheers, Philipp Becker, Peppertree Solutions

So this mostly about my provider i have to reply to some of the things that are not right

there are currently 220 outstanding issues listed on the project on CodePlex.

So actually there are only 5 open issues https://dnnckeditor.codeplex.com/work...

The current CKeditor does not work well because I think Ingo built it for his forum application which does not need styled html like the UI, part of the reason he does not want it used with the DNN Evoq content html module which btw comes with html agility dll.

Sorry but that is simply not true, i build the editor provider long before i used the forum module. And when did i ever said that i dont want the provider to be used with Evoq? If you would have read my comments on why i cannot support Evoq, because dnn no longer provides a trial version so iam unable to test my provider against evoq.

So while I can help with the issues I am more interested in the full CKeditor which by default includes inline editing based on their files on Github, features which Ingo is not interested in adding to his project.

Sorry but again something thats not true, i still have the request of your email in my inbox. The problem is that tecnically that is not possible with the current TextEditor control in dnn. And yes i'm interested in building an inline solution i already have a working prototype of the modfied html module with my InlineEditor Control. But as Sebastian already written inline editing needs to be implemented not only in the provider but also in dnn and every module that wants to support it.