Stirling-PDF
Stirling-PDF copied to clipboard
V2 Tauri integration
Description of Changes
Please provide a summary of the changes, including:
Add PDF File Association Support for Tauri App
๐ฏ Features Added
- PDF file association configuration in Tauri
- Command line argument detection for opened files
- Automatic file loading when app is launched via "Open with"
- Cross-platform support (Windows/macOS)
๐ง Technical Changes
- Added
fileAssociationsintauri.conf.jsonfor PDF files - New
get_opened_fileTauri command to detect file arguments fileOpenServicewith Tauri fs plugin integrationuseOpenedFilehook for React integration- Improved backend health logging during startup (reduced noise)
๐งช Testing
See
-
https://v2.tauri.app/start/prerequisites/
-
DesktopApplicationDevelopmentGuide.md
# Test file association during development: cd frontend npm install cargo tauri dev --no-watch -- -- "path/to/file.pdf"
For production testing:
- Build: npm run tauri build
- Install the built app
- Right-click PDF โ "Open with" โ Stirling-PDF
๐ User Experience
- Users can now double-click PDF files to open them directly in Stirling-PDF
- Files automatically load in the viewer when opened via file association
- Seamless integration with OS file handling
Checklist
General
- [ ] I have read the Contribution Guidelines
- [ ] I have read the Stirling-PDF Developer Guide (if applicable)
- [ ] I have read the How to add new languages to Stirling-PDF (if applicable)
- [ ] I have performed a self-review of my own code
- [ ] My changes generate no new warnings
Documentation
- [ ] I have updated relevant docs on Stirling-PDF's doc repo (if functionality has heavily changed)
- [ ] I have read the section Add New Translation Tags (for new translation tags only)
UI Changes (if applicable)
- [ ] Screenshots or videos demonstrating the UI changes are attached (e.g., as comments or direct attachments in the PR)
Testing (if applicable)
- [ ] I have tested my changes locally. Refer to the Testing Guide for more details.
โ Frontend License Check Passed
All frontend licenses have been validated and no compatibility warnings were detected.
The frontend license report has been updated successfully.
โ Frontend License Check Passed
All frontend licenses have been validated and no compatibility warnings were detected.
The frontend license report has been updated successfully.