X-Git-Url: http://git.ithinksw.org/extjs.git/blobdiff_plain/6746dc89c47ed01b165cc1152533605f97eb8e8d..HEAD:/docs/guides/forms/README.js diff --git a/docs/guides/forms/README.js b/docs/guides/forms/README.js index 5584001e..d1d37955 100644 --- a/docs/guides/forms/README.js +++ b/docs/guides/forms/README.js @@ -1,3 +1 @@ -Ext.data.JsonP.forms({ - "guide": "

Forms

\n\n
\n\n

Along with Grids, Forms are used in almost every Ext JS application. In version 3 we were a little constrained by the FormLayout, which made it difficult to get a form looking just right. Ext JS 4 removes the need for FormLayout altogether, enabling you to use any layout imaginable with your forms. Forms are also no longer tied to the DOM, making it easier than ever to have forms spanning multiple tabs without problems.

\n\n

With the addition of the new FieldLayout, any component can be placed into a form and given a label and even error messages. Because the definition of a Field has been moved into a Mixin, you can add a grid, tree or other component into a form and use it as a multi select.

\n" -}); \ No newline at end of file +Ext.data.JsonP.forms({"guide":"

Forms

\n\n
\n\n

A Form Panel is nothing more than a basic Panel with form handling abilities added.\nForm Panels can be used throughout an Ext application wherever there is a need to collect data from the user.\nIn addition, Form Panels can use any Container Layout, providing a convenient and flexible way to handle the positioning of their fields.\nForm Panels can also be bound to a Model, making it easy to load data from and submit data back to the server.\nUnder the hood a Form Panel wraps a Basic Form which handles all of its input field management, validation, submission, and form loading services.\nThis means that any of the config options of a Basic Form can be used directly on a Form Panel.

\n\n

Basic Form Panel

\n\n

To start off, here's how to create a simple form that collects user data:

\n\n
Ext.create('Ext.form.Panel', {\n    renderTo: Ext.getBody(),\n    title: 'User Form',\n    height: 130,\n    width: 280,\n    bodyPadding: 10,\n    defaultType: 'textfield',\n    items: [\n        {\n            fieldLabel: 'First Name',\n            name: 'firstName'\n        },\n        {\n            fieldLabel: 'Last Name',\n            name: 'lastName'\n        },\n        {\n            xtype: 'datefield',\n            fieldLabel: 'Date of Birth',\n            name: 'birthDate'\n        }\n    ]\n});\n
\n\n

This form renders itself to the document body and has three Fields - \"First Name\", \"Last Name\", and \"Date of Birth\". Fields are added to the Form Panel using the items configuration.\nThe fieldLabel configuration defines what text will appear in the label next to the field, and the name configuration becomes the name attribute of the underlying html field.\nNotice how this Form Panel has a defaultType of 'textfield'. This means that any of its items that do not have an xtype specified (the \"First Name\" and \"Last Name\" fields in this example), are Text Fields.\nThe \"Date of Birth\" field on the other hand has its xtype explicitly defined as 'datefield' which makes it a Date Field. Date Fields expect to only contain valid date data, and come with a DatePicker for selecting a date.

\n\n

See the Simple Form example for a live demo.

\n\n

Fields

\n\n

Field Types

\n\n

Ext JS provides a set of standard Field types out of the box. Any of the Fields in the Ext.form.field namespace can be used in a Form Panel. For more information see the API documentaion for each Field type:

\n\n\n\n\n

Validation

\n\n

1. Built-in Validations

\n\n

Ext JS has built in support for validation on any type of Field, and some Fields have built in validation rules.\nFor example if a value is entered into a Date Field and that value cannot be converted into a Date, the Field will have the x-form-invalid-field CSS class added to its HTML element.\nIf necessary, this CSS class can be changed using the invalidCls configuration. In the default theme, adding the invalidCls adds a red \"invalid underline\":

\n\n

