MVVM and MVC mix (Communication, createComponents)

answered 2012-05-09 10:01:30 +0800

juergenmw
79 ● 1

updated 2012-05-09 10:03:00 +0800

Hi Matze

Thanks - that's quite easy ;)

I played around with GlobalCommands:

Composer

private void doCustomerDialog(Customer customer) {

   	winCustomerCrud = (Window) Executions.createComponents("/WEB-INF/pages/customer.zul", null, null);
	HashMap map = null;
    	if ( customer != null ) {
    		map = new HashMap();
        	map.put("kunde", kunde);
        	BindUtils.postGlobalCommand(null, null, "setCustomer", map);
    	}
   	 winCustomerCrud.setPosition("center");
   	 winCustomerCrud.doModal();
	}

Then in MVVM

	@GlobalCommand
	@NotifyChange ("selectedCustomer")
	public void setCustomer(@BindingParam("customer") Customer customer)
		System.out.println("set customer id:" + customer.getId());
		this.setSelectedCustomer(customer);
	}

I guess this is not the best solution since it does not set the data on initialization (which would be better) but at least I got a working GlobalCommand between MVVM and MVC.

BR
juergenmw

answered 2012-05-12 19:33:41 +0800

juergenmw
79 ● 1

Hi

I thought it is a good idea to put a question concerning a related question in here again.

If I want to create a new component (eg window) from within an MVC application I simply use Executions.CreateComponents inside the Composer - for example when a button was clicked.

If I want to do the same in an MVVM environment I DONT wanna do that in the VM because I would have to create ZK components there which weakens the MVVM approach. What is best practice to include a zul file (or create a component) when a button is clicked without using @Command and createComponent server-side (VM)?

BR
Juergen

answered 2012-05-16 10:00:32 +0800

juergenmw
79 ● 1

Ok, I weakened MVVM and used a window object in VM:

	@Command("doDialog")
	public void doDialog(){
   	 	Window winInputlagerCrud = (Window) Executions.createComponents("/WEB-INF/pages/crud.zul", null, null);
   	 	winInputlagerCrud.setPosition("center");
   	 	winInputlagerCrud.doModal();
	}

Using this method has another disadvantage - it is not possible to use the existing VM (and it's referenced/selected data) for the new window.

So my goal is to:

1.) Use MVVM in Data Overview AND Detail (CRUD)
2.) CRUD should be implemented as overlay - most MVVM-only-examples show how to do it with an integrated form below/above the list
3.) I wan to use the same VM for the overlay - VM knows my selected data
4.) I don't think it is a good idea to use this in VM to create the overlay (see above)

Window winInputlagerCrud = (Window) Executions.createComponents

Is there any possibility to realize this? What is the "standard way" for this implementation?
Thanks for your help

juergenmw

answered 2012-05-16 12:45:47 +0800

juergenmw
79 ● 1

Hi Matze

Thanks for trying to help - I will explain it more detailed:

If you have a look at this ZK MVVM example and pics you can see that the data list and also the detail/form (CRUD) is in one "window" - it also uses one VM (sure, whatelse).

I want to do the same BUT my CRUD should be a (new) window/overlay.

So my knowledge to do this is:

1.) Create a new component (not a good idea because usually this is done in the controller and weakens MVVM)
2.) The new Component gets the selected element via ARG
3.) The new Component (window) has a new/separate Composer (MVC) or VM (MVVM)

So my questions are:

1.) Is there a "best practice" to create a new window without using CreateComponent on the backend - so just from the client?
2.) Can the new window also use the already existing VM binder because it knows my selected data row already - I only want to display (and edit) it inside an (newly created or hidden) overlay - I want to avoid writing a new VM for the overlay.

BR
juergenmw

answered 2012-05-16 14:13:42 +0800

juergenmw
79 ● 1

updated 2012-05-16 14:14:57 +0800

Hi Matze2

Thank you very much for your comment - I'll have a look at Ad1.

Regarding Ad2 - I think this came to my mind after going thru the given examples. They use just one ViewModel for list and detail view. The next logical step for me was to use this setup but using a new, dynamicaly created component (window) for the details instead of editing them inside the same view.

Everything else remains the same, so I thought there might be an easy way, Instead this little change (inline vs. window CRUD) changes a lot more in the background (window CRUD needs a new VM).

BR
juergenmw