More about me and CCIDB:
I am very bad at writing in the third person, so here's a first person perspective about me, and about CCIDB. Most people call me Wags (or Wagwan), but Wags is what I personally like more, so you can refer to me as that. All you need to know about me is that I like crypto (as in cryptography, never cryptocurrency) puzzles and ARGs (Alternate Reality Games) and the like. I maintain a personal website which you can visit here. It's got things like puzzles, a blog, and some other, future content coming Soon™. But that's enough backstory, more about how CCIDB started and why you're here.
I started making CCIDB during the COVID-19 pandemic/lockdown(s), as a way of cataloging my existing coin collection which had gone undocumented and untouched for a number of years. CCIDB initially started as a single text file with a small PHP backend, but quickly took on a life of its own, with the introduction of an SQLite database and full front and backend made in a combination of PHP, JavaScript, HTML, and even some Python. PHP was chosen for its ease of learning and capabilities, despite its negative reputation within certain circles. This project was made solely in my free time, with no monetary support from any person or company, and took approximately 3 years to reach a "stable" status. While every effort is made to document where certain bits of code came from (mostly online sources like Stack Overflow), and what each bit of code does functionality wise, not everything is 100% covered at this point in time. Speaking of code, you can find a full list of other resources that I found useful beyond comparison when developing CCIDB below. This includes other software either partially or fully implemented in CCIDB in some way or another (also known as dependencies).
I would also like to give a MASSIVE thank you to a member of the DA Freqs Puzzling Team (which I am part of as well), Doomaholic, for designing the layout of CCIDB from version 3 onwards.
FOSS Credits/Dependencies:
What: ZXing-CPP (Public copy of license)
Why: For the Take A Picture barcode detection and decoding portion of CCIDB.
What: amCharts Library (Public copy of license)
Why: For the collection heatmap portion of CCIDB, based on Numista's heatmapping system.
What: (The only proper) PDO tutorial
Why: For the PDO portion of CCIDB. PDO code in CCIDB heavily relies on this tutorial.
What: Tailwind CSS (Public copy of license)
Why: For the beautiful layout of the site. The basic design layout was made by Doomaholic in Tailwind, mentioned above.
What: PHPThumb Library (Public copy of license)
Why: For the thumbnail generation portion of both basic and advanced searches when displaying images. This prevents the results from "popping in" and saves a ton of data.
What: XDebug PECL Plugin (Public copy of license)
Why: For the constant, seemingly neverending debugging of CCIDB. Not implemented in the stable version, but still listed here.
I am very bad at writing in the third person, so here's a first person perspective about me, and about CCIDB. Most people call me Wags (or Wagwan), but Wags is what I personally like more, so you can refer to me as that. All you need to know about me is that I like crypto (as in cryptography, never cryptocurrency) puzzles and ARGs (Alternate Reality Games) and the like. I maintain a personal website which you can visit here. It's got things like puzzles, a blog, and some other, future content coming Soon™. But that's enough backstory, more about how CCIDB started and why you're here.
I started making CCIDB during the COVID-19 pandemic/lockdown(s), as a way of cataloging my existing coin collection which had gone undocumented and untouched for a number of years. CCIDB initially started as a single text file with a small PHP backend, but quickly took on a life of its own, with the introduction of an SQLite database and full front and backend made in a combination of PHP, JavaScript, HTML, and even some Python. PHP was chosen for its ease of learning and capabilities, despite its negative reputation within certain circles. This project was made solely in my free time, with no monetary support from any person or company, and took approximately 3 years to reach a "stable" status. While every effort is made to document where certain bits of code came from (mostly online sources like Stack Overflow), and what each bit of code does functionality wise, not everything is 100% covered at this point in time. Speaking of code, you can find a full list of other resources that I found useful beyond comparison when developing CCIDB below. This includes other software either partially or fully implemented in CCIDB in some way or another (also known as dependencies).
I would also like to give a MASSIVE thank you to a member of the DA Freqs Puzzling Team (which I am part of as well), Doomaholic, for designing the layout of CCIDB from version 3 onwards.
FOSS Credits/Dependencies:
What: ZXing-CPP (Public copy of license)
Why: For the Take A Picture barcode detection and decoding portion of CCIDB.
What: amCharts Library (Public copy of license)
Why: For the collection heatmap portion of CCIDB, based on Numista's heatmapping system.
What: (The only proper) PDO tutorial
Why: For the PDO portion of CCIDB. PDO code in CCIDB heavily relies on this tutorial.
What: Tailwind CSS (Public copy of license)
Why: For the beautiful layout of the site. The basic design layout was made by Doomaholic in Tailwind, mentioned above.
What: PHPThumb Library (Public copy of license)
Why: For the thumbnail generation portion of both basic and advanced searches when displaying images. This prevents the results from "popping in" and saves a ton of data.
What: XDebug PECL Plugin (Public copy of license)
Why: For the constant, seemingly neverending debugging of CCIDB. Not implemented in the stable version, but still listed here.