Sign up for notifications / polls / requests for comments from axxel #706
Replies: 22 comments 6 replies
-
|
zint testing, general interest in barcode decoding
…On Mon, Jan 29, 2024 at 10:03 PM axxel ***@***.***> wrote:
Time and again, I find myself in the position to want to get in touch with
"you" out there who have some stake in zxing-cpp. What I did in the past
multiple times is compiling a list of names add hoc based on earlier
contributions or random issue reports that I manage to remember. That is an
inefficient strategy. To my understanding, using the github notifications
feature is supposed to be used for that but that did not work very well
(e.g. with the two most recent poll discussions I started). Maybe most of
you did not sign up for that to not be bothered by random bug reports or ci
build failures?
Anyway, new idea: use this 'meta discussion' where every participant gets
notified when I post here to point your attention to a specific topic, like
I'm doing right now: #705
<#705> (Result ->
Barcode?).
To *subscribe*, anyone can simply post a 'hello world' comment here (I
don't expect this to happen very often). Ideally you'd write a sentence
about what your interests in zxing-cpp are, like e.g. "Author of an
Android App".
To *unsubscribe*, simply press the *Unsubscribe* button on the right.
To get this started I'll do this kind of name compilation one more time:
@gitlost <https://github.com/gitlost> @markusfisch
<https://github.com/markusfisch> @alexmanzer
<https://github.com/alexmanzer> @vkrause <https://github.com/vkrause>
@Sec-ant <https://github.com/Sec-ant> @benjohnde
<https://github.com/benjohnde> @siiky <https://github.com/siiky> @khoren93
<https://github.com/khoren93> @huycn <https://github.com/huycn> @okarmazin
<https://github.com/okarmazin> @duanqn <https://github.com/duanqn>
@SteveCookTU <https://github.com/SteveCookTU> @stumpylog
<https://github.com/stumpylog> @parallaxe <https://github.com/parallaxe>
@ryantrem <https://github.com/ryantrem> @duanqn
<https://github.com/duanqn>
In case I'm ignorant of fancy feature xyz of github that is way more
appropriate for this task: "let me know in the comments down below ;)".
—
Reply to this email directly, view it on GitHub
<#706>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AADVVPRPE3CCELEPYGWNBZTYRAMBNAVCNFSM6AAAAABCQF43K2VHI2DSMVQWIX3LMV43ERDJONRXK43TNFXW4OZWGE2TCMBTGE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
Hi, I'm using ZXingCpp in mobile apps, Android and iOS, professionally and also in side projects. I'm interested in reading, but also very much in writing barcodes. |
Beta Was this translation helpful? Give feedback.
-
|
Hello, I'm the author of flutter_zxing, and I appreciate your initiative to streamline communication regarding zxing-cpp. I've subscribed to this meta discussion to stay updated on relevant topics. |
Beta Was this translation helpful? Give feedback.
-
|
Hello, I'm the maintainer of zxing-wasm, one of the WASM wrappers. I'm interested in the reading part and it's usage in web applications. I'd like to subscribe to keep information updated. |
Beta Was this translation helpful? Give feedback.
-
|
Hi, I am a co-author of a commercial C++ program and we use ZXing-cpp for reading barcodes. I'm interested in improving the recognition rate for barcodes. |
Beta Was this translation helpful? Give feedback.
-
|
Representing KDE here, we use ZXing via its C++ API for "conventional" barcode scanning in mobile apps, for barcode decoding in PDF documents (pure mode), and for PDF417 rendering. I am subscribed to notifications of everything here already anyway, so I did notice the two recent discussions you mentioned, but since those don't really impact us (or as in case of the naming the impact is the same regardless of the new name) I didn't comment there. |
Beta Was this translation helpful? Give feedback.
-
|
I initially put the C wrapper ball rolling, which I use at work to read QR and PDF417 codes. |
Beta Was this translation helpful? Give feedback.
-
|
I guess everyone here has read about the new .NET wrapper somewhere by now but since I specifically set up this discussion here for this kind of information: #707 :) |
Beta Was this translation helpful? Give feedback.
-
|
It just so happens that already another subject requiring some community feedback came up: Please state your opinion regarding disabling of exception handling in this poll: #710. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for all the work ! Trying to evaluate if I may be able to use it at work. Mostly interested in C/CPP. Since the native is CPP, that bloats up my application size, trying to keep it to a minimum. |
Beta Was this translation helpful? Give feedback.
-
|
For a further discussion of this question please reply to #715. |
Beta Was this translation helpful? Give feedback.
-
|
The work I've just pushed in pursuit of helping detect inverted barcodes (see #711) led to a significant change in how the |
Beta Was this translation helpful? Give feedback.
-
|
Our test suite seems unaffected, but that is dominated by "pure" images which I'd assume aren't really impacted by this work anyway. |
Beta Was this translation helpful? Give feedback.
-
|
@vkrause that is correct. If you only have black and white pixels, the old and new implementation of the |
Beta Was this translation helpful? Give feedback.
-
|
Checked to be sure, we do that already indeed. |
Beta Was this translation helpful? Give feedback.
-
|
New poll: #722 (Should |
Beta Was this translation helpful? Give feedback.
-
|
And another poll: #725 (Mobile applications and the use of |
Beta Was this translation helpful? Give feedback.
-
|
New poll: #744 (How best to disable/remove the writer or reader functionality from the build?) |
Beta Was this translation helpful? Give feedback.
-
|
I changed the cmake build options to use the prefix |
Beta Was this translation helpful? Give feedback.
-
|
New poll: Add a JSON 'channel' to communicate symbology specific / niche bits of data (#862) |
Beta Was this translation helpful? Give feedback.
-
|
I "published" a 2.3.0-rc1 release and would be delighted if anyone interested could give it a quick check with their setup. I don't expect much reaction today and will likely do the 2.3.0 release tomorrow, because 1.1.25 sounds nice ;). |
Beta Was this translation helpful? Give feedback.
-
|
Anyone interested in the WinRT wrapper? Since @huycn has not responded to #882, yet. I fear he might not be available to the cause of this project anymore. Is there anyone else interested in the WinRT wrapper? Since maintaining this niche windows corner while not being a windows user myself is a burden, the future of this wrapper code and accompanying NuGet package is looking bleak. |
Beta Was this translation helpful? Give feedback.
-
|
Hi @axxel, I am a Windows user and I am willing to contribute, but I am relatively new to WinRT. I have read #882. Is there anything we need to do at the moment, apart from generating a new key? |
Beta Was this translation helpful? Give feedback.
-
|
I can't simply renew the key as I don't own the account. I could setup a new one or maybe use the one I created for the .NET wrapper. But that would basically mean, to publish a 'new' wrapper. And in that case, it would make sens to me to use the opportunity to modernize the API and bring it in line with the e.g. the .NET wrapper API. If you are interested in looking into this, please go ahead. |
Beta Was this translation helpful? Give feedback.
-
|
Everyone that uses pkg-config (specifically |
Beta Was this translation helpful? Give feedback.
-
|
Triggered by @gitlost's progress on zint work, specifically for the |
Beta Was this translation helpful? Give feedback.
-
|
Is anyone relying on the possibility to distinguish between any of the 4 variants of the same barcode "family" EAN/UPC, namely To be more specific, my proposal would
EDIT: To clarify even more: |
Beta Was this translation helpful? Give feedback.
-
|
Anyone who cares about what exactly |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Time and again, I find myself in the position to want to get in touch with "you" out there who have some stake in
zxing-cpp. What I did in the past multiple times is compiling a list of names add hoc based on earlier contributions or random issue reports that I manage to remember. That is an inefficient strategy. To my understanding, using the github notifications feature is supposed to be used for that but that did not work very well (e.g. with the two most recent poll discussions I started). Maybe most of you did not sign up for that to not be bothered by random bug reports or ci build failures?Anyway, new idea: use this 'meta discussion' where every participant gets notified when I post here to point your attention to a specific topic, like I'm doing right now: #705 (
Result->Barcode?).To subscribe, anyone can simply post a 'hello world' comment here (I don't expect this to happen very often). Ideally you'd write a sentence about what your interests in
zxing-cppare, like e.g. "Author of an Android App".To unsubscribe, simply press the Unsubscribe button on the right.
To get this started I'll do this kind of name compilation one more time: @gitlost @markusfisch @alexmanzer @vkrause @Sec-ant @benjohnde @siiky @khoren93 @huycn @okarmazin @duanqn @SteveCookTU @stumpylog @parallaxe @ryantrem @duanqn.
EDIT: To make one thing more clear: everyone mentioned here explicitly is already subscribed, but if you'd still like to drop us a line about your interests, please do so. :)
In case I'm ignorant of fancy feature xyz of github that is way more appropriate for this task: "let me know in the comments down below ;)".
Beta Was this translation helpful? Give feedback.
All reactions