1.0 Planning

[Xciles]

1.0 planning for MVP

Basic idea behind this library is to move a lot of boiler plating and repeating code to a generic implementation. This implementation has to be modular and it should be possible to override things.

We have to keep in mind that we want to use this for Xamarin based projects using MvvmCross and in a later stage Xamarin Forms. Other frameworks might also be added, however they have no priority at this moment.

---

Basic implementation is as follows.

The implementation follows an extended MVVM pattern adding the possibility to share Observables between multiple views.

Project should consist of:

• Business
  • An entity that will manage business logic
• Domain
  • Entities that will be used for storing data and for example service communication
• Observable
  • Entities that can be observed
• Presentation
  • An entity that will manage observable entities and make it possible to share the same entities between multiple viewmodels
• Services
  • Communication
• View models
  • The view model

A picture says more, so:

---

What 1.0 should do.

• DI based resolving
• Pub/sub for Business + Presentation and other classes that need it
• Business
  • Should contain no hard references to objects
  • Is the layer for logic between view models and services
    • View model communicates with the business classes
• Presentation
  • Manage Observables
    • Bind observables by ref instead of referencing
• ViewModel
  • Observable ref bindings instead of linking property in Presentation
• Domain
• Services
• Object Mapper
• Base implementation
• Shareable between multiple frameworks (MvvmCross, light, froms)
• Multiple data storage providers
  • NoSql provider
    • LiteDb Provider
• New file store provider
  • Encrypted file storage provider
• Presentation
  • Add a way to clean presentation lists when needed