Controller Issues with 0.67 about deftjs HOT 2 CLOSED

Claude,

If I understand what you're trying to do correctly, I have some good news. You don't need to jump through any of those hoops to avoid duplicate ids.

The selectors supplied in the control configuration for a Deft.ViewController are evaluated relative to the view. If you use itemId rather than id, you can completely avoid the duplicate id issue. You can have multiple components in the same application at different levels of the view hierarchy with the same 'itemId' (unlike with 'id').

So if you have a view like this:

Ext.create('MyApp.view.MyView', {
  extend: 'Ext.Container',
  mixins: ['Deft.Controllable'],
  controller: 'MyApp.controller.MyViewController',

  items: [
    {
      xtype: 'button',
      itemId: 'submitButton'
    },

    ...
  ],

  ...
});

And a ViewController like this:

Ext.create('MyApp.controller.MyViewController', {
  extend: 'Deft.ViewController',

  control: {
    submitButton: {
      click: 'onSubmitButtonClick'
    }
  },

  ...
  onSubmitButtonClick: function() {
     // TODO: Do something.
  }
});

You can create as many independent instances of MyApp.view.MyView as you want.

Each will get its own instance of MyApp.Controller.controller.MyViewController backing it.

Each of those MyViewController instances will evaluate the selectors provided via the control annotation relative to that view instance. In the example above, the selector is implicit - it will query for '#submitButton' within that view instance. (You can provide explicit selectors if needed through more verbose syntax, as shown on http://deftjs.org/)

So, that's an important distinction - Ext.Controller selectors are global, whereas Deft JS View Controller selectors are relative.

The problem of displaying multiple copies of the same view (each backed by independent view-specific controllers) is one of the problems Deft JS was built to solve.

Let me know if I understood your issue correctly, and if this helps resolve the problem you were having.

Best regards,

-J

from deftjs.

Perfect John! exactly what I wanted.. using itemId is the solution.. whoo hoo! :)

from deftjs.