Search:

That's awesome! Thank you for sharing your workaround! Feel free to create a PR https://github.com/alexeysolonets/extjs-mvvm-extensions

Hi Trevor, thanks for sharing!

Hi, thanks for your comment, I'm happy that it helps.

As far as I understand, the thing you want to achieve is called two-way binding, so you could've used the twoWayBindable config. But it...

I've published the article (2 articles to be exact). Yes, 4 months later, sorry. Anyway, could you please take a look at them

Ext JS MVVM Tricks: Part 1. Self Binding...

Hi, since I've posted the workaround, I've made some changes and created a project on GitHub.

https://github.com/alexeysolonets/extjs-mvvm-extensions

The explanation with examples is here (need...

To hide warnings manually add following lines to _variables.scss (they were in original file):

First line

//# fashion warn -elevation

Last line

//# fashion warn +elevation

Oh, yes, I missed it. It's sad that they don't pay attention for such a detailed bugreports like this one. Hope they will fix it someday considering workaround code is easy.

Confirm, same issue.
Here is a workaround



Ext.define('Ext.bf.data.session.BatchVisitor', {
override: 'Ext.data.session.BatchVisitor',

getBatch: function (sort) {
var...

Ok, I have updated the workaround and now it looks much better! It targets Ext.mixin.Bindable as it should. Finally it is possible to use ViewModels as we expect: create fully independent components...

Hi everyone. Check out the temporary solution here https://www.sencha.com/forum/showthread.php?300583-Fix-Child-component-ViewModel-breaks-it-s-publish-properties

I'm inviting everyone to check out and discuss the temporary solution here https://www.sencha.com/forum/showthread.php?300583-Fix-Child-component-ViewModel-breaks-it-s-publish-properties

Hi everyone. Check out the temporary solution here https://www.sencha.com/forum/showthread.php?300583-Fix-Child-component-ViewModel-breaks-it-s-publish-properties

Hi there!

This is a discussion about a temporary workaround.

There are several topics on the forum about defining a ViewModel inside a child component.

The problem is that a child component...

Another workaround that is better for me so far



Ext.define('Ext.bf.button.Button', {
override: 'Ext.button.Button',

enable: function (silent, fromParent) {
if...

Workaround (may be not perfect)


Ext.define('Ext.bf.button.Button', {
override: 'Ext.button.Button',

enable: function (silent, fromParent) {
fromParent = !!fromParent;
...

Ext version tested:

5.1.1.347
Description:

Container with button both set 'disabled: true' explicitly. When parent container is set enabled button also looks enabled.
Steps to reproduce the...

Workaround code example (as rhubarb65 mentioned):

Ext.define('MyNode', {
extend: 'Ext.data.Model',

fields: [{
name: 'id',
type: 'string' // explicit
}]

Hi James,

Thank you for your help, I appreciate it.

Yes, the example you have provided does work. And there is something you have also noticed in comments: the 'title' field exists in both...

Yes, of course, listeners this is how we all used to do. It would be great for this request to be realized. And I probably understand why it isn't yet: bindings are designed to work with references...

Hi

Thank you for your answer and for the fiddle. I'll answer the question about "viewModel: true" first. This is allowed and there is no big difference in internals between "true" or "{ data: {}...

Hi everyone.

Since we can use ViewControllers for any view regardless their nesting hierarchy I was expecting for ViewModels to work same way. But looks like in several cases I can use only one...

Confirm, same issue.
https://fiddle.sencha.com/#fiddle/hbt

Probably this is a duplicate. You can find the workaround here http://www.sencha.com/forum/showthread.php?288825 but it is only temporary because it's already fixed

Ext version tested:

Ext 5.0.1.1255
Browser versions tested against:

Chrome 31,
IE 11
Description:

I have a child model that is extended from a parent model which has some calculation...

Ext version tested:

Ext 5.0.1.1226
Browser versions tested against:

Chrome 31, IE 11
Description:

Margins in the responsiveConfig property works wrong
Steps to reproduce the problem: