You always bind to an ICollectionView, whether you make it explicit or not. Assume that we have var collection = new ObservableCollection<string>(); var collectionView = CollectionViewSource.GetDefaultView(collection); In this case, binding to collection or to collectionView is one and the same: the binding engine will bind to the default collection view (which is reference equal to … Read more
Note: As of jQuery 1.7, the .live() method is deprecated. Use .on() to attach event handlers. Users of older versions of jQuery should use .delegate() in preference to .live(). I’m working on the same thing (knockout + jquery mobile). I’m trying to write a blog post about what I’ve learned but here are some pointers … Read more
People use DataTemplates that way when they want to dynamically switch Views depending on the ViewModel: <Window> <Window.Resources> <DataTemplate DataType=”{x:Type local:VM1}”> <!– View 1 Here –> </DataTemplate> <DataTemplate DataType=”{x:Type local:VM2}”> <!– View 2 here –> </DataTemplate> </Window.Resources> <ContentPresenter Content=”{Binding}”/> </Window> So, if Window.DataContext is an instance of VM1, then View1 will be displayed, and if … Read more
Sorry if my answer became a little lenghty, but don’t blame me! Your question is lengthy as well. In summary, MVVM is not pointless. The clear case in point is adding support for a Modal dialog box. The correct way is to put up a dialog box and tie it to a view model. Getting … Read more
I like to think of it this way: Views, as you say, are dumb. Josh Smith, writer of the seminal and often linked MSDN article on MVVM, has said that views are “the clothes that data wears.” Views never actually contain data or directly manipulate it, they are just bound to properties and commands of … Read more
In my case as I’m using HILT, it was lacking one annotation above the Fragment that has a ViewModel: @AndroidEntryPoint @AndroidEntryPoint class BestFragment : Fragment() { …. Of course in your ViewModel class you also need to Annotate with what HILT needs: @ViewModelInject class BestFragmentViewModel @ViewModelInject constructor(var userManager: UserManager) : ViewModel() { …. }
You can access the context by implementing AndroidViewModel instead of ViewModel. class MainViewModel(application: Application) : AndroidViewModel(application) { fun getSomeString(): String? { return getApplication<Application>().resources.getString(R.string.some_string) } }
We can not create ViewModel on our own. We need ViewModelProviders utility provided by Android to create ViewModels. But ViewModelProviders can only instantiate ViewModels with no arg constructor. So if I have a ViewModel with multiple arguments, then I need to use a Factory that I can pass to ViewModelProviders to use when an instance … Read more
Please, code behind is not a bad thing at all. Unfortunately, quite a lot people in the WPF community got this wrong. MVVM is not a pattern to eliminate the code behind. It is to separate the view part (appearance, animations, etc.) from the logic part (workflow). Furthermore, you are able to unit test the … Read more
What I generally do is create an interface for an application service that performs this function. In my examples I’ll assume you are using something like the MVVM Toolkit or similar thing (so I can get a base ViewModel and a RelayCommand). Here’s an example of an extremely simple interface for doing basic IO operations … Read more