A Brief Summary
- Link to PR in PAPPL, which starts the scan journey by integrating PAPPL for Scanners.
- Link to MetaScan repository, which comprises the ScaniVerse.
- Link to SaneScanner-PapplRetrofit repository, the retrofit implementation for scanning drivers.
What are we waiting for? Let's dive into the dream!
Unveiling the Enigma: Sand-Boxed Scanner Application Framework ๐ญ
In the ever-evolving landscape of technology, an immense void has been begging for attention โ scanning devices. While printers, our desktop buddies, have soared into the future, the scanners often felt left in the past. However, with the Sand-Boxed Scanner Application Framework, the tides are turning.
Genesis of the Idea ๐ก
The mission of this project was straightforward: enable devices without driverless scanning capabilities to masquerade as driverless wonders using PAPPL's Scanner Application Framework. Beyond mere emulation, this application also sets the stage for a new generation of sandboxed Scanner Applications.
Community Bonding & the Code Dive ๐ค๐
The adventure began with a thorough exploration of the PAPPL codebase, which felt like deciphering an ancient script where each line told a story. Fortunately, the code's API can be better understood through this documentation. Initial documentation changes were made using CodeDoc.
The PAPPL Blueprint ๐บ๏ธ
As evident, the essence of PAPPL was clearly aligned with printers. My challenge? To weave together the stories of printers and scanners, particularly for multifunctional devices.
Chiseling the Sculpture ๐ ๏ธ
The foundation stone was laid by sketching the architecture of multifunction device scanning.
Client's Odyssey ๐งญ
Server's Dance ๐ป
I adopted the MOPRIA Scan Specifications, initiating a series of requests and responses. Most of these interactions were in the eSCL format, encompassing areas such as Scan Capabilities, Scanner Status, Scan Jobs, URI Generation, and Document Retrieval.
To make this work, I had to carefully design data structures. This involved translating XML and making sure the information flowed smoothly to and from the scanner drivers.
Mimicking the Scanner: The Dummy Driver โจ
To test the waters, a facsimile of the scanner driver was created. From capturing the request format to simulating the , it was all about shadowing the scanner every move.
The work on the above can be checked here.
Bridging the Old and New ๐
While the first phase above laid the foundation, the sequel was about blending SANE (Scanner Access Now Easy) into our potion. With PAPPL-RETROFIT acting as the crucible, the old met the new, with SANE API's magic dust sprinkled generously. But the enchantment doesnโt end here; it's an ongoing saga. Dive into the SANE implementation here.
The Path Ahead: Uncharted Territories ๐ค๏ธ
While we have set the stage and choreographed the initial dance, the performance is far from over. Here's a glance at what lies on the horizon:
Compatibility Checkpoints: Testing is the mirror that reflects an application's true potential. Testing the system with multiple scan clients is currently on the to-do list, ensuring the smooth waltz of every byte and bit.
Merging of Realms: At present, the pappl-retrofit application stands in its own independent domain. However, in the near future, it is set to merge with the main PAPPL retrofit repository, bringing together the old and new worlds.
Dreaming Beyond the Horizon: ScaniVerse ๐
During this journey, an epiphany struck. Why restrict ourselves to mere scanning? Why not a universe โ a Scaniverse! A cosmos where scanning coalesces with metadata archival, creating a self-contained realm. Dive into this expansive universe, here. And if curiosity still tugs at your heartstrings, join me as I unfold the ScaniVerse tale at the Ubuntu Summit 2023 in Riga. Explore more about my talk.
A Bow to the Maestros ๐
My gratitude to the guiding stars on this journey - Till Kamppeter, Aveek Basu, Rishabh Maheshwari, and Deepak Patankar.
A symphony of appreciation is dedicated to Till Kamppeter. Without his baton orchestrating the path, this musical journey through code would have been silent.