topic Re: XSD schemas and UI Control in Alfresco Archive

XSD schemas and UI Control

tonizz — Mon, 30 Jul 2007 11:08:10 GMT

When you want to create a general web content from "Create Web Content" afresco provides you an UI that offers you a rich text editor whith a lot of options: text format, alignment, colors, images, links, tables, styles….Otherwise if you begin the process of creating a content from a web form, here

Re: XSD schemas and UI Control

mark_smithson — Mon, 30 Jul 2007 14:42:52 GMT

Hi

Try using xs:string rather than xs:anyType

Mark

Re: XSD schemas and UI Control

tonizz — Mon, 30 Jul 2007 15:37:15 GMT

Yes, you are right but in this way you only can use the WCM editor, I would like to use TinyMCE Editor, this is much more complete.

Thanks for your reply.

Re: XSD schemas and UI Control

arielb — Mon, 30 Jul 2007 22:39:47 GMT

they are all tinymce editors other than minimal appearance for xs:string which produces a plaintexteditor. the preferred type to use is xs:string as opposed to xs:anyType. as of 2.1 there is a full appearance defined for this type which will result in more buttons.

<?xml version="1.0" encoding="ISO-8859-1"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:alf="http://www.alfresco.org">
<!– defines the form for creating a news –>
<xs:element name="content">
<xs:complexType>
<xs:sequence>
<xs:element name="title" type="xs:normalizedString"/>
<xs:element name="body" type="xs:string">
  <xs:appinfo><xs:annotation><alf:appearance>full</alf:appearance></xs:annotation></xs:appinfo>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:schema>
‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

Re: XSD schemas and UI Control

sirclueless — Tue, 31 Jul 2007 09:32:41 GMT

I get the following error if I try to use the webform above :

org.alfresco.web.forms.FormProcessor$ProcessingException: org.alfresco.web.forms.xforms.FormBuilderException: error parsing schema: at line 9 column 18: s4s-elt-must-match.1: The content of 'content' must match (annotation?, (simpleType | complexType)?, (unique | key | keyref)*)). A problem was found starting at: appinfo.

What do I wrong or what is my mistake ??

Re: XSD schemas and UI Control

mark_smithson — Tue, 31 Jul 2007 09:34:17 GMT

sounds like a spelling error on the xs:annotation element - did you copy/paste or type it?

Re: XSD schemas and UI Control

sirclueless — Tue, 31 Jul 2007 09:37:46 GMT

I copy-paste it. Here is my complete webform:

<?xml version="1.0"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:alf="http://www.alfresco.org" elementFormDefault="qualified" attributeFormDefault="unqualified">
   <!– defines the form for creating a company home –>
   <xs:element name="infeurope">
      <xs:complexType>
         <xs:sequence>
            <xs:element name="header" type="xs:normalizedString"/>
            <xs:element name="content" type="xs:string">
               <xs:appinfo><xs:annotation><alf:appearance>full</alf:appearance></xs:annotation></xs:appinfo> 
            </xs:element> 
         </xs:sequence>
      </xs:complexType>
   </xs:element>
</xs:schema>
‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

I thought that is correct ,or?

Re: XSD schemas and UI Control

tonizz — Tue, 31 Jul 2007 09:51:45 GMT

could be that the xs:string line is not close by "/>"???

Re: XSD schemas and UI Control

sirclueless — Tue, 31 Jul 2007 09:55:28 GMT

I think that`s correct, cause that is in the element-tag and this tag will close later. It`s in the example above the same.

Re: XSD schemas and UI Control

mark_smithson — Tue, 31 Jul 2007 10:01:48 GMT

Ah - should be this

<xs:annotation><xs:appinfo><alf:appearance>full</alf:appearance></xs:appinfo></xs:annotation>

Re: XSD schemas and UI Control

sirclueless — Tue, 31 Jul 2007 10:28:52 GMT

Yes thank you ! That was the mistake. Now it works !!!

Re: XSD schemas and UI Control

tonizz — Mon, 03 Sep 2007 08:22:23 GMT

This option is good. But it would be much better if we could use TinyMCE as editor. Is it possible?

Why if you try to create content without webform you can use TinyMCE and if you start the edition from a webform you have to use this limited editor?

Thanks.

Re: XSD schemas and UI Control

kvc — Tue, 04 Sep 2007 13:08:46 GMT

In 2.1.0, we now support different appearance for the xf:textarea control that we generated from an xs:string defined in your XSD.

By default, xs:string uses the general xf:textarea UI control which implements a limited set of controls in a TinyMCE instance. You can specify a MINIMAL appearance, which will produce a Plain Text Editor (no TinyMCE), a FULL appearance or define any custom appearance type you want (including defining whatever TinyMCE plug-ins you want to enable as well).

You can see the different options you have or the different options you can create in web-client-config-wcm.xml:


           <widget xforms-type="xf:textarea"
                   appearance="minimal"
                   javascript-class-name="alfresco.xforms.PlainTextEditor"/>
           <widget xforms-type="xf:textarea"
                   javascript-class-name="alfresco.xforms.RichTextEditor">
             <param name="theme_advanced_buttons1">bold,italic,underline,separator,forecolor,backcolor,separator,link,unlink,image</param>
           </widget>
           <widget xforms-type="xf:textarea"
                   appearance="full"
                   javascript-class-name="alfresco.xforms.RichTextEditor">
             <param name="theme_advanced_buttons1">bold,italic,underline,strikethrough,separator,fontselect,fontsizeselect</param>
             <param name="theme_advanced_buttons2">link,unlink,image,separator,justifyleft,justifycenter,justifyright,justifyfull,separator,bullist,numlist,separator,undo,redo,separator,forecolor,backcolor</param>
             <param name="height">400</param>
           </widget>
           <!–
               NOTE: only the table tinymce plugin is part of the default alfresco distribution.  
               to enable other tinymce plugins, the plugin code must first be copied into the
               tinymce distribution within the webapp.
             –>
           <widget xforms-type="xf:textarea"
                   appearance="custom"
                   javascript-class-name="alfresco.xforms.RichTextEditor">
             <param name="theme_advanced_buttons1">bold,italic,underline,strikethrough,separator,fontselect,fontsizeselect</param>
             <param name="theme_advanced_buttons2">link,unlink,image,separator,justifyleft,justifycenter,justifyright,justifyfull,separator,bullist,numlist,separator,undo,redo,separator,forecolor,backcolor</param>
             <param name="height">600</param>
             <param name="mode">exact</param>
             <param name="force_p_newlines">true</param>
             <param name="apply_source_formatting">true</param>
             <param name="plugins">table</param>
             <param name="theme_advanced_buttons3">tablecontrols</param>
           </widget>
           <!–
           <widget xforms-type="xf:textarea"
                   appearance="fullscreen"
                   javascript-class-name="alfresco.xforms.RichTextEditor">
             <param name="theme_advanced_buttons1">bold,italic,underline,strikethrough,separator,fontselect,fontsizeselect</param>
             <param name="theme_advanced_buttons2">link,unlink,image,separator,justifyleft,justifycenter,justifyright,justifyfull,separator,bullist,numlist,separator,undo,redo,separator,forecolor,backcolor</param>
             <param name="height">600</param>
             <param name="plugins">fullscreen</param>
             <param name="theme_advanced_buttons3">fullscreen</param>
           </widget>
           –>
‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

Also, for more info on how various XSD types are mapped to XForms controls, you can take a look at the following wiki page:

http://wiki.alfresco.com/wiki/Forms_Developer_Guide#Supported_XML_Schema_structures_and_data_types

Kevin