jsbeeb 1.1.1 → 1.3.3

package/.idea/jsLinters/jshint.xml

@@ -1,85 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<project version="4">
-  <component name="JSHintConfiguration" version="2.10.2" use-config-file="true">
-    <option asi="false" />
-    <option bitwise="false" />
-    <option boss="false" />
-    <option browser="true" />
-    <option browserify="false" />
-    <option camelcase="false" />
-    <option couch="false" />
-    <option curly="false" />
-    <option debug="false" />
-    <option devel="false" />
-    <option dojo="false" />
-    <option elision="false" />
-    <option enforceall="false" />
-    <option eqeqeq="true" />
-    <option eqnull="false" />
-    <option es3="false" />
-    <option es5="false" />
-    <option esnext="false" />
-    <option evil="false" />
-    <option expr="false" />
-    <option forin="true" />
-    <option freeze="false" />
-    <option funcscope="false" />
-    <option futurehostile="false" />
-    <option gcl="false" />
-    <option globalstrict="false" />
-    <option immed="false" />
-    <option iterator="false" />
-    <option jasmine="false" />
-    <option jquery="false" />
-    <option lastsemic="false" />
-    <option latedef="false" />
-    <option laxbreak="false" />
-    <option laxcomma="false" />
-    <option loopfunc="false" />
-    <option maxerr="50" />
-    <option mocha="false" />
-    <option module="false" />
-    <option mootools="false" />
-    <option moz="false" />
-    <option multistr="false" />
-    <option newcap="false" />
-    <option noarg="true" />
-    <option nocomma="false" />
-    <option node="false" />
-    <option noempty="true" />
-    <option nomen="false" />
-    <option nonbsp="false" />
-    <option nonew="true" />
-    <option nonstandard="false" />
-    <option notypeof="false" />
-    <option noyield="false" />
-    <option onevar="false" />
-    <option passfail="false" />
-    <option phantom="false" />
-    <option plusplus="false" />
-    <option proto="false" />
-    <option prototypejs="false" />
-    <option qunit="false" />
-    <option quotmark="false" />
-    <option rhino="false" />
-    <option scripturl="false" />
-    <option shadow="false" />
-    <option shelljs="false" />
-    <option singleGroups="false" />
-    <option smarttabs="false" />
-    <option strict="true" />
-    <option sub="false" />
-    <option supernew="false" />
-    <option trailing="false" />
-    <option typed="false" />
-    <option undef="true" />
-    <option unused="false" />
-    <option validthis="false" />
-    <option varstmt="false" />
-    <option white="false" />
-    <option withstmt="false" />
-    <option worker="false" />
-    <option wsh="false" />
-    <option yui="false" />
-  </component>
-</project>

package/.idea/jsLinters/jslint.xml

@@ -1,15 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<project version="4">
-  <component name="JSLintConfiguration">
-    <option bitwise="true" />
-    <option browser="true" />
-    <option devel="true" />
-    <option indent="4" />
-    <option maxerr="50" />
-    <option maxlen="100" />
-    <option node="true" />
-    <option plusplus="true" />
-    <option predef="window,Uint8Array,Uint16Array,Uint32Array,Int8Array,Int16Array,Int32Array,define" />
-    <option vars="true" />
-  </component>
-</project>

package/.idea/jsbeeb.iml

@@ -1,11 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<module type="WEB_MODULE" version="4">
-  <component name="NewModuleRootManager">
-    <content url="file://$MODULE_DIR$">
-      <sourceFolder url="file://$MODULE_DIR$/tests" isTestSource="true" />
-      <excludeFolder url="file://$MODULE_DIR$/out" />
-    </content>
-    <orderEntry type="inheritedJdk" />
-    <orderEntry type="sourceFolder" forTests="false" />
-  </component>
-</module>

package/.idea/misc.xml

@@ -1,6 +0,0 @@
-<project version="4">
-  <component name="JavaScriptSettings">
-    <option name="languageLevel" value="ES6" />
-  </component>
-  <component name="ProjectRootManager" version="2" languageLevel="JDK_1_3" default="false" project-jdk-name="Python 3.6 (compiler-explorer-image)" project-jdk-type="Python SDK" />
-</project>

package/.idea/modules.xml

@@ -1,8 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<project version="4">
-  <component name="ProjectModuleManager">
-    <modules>
-      <module fileurl="file://$PROJECT_DIR$/.idea/jsbeeb.iml" filepath="$PROJECT_DIR$/.idea/jsbeeb.iml" />
-    </modules>
-  </component>
-</project>

package/.idea/prettier.xml

@@ -1,7 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<project version="4">
-  <component name="PrettierConfiguration">
-    <option name="myConfigurationMode" value="AUTOMATIC" />
-    <option name="myRunOnSave" value="true" />
-  </component>
-</project>

package/.idea/runConfigurations/Debug.xml

@@ -1,5 +0,0 @@
-<component name="ProjectRunConfigurationManager">
-  <configuration default="false" name="Debug" type="JavascriptDebugType" uri="http://localhost:5173/" useFirstLineBreakpoints="true">
-    <method v="2" />
-  </configuration>
-</component>

package/.idea/scopes/scope_settings.xml

@@ -1,5 +0,0 @@
-<component name="DependencyValidationManager">
-  <state>
-    <option name="SKIP_IMPORT_STATEMENTS" value="false" />
-  </state>
-</component>

package/.idea/vcs.xml

@@ -1,8 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<project version="4">
-  <component name="VcsDirectoryMappings">
-    <mapping directory="$PROJECT_DIR$" vcs="Git" />
-    <mapping directory="$PROJECT_DIR$/tests/6502_65C02_functional_tests" vcs="Git" />
-    <mapping directory="$PROJECT_DIR$/tests/integration/dp111_6502Timing" vcs="Git" />
-  </component>
-</project>

package/.prettierignore

@@ -1,4 +0,0 @@
-dist
-tests/6502_65C02_functional_tests
-tests/integration/dp111_6502Timing
-package-lock.json

package/.prettierrc.json

@@ -1 +0,0 @@
-{}

package/.release-please-manifest.json

@@ -1,3 +0,0 @@
-{
-  ".": "1.1.1"
-}

package/.vscode/launch.json

@@ -1,14 +0,0 @@
-{
-  "version": "0.2.0",
-  "configurations": [
-    {
-      "type": "chrome",
-      "request": "launch",
-      "name": "Debug a running dev server",
-      "url": "http://localhost:8080?logFdcStateChanges&logFdcCommands&model=MasterADFS&disc=CodenameDroid-ADFS_E.adf",
-      "webRoot": "${workspaceFolder}",
-      "sourceMaps": true,
-      "trace": true
-    }
-  ]
-}

package/.vscode/settings.json

@@ -1,6 +0,0 @@
-{
-  "editor.defaultFormatter": "esbenp.prettier-vscode",
-  "[javascript]": {
-    "editor.defaultFormatter": "esbenp.prettier-vscode"
-  }
-}

package/CHANGELOG.md

