Merge pull request #16 from etienneschalk/develop

Release 0.4.0

Author: etienneschalk

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -106,8 +106,7 @@ body:
       placeholder: |
         Go to VSCode Settings (Ctrl+,) and search for "Scientific Data Viewer", then copy the relevant settings:
         - scientificDataViewer.maxFileSize: 
-        - scientificDataViewer.allowMultipleTabsForSameFile: 
-        - scientificDataViewer.plottingCapabilities:
+        - scientificDataViewer.allowMultipleTabsForSameFile:
     validations:
       required: false
 

.prettierrc

@@ -0,0 +1,18 @@
+{
+  "tabWidth": 2,
+  "singleQuote": true,
+  "overrides": [
+    {
+      "files": "**/*.{json,ts,js}",
+      "options": {
+        "tabWidth": 4
+      }
+    },
+    {
+      "files": "*.{md}",
+      "options": {
+        "tabWidth": 2
+      }
+    }
+  ]
+}

.vscode/settings.json

@@ -15,5 +15,6 @@
         "**/node_modules": true,
         "**/out": true,
         "**/.vscode-test": true
-    }
+    },
+    "prettier.configPath": ".prettierrc"
 }

CHANGELOG.md

@@ -6,7 +6,48 @@ All notable changes to the Scientific Data Viewer VSCode extension will be docum
 
 <!-- and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html). -->
 
-## [0.3.0] - 2025-01-27
+## [0.4.0] - 2025-10-06
+
+### Added
+
+- **Extension Virtual Environment**: Semi-standalone virtual environment stored in VSCode extension storage
+  - **uv Required**: Only works if `uv` is installed on the system
+  - **Python 3.13**: Uses uv to install and use Python 3.13 for latest features and performance
+  - **Isolated Storage**: Stored in VSCode's extension storage space
+  - **Fallback Support**: Falls back to Python extension behavior if uv is not available
+  - **Management Commands**: Create, manage, update, and delete extension environment
+  - **Status Display**: Shows extension environment status and creation tool in status bar
+- **Virtual Environment Management Command**:
+  - `Manage Extension Virtual Environment`: Create, update, delete extension environment
+- **Configuration Settings**:
+  - `scientificDataViewer.overridePythonInterpreter`: Override Python interpreter path (takes precedence over all other options)
+  - `scientificDataViewer.python.useExtensionOwnEnvironment`: Activate the use extension's own virtual environment with `uv`
+  - `scientificDataViewer.currentlyInUseInterpreter`: Currently active Python interpreter path (read-only, updated automatically)
+- **Split View**:
+  - Works for files opened via the file explorer, because the webviewPanel is reused (`ScientificDataEditorProvider`)
+  - Does not work with files/dirs opened via command nor context menu, because the webviewPanel is created from scratch
+
+### Enhanced
+
+- **Enhanced Status Bar**: Shows virtual environment type and interpreter information
+
+### Removed
+
+- Plotting Capabilities extension feature flag (always on)
+
+### Technical Improvements
+
+- Refactor zones of the code.
+
+### Known Bugs
+
+- Data Structure TreeView is not shown for manually created Webviews in Cursor. See when clause of `scientificDataViewer.outline`.
+  - When VSCode doc: https://code.visualstudio.com/api/references/when-clause-contexts
+  - Related: https://forum.cursor.com/t/webview-panels-and-commands-not-supported-in-cursor-breaks-extensions/115748
+
+### Fixed
+
+## [0.3.0] - 2025-10-03
 
 ### Added
 
@@ -219,7 +260,6 @@ All notable changes to the Scientific Data Viewer VSCode extension will be docum
 - `scientificDataViewer.maxFileSize`: Maximum file size (MB) to load automatically
 - `scientificDataViewer.defaultView`: Default view mode
 - `scientificDataViewer.allowMultipleTabsForSameFile`: Allow multiple tabs for same file **(Experimental)**
-- `scientificDataViewer.plottingCapabilities`: Enable plotting capabilities **(Experimental)**
 
 ### Available Commands
 

README.md

@@ -0,0 +1,159 @@
+# Scientific Data Viewer v0.4.0 Release Notes
+
+## 🎉 Major Release: Extension Virtual Environment with uv Support
+
+Version 0.4.0 introduces a significant enhancement to the Scientific Data Viewer extension by adding support for a semi-standalone virtual environment managed by `uv`, providing better isolation and Python 3.13 support. This release transforms the extension from a Python extension-dependent tool into a more self-contained solution while maintaining full backward compatibility.
+
+## ✨ What's New
+
+### 🐍 Extension Virtual Environment System
+
+- **uv Integration**: New virtual environment system using `uv` for Python 3.13 installation and management
+- **Semi-Standalone Operation**: Extension can run independently with only `uv` as a requirement
+- **Isolated Storage**: Environment stored in VSCode's extension storage space for complete isolation
+- **Fallback Support**: Gracefully falls back to Python extension behavior if `uv` is unavailable
+- **Management Commands**: Complete CRUD operations for extension environment through intuitive UI
+
+### ⚙️ Enhanced Configuration System
+
+- **`scientificDataViewer.python.overridePythonInterpreter`**: Override Python interpreter path (highest priority)
+- **`scientificDataViewer.python.useExtensionOwnEnvironment`**: Enable extension's own uv virtual environment
+- **`scientificDataViewer.python.currentlyInUseInterpreter`**: Read-only tracking of active interpreter
+- **Priority Order**: Clear precedence system for interpreter selection
+
+### 🎯 Improved User Experience
+
+- **Quick Pick Interface**: Replaced notification dialogs with intuitive quick pick menus for uv environment management
+- **Status Bar Integration**: Shows virtual environment type and interpreter information
+- **Split View Support**: Works for files opened via file explorer (webviewPanel reuse)
+- **Better Error Handling**: Improved error messages and recovery mechanisms
+
+## 🔧 Technical Improvements
+
+### 🏗️ New Architecture Components
+
+- **`ExtensionVirtualEnvironmentManager`**: Core virtual environment management (701 lines)
+- **`ScientificDataEditorProvider`**: Handles file editor integration
+- **`utils.ts`**: Utility functions for path handling and quoting
+- **Refactored PythonManager**: Complete rewrite with improved initialization flow
+
+### 📁 Code Quality Enhancements
+
+- **API Surface Reduction**: PythonManager API simplified and streamlined
+- **Better Error Handling**: Enhanced error recovery for missing `uv` installation
+- **Path Quoting**: Fixed path quoting issues for spawn calls
+- **Test Updates**: All test suites updated to reflect new API changes
+
+### 🧪 Testing and Reliability
+
+- **Comprehensive Testing**: Updated all test suites for new architecture
+- **Error Scenarios**: Better handling of edge cases and missing dependencies
+- **Compilation Fixes**: Resolved test compilation issues
+
+## 🐛 Bug Fixes
+
+- **Path Handling**: Fixed path quoting issues for passing paths as args in spawn calls
+- **Environment Detection**: Improved Python interpreter detection and validation
+- **UI Consistency**: Better handling of environment switching and refresh scenarios
+- **Test Infrastructure**: Fixed compilation issues and removed obsolete tests
+
+## 📊 Configuration Priority System
+
+The extension now uses a clear priority system for Python interpreter selection:
+
+1. **`overridePythonInterpreter`** (manual override - highest precedence)
+2. **Extension environment** (if uv available and enabled)
+3. **Python extension interpreter** (fallback)
+4. **System Python** (final fallback)
+
+## 🎮 New Commands
+
+| Command                                                        | Description                                                        |
+| -------------------------------------------------------------- | ------------------------------------------------------------------ |
+| `Scientific Data Viewer: Manage Extension Virtual Environment` | Create, update, delete, and view extension environment information |
+
+## ⚙️ New Settings
+
+### Python Environment Settings
+
+- **`scientificDataViewer.python.overridePythonInterpreter`**
+
+  - Type: `string`
+  - Default: `""`
+  - Description: Override Python interpreter path (takes precedence over all other options)
+
+- **`scientificDataViewer.python.useExtensionOwnEnvironment`**
+
+  - Type: `boolean`
+  - Default: `false`
+  - Description: Use the extension's own virtual environment (requires uv)
+
+- **`scientificDataViewer.python.currentlyInUseInterpreter`**
+  - Type: `string`
+  - Default: `""`
+  - Description: Currently active Python interpreter path (read-only, updated automatically)
+
+## 🚀 Getting Started with Extension Environment
+
+1. **Install uv**: Follow the [uv installation guide](https://docs.astral.sh/uv/getting-started/installation/)
+
+2. **Enable Extension Environment**:
+
+   - Press <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>P</kbd>
+   - Type "Scientific Data Viewer: Show Settings"
+   - Check "Scientific Data Viewer > Python > Use Extension Own Environment"
+
+3. **Manage Environment**:
+   - Press <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>P</kbd>
+   - Type "Scientific Data Viewer: Manage Extension Virtual Environment"
+   - Choose from: Create, Update, Delete, or View Information
+
+## ⚠️ Known Issues
+
+- **Data Structure TreeView**: Not shown for manually created Webviews in Cursor (occurs sometimes)
+- **Environment Switching**: Some edge cases may require manual refresh (Ctrl+Shift+P -> SDV: Refresh) so that the status bar reflects the correct state, eg when deleting manually a virtual environment
+
+## 🔄 Breaking Changes
+
+- **PythonManager API**: Reduced API surface (some methods made private)
+- **UIController**: Constructor signature changed
+- **Test Interfaces**: Updated test interfaces to match new architecture
+
+## 📈 Impact
+
+This release significantly improves the extension's Python environment management capabilities:
+
+- **Better Isolation**: Extension environment won't interfere with other projects
+- **Python 3.13 Support**: Latest Python version for optimal performance
+- **Almost Self-Contained**: Minimal external dependencies (only requires uv)
+- **Backward Compatible**: Falls back gracefully when uv is not available
+- **User Control**: Clear configuration options and management commands
+
+## 📊 Statistics
+
+- **23 files changed** with **2,419 additions** and **1,623 deletions**
+- **Net change**: +796 lines
+- **New Components**: 3 major new TypeScript files
+- **API Simplification**: Reduced PythonManager complexity
+- **Test Coverage**: Updated all test suites
+
+## 🔮 What's Next
+
+This release establishes a solid foundation for future enhancements:
+
+- **Enhanced Environment Management**: More sophisticated environment switching
+- **Performance Improvements**: Optimized Python environment operations
+- **Better Integration**: Improved VSCode and Cursor compatibility
+- **Advanced Features**: More sophisticated data processing capabilities
+
+## 🙏 Acknowledgments
+
+Thank you to all users who provided feedback and contributed to this release.
+
+---
+
+**Download now**: [VSCode Marketplace](https://marketplace.visualstudio.com/items?itemName=eschalk0.scientific-data-viewer) | [Open VSX](https://open-vsx.org/extension/eschalk0/scientific-data-viewer)
+
+**Documentation**: [GitHub Repository](https://github.com/etienneschalk/scientific-data-viewer)
+
+**Report Issues**: [GitHub Issues](https://github.com/etienneschalk/scientific-data-viewer/issues)

docs/RELEASE_NOTES_0.4.0.md

@@ -0,0 +1,49 @@
+# RFC #034: French Translation Support
+
+## Description
+
+Implement comprehensive French translation for the Scientific Data Viewer extension using AI-powered string extraction and translation to make the extension accessible to French-speaking users.
+
+## Requirements
+
+- Extract all user-facing strings from the extension codebase
+- Use AI translation services to translate strings to French
+- Implement i18n (internationalization) framework
+- Support language switching between English and French
+- Maintain translation quality and consistency
+- Handle technical terms appropriately
+- Support dynamic language switching without restart
+
+## Acceptance Criteria
+
+- [ ] All UI strings are extracted to translation files
+- [ ] French translation covers 100% of user-facing text
+- [ ] Language can be switched via VS Code settings
+- [ ] Technical terms are translated appropriately
+- [ ] Translation quality is verified by native speakers
+- [ ] No hardcoded strings remain in the codebase
+- [ ] Language switching works without extension restart
+- [ ] Error messages are properly translated
+
+## Priority
+
+Medium - Accessibility enhancement
+
+## Labels
+
+i18n, translation, french, accessibility, localization, user-experience
+
+## Status
+
+**PENDING** 📋
+
+## Implementation Notes
+
+This feature requires:
+
+- String extraction from TypeScript/JavaScript files
+- Translation service integration (AI-based)
+- i18n framework implementation
+- Language detection and switching
+- Quality assurance for translations
+- Testing with French-speaking users

docs/rfc/034-french-translation.md

@@ -0,0 +1,51 @@
+# RFC #035: Enhanced Error Handling System
+
+## Description
+
+Implement a comprehensive error handling system that provides better user feedback, error recovery mechanisms, and debugging information for the Scientific Data Viewer extension.
+
+## Requirements
+
+- Improve error messages with actionable guidance
+- Implement error recovery mechanisms
+- Add error logging and reporting
+- Provide better debugging information
+- Handle edge cases gracefully
+- Implement retry mechanisms for transient errors
+- Add error categorization and severity levels
+- Provide user-friendly error descriptions
+
+## Acceptance Criteria
+
+- [ ] All errors have clear, actionable messages
+- [ ] Error recovery mechanisms are implemented
+- [ ] Error logging is comprehensive and useful
+- [ ] Users can retry failed operations
+- [ ] Error severity levels are clearly indicated
+- [ ] Debugging information is accessible
+- [ ] Error messages are user-friendly
+- [ ] Error reporting system is functional
+
+## Priority
+
+High - User experience and reliability
+
+## Labels
+
+error-handling, user-experience, reliability, debugging, error-recovery
+
+## Status
+
+**PENDING** 📋
+
+## Implementation Notes
+
+This feature requires:
+
+- Error categorization system
+- User-friendly error message templates
+- Retry mechanism implementation
+- Error logging infrastructure
+- Debug information collection
+- Error recovery strategies
+- User feedback mechanisms