Praktická dokumentace podle verzí

Dokumentace Equarith.

Nainstalujte Equarith, spusťte první hledání, porozumějte výsledkům, automatizujte pracovní postupy a exportujte rovnice.

Tento obsah je momentálně dostupný v angličtině.Dokumentace v tomto jazyce zatím nebyla zveřejněna. Níže se zobrazuje anglická verze.

Installation and updates

Equarith 1.0.3 is distributed as a native desktop application. Official native packages include the required Java runtime, so end users do not need to install a JDK.

Available packages

The v1.0.3 packaging matrix covers:

  • Windows x64: EXE and MSI installers.
  • macOS Intel x64 and Apple silicon ARM64: DMG and PKG packages.
  • Linux glibc x64 and ARM64: DEB and RPM packages.

Choose the package matching both the operating system and processor architecture. The .equarith project file association is registered by supported installers.

The development JAR is different from the native application. Running it directly requires JDK 25. Developers should use the Maven Wrapper and the build instructions supplied with the source tree.

Install safely

  1. Download Equarith from the official Equarith website.
  2. Select the artifact for your platform and architecture.
  3. Where a checksum or publisher signature is supplied, verify it before installation.
  4. Complete the platform installer and start Equarith from the normal application launcher.

Production Windows and macOS artifacts are signed through the release pipeline. Platform warnings can still appear when an operating system has not yet built reputation for a new release. Confirm the publisher and download origin rather than bypassing an unexpected warning blindly.

Equarith is a desktop application with a dense scientific interface. Its default window is 1440 by 900 pixels and it will not shrink below approximately 1100 by 720 pixels.

Application data locations

Equarith keeps preferences, structured logs, recovery files, and local license state under the current user profile:

  • Windows: %APPDATA%\Equarith, with AppData\Roaming\Equarith below the user profile as a fallback.
  • macOS: ~/Library/Application Support/Equarith.
  • Linux: $XDG_DATA_HOME/equarith, or ~/.local/share/equarith when XDG_DATA_HOME is not set.

Logs and recovery archives use dedicated subdirectories. In the Settings workspace, use Open application data or Open log folder instead of guessing the path. Projects and exported files remain wherever you chose to save them.

Uninstalling the application may leave these user files in place. Remove them only if you no longer need preferences, recovery data, logs, or local license information. Keep independent backups of important .equarith projects.

Updates

At startup, Equarith can make a small request to the official release service to learn whether a newer version exists. It does not upload your dataset, project, formulas, or results. You can also run the check explicitly from Settings.

When an update is available, the banner lets you open the official download page, skip that specific version, or dismiss the message. Equarith does not silently replace its own executable. Download and install the desired package using the normal platform process.

If an update check fails, work continues normally and local search is unaffected. See Licensing, privacy, and network access for the complete list of network features.

Changing application language

The interface can follow the operating-system language or use one of the 30 bundled languages. Changing the effective language restarts the application so every workspace is rebuilt consistently. Before restarting, Equarith preserves the current project or recovery state and requests a checkpoint from an active search where possible.

Arabic, Hebrew, and Persian use right-to-left interface layout. Formulas, numbers, code, and scientific charts remain left-to-right for readability.

Upgrade precautions

  • Save the current project before installing another version.
  • Keep a copy of valuable projects and exported formulas outside the application-data directory.
  • Do not manually edit a project archive or checkpoint.
  • A future application may read older project formats, but v1.0.3 deliberately rejects unknown future schema versions.
  • Resume a checkpoint only with compatible data, settings, functions, costs, and application behavior.

For project storage details, read Projects, recovery, and checkpoints.