@@ -1,32 +0,0 @@
-# Changelog
-
-## [1.1.1](https://github.com/mattgodbolt/jsbeeb/compare/v1.1.0...v1.1.1) (2025-11-21)
-
-
-### Bug Fixes
-
-* Fix Windows Build support ([8ffa1a0](https://github.com/mattgodbolt/jsbeeb/commit/8ffa1a037fdfd7e38e072dca65da5b1959823fb2))
-
-## [1.1.0](https://github.com/mattgodbolt/jsbeeb/compare/v1.0.1...v1.1.0) (2025-11-21)
-
-
-### Features
-
-* Windows Electron build support ([1955a5f](https://github.com/mattgodbolt/jsbeeb/commit/1955a5f3ad7e9eb12cdff2e9860d8b0e304196ee))
-
-## [1.0.1](https://github.com/mattgodbolt/jsbeeb/compare/v1.0.0...v1.0.1) (2025-11-20)
-
-
-### Bug Fixes
-
-* Trying to get release-please to work
-
-## 1.0.0 (2025-11-20)
-
-First actual release with a changelog! These fixes below are not the only thing in this release, we previously had v0.0.7 which was 4+ years old. But - this include Electron support again!
-
-### Bug Fixes
-
-- add application icon for Electron ([#536](https://github.com/mattgodbolt/jsbeeb/issues/536)) ([64c8043](https://github.com/mattgodbolt/jsbeeb/commit/64c80438bf7c0f87db993b9a878665e3d3b090bc))
-- enable window scaling in Electron and modernize event handlers ([#533](https://github.com/mattgodbolt/jsbeeb/issues/533)) ([64551c9](https://github.com/mattgodbolt/jsbeeb/commit/64551c9d53c3a1a253dd1ac8f6b0f9dd9f266272))
-- remove invalid package-name parameter from release-please action ([#535](https://github.com/mattgodbolt/jsbeeb/issues/535)) ([5dd0436](https://github.com/mattgodbolt/jsbeeb/commit/5dd043601282e1aae976a8cd58c2071bd2b15954))

package/CLAUDE.md

@@ -1,136 +0,0 @@
-# CLAUDE.md
-
-This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
-
-## Build and Test Commands
-
-- `npm start` - Start development server (IMPORTANT: Never run this command directly; ask the user to start the server
-  as needed)
-- `npm run build` - Build production version
-- `npm run lint` - Run ESLint
-- `npm run lint-fix` - Run ESLint with auto-fix
-- `npm run format` - Run Prettier
-- `npm run test` - Run all tests
-- `npm run test:unit` - Run unit tests
-- `npm run test:integration` - Run integration tests
-- `npm run test:cpu` - Run CPU compatibility tests
-- `npm run ci-checks` - Run linting checks for CI
-- `vitest run tests/unit/test-gzip.js` - Run a single test file
-
-### Code Coverage
-
-- `npm run coverage:unit` - Run unit tests with coverage
-- `npm run coverage:all-tests` - Run all tests with coverage
-- Coverage reports are generated in the `coverage` directory
-- HTML report includes line-by-line coverage visualization
-
-## Code Style Guidelines
-
-- **Formatting**: Uses Prettier, configured in package.json
-- **Linting**: ESLint with eslint-config-prettier integration
-- **Modules**: ES modules with import/export syntax (type: "module")
-- **JavaScript Target**: ES2020 with strict null checks
-- **Error Handling**: Use try/catch with explicit error messages that provide context about what failed
-- **Naming**: camelCase for variables and functions, PascalCase for classes
-- **Imports**: Group by source (internal/external) with proper separation
-- **Documentation**: Use JSDoc for public APIs and complex functions, add comments for non-obvious code
-- **Error Messages**: Use consistent, specific error messages (e.g., "Track buffer overflow" instead of "Overflow in disc building")
-
-## Test Organization
-
-- **Test Consolidation**: All tests for a specific component should be consolidated in a single test file.
-  For example, all tests for `emulator.js` should be in `test-emulator.js` - do not create separate test files
-  for different aspects of the same component.
-- **Test Structure**: Use nested describe blocks to organize tests by component features
-- **Test Isolation**: When mocking components in tests, use `vi.spyOn()` with `vi.restoreAllMocks()` in
-  `afterEach` hooks rather than global `vi.mock()` to prevent memory leaks and test pollution
-- **Memory Management**: Avoid global mocks that can leak between tests and accumulate memory usage over time
-- **Test philosophy**
-  - Mock as little as possible: Try and rephrase code not to require it.
-  - Try not to rely on internal state: don't manipulate objects' inner state in tests
-  - Use idiomatic vitest assertions (expect/toBe/toEqual) instead of node assert
-
-## Project-Specific Knowledge
-
-- **Never commit code unless asked**: Very often we'll work on code and iterate. After you think it's complete, let me
-  check it before you commit.
-
-### Code Architecture
-
-- **General Principles**:
-  - Follow the existing code style and structure
-  - Use `const` and `let` instead of `var`
-  - Avoid global variables; use module scope
-  - Use arrow functions for callbacks
-  - Prefer template literals over string concatenation
-  - Use destructuring for objects and arrays when appropriate
-  - Use async/await for asynchronous code instead of callbacks or promises
-  - Minimise special case handling - prefer explicit over implicit behaviour
-  - Consider adding tests first before implementing features
-- **When simplifying existing code**
-  - Prefer helper functions for repetitive operations (like the `appendParam` function)
-  - Remove unnecessary type checking where types are expected to be correct
-  - Replace complex conditionals with more readable alternatives when possible
-  - Ensure simplifications don't break existing behavior or assumptions
-  - Try and modernise the code to use ES6+ features where possible
-
-- Prefer helper functions for repetitive operations (like the `appendParam` function)
-- Remove unnecessary type checking where types are expected to be correct
-- Replace complex conditionals with more readable alternatives when possible
-- Ensure simplifications don't break existing behavior or assumptions
-
-- **Constants and Magic Numbers**:
-  - Local un-exported properties should be used for shared constants
-  - Local constants should be used for temporary values
-  - Always use named constants instead of magic numbers in code
-  - Use PascalCase for module-level constants (e.g., `const MaxHfeTrackPulses = 3132;`)
-  - Prefer module-level constants over function-local constants for shared values
-  - Define constants at the beginning of functions or at the class/module level as appropriate
-  - Add comments explaining what the constant represents, especially for non-obvious values
-
-- **Pre-commit Hooks**:
-  - The project uses lint-staged with ESLint
-  - Watch for unused variables and ensure proper error handling
-  - YOU MUST NEVER bypass git commit hooks on checkins. This leads to failures in CI later on
-
-### Git Workflow
-
-- When creating branches with Claude, use the `claude/` prefix (e.g., `claude/fix-esm-import-error`)
-
-### Conventional Commits
-
-This project uses [Conventional Commits](https://www.conventionalcommits.org/) for automated versioning and changelog generation via release-please.
-
-**Commit types for user-facing changes** (appear in changelog, affect version):
-
-- `fix:` - Bug fixes (bumps patch version: 0.0.7 → 0.0.8)
-- `feat:` - New features (bumps minor version: 0.0.7 → 0.1.0)
-- `fix!:` or `feat!:` - Breaking changes (bumps major version: 0.0.7 → 1.0.0)
-
-**Commit types for internal changes** (do NOT appear in changelog, do NOT affect version):
-
-- `chore:` - Maintenance tasks, tooling updates, dependency updates
-- `ci:` - CI/CD configuration changes (GitHub Actions, etc.)
-- `build:` - Build system changes (webpack, vite, electron-builder config)
-- `docs:` - Documentation-only changes
-- `style:` - Code style changes (formatting, whitespace)
-- `refactor:` - Code refactoring without behavior change
-- `test:` - Test additions or modifications
-
-**Guidelines**:
-
-- Use `fix:` and `feat:` ONLY for changes that affect end users
-- Use `chore:`, `ci:`, or `build:` for internal tooling/infrastructure changes
-- Example: A release-please workflow fix should be `ci:` or `chore:`, not `fix:`
-- Breaking changes must include `BREAKING CHANGE:` in the commit body or use `!` (e.g., `feat!:`)
-
-**Examples**:
-
-```
-fix: enable window scaling in Electron app
-feat: add joystick support for gamepads
-chore: update dependencies to latest versions
-ci: fix release-please workflow configuration
-build: configure electron-builder icon settings
-docs: update README with installation instructions
-```

package/Dockerfile

@@ -1,22 +0,0 @@
-# NOTE: We create a temporary Docker container to build the webapp in, then copy
-# the generated distributable files to the final Docker image. This keeps the
-# final image tidy (since it doesn't contain any generated temporary artifacts),
-# and its size to a minimum.
-# NOTE: The version of Node must be kept in sync with what's in package.json.
-FROM node:22-alpine AS build
-
-# build the webapp
-WORKDIR /app/
-COPY package.json .
-RUN npm install
-COPY . .
-RUN npm run build
-
-# create the final Docker image
-# NOTE: The webapp is just a bunch of static files, so all we need is something to serve them.
-FROM nginx:1.27-alpine
-COPY docker/nginx-default.conf /etc/nginx/conf.d/default.conf
-COPY --from=build /app/dist /app
-
-EXPOSE 80
-CMD [ "nginx", "-g", "daemon off;" ]

package/Makefile

@@ -1,30 +0,0 @@
-NPM_UP_TO_DATE:=.npm-up-to-date
-NODE=node
-NPM=npm
-
-.PHONY: all
-all: test
-
-npm: $(NPM_UP_TO_DATE)
-
-.PHONY: npm
-test: npm
-	$(NPM) test
-
-$(NPM_UP_TO_DATE): package.json
-	$(NPM) install
-	touch $(NPM_UP_TO_DATE)
-
-HASH := $(shell git rev-parse HEAD)
-
-.PHONY: dist
-dist: npm
-	npm run build
-
-.PHONY: clean
-clean:
-	@rm -rf dist out
-
-.PHONY: spotless
-spotless: clean
-	@rm -f $(NPM_UP_TO_DATE)

package/docker/nginx-default.conf

@@ -1,10 +0,0 @@
-server {
-
-    server_name localhost ;
-    listen 80 ;
-
-    location / {
-        root /app ;
-    }
-
-}

package/docs/pal-comb-filter-research.md

@@ -1,129 +0,0 @@
-# Authentic PAL TV Comb Filter Research
-
-## Sources
-
-1. **Watkinson "Engineer's Guide to Decoding & Encoding"** (pages 37-39)
-2. **Jim Easterbrook PAL Decoder Page** (https://www.jim-easterbrook.me.uk/pal/)
-3. **Web search**: PAL television patents and implementations from 1980s
-
-## What Real PAL TVs Used
-
-### 2H Delay Line Comb Filters
-
-**Implementation:**
-
-- Used "64 microsecond quartz delay line" (2 line periods for PAL)
-- Delays of **2H** (two horizontal line periods) for PAL
-- Contrast with NTSC which uses 1H delays
-
-**Why 2H for PAL?**
-
-- PAL subcarrier: 283.75 cycles per line (fractional 0.75)
-- 2H spacing = 1.5 cycles = 540° = **180° phase shift** (mod 360°)
-- This ensures chroma signals are in opposite phase and cancel when added
-- V-switch state is SAME on lines N and N±2 (both inverted or both non-inverted)
-
-**From Watkinson (page 38):**
-
-> "The delays needed are of one line period [for NTSC]. The configuration for PAL is shown in b) in which the delays need to be of two line periods."
-
-### Complementary Decoder Approach
-
-**From Jim Easterbrook:**
-
-> "Some form of filter is used to extract the modulated chrominance from a PAL signal. Subtracting this chrominance from a suitably delayed PAL signal then yields luminance"
-
-This is the **complementary decoder** principle:
-
-1. Extract chroma from composite using a filter
-2. Subtract extracted chroma from **delayed** composite to get luma
-3. The decoder is "complementary" because chroma + luma = original PAL signal
-
-**Important Note:**
-
-> "Decoders like this are not widely used, as better subjective results can be obtained by using separate filters for chrominance and luminance, each optimised to give the best looking signals."
-
-**This explains our findings!**
-
-- Notch filter (complementary approach) is simpler but not what most TVs used
-- Real TVs used separate optimized filters for chroma and luma
-
-### Simple Line Comb for Luma (Most Common Approach)
-
-**From Watkinson Figure 3.4.2b:**
-
-- PAL comb uses 2H delays
-- **Simple averaging:** Add current line + line delayed by 2H
-- This is a LOWPASS filter for luma
-- Chroma cancels due to 180° phase inversion
-- Luma adds (in phase)
-
-**Coefficients:**
-
-- Simplest form: `luma = 0.5 * current + 0.5 * delayed_2H`
-- 3-tap variation: `luma = 0.25 * prev_2H + 0.5 * current + 0.25 * next_2H`
-
-### Tradeoffs and Limitations
-
-**From Watkinson (page 38-39):**
-
-> "Quite a lot of vertical luminance resolution is being lost, and becoming cross luminance, particularly in PAL."
-
-**The fundamental tradeoff:**
-
-- **More averaging** (comb filter) → Less cross-color, more vertical blur
-- **Less averaging** (notch filter) → Sharper, but more cross-color/cross-luma artifacts
-
-**Bandpass Comb Variation:**
-
-> "Some of this resolution loss can be overcome by restricting the combing to a bandpass region"
-
-This means applying the comb filter only to mid-frequencies where chroma lives, preserving low-frequency luma detail. However:
-
-> "Although the full luminance bandwidth is available, this is restricted to picture detail having vertical edges. Man-made subjects such as buildings give good results, but more natural scenes containing diagonal edges are less successful."
-
-### BBC Transform Decoder (Advanced)
-
-**Not a comb filter!** Uses Fourier transforms:
-
-> "Each frequency in the block is compared with its reflection about the colour sub-carrier frequency, and if the magnitudes are too dissimilar the pair of frequencies is rejected."
-
-This is much more sophisticated than simple comb filters and not what consumer TVs used.
-
-## Summary for Implementation
-
-### What Consumer PAL TVs Actually Did:
-
-1. **Most common:** Simple 2H comb filter for luma
-   - Average current line with line ±2H away
-   - Coefficients: 0.5 + 0.5 (or 0.25 + 0.5 + 0.25 for 3-tap)
-   - Accept vertical blur as tradeoff for reduced color artifacts
-
-2. **Some higher-end:** Separate optimized filters
-   - Not pure complementary decoder
-   - Custom filters for chroma and luma
-   - Try to balance sharpness vs artifacts
-
-3. **Not common:** Pure notch/complementary decoders
-   - Simpler but gave worse subjective results
-   - Used in some early/cheap implementations
-
-### What We Should Simulate:
-
-**Option 1: Authentic simple comb (most TVs)**
-
-- Use 2H comb with equal weighting: `luma = 0.5 * current + 0.5 * delayed_2H`
-- Accept some vertical blur (that's what real TVs had!)
-- Minimal checkerboard/cross-color
-
-**Option 2: Notch filter (current implementation)**
-
-- Sharper than real TVs
-- But with FIR_GAIN = 2.0, no checkerboard
-- Arguably "better" than real hardware, but less authentic
-
-**Recommendation:**
-Implement the simple 2H comb as an option so users can choose between:
-
-- "Sharp mode" (notch filter - better than real hardware)
-- "Authentic mode" (2H comb - what TVs actually did, with appropriate blur)