Explain why i migrated back to SimpleQRCode

[jyxjjj]

@codemasher
#311 (comment)

I mentioned two links there.

I came here because this repository supports GD, and SimpleQRCode wasn’t good enough for my needs. (Not graceful too.)
I spent about an hour reading through your code and docs.
I migrated back after seeing your comment on another issue where you mentioned planning to drop GD support.

And "How I know you":

Hey, GPT, I don't want to use SimpleQRCode anymore, please refer me a lib supports GD."

I did try installing Imagick, but not from the RPM package. My PHP was self-compiled, and I installed Imagick via PECL. Everything worked fine for several PHP 7 versions, but one day during an upgrade it suddenly started throwing segmentation faults. I tried many parameters, but nothing helped. So I gave up on Imagick completely and switched all my code to GD.
( I think it may because I am always using the latest ImageMagick lib from Fedora DNF Repo and Imagick didn't work with it )

I need PNG instead of SVG, so SimpleQRCode doesn’t fit. That’s why I’m here.

Later, when working on code completion, I got a deprecation warning about output type options. I couldn’t find any valid ones, and I really can’t stand seeing a strikethrough.

It’s just my habit — your repo is good, no worries. I’ll wait for what you said about “v7.” Once it fits my needs, I’ll come back again.

By the way, you probably shouldn’t have closed his issue, especially since you plan to turn it into property hooks. Also, I couldn’t figure out how “this ugly PHPDoc” actually works.

Everything above is just my personal opinion. Please don’t take offense, anyone.

[codemasher]

I migrated back after seeing your comment on another issue where you mentioned planning to drop GD support.

Oh, I see! Thank you for elaborating! Please don't worry, GD support won't go anywhere. The comment you refer to was a bit ironic, certainly not a plan to remove GD support. Out of curiosity: did chatGPT say GD support was going to be removed? (please do not believe the lying robot)
But even if that were the case, you see how flexible this library is, you could implement your own support in no time!

There is currently one deprecation warning for the $outputType option, which will be removed in favor of the $outputInterface option for more flexibility. The reasons for this change are explained in #223. This change is already in the main branch and I'm planning to release v6 shortly after PHP 8.5 is released (in about 4 weeks).

By the way, you probably shouldn’t have closed his issue, especially since you plan to turn it into property hooks. Also, I couldn’t figure out how “this ugly PHPDoc” actually works.

I closed the issue (#311) because it was not an issue and an explanation as to why was given. The "ugly block of code" I mentioned just exists so that PHPStorm doesn't yell at me all the time and it should offer code completion - you don't need to do anything about it.
Same for the property hooks I'm planning to introduce - you don't need to change anything in your own code, you won't notice the difference at all, except that code completion will work seamless and there will be no more warnings about magic access.

I need PNG instead of SVG, so SimpleQRCode doesn’t fit. That’s why I’m here.

Please give it another try - if you need help, just ask here in the discussions.