radicalfx / documentation Goto Github PK

Documentation for RadicalFx/Radical#236

https://github.com/RadicalFx/radical/wiki/BrokerObserver

• Restore branch protection
• Add fixed references to samples
• Remove rc-docs-changes from GitBook integration

https://github.com/RadicalFx/radical/wiki/Handling-change-tracking-in-a-simple-model

https://github.com/RadicalFx/radical/wiki/Change-Tracking-Service

Via GitBook plugins

https://github.com/RadicalFx/radical/wiki/MementoObserver

https://docs.radicalframework.com/presentation/conventions/bootstrap-conventions

Will be fixed by 79292f9

https://github.com/RadicalFx/radical/wiki/Handling-change-tracking-in-collections-and-complex-objects-graph

https://github.com/RadicalFx/radical/wiki/PropertyObserver

From @mauroservienti on March 25, 2014 4:32

Related to #7

Copied from original issue: RadicalFx/Radical#11

https://github.com/RadicalFx/radical/wiki/EntityViewListChangedObserver

Once migration to GitBook ( #2 ) is completed we need to understand how to handle redirects from the old wiki pages to the new documentation site.

Radical 1.x users depend on dependency installers specific to the container they are using. Documentation needs to be put in place on how to migrate to the new API

Dependabot couldn't parse the config file at .dependabot/config.yml. The error raised was:

(<unknown>): did not find expected key while parsing a block mapping at line 3 column 5

Please ensure the config file is a valid YAML file. An online YAML linter is available here.

From @mauroservienti on March 25, 2014 4:9

Espceially related to the following issue RadicalFx/Radical#7 (comment)

Copied from original issue: RadicalFx/Radical#9

https://github.com/RadicalFx/radical/wiki/Observers:-concepts

• https://docs.radicalframework.com/mvvm/
• https://github.com/RadicalFx/documentation/blob/master/docs/mvvm/index.md

Content is far from being clear: https://docs.radicalframework.com/memento/change-tracking-service/change-tracking-service-api

Replace the entire page with a few concepts only. First one: about transient objects

https://docs.radicalframework.com/how-tos/async-long-running-busy-status.html

Misses title and links

• https://dotnetthoughts.net/static-code-analysis-of-netcore-projects/
• https://docs.sonarqube.org/latest/analysis/scan/sonarscanner-for-msbuild/

https://docs.radicalframework.com/memento/change-tracking-service/handling-collection-sync

From the autocomplete one

https://github.com/RadicalFx/radical/wiki/Property-Metadata-for-the-Change-Tracking-Service

While investigating other things I discovered that Read The Docs support for markdown has improved. The read-the-docs branch contains some experiments.

We have doco on editors (https://github.com/RadicalFx/radical/wiki/Handling-change-tracking-in-collections-and-complex-ViewModels-graph) but nothing specific to how to sync changes back from the editor to the model via MVVM

1. Create a new .NET Core WPF project with the same name of the project you want to migrate
2. Replace the .NET Framework csproj file with the file of the project created on step 1 (the core project will scan and add all the files of the project, so no manual changes are needed)
3. Delete "Properties" folder
4. Copy "AssemblyInfo.cs" from the project created on step 1 to the root project folder
5. Take note of the NuGet references from the "packages.config" file and then delete it.
6. Add the needed references from NuGet

https://github.com/RadicalFx/radical/wiki/MementoEntity-and-MementoEntityCollection

• Drop current sample in Showcases #117
• New sample: #118

Spun off from #40

PoA

• Discover how to add a contribute via GitHub button to allow easy online edits of pages
• Add @micdenny to Read the Docs as maintainer
• Add @nazarenomanco to Read the Docs as maintainer
• merge to master overriding current documentation
• Add domain configuration to Read the Docs settings so to be hosted at docs.radicalframework.com
• change DNS CNAME settings in CloudFlare to point to readthedocs.io
• Verify CloudFlare CDN + SSL settings don't break doco

From @mauroservienti on August 19, 2015 5:6

Copied from original issue: RadicalFx/Radical#150

Copied from original issue: RadicalFx/Radical.Windows#5

The how to build section, should be under a solution structure section, where we also document how solutions are composed.

https://github.com/RadicalFx/radical/wiki/Abstract*Memento*ViewModel-and-the-Change-Tracking-Service

GitBook is a good compromise. The source of truth is still this repo, changes can be made here or in GitBook directly and there will be a 2 way sync.

Documentation is a available here: https://docs.radicalframework.com/

Keeping track of migration progress is here is not easy. So I decided to delete pages from the Wiki as they are migrated to GitBook.

Puzzle is now supported in WPF as well

• Source: https://github.com/RadicalFx/documentation/blob/master/docs/ioc/puzzle.md
• Rendered: https://docs.radicalframework.com/ioc/puzzle.html

Also

• Source: https://github.com/RadicalFx/documentation/blob/master/docs/ioc/index.md
• Rendered: https://docs.radicalframework.com/ioc/