The new radeditor toolbar defaults in DNN600 really fail totally to do justice to what the system is capable.  The dev's need to take a good look at what is capable of being done and give people strong reasons to want to use the tools they have.

The HTML Editor Manager - buried in the Host menu provides direct access to control of all the buttons and features that are available using the RadEditor - but sadly many of them are simply not defined or included in the default settings provided by the installer.
I'm sure this is going to lead to a huge number of support calls as people start to adopt dnn600.

Having said all this - what is really missing from the default settings are some of the more commonly used editing tools pretty much every user still expects to see.

Set font color, set font size by point, set background color - and the Left, Center, Right and Justify layout options -  yes i know some people will argue about bad html and the need for css - but most end users could care less they want a center button - and out of the bag its missing..

Using the HTML Editor Manager it is possible to add all these features back into the menu - but it does require some understanding of XML layout and a bit of digging on the internet to find the documentation that explains the settings.  The reason for this - all the settings are controlled by an XML file - which needs to be edited by hand  ---

At a minimum these need to be added to the default layout

<tool name="JustifyLeft" />
<tool name="JustifyCenter" />
<tool name="JustifyRight" />

<tool name="ForeColor" />
<tool name="BackColor"/>
<tool name="FontName"/>
<tool name="FontSize"/>

and finally for completeness

<tool name="RealFontSize"/>

And for those more power users - just by adding a couple of lines of code to the toolbar definition you get some of the most useful tools a inline html editor has ever provided,

The default settings for DNN looks like this:
    <modules>
        <module name="RadEditorStatistics" dockingZone="Bottom"/>
    </modules>
Try changing them to this:

<modules>
     <module name="RadEditorStatistics" dockingZone="Bottom" enabled="true" visible="true" dockable="true" />
     <module name="RadEditorDomInspector" dockingZone="Module" enabled="true" visible="true" dockable="true" />
     <module name="RadEditorNodeInspector" dockingZone="Module" enabled="true" visible="true" dockable="true" />
</modules>

Adds a bunch of amazingly useful info at the bottom of the html edit window especially when working with tables and other editable elements.

Westa

Hey Joe,

What would maybe be a good idea - is a setup similar to the demo on telerik - that is - a way to select from one of a couple of default templates in the HTML Config Manager: Full, Typical and Minimalist maybe.

I totally understand that admins like to lock end users down and thats totally cool - but its much easier to remove elements u dont want from the toolbar.xml config - than for an end user admin to try and find out how to add missing features they dont even know exist.

Just kinda feels odd to have this very powerful html editor - yet when people first see it in the demo install - it fails to show off its full capability.

Have said this - maybe another thought - how about another way of giving site installers some understanding of its power
 - this option would be to pre-configure a profile for EVERYONE and a separate profile for ADMIN and HOSTS - instead of the single EVERYONE profile that we have by default currently,

That way out of the box the HOST gets to see all the features and have a FULL template that lists all the supported options and shows what  the editor is capable of doing and ADMIN maybe gets a STANDARD config that covers the main features and EVERYONE config could them be a minimalist version.  This way out of the box everyone wins.

Just my two cents anyway . . . created my own custom templates back when guys at dnnwerk first got the feature released.

Cheers

Westa

PS - while im thinking of it - about the only feature that's currently missing is a way to define a editor config to a specific module on a page.

Xaevion,

You can configure the toolbar in the new editor in all the same ways that the old telerik provider toolbar can be configured.

BTW, 6.0.1 will add more defaults items to the toolbar.