Leaderboard

Good news. Our app is now available on the Mac Store and Apple finally approved the MacOS app. Long story short, for whomever runs into the same issue and has the same question... Just continue while not seeing an icon and submit the app. Tell to have Apple review the app and after that process the icon magically appears from then on, also inside Application Loader. Thus, the icns file was perfectly fine. Somehow this is/was at Apple's end, and in the end, nothing to worry about. Hope this helps!

I think I figured it out, when I created the DB using DBeaver, it simply created all columns with a CHARSET of "NONE". Now I'm trying to figure out a way to automate the conversion from NONE to UTF8 as there doesn't seem to be any straight-forward way of making it happen.

Arghhhh... who designs this stuff? Some warnings can be setup at one place, other in another... it is a mess...

Hi Ivana and welcome to the forum. To answer your question, CryptoLib4Pascal is the complete package and more. The hashes you requested and more can be found here sample for generating Key Pairs with Elliptic curves, signing and verifying can be found here and here AES and Chacha20 sample here Perks of CryptoLib4Pascal Constantly developed and improved Cross Platform and Cross Compiler support used in the real world on various products uses the friendly MIT License Best of all, it's free.

Our Open-Source https://github.com/synopse/mORMot/blob/master/SynCrypto.pas has almost all that you require. About performance, it is the only one in the Delphi area using AES-NI and optimized SSE3/SSE4.2 assembly - as far as I know. So it should blow alternatives. It is cross-compiler (Delphi and FPC) and cross-platform (Windows, Linux, BSD... thanks to FPC). For elliptical curves, see its sibbling https://github.com/synopse/mORMot/blob/master/SynEcc.pas It supports only secp256r1 but it is feature complete (e.g. simple CA management) and fast (1 ms to create a key pair, 0.4 ms to sign or verify on x86-64) - also cross-platform and cross-compiler. See the documentation at https://synopse.info/files/html/Synopse mORMot Framework SAD 1.18.html#TITL_187 Both are highly maintained, and used on production since years. They don't require any external dll (like OpenSSL) which tends to be a maintenance nightmare on Windows.

If you have documentation you cannot just yolo refactor code every release and break something...

If you don't document it - how do you expect to maintain backward compatibility? My code relies on REST.Json - ObjectInstance := TJson.JsonToObject<T>(aJsonString) ; - aJsonString := TJson.ObjectToJsonString(ObjectInstance, [joIgnoreEmptyStrings, joIgnoreEmptyArrays, joDateIsUTC, joDateFormatISO8601]); - TJSONInterceptor / JsonReflectAttribute for instructing the converter to drop TDateTime properties that have 0 as value. What are the equivalents in System.Json ?

CORRECT. The "time for docu work" was BEFORE THE FEATURE WAS RELEASED.

Python documentation is excellent. Likewise C# documentation. And so on. Delphi is an outlier here.

I wish the various Json classes were better documented. http://docwiki.embarcadero.com/Libraries/Rio/en/REST.JsonReflect is particularly poorly documented with regards to marshalling, interceptors and converters. I have long been wondering if the TJson.JsonToObject<T>(aJsonString) can be made to handle mixed type arrays {"list": [5, "text", {"prop": "value"}]} by injecting converters, but it seems impossible - but then again - the above mentioned tools are undocumented.

To remember when things were documented is to be old.