Hello,
I proposed to use the RadRichTextEditor to edit simple Docx documents and use the format providers to convert the docx documents to html (for sending as html e-mail).
But now I found that there is also the new WordsProcessing which can do the same conversions.
If I am right WordsProcessing does not (yet?) have an editor for visual editing. (Is that proposed? Or is the RadRichTextEditor the proposed way to go?).
For the conversion from Docx to Html, are there any pros or cons or difference in quality in using the format providers found in the RichTextEditor assembly or the WordsProcessing assemblies?
Or use they in fact the same code base?
I proposed to use the RadRichTextEditor to edit simple Docx documents and use the format providers to convert the docx documents to html (for sending as html e-mail).
But now I found that there is also the new WordsProcessing which can do the same conversions.
If I am right WordsProcessing does not (yet?) have an editor for visual editing. (Is that proposed? Or is the RadRichTextEditor the proposed way to go?).
For the conversion from Docx to Html, are there any pros or cons or difference in quality in using the format providers found in the RichTextEditor assembly or the WordsProcessing assemblies?
Or use they in fact the same code base?
1 Answer, 1 is accepted
0
Hi Jaap,
RadWordsProcessing is intended as a library completely independent from UI. For this reason it doesn't provide UI and we have no plans to introduce such functionality. If you need to show and edit documents, RadRichTextEditor is the way to go.
The two components don't share a common code base, although they both use some utility methods and classes. As to the quality of the import-export roundtrip you want to achieve, this greatly depends on the exact content that your documents have. WordsProcessing is fairly new, so it still misses some features although we are actively working on implementing them. Also, it's a bit easier for us to add new features to it, since there is no need to implement them in the UI. RichTextEditor, on the other hand, is almost feature-complete but has some limitations in terms of HTML support.
My suggestion to you would be to try them both and see which one fits your needs better. If you have any questions or concerns, do not hesitate to get back to us.
Regards,
Petya
Telerik
RadWordsProcessing is intended as a library completely independent from UI. For this reason it doesn't provide UI and we have no plans to introduce such functionality. If you need to show and edit documents, RadRichTextEditor is the way to go.
The two components don't share a common code base, although they both use some utility methods and classes. As to the quality of the import-export roundtrip you want to achieve, this greatly depends on the exact content that your documents have. WordsProcessing is fairly new, so it still misses some features although we are actively working on implementing them. Also, it's a bit easier for us to add new features to it, since there is no need to implement them in the UI. RichTextEditor, on the other hand, is almost feature-complete but has some limitations in terms of HTML support.
My suggestion to you would be to try them both and see which one fits your needs better. If you have any questions or concerns, do not hesitate to get back to us.
Regards,
Petya
Telerik
Check out the Telerik Platform - the only platform that combines a rich set of UI tools with powerful cloud services to develop web, hybrid and native mobile apps.