.Net Standard version of Typography

[Happypig375]

Currently two files of this same type exists in two different places (PixelFarm.Typography and DrawingGL.Common). GlyphPathBuilder.cs, GlyphPathBuilderBase.cs and HintTechnique.cs should reside in the Typography.Contours project (as they should be proper APIs) and not hidden in the Demo projects.

I tried to move them but all of the projects rely on Typography.Contours targeting .NET Framework 2.0 and the mobile demo projects yelled at me. I tried to create Typography.Contours build projects like Typography.OpenFont and Typography.GlyphLayout but the reference errors are too much for me. Finally, turning Typography.Contours into a .NET Standard project to make every project happy results in

Error CS0012 The type 'ValueType' is defined in an assembly that is not referenced. You must add a reference to assembly 'mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'.

Welp, a day of work spent on nothing. I just wanted to make use of these files and follow the code in demos...

The same applies to a lot of types in demo projects that should be proper APIs.

[prepare]

Is it Ok if I turn Typography.Contours to .NET standard project?

[Happypig375]

I don't know. If this project targets .NET Standard, other projects, including the demo ones, cannot target .NET Framework 2.0 anymore.

[zwcloud]

I would recommend using a shared project to share source code files between .NET Standard Class Library and .NET Framework 2.0 Class Library.

And in the source code, using #if NET_2_0 #elif ... to conditionally include code sections that is used for .NET 2.0. You can define NET_2_0 in the .NET Framework 2.0 class library project manually.

[Happypig375]

@zwcloud
Actually, that is already the case with the shared projects Typography.OpenFont and Typography.GlyphLayout and the 8 projects in the Build folder. Just that the shared platforms are Xamarin.iOS, Xamarin.Android, .NET Framework 2.0 and .NET Core 1.1.

It is very hard to make another one of those for Typography.Contours though.

[zwcloud]

Hah, that's actually introduced by me. Then just do it. @prepare :)

BTW,
Xamarin.iOS and Xamarin.Android now should be compatible with .NET Standard 2.0. See .NET Standard. So those libraries could be merged into one .NET Standard 2.0 class library.

[prepare]

Add .net standard support for Typography.Contours

please check this b7cf599 is fit to your need?

[zwcloud]

So Typography.Contours is a lower level of core Typography API. 😆
It's a good start point for a better API design. @prepare

[prepare]

It is a very + dirty quick fix :)

It needs more cleanup.

Always welcome all suggestions + API design.
(+ PR(s))

[prepare]

So Typography.Contours is a lower level of core Typography API

the 'inner core' to 'outer' one => by order

1. Typography.OpenFont
2. Typography.GlyphLayout

other than those (eg. Contours) are not need.

[Happypig375]

@prepare
Seems you forgot to commit the Android and iOS build projects for Typography.Contours though.

[prepare]

please see : 78b3bd7
I added .net standard version of OpenFont, GlyphLayout ,Contours.
You can reference these in new iOS and Android App.

(Also removed old Android and iOS project)

---

Also update Android and iOS examples

add 'DroidSans.ttf' for iOS :)

---

DroidSans.ttf, iOS Emu, Xamarin + GLES2 surface

---

DroidSans.ttf, Android Emu, Xamarin + GLES2 surface

[prepare]

Android and iOS examples are 'just work' but not optimized yet
(see #45)

I'm fixing it on the main PixelFarm project.
(esp. PaintLab/PixelFarm#20)

[Happypig375]

One thing that I don't understand is why the .NET Framework 2.0-targeting build projects add files as link instead of referencing the shared project. Why add files in two places when you can do it with just one only?

[prepare]

for VS2010 (old, with commercial license).
It can't open shared source project.

[zwcloud]

Personally, I think it's better to drop support for VS2010.

[prepare]

Yes, after I buy a new Visual Studio Professional :)

[Happypig375]

Oh, ok. Thanks for replying.

[Happypig375]

@prepare

Yes, after I buy a new Visual Studio Professional :)

Why is Visual Studio 2017 Community not enough for you? ❔

[prepare]

Community Edition is fine for this project.

But on another side, I can't use it to develop a software for an enterprise.

(see: https://www.visualstudio.com/vs/compare/
topic: Supported Usage Scenarios > Enterprise )

[Happypig375]

Footnotes:

1. Enterprise organizations are defined as >250 PCs or > $1 Million US Dollars in annual revenue.

I don't think you ever need to support an organisation this big. If the organisation does reach this big, it can probably afford Visual Studio Enterprise already.

[charlesroddie]

I don't think this issue should be closed as there are references to
v2.0
even in newer branches.

I would just simplify this to have everything target .net standard, and the "standard" version of .net standard to target is 2.0. (Unrelated to the 2.0 above!)

It's not essential because .net standard 2.0 projects can reference .net framework 4.6.1 code, 99% reliably. But it would be cleaner.

[Happypig375]

Hi @prepare, can you please also create .NET Standard versions of Typography.TextServices, TextBreak and TextFlow? I am planning to use them in CSharpMath.

[prepare]

@Happypig375 ,

TextServices, TextFlow and TextBreak in the PixelFarm are more developed than in this repo.

Give me a time to merge them back to this repo.

[prepare]

.Net Standard version of Typography

Is now on dev branch.

see: dbea27b

But Porting back of TextServices, TextFlow, TextBreak are not finish,
so the 3 projects are still the old code (not the latest from PixelFarm) => but in new .net std layout format.

(Porting should be finish soon)

---

[prepare]

.Net standard version is still 1.6
but you can upgrade it the 2.0 easily.

[prepare]

Now, move down to .net-std 1.3