Update doco for 0.10.0

Closes #172

Author: japgolly

README.md

@@ -22,7 +22,7 @@ Includes a router, testing utils, performance utils, more.
   - [Performance Management](extra/PERF.md).
   - [Smaller stuff](extra/README.md).
 - [Testing](test/README.md).
-- [Changelogs](doc/) — [Latest](doc/CHANGELOG-0.9.md).
+- [Changelogs](doc/) — [Latest](doc/CHANGELOG-0.10.md).
 
 
 ##### External Resources
@@ -41,6 +41,6 @@ Includes a router, testing utils, performance utils, more.
 
 
 ##### Requirements:
-* React 0.12 *(0.13 probably works too, 0.14 will be fully supported when released)*
+* React 0.14
 * Scala 2.11
 * Scala.JS 0.6.4+

doc/CHANGELOG-0.10.md

@@ -303,18 +303,18 @@ the render function name. Conversely, it's now always obvious what's happening b
 All `render*` functions take as their sole argument a function that returns a `ReactElement` (which is a `ReactComponent` or DOM element).
 
 The `render` function takes a function which has as its first argument a `CompScope`,
-which is broadly analogous to javascript's `this`, and which scalajs-react conventionally designates with `$`. 
+which is broadly analogous to javascript's `this`, and which scalajs-react conventionally designates with `$`.
 
 |Method|Argument|Example|
 | --- | --- | --- | --- |
 |`render`|Function taking `CompScope`<br>(Component scope: analogous to javascript `this`)|`.render { $ => <.div() }`|
 
-Additional `render*` convenience functions *without an underscore* specify (and unwrap) additional arguments, 
-which scalajs-react conventionally designates as `P` for `props`, `C` for `propsChildren`, and `S` for `state` 
-(see table below). The uppercase is not an accident: all of these are the types of generic arguments 
+Additional `render*` convenience functions *without an underscore* specify (and unwrap) additional arguments,
+which scalajs-react conventionally designates as `P` for `props`, `C` for `propsChildren`, and `S` for `state`
+(see table below). The uppercase is not an accident: all of these are the types of generic arguments
 explicitly or implicitly given to `ReactComponentB`.
 
-These additional `render*` functions are convenience functions, as all of these additional arguments can be 
+These additional `render*` functions are convenience functions, as all of these additional arguments can be
 found as members of the `CompScope` argument.
 
 E.g.:
@@ -323,16 +323,16 @@ E.g.:
         val p = $.props
         val c = $.propsChildren
         val s = $.state
-        
+
         <.div()
      }
-      
+
 is equivalent to:
 
     .renderPCS { ($, p, c, s)  =>
         <.div()
      }
-     
+
 |Method|Argument|Example|
 | --- | --- | --- | --- |
 |`renderPCS`|Fn taking `CompScope`, props, children, state|`.renderPCS(($, p, c, s) => <.div())`|
@@ -343,9 +343,9 @@ is equivalent to:
 |`renderC`  |Fn taking `CompScope`, children|`.renderC(($, c) => <.div())`|
 |`renderS`  |Fn taking `CompScope`, state|`.renderS(($, s) => <.div())`|
 
-`render*` function overloads *with* an underscore take a function which takes has only that single part of the 
+`render*` function overloads *with* an underscore take a function which takes has only that single part of the
 `CompScope` called out in the function name. The `CompScope` itself is not passed to the function passed.
- 
+
 |Method|Argument|Example|
 | --- | --- | --- | --- |
 |`render_P` | Fn taking only props.    |`.render_P(p => <.div())`|
@@ -432,16 +432,31 @@ Unlike the `render` methods, this migration can be automated (see below).
 
 * Small improvements to `ReusabilityOverlay`.
 
-* Upgrade [scala-js-dom](https://github.com/scala-js/scala-js-dom) 0.8.{1 ⇒ 2}.
+* Upgrade [scala-js-dom](https://github.com/scala-js/scala-js-dom) from 0.8.1 to 0.8.2.
 
 * Added `ReactTagOf` to provide more specific types for virtual DOM (ScalaTags).
-  `ReactTag` is the kept the same as before for compatibility or if you don't need it.  
+
+  `ReactTag` is the kept the same as before for compatibility or if you don't need it.
 
   ```scala
   val specific: ReactTagOf[html.Anchor] = <.a(^.href := "https://google.com", "Google")
   val general: ReactTag = specific
   ```
 
+* React components now have the following type members:
+
+  ```scala
+  type Props     = P
+  type State     = S
+  type Backend   = B
+  type DomType   = N
+  type Mounted   = ReactComponentM[P, S, B, N]
+  type Unmounted = ReactComponentU[P, S, B, N]
+  ```
+
+  These are in the constructors (`ReactComponentC`) which are equivalent to Scala objects.
+  Component instances (`ReactComponentU`, `ReactComponentM`), equivalent to Scala classes, do not have these types.
+
 ---
 
 ### Migration commands

doc/FP.md

@@ -2,11 +2,24 @@
 
 *For now, please just browse the source (it's not massive) and follow the types.*
 
+Callback
+========
+
+Included is a type `CallbackTo[A]` which captures effects designated for use in React callbacks.
+`Callback` is `CallbackTo[Unit]` with a different companion object, full of different goodies that all return `Unit`.
+ <br>*(See also [USAGE.md](USAGE.md).)*
+
+It is roughly equivalent to `IO`/`Task` in Scalaz, Haskell's `IO` monad, etc.
+
+Living in the `core` module with no FP dependencies,
+many ops normally provided via typeclasses (eg. `<*`, `>>=`, etc.) are built-in directly.
+The Scalaz module contains typeclass instances for it.
+
 Scalaz
 ======
 
 ```scala
-libraryDependencies += "com.github.japgolly.scalajs-react" %%% "ext-scalaz71" % "0.9.2"
+libraryDependencies += "com.github.japgolly.scalajs-react" %%% "ext-scalaz71" % "0.10.0"
 ```
 
 Included is a Scalaz module that facilitates a more functional and pure approach to React integration.
@@ -23,11 +36,10 @@ Monocle
 =======
 
 ```scala
-libraryDependencies += "com.github.japgolly.scalajs-react" %%% "ext-monocle" % "0.9.2"
+libraryDependencies += "com.github.japgolly.scalajs-react" %%% "ext-monocle" % "0.10.0"
 ```
 
 A module with a extensions for [Monocle](https://github.com/julien-truffaut/Monocle) also exists under `ext-monocle`.
 
 There's one example online that demonstrates Monocle usage:
 [`ExternalVar` example](https://japgolly.github.io/scalajs-react/#examples/external-var).
-

doc/TYPES.md

@@ -48,9 +48,9 @@ Namely...
 
 | Type | Desc |
 | ---- | ---- |
-| `ComponentScope.DuringCallbackU[P, S, +B]` | An unmounted component's `this` scope. |
-| `ComponentScope.DuringCallbackM[P, S, +B]` | A mounted component's `this` scope. |
-| `ComponentScope.WillUpdate[P, S, +B, +N]` | A component's `this` scope during `componentWillUpdate`. |
+| `CompScope.DuringCallbackU[P, S, +B]` | An unmounted component's `this` scope. |
+| `CompScope.DuringCallbackM[P, S, +B]` | A mounted component's `this` scope. |
+| `CompScope.WillUpdate[P, S, +B, +N]` | A component's `this` scope during `componentWillUpdate`. |
 | `BackendScope[P, S]` | A component's `this` scope as is available to backends. |
 
 For using JS React Components, you can use follow facade interfaces.
@@ -95,10 +95,23 @@ One of the suffixes below can be added to any the ReactEvents above, to provide
 
 For example, `ReactDragEventI` is a `ReactDragEvent` over a `HTMLInputElement` (an `<input>`), the same as writing `SyntheticDragEvent[HTMLInputElement]`.
 
+### Component-scope access
+
+To prevent issues such as
+backends' props/state being used in such a way that they go stale at runtime (a suprisingly easy mistake to make),
+component/backend scope access is as follows:
+
+| Method | `BackendScope` | During Callback | External Access |
+| --- | --- | --- | --- |
+| `.props` | `CallbackTo[P]` | `P` | `P` |
+| `.state` | `CallbackTo[S]` | `S` | `S` |
+| `.setState` | `Callback` | `Callback` | `Unit` |
+| `.modState` | `Callback` | `Callback` | `Unit` |
+| `.forceUpdate` | `Callback` | `Callback` | `Unit` |
+
 # Other
 
 | Type | Desc |
 | ---- | ---- |
-| `ComponentStateFocus[T]` | Rather than give functions full access to a components state, you can narrow the state down to a subset and pass that around via this type. |
 | `Ref[+N]` | A named reference to an element in a React VDOM. (See [React: More About Refs](https://facebook.github.io/react/docs/more-about-refs.html).) |
 | `RefP[I, +N]` | As above but references multiple, related DOM elements and requires a parameter `I` (usually an ID) to disambiguate. |