Defining template default toolbars

System

Hi,

I have a custom template that includes toolbars such as font(bold,italic,etc..) as well as one that presents the document in 2 different views either

a. View as WYSIWYG or b. View Source

below is the code for the 2 buttons on the toolbar

viewas enabled="true" publish="cleanhtml" mode="body" unicode="false"
cmd name="cmdviewaswysiwyg" key="page" ref="cmdVAW" /
cmd name="cmdviewashtml" key="pagetag" ref="cmdVAH" /
cmd name="cmdviewasproperties" key="viewprop" ref="cmdVAProp" /
/viewas

Is there a way to set the default as the "cmdviewashtml" mode instead of the way it is now as "cmdviewaswysiwyg"?

Thanks a bunch

Frederik

this is the 2nd such request in 2 weeks, so I got intrigued

I couldn't find a straightforward way (via configs), but after a few hours trying, I got something with FormAPI that might be acceptable for some people.

This code is supposed to be self-documenting, so it's overloaded with alerts and comments, and other less-than-efficient operations. It also only handles one VFE per DCT.

The basic concept is to set a repeating 'task' that checks every 0,5 seconds whether the VisualFormat Editor is loaded, and if so, will change it to ViewAs HTML. It then stops rescheduling itself, so user can choose to move back and forth between WYSIWYG and HTML views. Also, I noticed that if a user *interactively* switches from WYSIWYG to HTML, most of the formatting menu buttons get grayed out, which doesn't happen if the change to HTML-view is done by this code. So be it.

//------------------------------------------------------------------------------------
// FormAPI code. Add this to DCT between < script>...< /script>

function init() {

  // we CAN optionally setFocus so that the activeX gets loaded from the beginning and
  //  the messages we send later on (ExecCommand) have a better chance of getting executed
  // uncomment next line if you want that
  //IWDatacapture.getItem("/item/path/to/textarea").setFocus();

  // Note that loading the ActiveX runs in the background... at this time, the following holds:
  //   top._dcWin.eWebEditPro.instances[0].isEditor() == 0 (false)
  //   top._dcWin.eWebEditPro.instances[0].editor     == null

  setVFhtml();
}

function setVFhtml(){
  var vfobj = top._dcWin.eWebEditPro.instances[0];
  if ( vfobj.isEditor() ) {
    // Note: if no 'setFocus' was done before on the VF field,
    //  then after some time, the isEditor will be true, but the ExecCommand will not actually execute
    //  However, I found no direct way to detect when that happens (no exception thrown, no special return value)
    //  Also vfobj.status == 'loaded' at this point
    // !But! it seems that we can test with the Toolbars() function
    // It would be logical to combine the following 'if' with the previous, but keeping it like this
    //  for the educational value
    if (vfobj.editor.Toolbars() != null) {
       vfobj.editor.ExecCommand('cmdviewashtml', '', 0);
       // alert('Should be ok now!');
       return;
    } else {
       // alert('Toolbars NULL, VFE not active, will reschedule');
    }
  }
  setTimeout("setVFhtml()", 1000);
  //alert('rescheduled');
}

IWEventRegistry.addFormHandler("onFormInit", init);

//------------------------------------------------------------------------------------

Note that the VFE still first opens in WYSIWYG mode, with all the possible (auto)cleaning performed (AFAIK).