Plugin Conversion & Implementation

How Conversion Works

Seer treats plugins as external executors. When a file is triggered, Seer executes the configured program, passing file paths via placeholders.

Placeholder Variables

• ${input_file}: Absolute path of the source file.
• ${output_file}: Path where the plugin should save the processed/converted output.

Execution Workflow

1. Trigger: User presses SPACE on a file.
2. Resolution: Seer identifies the plugin associated with the file extension.
3. Execution: Seer runs the executable (e.g., ApkMetaInfo2Json.exe "${input_file}" "${output_file}.json").
4. Display: Once the process exits, Seer reads the generated file at ${output_file} and renders it.

Plugin Types

A plugin can be any executable capable of handling input/output via CLI: * Scripts: .cmd, .bat * Third-party Tools: ImageMagick, exiftool, dll_lib_exports, etc. * Custom Binaries: Compiled programs (e.g., Qt-based viewers).

Temporary File Management

Plugins often generate intermediate files. * Auto-Cleanup: Seer automatically purges temp files older than 20 days. * Forced Removal: Append ${no_cache} to your command parameters to instruct Seer to delete the temporary file immediately after display.

DLL Plugins

For high-performance or deep integration, Seer supports DLL-based plugins. Refer to these official repositories for the plugin interface implementation: