            :types [[:app-model :types] [:app-model :navbar]]
            :tag-stats [[:app-model :tag-stats] [:app-model :navbar]]
            :all [[:app-model :all] [:app-model :navbar]]
-           :search [[:app-model :search] [:app-model :home] [:app-model :navbar]]
+           ;; dynamic focii we define with :search transform
+           ;:search-* [[:app-model :search] [:app-model :home] [:app-model :navbar]]
            :default :home}})
 

          {:init init-all}
          [#{[:all-results]} (app/default-emitter [:app-model :all])]

          ;{:init init-search}
          [#{[:search]} sub-search]
          [#{[:* :search-title] [:* :search-results]} (app/default-emitter [:app-model :search])]

          {:init navbar-deltas}

;;
(defn home-deltas []
  [[:transform-enable [:app-model :home :create-url] :create-url [{msg/type :set-value msg/topic [:create-url] (msg/param :value) {}}]]
   ;; Using add-named-paths creates dynamic focii. With this approach each search result is
   ;; navigable via html5 history. Although adding a named path only needs to happen once per unique
   ;; search, the cost of sending an :add-named-paths message is pretty low - just an assoc.
   [:transform-enable [:app-model :home :search] :search [{msg/type :add-named-paths msg/topic msg/app-model (msg/param :name) {} (msg/param :paths) {}}
