Skip to content

[LDA] - (Import) LuxImport @ 3.0.0 (New Version) #484

@qerdinger

Description

@qerdinger

LuxImport v3.0 Specifications

Potential Layout :

Image

The next layout will be supported by LMGUI #40. It is splitted up into 4 components (Left, Main, Right, Bottom).

Root feature selection :
When the "Import" button is clicked (It might be renamed by "Collections", "Library" or "Workspace"), the two following options might be offered.

  • Standard
  • Express

Once the deployment of the new version released, the legacy view and process could also be used by clicking (right-click) on "Import", and selecting "Legacy Mode".

Standard Importation

The standard way of importing, open on LMGUI sections all required views, such as :

Left-hand side :

This section is cut in two parts, (3/4 long) / (1/4)

  • System File Explorer (with Drive Selection (C:, Disk, SD Card, ...)) (3/4)
  • Previous opened emplacements

When a selection of the emplacement is done, the main window displays all items in this selected area. Each picture is by default enabled, the user should uncheck pictures that he/she does not want.

The File explorer should work in a recursive path discovery, specified as follows :
Folder1 :

  • Folder 2 :
    • Folder 3:

If the user clicks on Folder 2, it should inclues all subfolders starting from Folder 2, an option could also be specified such as the importation depth, which specifies how far the importation should go at, by default (somethings like 10/15 folders should be enough).

Note: At each moment of the importation, the user could switch emplacement without losing its previous context.

Example of Layout :

Image

Main Window (Main area) :

This section is the most complete and useful, it serves as a AssetLibrary, by default all assets should be rendered on a grid, responsive depending of the size of the window.

If the user clicks on a specific asset, the grid should be replaced by the asset, displayed full-size.
On that view, some key bindings should work, defined as :
[Space]: Skip
[X]: Exclude

All rendering process should be triggered and rendered NOT on the UI thread, for performance purpose.
It might be very useful, to pre-load all assets as lower quality as default and render asset with full quality on demand or when resources available.

Bottom Area :

Displays CollectionExplorer when Asset by Asset display mode selected.
When importation is under way, it should display the importation process with an ETA, progress status, etc.

Right-hand size :

The section should be dedicated to the output (1/2 long) and import. settings (1/2 long)

Output

Where to "clone" the collection, what should be the strategy in case of template naming, collision, etc.

Importation Settings

Lot of options, a few samples below :
Should it be pre-loaded [True/False]
Should it be pre-rendered in full-quality [True/False]
Would you apply the default export strategy [True/False]
Exportation in background task [True/False]

Express Importation

Legacy batch importation mode

Metadata

Metadata

Assignees

Labels

FeatureNew feature or request

Projects

Status

In Development

Relationships

None yet

Development

No branches or pull requests

Issue actions