Is Monotouch.Dialog a suitable replacement for all UITableviews?

This question is mainly aimed at Miguel as the creator of MT.Dialog, but I would like to hear the opinions of others. I am currently reorganizing a project that has many tabular views. I am wondering if I should replace all of them with MT.Dialog.

My pros:

  • easy to use
  • simple code
  • I hope that Xamarin will offer him a cross-platform one day.

Minuses:

  • my cells are completely custom made. Does it make sense in this case?
  • performance? This is problem?
  • violation of MVC paradigms (the source is no longer separated from the view and controller)

Generally, is it better to use MT.Dialog or inherit it for specific use cases? What are your impressions?

+5
2

.

MonoTouch.Dialog UITableView , , , . MonoTouch.Dialog , /. UITableView , .

UITableView , , , , . , , UITableView .

:

(1) , , . , .

(2) , . , , , , TweetStation, " ".

, , MonoTouch.Dialog. , . , Tweetstation "TweetElement", , TweetElement .

UITableView . - , .

, , .

(3) . UIKit. , , UITableViewSource -, UITableView. - , , , .

, , UITableView ( , XML, , Redis).

UITableView UITableViewSource. MonoTouch.Dialog adatpro , RootElement DialogViewController.


, UITableView MonoTouch.Dialog, .

+11

MonoTouch.Dialog( QuickDialog objc) , tableview. .

, , , - . MT.D/QD , , , , .

" MVC", . - MT.D. - JSON ( fork https://github.com/escoz/MonoMobile.Forms), MT.D.

+4

All Articles