|ReleasedLast Release||Jun 2017|
|Apps WeekApps This Week||26|
|Test WeekTests This week||6|
|LOCLines of Code||6,380|
Spots is a cross-platform view controller framework for building component-based UIs. The internal architecture is built using generic view models that can be transformed both to and from JSON. So, moving your UI declaration to a backend is as easy as pie. Data source and delegate setup is handled by Spots, so there is no need for you to do that manually. The public API is jam-packed with convenience methods for performing mutation, it is as easy as working with a regular collection type.
If you are looking for a way to get started with
Spots, we recommend taking a look at our Getting started guide.
We wrote a Medium article about how and why we built
You can find it here: Hitting the sweet spot of inspiration
Apple's definition of a universal applications is iPhone and iPad. Spots takes this a step further with one controller tailored to each platform to support all your UI related update needs. Internally, everything conforms to the same shared protocol. What this means for you, is that get a unified experience when developing for iOS, tvOS or macOS.
Use the following links to dive a bit deeper into how Spots works.
At the top level of Spots, you have the SpotsController which is the replacement for your view controller.
Inside of the SpotsController, you have a SpotsScrollView that handles the linear layout of the components that you add to your data source. It is also in charge of giving the user a unified scrolling experience. Scrolling is disabled on all underlaying components except for components that have horizontal scrolling.
So how does scrolling work? Whenever a user scrolls, the SpotsScrollView computes the offset and size of its children. By using this technique you can easily create screens that contain lists, grids and carousels with a scrolling experience as smooth as proverbial butter. By dynamically changing the size and offset of the children, SpotsScrollView also ensures that reusable views are allocated and deallocated like you would expect them to. SpotsScrollView uses KVO on any view that gets added so if one component changes height or position, the entire layout will invalidate itself and redraw it like it was intended.
SpotsController supports multiple Component's, each represent their own UI container and hold their own data source. Components all share the same data model called
ComponentModel, it includes layout, interaction and view model data. Component gets its super-powers from protocol extensions, powers like mutation, layout processing and convenience methods for accessing model information.
Componenthas its own set of
Item’s. which is maintained internally and is there at your disposable if you decide to make changes to them.
Spots is available through CocoaPods. To install it, simply add the following line to your Podfile:
Spots is also available through Carthage. To install it, add the following to your
Looking for a change log? You can find it here
Itemcaching when initializing a
CoreComponentobject with a cache key.
We would love you to contribute to Spots, check the CONTRIBUTING file for more info.
SpotsScrollView, we salute you. Reference: http://oleb.net/blog/2014/05/scrollviews-inside-scrollviews/
Spots is available under the MIT license. See the LICENSE file for more info.