ReactiveUI: The Book

[anaisbetts]

This massive PR is the PR for the new version of the ReactiveUI documentation. This documentation is intended to be a comprehensive usage guide / reference for the library.

TODO:

[ ]   ├── getting-started.md
[ ]   ├── library-overview.md
[X]   ├── migrating-from-rxui4.md
[ ]   ├── overview.md
[ ]   ├── rac-info.md

      ├── advanced
[ ]   │   ├── act-on-every-object.md
[ ]   │   ├── autopersist.md
[ ]   │   ├── create-derived-collection.md
[ ]   │   ├── handle-observable-errors.md
[ ]   │   ├── index.md
[ ]   │   ├── memoizing-mru-cache.md
[ ]   │   ├── orderedcomparer.md
[ ]   │   ├── property-binding-continued.md
[ ]   │   ├── reflection-utils.md
[ ]   │   ├── serialization.md
[ ]   │   ├── suspension-host.md
[ ]   │   ├── testing.md
[ ]   │   └── when-navigated-to.md

      ├── android
[ ]   │   ├── activities-and-fragments.md
[ ]   │   ├── initialization.md
[ ]   │   └── platform-info.md

      ├── basics
[X]   │   ├── binding.md
[X]   │   ├── create-derived-collection.md
[X]   │   ├── dependency-resolution.md
[X]   │   ├── errors.md
[ ]   │   ├── index.md
[X]   │   ├── logging.md
[X]   │   ├── messagebus.md
[X]   │   ├── reactive-command-async.md
[X]   │   ├── reactive-command.md
[X]   │   ├── reactive-list.md
[X]   │   ├── reactive-object.md
[ ]   │   ├── routing.md
[ ]   │   ├── rx-cocoa-delegates.md
[ ]   │   ├── rx-events.md
[ ]   │   ├── schedulers.md
[ ]   │   ├── testing.md
[ ]   │   ├── to-property.md
[ ]   │   ├── unit-test-detection.md
[ ]   │   ├── view-location.md
[ ]   │   └── whenany.md

      ├── cocoa
[ ]   │   ├── initialization.md
[ ]   │   ├── kvo-observation.md
[ ]   │   ├── platform-info.md
[ ]   │   ├── reactive-view-controllers.md
[ ]   │   └── reactivetableviewsource.md

      ├── customization
[ ]   │   ├── binding-type-converters.md
[ ]   │   ├── creates-command-binding.md
[ ]   │   ├── creates-observable-for-property.md
[ ]   │   ├── dependency-resolution.md
[ ]   │   ├── index.md
[ ]   │   ├── registrable-interfaces.md
[ ]   │   └── startup.md

      └── xaml
[ ]       ├── auto-data-template.md
[ ]       ├── booleantovisibilitytypeconverter.md
[ ]       ├── platform-info.md
[ ]       └── transitioning-content-control.md

[jlaanstra]

I've used the MessageBus a couple of times for a ListPage <-> DetailPage scenario where I put the selected item on the MessageBus. Is that a use case we should mention for the MessageBus?

[bradphelan]

Yeah it works really well but I always get the feeling I'm just using
global variables with a fancy facade. With master detail you can create two
models. The master model is a reactive list + the selected index and the
detail model has a property that you bind to the selected item of the
master model. You could do this binding through a message bus but if you
create both the master view model and detail view model together it's
pretty easy to bind them together without a message bus.

I've used both message bus and direct binding and it works well either way.
On 04/11/2013 9:25 PM, "Johan Laanstra" notifications@github.com wrote:

I've used the MessageBus a couple of times for a ListPage <-> DetailPage
scenario where I put the selected item on the MessageBus. Is that a use
case we should mention for the MessageBus?

—
Reply to this email directly or view it on GitHubhttps://github.com//pull/391#issuecomment-27719430
.

[arlair]

Hi, this is just some info from someone trying to learn ReactiveUI :).

I was wondering why the doc branch is not kept in sync with master and the latest documentation not stored with each release? Via a link Paul posted on StackOverflow, I stumbled upon this treasure trove of information. I'm pretty sure that originally (weeks before I found this page) I went to:

https://github.com/reactiveui/ReactiveUI/tree/master/docs

and found it pretty empty and figured that was it. I realise the documentation is not complete yet, and sometimes out of date, but it definitely helped me a lot when piecing it together with other sources found on the web.

If that is not possible (I'm also a bit of a Git noob ;), it might be nice to link to the doc branch somewhere highly visible on Github and maybe reactiveui.net.

Thanks for the great work on ReactiveUI. After being a bit scared off at my lack of Reactive Extensions knowledge and finding it hard to figure out ReactiveUI, I came back and have been putting in a bigger effort to merge all the events in my head together.

[shiftkey]

I was wondering why the doc branch is not kept in sync with master and the latest documentation not stored with each release?

It was something that was started before the major release shipped. It'd be great to keep them in sync, but getting them completed is the first headache to solve.

it might be nice to link to the doc branch somewhere highly visible on Github and maybe reactiveui.net.

Yeah, I think this is much easier to do once we get this merged in. See also #574 for making the website better.

[kjellski]

Is there any way to have a look at this in a complete view? Or even better, merge parts of it already? The documentation as it is right now is nearly completely deprecated isn't it? I tried to spin up from samples and got lost in translation.
Any suggestions on how to help out maybe?

[ljani]

@kjellski See or checkout the docs branch for "a complete view", I'm not sure how complete it's though :)

[kjellski]

👍 thanks a lot! :) great progress already!

[jlaanstra]

👍