# simulator A broad categorization of video games, generally designed to closely simulate real world activities. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## EA is using genAI for commentator voiceover in NHL 27 DevFeed: [EA is using genAI for commentator voiceover in NHL 27]() Original publisher: [Read original article]() Author: Diego Argüello Published: 2026-09-10T17:18:45Z Content type: news Language: en Sources: [gamedeveloper]() Topics: [genai](), [Artificial Intelligence](), [Sports](), [simulator]() Tags: [ai](), [gaming](), [genai](), [simulator](), [sports]() ### AI overview EA says NHL 27 uses AI voice technology to expand commentary recordings made with John Buccigross and Darren Pang, with their consent and active collaboration. The article also reports earlier claims about the technology and notes that AI-generated lines can require correction. ### Source excerpt EA says it's using the tech to expand on recording sessions with John Buccigross and Darren Pang's 'full consent and active collaboration.' ## What to expect at the Zephyr Project Meetup (September 15, 2026) - Amsterdam, Netherlands DevFeed: [What to expect at the Zephyr Project Meetup (September 15, 2026) - Amsterdam, Netherlands]() Original publisher: [Read original article]() Author: Susan Remmert Published: 2026-09-09T05:00:04Z Content type: article Language: en Sources: [Zephyr Project]() Topics: [Zephyr RTOS](), [Embedded Systems](), [Open Source](), [Fuzzing/Fuzz testing](), [simulator](), [developer tooling]() Tags: [2026](), [blog](), [bugs](), [community](), [contributors](), [embedded](), [embedded-systems](), [event](), [events](), [firmware](), [fuzzing](), [harness](), [meetup](), [open-source](), [simulator](), [talk](), [technologies](), [tooling](), [tools](), [zephyr]() ### AI overview The Zephyr Project Meetup in Amsterdam on September 15, 2026, will bring together embedded developers, contributors, students, and engineers to exchange practical knowledge about Zephyr RTOS. The agenda includes talks on JetBrains' work with Zephyr, fuzzing Zephyr applications with AFL and Renode, and making hardware development easier with Schematik. ### Source excerpt What are developers in the Netherlands building with Zephyr? On September 15, the embedded community will meet in Amsterdam to exchange practical knowledge, discuss current work, and learn more about the Zephyr RTOS. The event is open to experienced contributors, first-time users, students, engineers, and anyone curious about open source embedded development. ## Warplanes & Prison Boss VR Are Quest's Horizon+ Monthly Games For September 2026 DevFeed: [Warplanes & Prison Boss VR Are Quest's Horizon+ Monthly Games For September 2026]() Original publisher: [Read original article]() Author: James Tocchio Published: 2026-09-01T22:07:40Z Content type: news Language: en Sources: [UploadVR]() Topics: [Meta](), [simulator](), [Flight]() Tags: [2026](), [aviation](), [games](), [meta](), [september-2026](), [simulator](), [subscription](), [vr-gaming]() ### AI overview Meta Horizon+ added Warplanes: Air Corp and Prison Boss VR as its September 2026 Monthly Games, along with seven titles across its Games and Indie Catalogs. ### Source excerpt From a modern combat flight game to a comedic prison gang simulator, here are Quest's Meta Horizon+ subscription monthly redeemable titles for September 2026. ## Mobile UI Testing with Claude Code, Cursor and Codex DevFeed: [Mobile UI Testing with Claude Code, Cursor and Codex]() Original publisher: [Read original article]() Author: Ashish Kharche Published: 2026-09-01T10:00:00Z Content type: tutorial Language: en Sources: [mobile.dev - Medium]() Topics: [Testing](), [Mobile](), [Model Context Protocol](), [Android](), [iOS](), [Emulator](), [simulator]() Tags: [agent](), [android](), [chromium](), [claude-code](), [cli](), [codex](), [cursor](), [emulator](), [ios](), [maestro](), [mcp](), [mobile](), [regression](), [simulator](), [testing](), [yaml]() ### AI overview This tutorial explains how Claude Code, Cursor, Codex, and other MCP-enabled coding agents can use Maestro MCP to explore mobile app interfaces on iOS Simulators, Android emulators, physical Android devices, and Chromium, then save the tested steps as reusable Flow files. The saved Flows can be rerun through an agent or the CLI, including in CI, to detect UI changes. ### Source excerpt Have Claude Code, Cursor or Codex run a UI test on an iOS Simulator or Android emulator, then save it as a Flow and run the same test again. ## Prison-Break Comedy Sandbox Bad Inmate Coming Soon To Quest & PlayStation VR2 DevFeed: [Prison-Break Comedy Sandbox Bad Inmate Coming Soon To Quest & PlayStation VR2]() Original publisher: [Read original article]() Author: James Tocchio Published: 2026-08-31T15:43:03Z Content type: news Language: en Sources: [UploadVR]() Topics: [simulator]() Tags: [games](), [physics](), [release](), [sandbox](), [simulator](), [vr-gaming]() ### AI overview HyperVR Games announced that Bad Inmate, a physics-driven comedic prison-break sandbox game, will launch for Meta Quest and PlayStation VR2 on October 15. A SteamVR release is planned, but its date has not been announced. ### Source excerpt The physics-driven comedic prison-break sandbox game is coming to Quest and PlayStation VR2 in October. ## SQLite Across Every Port: One Contract, One Encrypted File Format DevFeed: [SQLite Across Every Port: One Contract, One Encrypted File Format]() Original publisher: [Read original article]() Author: Shai Almog Published: 2026-08-21T00:00:00Z Content type: article Language: en Sources: [CodeName One]() Topics: [SQLite](), [Encryption](), [Android](), [iOS](), [JavaScript](), [Linux](), [simulator](), [Windows](), [tvOS](), [watchOS]() Tags: [android](), [encryption](), [ios](), [javascript](), [linux](), [simulator](), [sqlite](), [watchos](), [windows]() ### AI overview Codename One describes a unified, tested SQLite contract across its supported ports, replacing platform-dependent implementations. The update also supports encrypted database files that can move between ports and open in standard SQLCipher 4 clients, using passphrase, managed-key, or raw-key encryption. ### Source excerpt Codename One now runs the same tested SQLite contract across Android, iOS, JavaScript, Windows, Linux, watchOS, tvOS, and the simulator, with passphrase, managed-key, and raw-key encryption. ## Codename One's Cross-Platform Health API and Its Privacy Design DevFeed: [Codename One's Cross-Platform Health API and Its Privacy Design]() Original publisher: [Read original article]() Author: Shai Almog Published: 2026-08-01T00:00:00Z Content type: article Language: en Sources: [CodeName One]() Topics: [API](), [Android](), [iOS](), [Bluetooth](), [simulator](), [Testing]() Tags: [android](), [api](), [bluetooth](), [ios](), [privacy](), [sensor](), [simulator](), [testing]() ### AI overview This article examines Codename One's cross-platform health API for HealthKit, Health Connect, workouts, nutrition, Bluetooth health sensors, and deterministic simulation. It explains capability-based behavior, privacy-preserving permission handling, unit-aware samples, and cross-platform result normalization. ### Source excerpt A deep look at Codename One's HealthKit, Health Connect, workout, nutrition, Bluetooth sensor, and simulator API, including the privacy rules that shape its unusual design. ## Bluetooth Support Across Every Codename One Target DevFeed: [Bluetooth Support Across Every Codename One Target]() Original publisher: [Read original article]() Author: Shai Almog Published: 2026-07-26T00:00:00Z Content type: article Language: en Sources: [CodeName One]() Topics: [Bluetooth](), [API](), [simulator](), [Web](), [JavaScript]() Tags: [api](), [ble](), [bluetooth](), [browser](), [chrome](), [core](), [desktop](), [hardware](), [javascript](), [permission](), [platform](), [protocol](), [simulator](), [tests](), [web]() ### AI overview Codename One's core Bluetooth API adds cross-target support for BLE, GATT, L2CAP, classic RFCOMM, Web Bluetooth, and a scriptable simulator. The API exposes platform capabilities and limits, while the implementation handles queued GATT operations and callback timeouts. ### Source excerpt The core Bluetooth API covers BLE, GATT, L2CAP, classic RFCOMM, Web Bluetooth, and a scriptable simulator while exposing each platform's limits. ## On-Device Debugging And JUnit 5 DevFeed: [On-Device Debugging And JUnit 5]() Original publisher: [Read original article]() Author: Shai Almog Published: 2026-05-30T00:00:00Z Content type: tutorial Language: en Sources: [CodeName One]() Topics: [debugging](), [IntelliJ IDEA](), [Android](), [iOS](), [ide](), [simulator](), [Tooling](), [Code](), [Emulator](), [SDK](), [Visual Studio Code]() Tags: [android](), [android-apps](), [android-studio](), [apk](), [app](), [breakpoint](), [build](), [code](), [debugging](), [developer](), [emulator](), [ide](), [intellij](), [intellij-idea](), [ios](), [java](), [junit](), [linux](), [on-device](), [simulator]() ### AI overview This tutorial describes Codename One's new JDWP-based on-device debugging for ParparVM iOS and Android apps. It explains debugging Java code and objects on simulators and physical devices using IntelliJ IDEA or other JDWP-speaking debuggers, and briefly covers standard JUnit 5 integration with the JavaSE simulator. ### Source excerpt A walk-through of the new JDWP-based on-device debugging pipeline for ParparVM iOS apps and Android apps, with a step-by-step IntelliJ tutorial for each, and a short tutorial on the new standard JUnit 5 integration against the JavaSE simulator. ## Skills, Java 17, And Theme Accents DevFeed: [Skills, Java 17, And Theme Accents]() Original publisher: [Read original article]() Author: Shai Almog Published: 2026-05-15T00:00:00Z Content type: article Language: en Sources: [CodeName One]() Topics: [Java](), [AI Agent](), [simulator]() Tags: [agent](), [agents](), [java](), [simulator](), [skills]() ### AI overview Codename One now generates new projects with Java 17 as the default, while Java 8 remains selectable. Java 17 projects also include an AGENTS.md file and a Codename One authoring skill for AI agents. The article additionally covers a runtime accent palette for native themes, Metal updates, a JDK 11+ String API improvement, and delayed iOS push permission prompts. ### Source excerpt Java 17 is the new Initializr default, generated projects ship an AGENTS.md authoring skill that any AI agent can pick up (including a workflow that lets agents drivejdb against the simulator), native themes get a runtime accent palette, plus Metal follow-ups and iOS push that no longer prompts at launch. ## Codename One Adds Metal Rendering, Skin Designer, and iOS Diagnostics DevFeed: [Codename One Adds Metal Rendering, Skin Designer, and iOS Diagnostics]() Original publisher: [Read original article]() Author: Shai Almog Published: 2026-05-08T00:00:00Z Content type: article Language: en Sources: [CodeName One]() Topics: [iOS](), [browser](), [simulator](), [Open Source]() Tags: [browser](), [crash](), [image](), [ios](), [new-feature](), [open-source](), [simulator]() ### AI overview Codename One presents a new Metal rendering backend for iOS, a browser-hosted Skin Designer, an iOS Return-as-Done flag, status-bar tap diagnostics, and a simulator dark/light toggle. The article also explains how the project handles quality and discusses bugs in newly released behavior, including an iOS image API crash caused by oversized stack buffers in SIMD code. ### Source excerpt A new Metal rendering backend for iOS, a browser-hosted Skin Designer that retires the skin downloader, an iOS Reminders-style Return-as-Done flag, status-bar tap diagnostics, a simulator dark/light toggle, and a candid look at how we balance quality with the speed of a small open source company. Build hint to enable Metal:ios.metal=true -- the default flips within two weeks. ## Liquid Glass, Material 3, And A Lot Of Plumbing DevFeed: [Liquid Glass, Material 3, And A Lot Of Plumbing]() Original publisher: [Read original article]() Author: Shai Almog Published: 2026-05-01T00:00:00Z Content type: article Language: en Sources: [CodeName One]() Topics: [Android](), [iOS](), [liquid glass](), [cross-platform](), [simulator]() Tags: [android](), [cross-platform](), [improvements](), [ios](), [liquid-glass](), [native](), [performance](), [simulator]() ### AI overview Codename One introduces new iOS Modern and Android Material 3 native themes. The article explains their default use in the Playground, simulator selection, device ports, compatibility with older themes, and related performance and interface improvements. ### Source excerpt New iOS Modern (liquid glass) and Android Material 3 native themes, how they work in the Playground, in the simulator, and on devices, plus a week of performance and look-and-feel improvements including sticky headers. Cross-platform shortcut:nativeTheme=modern; finer control viaios.themeMode=modern andand.themeMode=modern. ## Compliance Improvements, Simulator Updates, and More DevFeed: [Compliance Improvements, Simulator Updates, and More]() Original publisher: [Read original article]() Author: Shai Almog Published: 2026-04-03T00:00:00Z Content type: release Language: en Sources: [CodeName One]() Topics: [Java](), [Java Language](), [Android](), [simulator](), [JavaScript]() Tags: [android](), [bug-fixes](), [compatibility](), [improvements](), [java-language](), [performance](), [proguard](), [updates]() ### AI overview This Codename One update removes Proguard from the build process and replaces it with a custom compliance validator. It also rewrites String.split() calls for consistent simulator and device behavior, expands runtime support, enables newer Java features to remain compatible with Android JDK 17, and updates simulator location support. ### Source excerpt In todays update were finally removing Proguard from the build process with many implications for all of us. ## Using Wokwi with NuttX DevFeed: [Using Wokwi with NuttX]() Original publisher: [Read original article]() Author: John Lee Published: 2024-11-12T23:08:20Z Content type: tutorial Language: en Sources: [Blog on Developer Portal]() Topics: [NuttX](), [simulator](), [Simulation](), [ESP32](), [qemu](), [RISC-V]() Tags: [alternatives](), [apache](), [blog](), [esp32](), [linux](), [nuttx](), [posix](), [qemu](), [real-time](), [risc-v](), [simulation](), [simulator](), [wokwi](), [xtensa]() ### AI overview A tutorial on using the NuttX real-time operating system with the Wokwi simulator. It explains Wokwi's advantages and limitations, compares it with QEMU, and describes compiling NuttX locally before simulating the output on supported ESP32 Xtensa- and RISC-V-based devices. ### Source excerpt In this article, we will examine how the NuttX real-time operating system (RTOS) can be used on the Wokwi simulator, what adjustments need to be made on the NuttX side for this and what advantages the Wokwi simulator offers. Note! Note: Reviewing this article together with NuttX on an emulated ESP32 using QEMU article will help the user to distinguish between the two solutions and to determine the most suitable solution for the needs. ## Accelerate iOS Development Using Deep Links DevFeed: [Accelerate iOS Development Using Deep Links]() Original publisher: [Read original article]() Author: Doximity Published: 2023-03-13T09:18:00Z Content type: tutorial Language: en Sources: [Doximity]() Topics: [Development](), [iOS](), [Mobile](), [simulator](), [App]() Tags: [debug](), [demo](), [guide](), [guides](), [how-to](), [ios-development](), [simulator](), [ui]() ### AI overview This tutorial explains how to use Alfred workflows to organize deep links and launch them on running iOS simulators. It uses Apple Maps Guides as an example and shows how the workflow can document deep links, select one, and choose a simulator. ### Source excerpt Do you work on a large app with lots of deep links and dynamic content? This article will show you how to manage and leverage those deep links so you can spend more time coding and less time navigating the app. Here on the News team at Doximity, we have lots of content to manage, including articles, comments, and collections of articles. The problem compounds when considering that articles have a lot of different variations, and some of those variations are uncommon. The variety can make it hard to test the entire app, and a real pain when trying to debug a problem on a specific piece of content. Fortunately, most of that content is accessible via a deep link with the correct IDs. Unfortunately, that often means keeping a list of links in a notes document or sending a link to yourself in Slack. It's even worse when using the simulator since you cannot access those tools easily. That's where Alfred comes in. Alfred is an application launcher and productivity application that includes a rich set of tools for creating custom workflows. An Alfred workflow can organize deep links and launch them on any running simulator. Let's use Apple Maps as an example, as it's available on all simulators and supports deep linking to Guides. (Provided by Apple, Guides are curated collections of related points of interest. They can be accessed with a deeplink in the format maps://?pg=). Apple Maps has many Guides with different combinations of features to test. Finding a particular guide using the in-app search can take a lot of time. The Alfred workflow becomes both documentation of the various guides and a fast way to navigate to them. In the demo below, a hotkey triggers the workflow. Note that the workflow prompts to select a simulator when there are multiple running. The Alfred workflow consists of 4 work performing steps and some glue. The image below shows the Alfred workflow (which can be downloaded at the bottom of this article). The green steps cover selecting the d ## Codename One Simulator Facelift DevFeed: [Codename One Simulator Facelift]() Original publisher: [Read original article]() Author: Steve Hannah Published: 2022-03-18T00:00:00Z Content type: article Language: en Sources: [CodeName One]() Topics: [simulator](), [ui](), [Maven](), [configuration](), [monitor](), [Tool]() Tags: [configuration](), [features](), [interface](), [monitor](), [new-features](), [simulator](), [toolbar](), [update](), [updates]() ### AI overview This article describes a Codename One simulator update delivered with Maven 7.0.61. The update consolidates the simulator, component inspector, network monitor, and other tools into one configurable window, with layouts and detached panels remembered between runs. It also moves some simulator controls to a new toolbar. ### Source excerpt With the latest Maven update (7.0.61), you will notice a few changes to the Codename One simulator that should improve your development experience. ## Silencing iOS simulator log noise DevFeed: [Silencing iOS simulator log noise]() Original publisher: [Read original article]() Author: Keith Smiley Published: 2021-11-17T02:00:00Z Content type: tutorial Language: en Sources: [Keith Smiley]() Topics: [iOS](), [simulator](), [configuration]() Tags: [commands](), [configuration](), [ios](), [logs](), [scheme](), [simulator](), [streaming]() ### AI overview This article explains how to reduce noisy iOS simulator logs without disabling os_log entirely. It recommends using log configuration commands to disable selected subsystems or categories and describes targeting either the booted simulator or a specific simulator UDID. ### Source excerpt When Apple transitioned to using os_log for system logs it seemed they also decided to open the floodgates for what logs were surfaced in our apps. This lead to a plethora of stackoverflow questions recommending you disable os_log entirely by setting OS_ACTIVITY_MODE=disable in your target's scheme. This is fine for some cases but might also silence some actually useful logs, or your own logs if you want to use os_log for its feature-set. os_log has a nice set of categorization for logs, for example when viewing streaming logs in Console.app you can show the process, subsystem, and category for each log. Perhaps ideally we could use an environment variable with more granular filtering based on this categorization, but that would likely get complex quickly. Instead we can update OS log's configuration to disable some specific types of logs. Here are a few examples I found useful for Lyft's iOS project: xcrun simctl spawn booted log config --subsystem com.apple.CoreBluetooth --mode level:off xcrun simctl spawn booted log config --subsystem com.apple.CoreTelephony --mode level:off xcrun simctl spawn booted log config --subsystem com.apple.network --category boringssl --mode level:off You can replace booted here with a specific iOS simulator UDID, which can be found by running xcrun simctl list devices. Since this is simulator specific, you will have to re-run whatever commands you decide on when you create new simulators. More options for the log command can be found with man log ## LLDB Reproducers DevFeed: [LLDB Reproducers]() Original publisher: [Read original article]() Author: Keith Smiley Published: 2020-09-30T02:39:00Z Content type: tutorial Language: en Sources: [Keith Smiley]() Topics: [debugging](), [Xcode](), [Swift](), [macOS](), [Terminal](), [Command-line interface](), [iOS](), [simulator](), [bug]() Tags: [apple](), [bug](), [cli](), [debugging](), [ios](), [macos](), [simulator](), [swift](), [terminal](), [xcode]() ### AI overview This article explains how LLDB reproducers capture debugging-session information so Swift developers can provide Apple with more useful and repeatable bug reports. It covers the limitation that launching LLDB from Xcode does not enable capture mode by default, privacy risks involving binaries and memory, and workflows for macOS programs and iOS apps running in the simulator. ### Source excerpt Swift developers love to complain about LLDB. While there are many reasonable complaints, the important question is what can we do to make it better. Enter reproducers. Reproducers provide a way to run LLDB while also capturing information about your debugging session. With this information you can submit a more useful bug report to Apple with a reliable reproduction case. How? Although the steps to use reproducers are mostly straightforward, launching LLDB from Xcode does not enable --capture mode (FB7878562). This means if you want to provide a reproducer for an issue you've experienced in a Xcode debugging session, you need to reproduce it outside of Xcode instead. Update: the folks from PSPDFKit pointed out as of Xcode 12 there is a private default for enabling capture mode for debugging sessions launched from Xcode: defaults write com.apple.dt.Xcode IDEDebuggerEnableReproducerCapture -bool YES Note: to provide enough information to reproduce your issue, LLDB bundles all files the debugging session touched. This includes binaries with debug info that you may consider sensitive. As pointed out on Twitter this will also contain anything in memory at the time of capture. Be sure to verify what you're sharing with Apple before you send it. CLI / macOS app If you're debugging a program on your Mac, there are a few steps: Run the app in Xcode and stop it. This way you know the binary is up to date. In Terminal.app navigate to your DerivedData directory (you can find this by right clicking on your app in the "Products" section of Xcode's project navigator, and clicking "Show in Finder"). Run lldb --capture /path/to/Your.app. In the LLDB session run process launch --stop-at-entry. Now you're in a paused LLDB session. Here you can set the breakpoints you need to reproduce your issue. Often for me this means breaking at a specific place, and running some version of po foo that causes an issue. Once you're done reproducing the issue, run reproducer generate in LLDB. This w ## Codename One Adds Optional CEF Support to Its Simulator and Changes JavaFX Installation DevFeed: [Codename One Adds Optional CEF Support to Its Simulator and Changes JavaFX Installation]() Original publisher: [Read original article]() Author: Shai Almog Published: 2020-07-16T00:00:00Z Content type: release Language: en Sources: [CodeName One]() Topics: [Chromium](), [WebRTC](), [JavaFX](), [simulator](), [debug]() Tags: [chromium](), [debug](), [open](), [webrtc]() ### AI overview Codename One released support for CEF in its simulator. CEF is off by default during the transition, while JavaFX will no longer install automatically when missing; applications that depend on media or web features may encounter simulator or debugger problems. The article recommends ZuluFX as a short-term workaround and explains that CEF enables Chromium-based browser features including WebRTC. ### Source excerpt Today we released one of the biggest changes to Codename One's simulator in ages. We added the ability to use CEF (Chrome Embedding Framework). This is currently off by default but even if you don't use it you might feel the impact so it's crucial that you read this post. __ Updated July 31st with additional platform instructions below __ Updated August 2nd with correction to the Linux install script __ Updated August 4th with another correction to the Linux install script The TL;DR The big change for those of you who don't care about the details is this: FX will no longer install automatically if it's missing. That might be a good thing for some applications. But if you rely on media/web things might break in the simulator/debugger. ## Runtime Debugging with Groovy Console DevFeed: [Runtime Debugging with Groovy Console]() Original publisher: [Read original article]() Author: Steve Hannah Published: 2019-11-04T00:00:00Z Content type: tutorial Language: en Sources: [CodeName One]() Topics: [Groovy](), [debugging](), [Tool](), [simulator](), [ui]() Tags: [code](), [debugging](), [dialog](), [groovy](), [programming-language](), [simulator](), [tool](), [ui]() ### AI overview The article introduces a Groovy Console in the Codename One simulator for running code snippets in an app's runtime environment. It demonstrates inspecting the current form, displaying dialogs, and using ComponentSelector to inspect component properties and state. ### Source excerpt We recently added a new tool to the Codename One simulator that will allow you to run arbitrary code snippets in your app's runtime environment. You can access it from "File" > "Groovy Console", while your app is running in the simulator. This will open the following dialog that will allow you to execute arbitrary Groovy code: As you may suspect, you should use the Groovy programming language in this console. If you're not familiar with Groovy, don't worry. The language is basically just Java with some nice short-cuts. In fact, in many cases, you can probably just write Java code, and it will still work. Personally, I like the way that Groovy lets you refer to object properties via their property name, so you don't need to use the getter or setter methods explicitly. E.g. You can do "form.title", instead of "form.getTitle()", to get the form's title. The former is converted into the latter automatically for you. ## Announcing the Firestore Security Rules Simulator! DevFeed: [Announcing the Firestore Security Rules Simulator!]() Original publisher: [Read original article]() Author: Sam Horlbeck Olsen Published: 2018-06-20T00:00:00Z Content type: release Language: en Sources: [Firebase Blog]() Topics: [Firestore](), [Security](), [Access Control](), [simulator](), [Documentation]() Tags: [access-control](), [authentication](), [documentation](), [firebase](), [firestore](), [launch](), [news](), [release](), [security](), [security-rules](), [simulator](), [testing](), [updates]() ### AI overview Firebase announces the Firestore Security Rules Simulator, which lets developers test reads, writes, and deletes, simulate authenticated users, and preview authentication tokens before deploying rules. The update also raises document access-call limits and improves reference documentation. ### Source excerpt News, tutorials, and updates from the Firebase team. ## Meltdown and Spectre Server Updates and Codename One Feature Updates DevFeed: [Meltdown and Spectre Server Updates and Codename One Feature Updates]() Original publisher: [Read original article]() Author: Shai Almog Published: 2018-01-16T00:00:00Z Content type: article Language: en Sources: [CodeName One]() Topics: [Vulnerabilities](), [Server](), [IO](), [Objective-C](), [Java](), [iOS](), [Barcode](), [QR Code](), [simulator](), [API]() Tags: [announcement](), [api](), [blog](), [io](), [ios](), [java](), [objective-c](), [qr-code](), [servers](), [simulator](), [updates](), [vulnerabilities]() ### AI overview The post announces server updates in response to the Meltdown and Spectre chip vulnerabilities, with possible short-term downtime and limited expected impact on build speed because IO, rather than CPU speed, is the main bottleneck. It also mentions new Codename One libraries for Objective-C interoperability and Scandit barcode and QR code scanning, plus a push notification simulator feature. ### Source excerpt I've been so busy I just don't have time to blog as much as I should. I do hope next month will be better in this regard (more on that below) but right now I have to make an important announcement. There are new chip vulnerabilities I'm sure you heard a lot about specifically Meltdown & Spectre. Thankfully we are at a layer that shouldn't be impacted by these issues but we need to update our servers and will be doing so over the course of the next few days (possibly more as patches get updated). ## Clone and Run Codename One Demos In Single Line of Code DevFeed: [Clone and Run Codename One Demos In Single Line of Code]() Original publisher: [Read original article]() Author: Steve Hannah Published: 2017-11-27T00:00:00Z Content type: tutorial Language: en Sources: [CodeName One]() Topics: [Command-line interface](), [Demo](), [simulator](), [Code](), [Tool](), [GitHub]() Tags: [cli](), [code](), [command-line](), [demo](), [github](), [simulator](), [tool]() ### AI overview A tutorial showing how to use the Codename One CLI to clone Codename One demo projects from GitHub, download their dependencies, run them in the Codename One simulator, search for tagged demos, and add projects to the searchable demo list. ### Source excerpt We have loads of demo Codename One apps hosted on Github, however cloning and running a project can be a little tricky because we generally don't publish the dependent jar files (e.g. CodenameOne.jar) in the Github repository. This helps keep the repository lean, but it adds some steps to the process of cloning and running the project. For use cases like this, you may want to try the Codename One CLI tool, as it provides many useful functions directly on the command line. In this post I'll demonstrate how you can easily clone a Codename One project from Github and run it in the Codename One simulator using a single line of code. ## Always on Top and Style Parser DevFeed: [Always on Top and Style Parser]() Original publisher: [Read original article]() Author: Shai Almog Published: 2017-09-24T00:00:00Z Content type: article Language: en Sources: [CodeName One]() Topics: [simulator](), [GUI](), [ui](), [CSS]() Tags: [css](), [debugging](), [gui](), [issue-tracker](), [new-feature](), [release](), [simulator](), [ui]() ### AI overview The article discusses Codename One 3.7.3, including an always-on-top simulator feature and a built-in string-based style parser for customizing component styles in the GUI builder. It distinguishes this style mode from the CSS plugin and notes that the new feature may have issues in the 3.7.3 release. ### Source excerpt It's been a busy week with 3.7.3 released and a lot of new things. Diamond made several PR's over the past couple of weeks but one interesting PR is an "always on top" feature for the simulator which is exactly what it sounds... This is very useful for me personally as it will allow me to film coding while showing the simulator floating on top (thanks Diamond!) but it should be super useful for everyone. You can inspect the code/debugging values while the simulator floats on top. You can activate it using the simulator menu option. [Next page]()