问题
For a multi-platform application using native components, the standard Delphi approach is no longer sufficient. So far our structure had only to parts: GUI (Forms) and Business logic. We now need to split the "Forms" part into two, which in a MVVM context would be View and ViewModel.
The bindings between View and ViewModel can be handled in different ways:
- LiveBindings in Delphi
- DSharp (Delphi Sorcery)
- Delphi Spring (Spring4D)
There might be more. I know this is a religious question to some, but I still hope it is possible to get objective answers:
If you are using a solution in your Firemonkey application that is suitable for multi-platform development on a long term perspective: What considerations was behind the decision you made?
来源：https://stackoverflow.com/questions/27360062/best-way-to-implement-mvvm-bindings-view-viewmodel-in-delphi