Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>You're going to have to load and send the fields in a format ExtJS understands. The simplest way, if you don't mind coupling directly to the ExtJS format, would be to generate the ExtJS template style on the backend. In that case, your php script would generate something like this:</p> <pre><code>new Ext.form.FormPanel({ width: 350, defaultType: 'textfield', items: [{ xtype: '&lt;?php echo $field ?&gt;', value: '&lt;?php echo $value ?&gt;' }] }); </code></pre> <p>Obviously, you could rearrange this so the "items" array is built up beforehand in a loop, and you can add as many items as you need. </p> <p>Also, depending on how you set this up, you can also just return the array of items and add them to the form on the fly, removing the need to send the "new Ext.form.. etc" portion, and decoupling your code a little better. Personally, that's the way I'd go.</p> <p>Edit:</p> <p>In reply to your comment, if you return the JSON array in a proper ExtJS structure, all you'll need to do is use the "panel.add(myItems);" [1] method, and possibly a call to "panel.doLayout();" to force it to re-render nicely.</p> <p>Check out the details on "components" [2] for how the xtype works.</p> <p>[1] <a href="http://www.extjs.com/deploy/dev/docs/?class=Ext.form.FormPanel" rel="nofollow noreferrer">http://www.extjs.com/deploy/dev/docs/?class=Ext.form.FormPanel</a></p> <p>[2] <a href="http://www.extjs.com/deploy/dev/docs/?class=Ext.Component" rel="nofollow noreferrer">http://www.extjs.com/deploy/dev/docs/?class=Ext.Component</a></p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload