robmaister / sharpfont.harfbuzz Goto Github PK

Currently GlyphInfo and GlyphPosition are classes. Allocating large numbers of these puts a lot of pressure on the GC. Therefore, these should be structs.

It looks like Windows, Mac and Linux are currently supported, is this correct?

What would it take to support Xamarin.iOS, Xamarin.Android and Windows 10 Universal?

It would also be very helpful if this is made into a NuGet package.

I'd be happy to help.

I got this message when I try to build application.

Just checking in to see whether the discussion in #7 is still alive. I am finally concentrating solely on using SharpFont and SharpFont.HarfBuzz. This issue is to help reboot the threads of the other discussion.

Since SharpFont has already taken a step in the right direction, some suggestions:

1. SharpFont.HarfBuzz currently depends on the old version of the SharpFont code, so it would be great to have it running against the new code.

2. There are currently three projects - SharpFont, SharpFont.Portable, and SharpFont.iOS. The only difference between SharpFont.Portable and SharpFont is the bitmap code in FTBitmap.cs, so maybe just that code can be abstracted into a separate library named SharpFont.System.Drawing or some such?

Additionally, perhaps SharpFont.iOS could be removed? The currently #ifdef'd out APIs could just throw an exception at runtime if they are called on the wrong OS. It seems the #if's should be checking for macOS rather than iOS, i.e.:
#if macOS
rather than
#if !iOS

To do this without conditionally compiled code requires a way to determine the OS from the portable class library, which is possible in this specific case. I'll prepare a pull request for this.

tl;dr: Replace all three dll's with a single portable library, and move the platform-specific bitmap code to a different assembly (or just publish it as a source file to be included directly.

3. Is the 64-bit patch to freetype really required? I ask because it would be ideal to not have to worry about producing custom builds of the native binaries. On the other hand, if native builds are needed for other reasons, then this doesn't matter as much.

4. It would be great if there were a self-contained version of SharpFont.HarfBuzz that included all the dependencies, including C# FreeType wrappers and the native libraries, i.e. everything that is currently in SharpFont. Is this feasible?

5. Any traction on getting rid of the glib dependency that was mentioned in #7?

Cheers,

I think first step would be being able porting some parts of this sample (found from this page)