We are switching from CuteEditor to RadEditor but have one problem that I am so far unable to resolve.
We are using the RadEditor in the backend admin area to design content displayed in the front end. This content is itself dependent on url based theming. We override all the global styles for the front end editable page area by wrapping them in a div with ID/Class.
This makes it particularly easy to then display the content in the correct fashion in the backend preview areas by also wrapping them in an equivalent div. With CuteEditor, I was also able to set the Editor's content window with a class or ID which was great as the css inheritance could still be used.
Do you have any suggestions
I am setting the appropriate css files in the code behind for the default and themed style sheets:
"/App_Themes/" + subApp.Theme + "/ThemedPageContent.css");
my global styles are then
.pagetemplate li etc......