ECO ViewModels
Short description
The
feature is about defining UI architecture independent view models that
can later be rendered in your UI and hooked up to your domain objects
Survey Info
The aim is to check if this feature is goung to be useful for developers.
It has couple of questins to be answered.
My opinion
From my experience all the magic stuff just doesn't work in real projects. You always need a little thing that you cannot do.
I find AutoForms and Eco Dubugger useful ONLY for administrative purposes. (I don't want to spend 20% of time implementing screens that users won't use but I still need those screens).
I find automatic UI useless. It just never works for real users, they always want something custom. Thou might be good to show a prototype. So you will spend time to prepare prototype (with all the problems you posted in the other post), then time to implement normal screens (why not just do the former and once?).
And as soon as I see "Object reference not set to an instance of an object" in simple situations. I fall back from it; it doesn't seem to be ready.
ECO already has AutoForms (a little buggy, but it mostly do the job), ECO Debugger. This is sufficient for Back-Office/Admin usage.
In my opinion, ECO should concentrate on real outstanding issues (especially querying abilities InPs) and not invent smartnesses that won't be useful for developers (let's conduct survey if ViewModels ar going to be useful?).
There are A LOT of OR/M tools on the market nowdays and ECO should become competitive in that area, which I think it hardly is. ECO does really good the UML part, but not OR/M.
Questions
Do you use automatic UI in your projects?
How likely is that you will use ViewModels feature in your projects:
Thanks for the answers.
|