Hi Seamus,
As long as you have the aljabr dependency in your project.clj (don't need to include core.matrix also, as it will come with aljabr), then you shouldn't need to do anything besides require clojure.core.matrix and thinktopic.aljabr.core. I just created a simple cljs test app with the 0.1.1 release on Clojars in the project.clj, and this works as expected.
The warning about dynamic loading is because in Clojure when you do (mat/set-current-implementation :vectorz) it will call require for you under the hood, loading the library as long as it is on your classpath. In Clojurescript if you don't explicitly require aljabr in at least one namespace then the compiler might not send it to the browser, in which case a dynamic require won't be able to load. Anyways, try it out as is below, and let us know if you have any more problems.
Cheers,
Jeff
(ns foo.core
(:require [reagent.core :as reagent :refer [atom]]
[secretary.core :as secretary :include-macros true]
[accountant.core :as accountant]
[thinktopic.aljabr.core :as aljabr]
[clojure.core.matrix :as mat]))
;(mat/set-current-implementation :aljabr)
(enable-console-print!)
;; -------------------------
;; Views
(defn home-page []
(let [a (mat/new-array [2 2])
b (mat/new-array [2 2])
c (mat/add a b)
d (mat/mmul [[1 2] [3 4]] [[5 6] [7 8]])]
[:div [:h2 "Welcome to foo"]
[:div (str c)]
[:div (str d)]
[:div [:a {:href "/about"} "go to about page"]]]))
(defn about-page []
[:div [:h2 "About foo"]
[:div [:a {:href "/"} "go to the home page"]]])