Tags
People
Badges
Help-
CORE FRAMEWORK
FEATURED COMPONENTS
-
RESOURCES
-
LEARN ZK
RESOURCES
I have just used the MVVM to bind data to my zul file, but as I initialler used a controller also on this screen was wondering how this fits into the MVVM architecture if at all ?
The controller is useful for manipulating the UI, especially in my case when I am loading and building PortLayout components from the database.
If their best practice to using the controller with MVVM.
Thanks.
The consensus seems to be that if your manipulating specific pieces of the UI, then use a Composer. The theory is that the ViewModels of MVVM shouldn't have "UI" code in them.
*note, I say the "theory" is, since I often break that theory in practice and haven't noticed any ill consequences. For example, I'll often use Messagebox within my ViewModel commands. In theory I'm breaking the pure separation, but I'm not sweating it too much.
Asked: 2013-04-09 04:18:40 +0800
Seen: 36 times
Last updated: Apr 22 '13
Great.
Thanks for the reply, I am using a hybrid at the moment, but when using ViewModel it is all data related. So I am happy with a happy medium so to speak.
JustinFrost ( 2013-04-22 09:24:53 +0800 )edit