Skip to content

library: document the two J2ME cores - #1191

Merged
fpscan merged 1 commit into
libretro:masterfrom
WizzardSK:j2me-docs
Sep 12, 2026
Merged

library: document the two J2ME cores#1191
fpscan merged 1 commit into
libretro:masterfrom
WizzardSK:j2me-docs

Conversation

@WizzardSK

Copy link
Copy Markdown
Contributor

Adds library/freej2me.md and library/freej2me_plus.md, and a Mobile Emulation section to the nav to hold them.

This is the docs half of what gouchi asked for in libretro/libretro-super#2094: both cores already have info files (libretro/libretro-super#2093) and a database (Mobile - J2ME.dat), but neither had a page here.

Each page carries the usual sections — extensions, database, BIOS, the feature table, geometry and timing, every core option with its values and default, and the pad mapping — with the option lists and pad tables taken from each core's own retro_core_option_v2_definition and retro_input_descriptor tables rather than written from memory.

Three things about these cores that the pages spell out, since they are not the usual arrangement:

  • the core is a front end for the emulator's own Java application, so a Java runtime has to be installed (java -jar, javaw on Windows);
  • freej2me-lr.jar / freej2me_plus-lr.jar has to be in the system directory — it is listed under BIOS, which is also how the info files declare it;
  • sound is produced by that Java application rather than sent through the frontend, and saves are written by it, which is why there are no save states, no rewind and no netplay.

Both FreeJ2ME and FreeJ2ME-Plus have core info files and a database entry but
no page here, which libretro/libretro-super#2094 asks for before the buildbot
picks them up.

The pages follow the usual shape - extensions, database, features, geometry,
every core option with its values and default, and the pad mapping taken from
each core's own input descriptors - with the two things that are unusual about
these cores said plainly: the core is a front end for the emulator's Java
application, so a Java runtime has to be installed, and the .jar that goes with
the core has to be in the system directory. Sound comes out of that Java
application rather than through the frontend, and saves are written by it too,
which is why there are no save states.
@gouchi

gouchi commented Sep 12, 2026

Copy link
Copy Markdown
Member

@fpscan Should be good to go ;)

@fpscan
fpscan merged commit d9c47ca into libretro:master Sep 12, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants