Forum OpenACS Q&A: Re: xowiki Folder Object

No luck so far.

R.

The parameter WidgetSpec is used when displaying those forms used for creating/editing xowiki objects, i.e. : Pages, PageInstances, Forms, etc. So if you take your example and change "bannerpages_pagetext_para01" for "text"; you will see that every time you create/edit a Page the "Content" field uses the Xinha configuration you provided.

But if you want to provide such customization for a form-field ( I guess your form-field in this example is called: banner_pagetext_para01) you would have to configure your formfield as follows ( on the form constraints section )

{bannerpages_pagetext_para01=richtext,editor=xinha,label=Content,plugins=Stylist OacsFs,javascript=xinha_config.stylistLoadStylesheet('/resources/xowiki/examples/xinha-mc-styles.css');}

I hope this helps you on what you are trying to achieve.

Best,

Thank you for this reply. The Stylist form-field configuration works fine done like this. However, when I try to specify the toolbar config, the form-field chokes on the '[' and the ']'. I presume that this is a security issue since these characters have special meaning in tcl.

Is there a way to submit a toolbar config to xinha for a form-field without using the '[' and ']' characters.

Regards
Richard

var xinha_config.toolbar = new Array('popupeditor','separator','textindicator');

However, this won't work because xowiki interprets the commas as delimiters even when inside curly braces.

The following works:

var xinha_config.toolbar = new Array('popupeditor');

....but clearly this is not much use! 😊

I would like to be able to put the following nested array specification into a form field specification:

{main_page_content:richtext,editor=xinha,label=Other Content,plugins=Stylist OacsFs,javascript=var xinha_config.toolbar = new Array(new Array('popupeditor'),new Array('separator','textindicator'),new Array('separator','justifyleft','justifycenter','justifyright','justifyfull'),new Array('separator','insertorderedlist','insertunorderedlist','outdent','indent'),new Array('separator','inserthorizontalrule','createlink','insertimage','inserttable'),new Array('linebreak','undo','redo','separator','selectall','print'), (Xinha.is_gecko ? [] : ['cut','copy','paste','overwrite','saveas']), new Array('separator','killword','clearfonts','removeformat','toggleborders','splitblock','lefttoright','righttoleft'), new Array('separator','htmlmode','showhelp','about'));}

Regards
Richard

{_text:richtext,editor=xinha,javascript=
xinha_config.toolbar = [
    ['popupeditor'__COMMA__ 'bold'__COMMA__'italic'__COMMA__'createlink'__COMMA__'insertimage'__COMMA__'separator']__COMMA__
    ['killword'__COMMA__'removeformat']
  ];
}

Thank you for the reply. The __COMMA__ substitution is extremely helpful thankyou.

For the sake of completeness I wanted to let you know that the above proposed notation (i.e. with square brackets) does not in fact work because the '[' and ']' fail the form validation checks in xowiki.

However, this notation works:

{main_page_content:richtext,editor=xinha,label=Content,plugins=Stylist OacsFs,javascript=xinha_config.toolbar=new Array(new Array('popupeditor')__COMMA__new Array('separator'__COMMA__'textindicator'));}

This is exactly what I wanted to achieve, however it still pains me that I cannot work out why the more general widgetspec parameter specification method doesn't work for me.

Regards
Richard

That is strange. I have just tried this again by creating a test form with a single field on it. I have copied your code from the forum post and I receive this error:

Error in field Form Constraints: Form constraint contains invalid characters

Could it be that the form validation on my setup is different for some reason? Is your form validation set to the default?

Content:  @test_var@

Form:  <form>@test_var@</form>

Form Constraints:  {test_var:richtext,editor=xinha,javascript=
xinha_config.toolbar = [
    ['popupeditor'__COMMA__ 'bold'__COMMA__'italic'__COMMA__'createlink'__COMMA__'insertimage'__COMMA__'separator']__COMMA__
    ['killword'__COMMA__'removeformat']
  ];
}

Regards
Richard

I now finally understand that adding a xinha config to a formfield spec is the only way currently to configure the editor for Xowiki.Form fields.

In my current experiment, where I have several textarea fields that all need xinha activated with the same configuration, this is very verbose and repetitive.

It would be great to have the ability to set a default spec for xinha for use when filling-out/ creating instances of Xowiki.Forms.

regards
Richard