minor edits to Using D.S. in Proj.

master
Craig Oates 5 years ago
parent
commit
0236632a01
  1. 4
      Using-Death-Socket-in-Your-Project.md

4
Using-Death-Socket-in-Your-Project.md

@ -40,7 +40,7 @@ IMAGE OF SYSTEM FLOW.
- [Graphics Class](https://docs.microsoft.com/en-us/dotnet/api/system.drawing.graphics?view=netframework-4.8#applies-to) (this is probably a good place to start with *System.Drawing*)
- [SkiaSharp Graphics in Xamarin Forms](https://docs.microsoft.com/en-us/xamarin/xamarin-forms/user-interface/graphics/skiasharp/) (provides an introductory overview to SkiaSharp)
This next bit is an aside; So, feel free to skip over this bit and jump straight into the next section... I admit I should have dropped the *System.Drawing* part and focused on *SkiaSharp*, at least in the long-term. The reason I did not is because using *SkiaSharp* with a Xamarin project annoyed me. Long story short... I developed D.S. as the foundation for Paint Grid which is a G.U.I. version of D.S. Paint Grid exists as a W.P.F. and Xamarin (MacOS) application. (The Mac version is not published at the time of writing.) I built the W.P.F. version first with *System.Drawing* and it was fine. I discovered Xamarin does not work with *System.Drawing* and it recommended *SkiaSharp*. This was not as easy to make as the W.P.F. version. So, by the time I finished writing the application, I was annoyed and want to throw my toys out of the pram. I decided to keep the *System.Drawing* code in D.S. so I would not need to use the *SkiaSharp* bits if I needed it for another project. Do not let this put you off using the *SkiaSharp* part of D.S., though. If you are building a cross-platform application, I recommend you use the *SkiaSharp* stuff. I would even go as far as saying I would probably write D.S. with just *SkiaSharp* if I had to start from scratch -- having calmed down.
This next bit is an aside; So, feel free to skip over this bit and jump straight into the next section... I admit I should have dropped the *System.Drawing* part and focused on *SkiaSharp*, at least in the long-term. The reason I did not is because using *SkiaSharp* with a Xamarin project annoyed me. Long story short... I developed D.S. as the foundation for Paint Grid which is a G.U.I. version of D.S. Paint Grid exists as a W.P.F. and Xamarin (MacOS) application. (The Mac version is not published at the time of writing.) I built the W.P.F. version first with *System.Drawing* and it was fine. I discovered Xamarin does not work with *System.Drawing* and it recommended *SkiaSharp*. This was not as easy to make as the W.P.F. version. So, by the time I finished writing the application, I was annoyed and wanted to throw my toys out of the pram. I decided to keep the *System.Drawing* code in D.S. so I would not need to use the *SkiaSharp* bits if I needed it for another project. Do not let this put you off using the *SkiaSharp* part of D.S., though. If you are building a cross-platform application, I recommend you use the *SkiaSharp* stuff. I would even go as far as saying I would probably write D.S. with just *SkiaSharp* if I had to start from scratch -- having calmed down.
## The Pieces You Will Work With
@ -53,7 +53,7 @@ The above image shows the flow of a typical code-base using D.S. Looking at this
To help you get started, I recommend you keep the following two files open when writing your code;
- [GridPainter.fs](https://gitlab.com/craig.oates/Death-Socket/blob/master/DeathSocket/GridPainter.fs)
- [Domain.fs link](https://gitlab.com/craig.oates/Death-Socket/blob/master/DeathSocket/Domain.fs)
- [Domain.fs](https://gitlab.com/craig.oates/Death-Socket/blob/master/DeathSocket/Domain.fs)
### Domain Module

Loading…
Cancel
Save