Scripting and plug-in compatibility: Command Line, MEL, Python, API, plug-ins

Aperta
  • Qualcosa non va?
#57 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
8/100
Tipo di issue
Funzionalità
Chiarezza
Da chiarire
Stato di attività
Attiva
Stack tecnologico
python, rust
Ambito
tooling

Direzione di ricerca

This is a parent tracking issue, not a starting point: the checklist asks for an architecture decision record on script and plug-in boundaries and for each item to be split into child issues before any work begins. The files it names are known-issues.md and .project-docs/parity.md, which show the current gap. A newcomer's useful first step is to comment asking which child issue to take, not to write code. Done here means the child issues exist with sourced workflow lists.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

area/scripting effort/xl epic impact/many priority/p3 severity/medium triaged type/feature urgency/eventually

Problem

Not implemented; plug-in compatibility unverified.

Current behavior

known-issues.md ("Existing Maya plug-in compatibility unverified", severity high); .project-docs/parity.md (Scripting and extensions).

Expected behavior

Architecture/API/ABI boundaries, then MEL/Python execution and plug-in loading. References: scripting https://help.autodesk.com/cloudhelp/2026/ENU/Maya-Scripting/files/GUID-49701DA7-9224-424D-93F7-EC1DA779C99C.htm , plug-in loading https://help.autodesk.com/cloudhelp/2026/ENU/Maya-Customizing/files/GUID-07A89E6C-199C-4719-98A0-11C3A2BCDF21.htm , developer help https://help.autodesk.com/view/MAYADEV/2026/ENU/ .

Checklist:

  • Architecture decision record for script and plug-in boundaries
  • Command engine shared by UI and MCP
  • MEL
  • Python
  • Plug-in loading and API/ABI fixtures run against both applications

Security: imported scene scripts stay inert data until an explicit design says otherwise.

Acceptance criteria

  • Each checklist item is split into its own issue before work starts, with a sourced workflow list.
  • Every child follows the feature gates: visibly unsupported until done, MCP coverage with schemas, Editor protocol tests and docs, native visual check.
  • No percentage or parity claim until the pinned reference (#5) and the audited inventory exist.
Lingua principale
Rust
Stelle
4
Fork
2
Merge medio
9h 11m
PR unite (30g)
181

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di cristim/AztecCraft

Tutte le issue di cristim/AztecCraft

Issue simili

Altre issue su Rust

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.