/
index.html
55 lines (46 loc) · 1.73 KB
/
index.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
---
layout: default
navPage: docs
heading: Field Types
breadcrumbs:
- User Documentation,/userdoc/
- Field Types
prev: Customizing validation,/userdoc/field_validation/customizing_validation/
next: How field types are used,/userdoc/field_types/how_field_types_are_used/
categories: userdoc
page_type: introduction
tags: field_types
---
{% include open_section.html nav='nav_userdoc_field_types.html' selected='field_types' %}
{% include screenshot.html item="i190.jpg" %}
<p>
Form Tools 2.1.0 radically changed the way form field types were handled. Before 2.1, there was the following
hardcoded list of supported field types:
</p>
<ul>
<li>Textbox</li>
<li>Textarea</li>
<li>Password</li>
<li>WYWISYG (<a href="http://tinymce.moxiecode.com/">TinyMCE</a>)</li>
<li>File</li>
<li>Radio Buttons</li>
<li>Checkboxes</li>
<li>Dropdown</li>
<li>Multi-select dropdown</li>
</ul>
<p>
While these fields covered most typical uses, occasionally you'd run into a situation where you'd need
something different. So, Form Tools 2.1.0 was designed to allow you to extend it to support any type of field
you want - for example, <a href="{{site.baseurl}}/modules/field_type_google_maps/">Google Maps fields</a>,
<a href="ft_phones/">Phone number fields</a>, or any of the HTML5 field
types currently gaining traction with the browser vendors.
</p>
<p>
The following section documents the ins and outs of the field types that are bundled
with Form Tools 2.1, including the File and TinyMCE field type modules.
</p>
<p>
Actual customization of the field types is done with the aid of the
<a href="{{site.baseurl}}/modules/custom_fields/">Custom Fields module</a>.
</p>
{% include close_section.html %}