Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Anatomy Presets: Resolve schema addition. #992

Open
1 task
kobflo opened this issue Jan 23, 2025 · 2 comments
Open
1 task

Anatomy Presets: Resolve schema addition. #992

kobflo opened this issue Jan 23, 2025 · 2 comments
Labels
community Issues and PRs coming from the community members type: feature Adding something new and exciting to the product

Comments

@kobflo
Copy link

kobflo commented Jan 23, 2025

Story

As any user
Building anatomy presets

Quick viewable example of the expected result of the file name/ directory template.

Problems/ current view.

directory template: {root[work]}/{project[name]}/{hierarchy}/{folder[name]}/work/{task[name]}
file name template: {project[code]}{folder[name]}{task[name]}{@Version}<{comment}>.{ext}

Proposal

on hover over, or a middle click or a help icon, resolve the expression into an artist readable view.
ie, /mnt/projects/SOMECOOLSHOW/EP002/BAK-020/SH-101/work/FX

TODO

  • ...

Attachments

@kobflo kobflo added the type: feature Adding something new and exciting to the product label Jan 23, 2025
@kobflo kobflo changed the title Anatomy Presets: Hover over example schema. Anatomy Presets: Resolve schema addition. Jan 23, 2025
@m-u-r-p-h-y m-u-r-p-h-y added the community Issues and PRs coming from the community members label Jan 23, 2025
@m-u-r-p-h-y
Copy link
Member

It seems easy, but it is not trivial, as to resolve some templates properly you need to know the exact context.

so one template can produce many different paths so without knowing the context it is just guessing game.

@kobflo
Copy link
Author

kobflo commented Jan 23, 2025

It seems easy, but it is not trivial, as to resolve some templates properly you need to know the exact context.

so one template can produce many different paths so without knowing the context it is just guessing game.

Agreed!

Maybe each field could have a best guess assumption based on the easier things that could be resolved?

or

a selected project to guess from?

Just thoughts :)

Thanks for the response :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
community Issues and PRs coming from the community members type: feature Adding something new and exciting to the product
Projects
None yet
Development

No branches or pull requests

2 participants