ModelAssistant alternatives and similar libraries
Based on the "Database" category.
Alternatively, view ModelAssistant alternatives based on common mentions on social networks and blogs.
9.9 8.2 ModelAssistant VS MMKVAn efficient, small mobile key-value storage framework developed by WeChat. Works on Android, iOS, macOS, Windows, and POSIX.
9.9 9.2 L2 ModelAssistant VS RealmRealm is a mobile database: a replacement for Core Data & SQLite
9.8 0.3 ModelAssistant VS WCDBWCDB is a cross-platform database framework developed by WeChat.
9.1 0.0 L1 ModelAssistant VS YapDatabaseYapDB is a collection/key/value store with a plugin architecture. It's built atop sqlite, for Swift & objective-c developers.
8.2 8.9 L1 ModelAssistant VS Couchbase MobileLightweight, embedded, syncable NoSQL database engine for iOS and MacOS apps.
6.3 6.8 L4 ModelAssistant VS MongoKittenNative MongoDB driver for Swift, written in Swift
5.0 0.0 L2 ModelAssistant VS RealmIncrementalStoreRealm-powered Core Data persistent store
4.8 5.2 ModelAssistant VS ObjectBoxObjectBox Swift - persisting your Swift objects superfast and simple
4.0 0.0 L4 ModelAssistant VS realm-cocoa-converterA library that provides the ability to import/export Realm files from a variety of data container formats.
3.5 0.0 L1 ModelAssistant VS MySQLA stand-alone Swift wrapper around the MySQL client library, enabling access to MySQL servers.
3.0 4.8 ModelAssistant VS PersistenceKitStore and retrieve Codable objects to various persistence layers, in a couple lines of code!
2.3 0.0 L3 ModelAssistant VS MongoDBA stand-alone Swift wrapper around the mongo-c client library, enabling access to MongoDB servers.
2.2 0.0 L4 ModelAssistant VS PostgreSQLA stand-alone Swift wrapper around the libpq client library, enabling access to PostgreSQL servers.
2.0 0.0 L5 ModelAssistant VS Storez💾 Safe, statically-typed, store-agnostic key-value storage written in Swift!
1.9 0.0 L4 ModelAssistant VS FileMakerA stand-alone Swift wrapper around the FileMaker XML Web publishing interface, enabling access to FileMaker servers.
1.9 0.0 L4 ModelAssistant VS SQLiteA stand-alone Swift wrapper around the SQLite 3 client library.
* Code Quality Rankings and insights are calculated and provided by Lumnify.
They vary from L1 to L5 with "L5" being the highest.
Do you think we are missing an alternative of ModelAssistant or a related project?
An assistant to manage the interactions between view and model
ModelAssistant is a mediator between the view and model. This framework is tailored to work in conjunction with views that present collections of objects. These views typically expect their data source to present results as a list of sections made up of rows. ModelAssistant can efficiently analyze model objects and categorize them in sections. In addition it updates adopted view to its delegate, based on model objects changes.
- What's New
- Advanced Usage
- [x] Inserting / Removing / Ordering / Updating model objects
- [x] Notifies changes to view
- [x] Full compatible with UITableView and UICollectionView
- [x] Supports Sections
- [x] Supports index titles
- [x] Compatible with Server data source
- [x] Compatible with all kind of persistent stores
- [x] Compatible with all design patterns
- [x] Easy to use
- [x] Thread safe
- [x] Fault Ability
- [x] Complete Documentation
Now using modelAssitant is really easy with just two lines of codes, and delegates will be implement automatically to your collection view.
See Usage for new way of implementing modelAssistant.
Upgraded to Swift 5
- Fault Ability: Now you can make entities in an specific range fault or fire them. For more information see Advanced Usage
- iOS 8.0+
- Xcode 8.3+
- Swift 3.1+
CocoaPods is a dependency manager for Cocoa projects. You can install it with the following command:
$ gem install cocoapods
To integrate ModelAssistant into your Xcode project using CocoaPods, specify it in your
source 'https://github.com/CocoaPods/Specs.git' platform :ios, '10.0' use_frameworks! target '<Your Target Name>' do pod 'ModelAssistant' end
If you are not upgraded to Swift 4.2, use the last non-swift 4.2 compatible release:
If you are using swift 4, replace
pod 'ModelAssistant' with this:
pod 'ModelAssistant', '1.0.1' #Swift 4
If you are using swift 3, replace
pod 'ModelAssistant' with this:
pod 'ModelAssistant', '1.0.0' #Swift 3
Carthage is a decentralized dependency manager that builds your dependencies and provides you with binary frameworks.
You can install Carthage with Homebrew using the following command:
$ brew update $ brew install carthage
To integrate ModelAssistant into your Xcode project using Carthage, specify it in your
carthage update --platform iOS to build the framework and drag the built
ModelAssistant.framework into your Xcode project.
If you prefer not to use any of the aforementioned dependency managers, you can integrate ModelAssistant into your project manually.
- Open up Terminal,
cdinto your top-level project directory, and run the following command "if" your project is not initialized as a git repository:
$ git init
- Add ModelAssistant as a git submodule by running the following command:
$ git submodule add https://github.com/ssamadgh/ModelAssistant.git
Open the new
ModelAssistantfolder, and drag the
ModelAssistant.xcodeprojinto the Project Navigator of your application's Xcode project.
It should appear nested underneath your application's blue project icon. Whether it is above or below all the other Xcode groups does not matter.
ModelAssistant.xcodeprojin the Project Navigator and verify the deployment target matches that of your application target.
Next, select your application project in the Project Navigator (blue project icon) to navigate to the target configuration window and select the application target under the "Targets" heading in the sidebar.
In the tab bar at the top of that window, open the "General" panel.
Click on the
+button under the "Embedded Binaries" section.
You will see two different
ModelAssistant.xcodeprojfolders each with a
ModelAssistant.frameworknested inside a
It does not matter which
Productsfolder you choose from.
And that's it!
ModelAssistant.frameworkis automagically added as a target dependency, linked framework and embedded framework in a copy files build phase which is all you need to build on the simulator and a device.
What is the position of ModelAssistant in design patterns?
ModelAssistant is fully compatible with all kind of design patterns. It doesn't violate them, instead it finds its place and sit there! As a guide the position of ModelAssistant in some of famous design patterns is as follows:
|Design Pattern||ModelAssistant Position|
ModelAssistant is released under the MIT license. See LICENSE for details.
*Note that all licence references and agreements mentioned in the ModelAssistant README section above are relevant to that project's source code only.