\"Invalid

\n\n

A Field containing invalid data will also display an error message. By default this message displays as a tool tip:

\n\n

\"Invalid

\n\n

It's easy to change the location of a Field's error message using the msgTarget configuration, and the invalidText configuration changes the error message.\nEach Field provides its own implementation of invalidText, and many support token replacement in the error message.\nFor example, in a Date Field's invalidText, any occurrences of \"{0}\" will be replaced with the Field's value, and any occurrences of \"{1}\" will be replaced with the required date format.\nThe following code demonstrates placing the error message directly under the Field, and customizing the error message text:

\n\n
{\n    xtype: 'datefield',\n    fieldLabel: 'Date of Birth',\n    name: 'birthDate',\n    msgTarget: 'under', // location of the error message\n    invalidText: '\"{0}\" bad. \"{1}\" good.' // custom error message text\n}\n
\n\n

\"Custom

\n\n

2. Custom Validations

\n\n

Some validation requirements cannot be met using the built-in validations. The simplest way to implement a custom validation is to use the Text Field's regex configuration to apply validation rules, and the maskRe configuration to limit which characters can be typed into the field. Here's an example of a Text Field that validates a time.

\n\n
{\n    fieldLabel: 'Last Login Time',\n    name: 'loginTime',\n    regex: /^([1-9]|1[0-9]):([0-5][0-9])(\\s[a|p]m)$/i,\n    maskRe: /[\\d\\s:amp]/i,\n    invalidText: 'Not a valid time.  Must be in the format \"12:34 PM\".'\n}\n
\n\n

While the above method works well for validating a single field, it is not practical for an application that has many fields that share the same custom validation.\nThe Ext.form.field.VTypes class provides a solution for creating reusable custom validations. Here's how a custom \"time\" validator can be created:

\n\n
// custom Vtype for vtype:'time'\nvar timeTest = /^([1-9]|1[0-9]):([0-5][0-9])(\\s[a|p]m)$/i;\nExt.apply(Ext.form.field.VTypes, {\n    //  vtype validation function\n    time: function(val, field) {\n        return timeTest.test(val);\n    },\n    // vtype Text property: The error text to display when the validation function returns false\n    timeText: 'Not a valid time.  Must be in the format \"12:34 PM\".',\n    // vtype Mask property: The keystroke filter mask\n    timeMask: /[\\d\\s:amp]/i\n});\n
\n\n

Once a custom validator has been created it can be used on Text Fields throughout an application using the vtype configuration:

\n\n
{\n    fieldLabel: 'Last Login Time',\n    name: 'loginTime',\n    vtype: 'time'\n}\n
\n\n

See Validation Example for a working demo. For more information on custom validations please refer to the API Documentation for VTypes.

\n\n

Handling Data

\n\n

Submitting a Form

\n\n

The simplest way to submit data to the server is to use the url configuration of Basic Form. Since Form Panel wraps a Basic Form, we can use any of Basic Form's configuration options directly on a Form Panel:

\n\n
Ext.create('Ext.form.Panel', {\n    ...\n    url: 'add_user',\n    items: [\n        ...\n    ]\n});\n
\n\n

The Basic Form's submit method can be used to submit data to the configured url:

\n\n
Ext.create('Ext.form.Panel', {\n    ...\n    url: 'add_user',\n    items: [\n        ...\n    ],\n    buttons: [\n        {\n            text: 'Submit',\n            handler: function() {\n                var form = this.up('form').getForm(); // get the basic form\n                if (form.isValid()) { // make sure the form contains valid data before submitting\n                    form.submit({\n                        success: function(form, action) {\n                           Ext.Msg.alert('Success', action.result.msg);\n                        },\n                        failure: function(form, action) {\n                            Ext.Msg.alert('Failed', action.result.msg);\n                        }\n                    });\n                } else { // display error alert if the data is invalid\n                    Ext.Msg.alert('Invalid Data', 'Please correct form errors.')\n                }\n            }\n        }\n    ]\n});\n
\n\n

In the above example a button is configured with a handler that handles form submission. The handler takes the following actions:

\n\n
    \n
  1. First a reference to the Basic Form must be acquired.
  2. \n
  3. Then the isValid method is called before submission to verify that none of the fields have validation errors.
  4. \n
  5. Finally the submit method is called, and two callback functions are passed - success and failure. Within these callback functions action.result refers to the parsed JSON response.
  6. \n
\n\n\n

The above example expects a JSON response that looks something like this:

\n\n
{ \"success\": true, \"msg\": \"User added successfully\" }\n
\n\n

Form Submission Example

\n\n

Binding a Form to a Model

\n\n

The Model class is used throughout Ext JS for representing various types of data, as well as retrieving and updating data on the server.\nA Model representing a User would define the fields a User has, as well as a proxy for loading and saving data:

\n\n
Ext.define('User', {\n    extend: 'Ext.data.Model',\n    fields: ['firstName', 'lastName', 'birthDate'],\n    proxy: {\n        type: 'ajax',\n        api: {\n            read: 'data/get_user',\n            update: 'data/update_user'\n        },\n        reader: {\n            type: 'json',\n            root: 'users'\n        }\n    }\n});\n
\n\n

For more details on working with Models please refer to the Data Guide.

\n\n

Data can be loaded into a Form Panel directly from a Model using the loadRecord method:

\n\n
Ext.ModelMgr.getModel('User').load(1, { // load user with ID of \"1\"\n    success: function(user) {\n        userForm.loadRecord(user); // when user is loaded successfully, load the data into the form\n    }\n});\n
\n\n

Finally, instead of using the submit method to save the data, Basic Form's updateRecord method is used to update the record with the form data, and the Model's save method is called to save the data to the server:

\n\n
Ext.create('Ext.form.Panel', {\n    ...\n    url: 'add_user',\n    items: [\n        ...\n    ],\n    buttons: [\n        {\n            text: 'Submit',\n            handler: function() {\n                var form = this.up('form').getForm(), // get the basic form\n                    record = form.getRecord(); // get the underlying model instance\n                if (form.isValid()) { // make sure the form contains valid data before submitting\n                    form.updateRecord(record); // update the record with the form data\n                    record.save({ // save the record to the server\n                        success: function(user) {\n                            Ext.Msg.alert('Success', 'User saved successfully.')\n                        },\n                        failure: function(user) {\n                            Ext.Msg.alert('Failure', 'Failed to save user.')\n                        }\n                    });\n                } else { // display error alert if the data is invalid\n                    Ext.Msg.alert('Invalid Data', 'Please correct form errors.')\n                }\n            }\n        }\n    ]\n});\n
\n\n

Model Binding Example

\n\n

Layouts

\n\n

Layouts are used to handle sizing and positioning of components in an Ext JS application. Form Panels can use any Container Layout. For more information on Layouts please refer to the Layouts and Containers Guide.

\n\n

For example, positioning fields in a form horizontally can easily be done using an HBox Layout:

\n\n
Ext.create('Ext.form.Panel', {\n    renderTo: Ext.getBody(),\n    title: 'User Form',\n    height: 100,\n    width: 515,\n    defaults: {\n        xtype: 'textfield',\n        labelAlign: 'top',\n        padding: 10\n    },\n    layout: {\n        type: 'hbox'\n    },\n    items: [\n        {\n            fieldLabel: 'First Name',\n            name: 'firstName'\n        },\n        {\n            fieldLabel: 'Last Name',\n            name: 'lastName'\n        },\n        {\n            xtype: 'datefield',\n            fieldLabel: 'Date of Birth',\n            name: 'birthDate'\n        }\n    ]\n});\n
\n\n

See the Layout Example for a live demo.

\n","title":"The Form Package"}); \ No newline at end of file