anmonteiro Code ramblings

Om Next and Bootstrapped ClojureScript

A small number of changes to Om Next makes it possible to use it from self-hosted ClojureScript environments. Read on!

Read more  ➙

ClojureScript `require` now supports `:rename`

There exist a number of differences between Clojure and ClojureScript, especially concerning namespace declarations and require specifications. Some of these differences have recently been addressed with the introduction of Clojure namespace aliasing (JIRA ticket) and implicit macro loading. A further upcoming enhancement introduces the possibility to :rename referred symbols in dependency specifications.

Read more  ➙

The quest for a unified routing solution in Om Next

There are several different options to implement routing in an Om Next application. However, any one of those approaches is not straightforward to accomplish, and often requires more time than one would like to get right. Until now.

Read more  ➙

'Clients in control' — Om Next at Craft Conference 2016

At the end of April, I gave a talk about Om Next at Craft Conf in Budapest. The talk was recorded and the link is below.

Read more  ➙

Routing in Om Next — a Catalog of Approaches

Although a standard routing solution is an orthogonal concern to Om Next’s design and, at the time of this writing, there is still ongoing development with the objective of introducing simpler routing hooks, there are already several ways in which one can add proper route navigation to an Om Next app. This post aims to decrease the general community confusion around this topic by introducing a variety of different approaches that can be used to integrate routing in an Om Next app.

Read more  ➙