Urgent.News

What's breaking now, across thousands of outlets.

Tech

CodeScanner.scan(): Barcode Scanning Without Rebuilding the Camera Pipeline

The new vision analyzers could read barcodes, faces, poses, text, documents, and segmentation masks. Scanning one QR code still meant opening a camera, configuring a session, listening for frames, converting each frame, feeding a pipeline, moving the result to the event thread, and restoring the previous form. What is Codename One? Codename One is an open-source framework for building native iOS,…

Codename One, an open-source framework, facilitates building native applications across multiple platforms using a single codebase. The latest update introduces VisionCameraView, a component that manages camera access and analysis results, eliminating the need for developers to rebuild the camera pipeline for each feature. Scanning a QR code now requires just one call to CodeScanner.scan(), which handles the entire process, from opening the scanner form to returning the first accepted code.

This streamlined approach simplifies barcode scanning and other image analysis tasks like face detection, pose recognition, and text extraction without requiring developers to manually configure the camera, session, frame conversion, or event thread. Developers can now customize the scanner screen's text and accepted formats using CodeScannerOptions, and set restrictions to prevent incorrect code scans.

VisionCameraView automatically handles camera opening, frame management, result delivery, and camera release, while the analyzer remains caller-constructed to ensure efficient resource management. Results are represented by predefined types like BarcodeFormat, FaceLandmarks, and PoseLandmarks, making it easier for developers to integrate the analyzer's output into their applications.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

Two Actors, one agent, and the three ways my chain broke

A client asked a question that sounds simple: which sellers on the marketplaces are risky to buy from? Answering it takes two steps.

  • Two actors processed different task parts, but agent failed to connect them properly
  • First actor scraped sellers with tax ID, legal name, store URL; second actor calculated risk scores
  • Data format mismatch, empty strings as input caused incorrect risk scores and chain failure

Revisiting Joel's Test - exe.dev blog

  • Joel Spolsky's 12-step test remains relevant despite tech advancements
  • Shelley Test replaces human code review with LLM adversarial reviews
  • Athena agentic bot supervises continuous deployments and logs

More from Wednesday 2 September →