This would enable a component to get its master easily, without having to setup an onBindApply event and using a separate variable.
This would make creating reussable master-slave components easier.
Discussion at http://disq.us/p/23qvnd7.
Hey @dandv, continuing our discussion from before, there is actually another way to do this that you might find more convenient. While binding the slave component to the master, you can add a property containing the reference to the master:
component.bind(source);
component.config.$bindMaster = source;
Which would allow you to get the master view at a later point when you need it.
As an example, it would look something like this: https://snippet.webix.com/x5n13z5h.
As for the implementation of the getMaster() method, we don’t see the need to add this method, since it goes against the general concept of data binding. The data binding itself assumes the strict data/updates transferring and no possibility to affect the master component with additional custom methods, adding this method would mean breaking this concept and making the code more closely coupled, which is overall a bad thing.