Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>you are very close to doing this already - just call your <strong>newRulesField</strong> function from your <strong>handleRuleKeypress</strong> function. something like this:</p> <pre><code>function handleNewRuleSetClick(nodes) { var nameField = new Ext.form.TextField({ fieldLabel: 'Name', name: 'ruleSetName', anchor: '100%', allowBlank: false, grow: false }); var descField = new Ext.form.TextField({ fieldLabel: 'Description', name: 'ruleSetDescription', anchor: '100%', allowBlank: false, grow: false }); var form = new Ext.FormPanel({ labelWidth: 75, defaultType: 'textfield', bodyStyle: 'padding:30px', id: 'newRuleSetPanel', name: 'newRuleSetPanel', title: 'New Rule Set', buttons: [{ text: 'Save', id: 'saveBtn', hidden: false, handler: function() { form.getForm().submit({ url: 'server/new-rule-set', waitMsg: 'Saving...', success: function(f, a) { Ext.Msg.alert('Success', 'It worked'); }, failure: function(f, a) { Ext.Msg.alert('Warning', 'Error'); } }); } }, { text: 'Cancel', id: 'cancelBtn', hidden: false }] }); function handleRuleKeypress(a, b) { form.add(newRulesField('rules' + Ext.id())); } function newRulesField(name) { var rulesField = new Ext.form.TextArea({ fieldLabel: 'Rules', anchor: '100%', name: name, allowBlank: false, grow: false, enableKeyEvents: true, listeners: { keypress: handleRuleKeypress } }); return rulesField; } form.add(nameField); form.add(descField); form.add(newRulesField('rules1')); this.add(form); this.doLayout(); } </code></pre> <p>you will want additional logic for checking if you have already added the new text area (or you will get a new one for each key press), perhaps removing the additional text area if the latest rule is emptied later on, and fixing the textarea id's a little prettier (all this is your <strong>handleRuleKeypress</strong> func).</p> <p>My general thoughts on your application design is to keep the FormPanel as a class member somewhere instead of a private function member, this will make it easier to access whenever it comes to modifying it after creation - stacking functions like this is not very pretty nor readable.</p>
    singulars
    1. This table or related slice is empty.
    1. PODynamically add TextAreas to a FormPanel on User Input with ExtJS
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USTewr
    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. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI find that inner functions are a wonderful way to hide your data so it's only available where you need it. It may be that for larger apps you may need access to that var somewhere else, but many times you don't... and that helps you know that that variable cannot be used anywhere else
      singulars
      1. PO
      1. USJuan Mendes
    2. COI prefer the same code style as used in the extjs source, I mark the function as private in its comment rather than stacking functions inside each other. Not only to conform, but also because I think its more tidy and easier to read. This makes it possible to re-use a function in several other (public/private) functions of the class. But finally I guess it is just a matter of taste...
      singulars
      1. PO
      1. USTewr
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

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