Hi
On 2012.02.28 09:04, Stuart Lodge wrote:
I like that Norway flights example - wish I'd seen that earlier!
I've personally found that as long as you put as much of your code as
possible into the shared ViewModel and lower classes (Model, Services,
BL, DAL, whatever, ...) inside their own project, then refactoring
isn't too painful - it's maybe only 80% automatic, which I personally
don't find unworkably painful.
This is my experience too...
I have folded M and C in MVC, M and P (in MVP) into one project - in
other words everything
that has nothing to do with UserControls, Controls, Widgets, Forms,
layouts, etc...
One thing that's helped me is that the way I've tackled this so far is
to build one Mvvm platform first (e.g. WP7) and to then build the
others- I haven't tackled this by having all 3 platforms being
developed concurrently. If you really have to develop all 3
concurrently then that might be harder.
In our case MVVM is not heavily used, because AFAIK it is based on Data
Binding and
this is not (yet) part of M4A, MTch (WinForms in xaml sense) etc..
So for 3 project types (where one has 2% market) it does not pay-off - yet.
We'll start using it when I get more time to learn about Your
baby-project MVVMCross.
Gruesse
mc
--
Miljenko Cvjetko dipl.ing. ET
Direktor/CEO
Projektant rješenja/Solution Architect
Razvojni programer/Senior developer
Voditelj projekta/Project Manager
IX južna obala 13
Kajzerica Zagreb
T: 385 1 7775555
M: 385 91 557 447 3
F: 385 1 7779556
e: [email protected]
w: http://www.holisticware.net
_______________________________________________
Monodroid mailing list
[email protected]
UNSUBSCRIBE INFORMATION:
http://lists.ximian.com/mailman/listinfo/monodroid
