retroact.next
app-refsclj
app-watchclj
(app-watch watch-key app-ref old-value new-value)apply-attributesclj
(apply-attributes {:keys [onscreen-component app-ref old-view new-view]})build-uiclj
(build-ui app-ref view)Take a view and realize it.
Take a view and realize it.
children-applier?clj
(children-applier? attr-applier)component-applier?clj
(component-applier? attr-applier)component-did-mount?clj
(component-did-mount? old-value new-value)createclj
(create)(create app-ref)(create app-ref opts)Creates a ref (default type atom of a map) to what can be used as the application state. Retroact needs to track some state and puts some state in the map under the :retroact key. Optionally, a toolkit and look and feel may be specified. The look and feel (laf) is a Retroact thing and not the toolkits laf. Retroact has a way of modifying the toolkit's laf from the developer's point of view. old docs: Takes toolkit bindings and returns a Retroact handle to be used for initializing applications. The default toolkit bindings are legacy swing and should not be used. They exist for backward compatibility. Specify a toolkit using its get-<toolkit-name>-bindings fn. config is {:toolkit-bindings tb :look-and-feel laf} where both are optional and the empty map is acceptable.
Creates a ref (default type atom of a map) to what can be used as the application state. Retroact needs to track some
state and puts some state in the map under the :retroact key. Optionally, a toolkit and look and feel may be
specified. The look and feel (laf) is a Retroact thing and not the toolkits laf. Retroact has a way of modifying the
toolkit's laf from the developer's point of view.
old docs: Takes toolkit bindings and returns a Retroact handle to be used for initializing applications. The default
toolkit bindings are legacy swing and should not be used. They exist for backward compatibility. Specify a toolkit
using its get-<toolkit-name>-bindings fn. config is {:toolkit-bindings tb :look-and-feel laf} where both are optional
and the empty map is acceptable.create-compclj
(create-comp app-ref comp)(create-comp app-ref comp props)Create a new top level component. There should not be many of these. This is akin to a main window. In the most extreme cases there may be a couple of hundred of these. In a typical case there will be between one component and a half a dozen components. The code is optimized for a small number of top level components. Legacy apps that wish to mount components in an existing non-Retroact component can use this to construct such "detached" components, which are essentially top level components as far as Retroact is concerned but not in the native windowing system. Note, the onscreen-component is built asynchronously and may be added to the legacy component in its component-did-mount or ... TODO: in the future there may be another way to do this.
Create a new top level component. There should not be many of these. This is akin to a main window. In the most extreme cases there may be a couple of hundred of these. In a typical case there will be between one component and a half a dozen components. The code is optimized for a small number of top level components. Legacy apps that wish to mount components in an existing non-Retroact component can use this to construct such "detached" components, which are essentially top level components as far as Retroact is concerned but not in the native windowing system. Note, the onscreen-component is built asynchronously and may be added to the legacy component in its component-did-mount or ... TODO: in the future there may be another way to do this.
destroy-compclj
(destroy-comp app-ref comp-id)Destroy a component. You'll need to keep comp-id created with create-comp in order to call this.
Destroy a component. You'll need to keep comp-id created with create-comp in order to call this.
get-app-idclj
(get-app-id app-ref)get-bean-property-descriptorclj
(get-bean-property-descriptor object prop-name)init-appclj
(init-app)(init-app comp)(init-app comp props)Initialize app data as an atom and return the atom. The atom is wired in to necessary watches, core.async channels, and any other fns and structures to make it functional and not just a regular atom. The result is an atom that is reactive to changes according to FRP (Functional Reactive Programming). Components may subsequently be added to the app. For convenience there is a single arg version of this fn that will create a component. Although nothing prevents multiple calls to init-app and the code will work properly when multiple calls are made, init-app is intended to be called once. The resources (including threads) allocated are done so as if this is for the entire application.
Initialize app data as an atom and return the atom. The atom is wired in to necessary watches, core.async channels, and any other fns and structures to make it functional and not just a regular atom. The result is an atom that is reactive to changes according to FRP (Functional Reactive Programming). Components may subsequently be added to the app. For convenience there is a single arg version of this fn that will create a component. Although nothing prevents multiple calls to init-app and the code will work properly when multiple calls are made, init-app is intended to be called once. The resources (including threads) allocated are done so as if this is for the entire application.
instantiate-classclj
(instantiate-class view)padclj
(pad col length)retroact-cmd-chanclj
stateclj
update-childrenclj
(update-children onscreen-component app-ref name old-children new-children)cljdoc is a website building & hosting documentation for Clojure/Script libraries
× close