Complete File Handler support #119488

Open
opened 2024-03-14 21:34:39 +01:00 by Jesse Yurkovich · 1 comment

Overview

There are a variety of tasks remaining to complete the new File Handler capabilities inside Blender. Currently, while a large amount of net-new functionality has been provided, it is difficult to convey to users what is expected to work since there's a few missing pieces for support still.

Work generally falls into one of the following categories:

  • Fix UI issues preventing drag-n-drop from working for Python importers
  • Unify importer behavior when trying to import multiple files
  • Unify more of the existing drop-box code with File Handlers so that addon authors can extend drag-n-drop behavior without conflicting with file types already registered

Tasks

User Interface Fixes and Changes

  • Popup dialogs need to support layout panel API (aa03646a74, PR blender/blender!119519)
    • Blocks drag-n-drop for Python importers entirely
    • Blocks using layout panels in the C++ importers (they currently use layout boxes)
  • Popup dialog panels need to be drawn with correct colors (PR blender/blender!119803)

Use layout panels in Python importers/exporters (required for proper drag-n-drop support & Collection IO)

Use layout panels in C++ importers/exporters (for consistency and organization)

  • Blocked until Popup dialogs support layout panels
  • USD has an old-style implementation in universal-scene-description branch - start with that layout
  • Other formats

Ensure all importers provided by Blender support multiple files

Ensure File Handlers and old drop-box code work well together

  • Rationalize the existing drag/drop handling code with the new FileHandlerType support (#117621)

Ensure all drag-n-drop handlers provided by Blender support multiple files where reasonable

Rationale

PanelType layouts vs. the layout Panel API

Existing PanelType layouts are very cumbersome to setup and only work inside the File Browser space. They would not work inside popup dialogs or for the Collection IO project which attaches Exporters to Collections. As such, we need to use the layout Panel API in general.

C++ changes to use layout Panels

Currently none of the C++ importers/exporters use any sort of panel layout for organization and layout purposes. To better unify things it would be best if they switched from their "box" layouts to panels as well.

## Overview There are a variety of tasks remaining to complete the new File Handler capabilities inside Blender. Currently, while a large amount of net-new functionality has been provided, it is difficult to convey to users what is expected to work since there's a few missing pieces for support still. Work generally falls into one of the following categories: * Fix UI issues preventing drag-n-drop from working for Python importers * Unify importer behavior when trying to import multiple files * Unify more of the existing drop-box code with File Handlers so that addon authors can extend drag-n-drop behavior without conflicting with file types already registered ## Tasks ### User Interface Fixes and Changes * [x] Popup dialogs need to support layout panel API (aa03646a740729a9e3aa2ba3ae22b47c8298f44a, PR blender/blender!119519) * Blocks drag-n-drop for Python importers entirely * Blocks using layout panels in the C++ importers (they currently use layout boxes) * [ ] Popup dialog panels need to be drawn with correct colors (PR blender/blender!119803) ### Use layout panels in Python importers/exporters (required for proper drag-n-drop support & Collection IO) * [x] Common `io_util` code (af7a34dee7d4cc67d1ea1d3da7ead86a559e747d, PR blender/blender!119774) * [x] FBX (blender/blender-addons@1a7c9197b7ce070d3b1438b75a3f345c9ddb4dc9, PR blender/blender-addons!105238) * [x] glTF (blender/blender-addons@033d552a, PR https://github.com/KhronosGroup/glTF-Blender-IO/pull/2193) * [x] 3DS (blender/blender-addons@ * [ ] Not started: others... ### Use layout panels in C++ importers/exporters (for consistency and organization) * [x] Blocked until Popup dialogs support layout panels * [ ] USD has an old-style implementation in universal-scene-description branch - start with that layout * [ ] Other formats ### Ensure all importers provided by Blender support multiple files * [ ] Collada * [ ] Alembic * [ ] USD * [x] SVG as Grease Pencil (blender/blender@16129d6a485edf35ebf8ac65c0548d79114816cc) * [x] Wavefront OBJ (blender/blender@16129d6a485edf35ebf8ac65c0548d79114816cc) * [x] Stanford PLY (blender/blender@16129d6a485edf35ebf8ac65c0548d79114816cc) * [x] STL (blender/blender@16129d6a485edf35ebf8ac65c0548d79114816cc) * [ ] SVG * [x] FBX (blender/blender-addons@b57772a8831e1f618d37ac4a3386c070dbc425b6) * [x] glTF () * [ ] ... others ### Ensure File Handlers and old drop-box code work well together * [ ] Rationalize the existing drag/drop handling code with the new FileHandlerType support (https://projects.blender.org/blender/blender/issues/117621) ### Ensure all drag-n-drop handlers provided by Blender support multiple files where reasonable * [x] Background / reference images inside 3D Viewport editor (blender/blender@8b6a21c122e) * [x] Images inside Image editor space (blender/blender@b97ac126f8489f) * [ ] Images inside Node editor space * [ ] Sound and movie clips inside VSE editor space etc. ## Rationale #### PanelType layouts vs. the layout Panel API Existing PanelType layouts are very cumbersome to setup and only work inside the File Browser space. They would not work inside popup dialogs or for the Collection IO project which attaches Exporters to Collections. As such, we need to use the layout Panel API in general. #### C++ changes to use layout Panels Currently none of the C++ importers/exporters use any sort of panel layout for organization and layout purposes. To better unify things it would be best if they switched from their "box" layouts to panels as well.
Jesse Yurkovich added the
Module
Pipeline, Assets & IO
Type
To Do
Status
Confirmed
labels 2024-03-14 21:34:40 +01:00
Contributor

Multiple images in Shader Editor/node editors is one of the most requested ones. It's impossible to drag&drop entire PBR set right now.

Multiple images in Shader Editor/node editors is one of the most requested ones. It's impossible to drag&drop entire PBR set right now.
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#119488
No description provided.