The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning. Learn more →
TextLayoutSampler Alternatives
Similar projects and alternatives to TextLayoutSampler
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
Onnx2Text
Converts an ONNX ML model protobuf from/to text, or tensor from/to text/CSV/raw data. (Windows command line tool)
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
FontSetViewer
Utility to display items in an IDWriteFontSet and browse their name strings and preview. (Windows GUI exe)
-
BiNums
Binary numbers - command line tool displays various numeric formats in binary and vice versa.
TextLayoutSampler reviews and mentions
-
C++/C# interop for Windows (desktop) applications using WinRT
All of them :b (TextLayoutSampler, FontSetViewer, Onnx2Text, LunaSvgSampleTest, BiNums). With the exception of multicolor fonts (e.g. Segoe UI Emoji) and more robust vertical text support for Japanese text, there just haven't been any new APIs since Windows 7 that warrant moving forward for me 🤷♂️. Note all of those are fully C++ based, but I'm also working on a pixel format viewer for which I want C# interop to potentially utilize existing Paint.NET imaging/effect plugins.
-
figcone - Read JSON, YAML, TOML, XML or INI configuration by declaring a struct
I appreciate that you support multiple libraries/file types for the backing serialized text tree representation, for I always thought it silly that configuration tools would often support only a single file type - interop matters! (I had something similar for one of my apps, a general text tree class where the input/output can be JSON/XML/INI)
-
Modules support in visual studio
I can identify with that pain. I first started modularizing one of my projects in 2017, and after reporting another bug, I'd try every new VS release, only to make it another 20% further in the build and encounter another internal compiler issue. Though, it did finally build 100% in VS 2019, consuming Windows.h, some DirectX headers, and various std headers. Boost though, that might still be a beast of complexity beyond.
-
Stability of modules in Visual Studio?
Well I haven't seen that one, but I've gotten other ICE's and linker errors while incrementally modularizing this app over the years. e.g. Common.Variant.ixx(106,1): fatal error C1001: Internal compiler error. I definitely want to file bugs, and have been, but it's tedious to narrow down the ~20'000 line program for a repro 😑, as often times the change is due to elsewhere rather than the reported line itself. I did though get another program of mine (~15'000 lines) completely modularized successfully yesterday with VS2019 16.10.0 Preview 2, after applying the work-around for one linker error and disabling PCH's with modules. 😊 So it's definitely improving.
-
A note from our sponsor - WorkOS
workos.com | 27 Apr 2024
Stats
fdwr/TextLayoutSampler is an open source project licensed under MIT License which is an OSI approved license.
The primary programming language of TextLayoutSampler is C++.
Sponsored