How auto-redrawing-works -Integrating multiple execution threads -Integrating to legacy code -Signature
+Typically, m.startComputation / m.endComputation don't need to be called from application space. These methods are only intended to be used by people who are writing libraries that do things asynchronously, or when calling vanilla javascript asynchronous functions from template config functions.
If you need to do custom asynchronous calls without using Mithril's API, and find that your views are not redrawing, or that you're being forced to call m.redraw manually, you should consider using m.startComputation / m.endComputation so that Mithril can intelligently auto-redraw once your custom code finishes running.
Usage -Retrieving a value via the getter-setter API -Integrating to the Mithril redrawing system -Differences from Promises/A+ -The exception monitor -Signature
+This is a low-level method in Mithril. It's a modified version of the Thenable API.
A deferred is an asynchrony monad. It exposes a promise property which can bind callbacks to build a computation tree.
This function overwrites the reference to the window object that is used internally by Mithril. It is useful for injecting a mock window dependency for the purposes of testing and for running Mithril in non-browser environments. The mock object used by Mithril for its own test suite can be found in the development repo.
By default, Mithril uses window itself as the dependency. Note that Mithril only uses the mock object for browser APIs such as the DOM API and requestAnimationFrame, but relies on the environment for ECMAScript features like Object.keys.
Usage -Binding to data -Using HTML entities -Accessing the real DOM element -Persisting config data -Destructors -SVG -Dealing with focus -Dealing with sorting and deleting in lists -Signature
+This is a convenience method to compose virtual elements that can be rendered via m.render().
You are encouraged to use CSS selectors to define virtual elements. See "Signature" section for details.
diff --git a/archive/v0.1.22/mithril.min.zip b/archive/v0.1.22/mithril.min.zip index c14a8352..433baebd 100644 Binary files a/archive/v0.1.22/mithril.min.zip and b/archive/v0.1.22/mithril.min.zip differ diff --git a/archive/v0.1.22/mithril.module.html b/archive/v0.1.22/mithril.module.html index 8b782300..562e8705 100644 --- a/archive/v0.1.22/mithril.module.html +++ b/archive/v0.1.22/mithril.module.html @@ -77,9 +77,11 @@Usage -Unloading modules -Signature
+A module is an Object with two keys: controller and view. Each of those should point to a Javascript function.
When using m.module, Mithril instantiates controllers as if they were class constructors. However, controllers may return objects if you want to use that Javascript feature to have more fine-grained control over a controller's lifecycle.
Usage -Third-party promise library support -Serializing getter-setters -Signature
+This is a getter-setter factory utility. It returns a function that stores information.
Note that modifying the values of m.prop getter-setters does not trigger redrawing. Instead, Mithril's redrawing system relies on m.startComputation and m.endComputation. These functions are internally called by Mithril when you initialize a module via m.module or m.route, and when you trigger event handlers that were created within templates with m().
Changing redraw strategy -Preventing redraws on events -Forcing redraw -Signature
+Redraws the view for the currently active module. Use m.module() to activate a module.
This method is called internally by Mithril's auto-redrawing system. Usually you don't need to call it manually unless you are doing recurring asynchronous operations (i.e. using setInterval) or if you want to decouple slow running background requests from the rendering context (see the background option in m.request.
Usage -Subtree directives -Signature
+This method generates a DOM tree inside of a given HTML element.
If the method is run more than once with the same root element, it diffs the new tree against the existing one and intelligently modifies only the portions that have changed.
diff --git a/archive/v0.1.22/mithril.request.html b/archive/v0.1.22/mithril.request.html index d05f4b08..d8cbeb4a 100644 --- a/archive/v0.1.22/mithril.request.html +++ b/archive/v0.1.22/mithril.request.html @@ -77,20 +77,22 @@Basic usage -Processing-web-service-data -Bind redirection code -Binding errors -Queuing operations -Casting the Response Data to a Class -Unwrapping Response Data -Using Different Data Transfer Formats -Using variable data formats -Extracting Metadata from the Response -Custom request rejections -Configuring the underlying XMLHttpRequest -Aborting a request -Signature
+This is a high-level utility for working with web services, which allows writing asynchronous code relatively procedurally.
By default, it assumes server responses are in JSON format and optionally instantiates a class with the response data.
diff --git a/archive/v0.1.22/mithril.route.html b/archive/v0.1.22/mithril.route.html index 520c1211..01028a8e 100644 --- a/archive/v0.1.22/mithril.route.html +++ b/archive/v0.1.22/mithril.route.html @@ -77,13 +77,15 @@Defining routes -Variadic routes -Routes with querystrings -Running clean up code on route change -Redirecting -Reading the currently active route -Mode abstraction
+Routing is a system that allows creating Single-Page-Applications (SPA), i.e. applications that can go from a page to another without causing a full browser refresh.
It enables seamless navigability while preserving the ability to bookmark each page individually, and the ability to navigate the application via the browser's history mechanism.
diff --git a/bubbles.html b/bubbles.html new file mode 100644 index 00000000..64eec728 --- /dev/null +++ b/bubbles.html @@ -0,0 +1,4 @@ + + \ No newline at end of file diff --git a/chain.html b/chain.html new file mode 100644 index 00000000..1cd5a7e7 --- /dev/null +++ b/chain.html @@ -0,0 +1,98 @@ + + + +