Search Results for "fb2k-component"

...The first is the CardsViewController which will display the cards. It is responsible for displaying cards in the proper order and managing the lifetime of the cards. The second major component is the cards themselves which are typically instances of CardPartsViewController. Each instance of CardPartsViewController displays the content of a single card, using one or more card parts (more details later).

...It's been designed to be extensible and performant. Along with Chatto there is ChattoAdditions, a companion framework which includes cells for messages and an extensible input component. You can find more details about how it was implemented in our blog. Chatto is a Swift framework to ease the development of chat applications. At the UI level, it takes care of managing the UICollectionView where the messages are displayed and provides a placeholder for an input component. Provides support for interactive dismissal of the keyboard and adjusts the insets automatically when it appears. ...

...You simply describe the layout for your UI based on a set of inputs and the framework takes care of the rest (diff and reconciliation from virtual view hierarchy to the actual one under the hood). CoreRender includes the robust and battle-tested Facebook's Yoga as default layout engine. Any component such as a text or image can be recycled and reused anywhere in the UI.

LeeGo is a lightweight Swift framework that helps you decouple & modularise your UI component into small pieces of LEGO-style's bricks, to make UI development declarative, configurable and highly reusable. We all know that MVC pattern has some serious problems when dealing with a complex iOS project. Fortunately, there are also a bunch of approaches that aim to fix the problems, most of them mainly address the Controller part, such as MVP, MVVM, MVSM or VIPER.

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. ...