Introduction to Keechma
Keechma implements a set of utilities that make it easier to develop predictable, consistent and deterministic applications.
- Application: a combination of the routes, controllers, components and subscriptions that work together as a unit. Application state is stored in the internal atom.
- Routes: a list of route patterns that describe how to transform the URL to data and data to the URL.
- Controller Manager: internal part of the application that starts or stops controllers based on the current route params.
- Controllers: Clojure records that implement the
controller/IController protocol. They are managed by the controller manager. Controllers are responsible for the following:
- When started they (can) mutate the application state and load the data.
- When stopped they (can) mutate the application state and clean up the loaded data.
- When the user sends a command (e.g. by clicking on a button) it is routed to the appropriate controller which reacts to the command and mutates the application state accordingly.
- Subscriptions: functions that return a subset of the application state to UI components.
- Entity DB: stores the application entities.
- Entities of the same type with the same identity will be stored only once and referenced from the collections or named item slots.
- Entity state in the EntityDB will be automatically propagated to all collections or named item slots that reference that entity.
- UI component system: a set of utilities that allow you to write decoupled, reusable components. Each component declares it's dependencies which are injected into the component when the application is started.
There are two ways to affect the application state:
- URL change
- UI action (e.g. clicking on a button) which sends the command to the controller
URL change flow
- When the URL changes, the router will transform the URL into a map that represents the data contained in the URL.
- The route params map will be sent to the controller manager which will then start or stop the controllers accordingly.
- Each controller can mutate the application state
- Application state changes are propagated to the UI
UI action flow
- When the user performs an action (e.g. clicks on a button) the command is sent to the controller manager.
- The Controller manager routes the command to the appropriate controller (based on the command
- The controller reacts to the command and mutates the application state
- The application's state changes are propagated to the UI
The code that mutates the application state is always placed in the controllers. Controllers are the only place in the application where you can mutate the application's state.
Credits and Inspiration
The libraries that had the biggest impact on Keechma:
- CanJS - Keechma's router is ported from CanJS and EntityDB is inspired by the CanJS model store
- Re/Frame. - One-big-atom store, subscriptions and handlers are based of my experience with Re/Frame
- Reagent - Keechma would be much harder to implement without Reagent's approach to components
- Om - Without Om I probably wouldn't have tried ClojureScript — and Keechma wouldn't exist.