Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

XAML Studio v2 Roadmap

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

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
20/100
Tipo di issue
Funzionalità
Chiarezza
Da chiarire
Stato di attività
Ferma
Stack tecnologico
csharp
Ambito
desktop, tooling

Direzione di ricerca

Questa è una roadmap di tracciamento v2 ampia, non un'attività circoscritta; il lavoro dovrebbe confluire in sub-issue. Inizia leggendo la issue #4 di XmlSyntaxVisualizerUWP e le issue referenziate #5 e #11, quindi esamina le iniziative WinUIEdit, preview, parser e UWP/WinUI 3. Il completamento è definito dal completamento di elementi della roadmap con ambito individualmente definito in vista delle milestone 2.0-beta e 2.0.

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

Descrizione

documentation help wanted

Open sourcing XAML Studio was just the start. There's a lot of great new features. Though many of them are still experimental and still need work before releasing a stable version. Please provide feedback on using those or look towards those individual issues for areas of specific improvements they need.

There are no larger tooling features planned for v2 outside what's been revealed already. However, there's a lot of back-end work/refactoring which should be completed to enable development to move forward.

Below are some other larger initiatives which need to be mapped out and completed:

  • Finish "real-time" preview loop (basically always show all valid XAML even if incomplete), needs understanding of https://github.com/michael-hawker/XmlSyntaxVisualizerUWP/issues/4 (the latest branch there also experimented with switching to WinUIEdit, see next; so maybe those go hand-in-hand a bit if this is figured out).
    • Ideally some of the incremental edit/parsing system from Guilabs is used, but that's not well understood either... 😅
  • Switch to WinUIEdit over Monaco (provides better performance, option to consolidate to single editor with better serialization/workbench state, and compatibility with UWP + WinUI 3 and AOT; however, unless we abstract some editor interop we lose future Uno Monaco WASM re-use for future v3)
  • Support building for (Modern) UWP and WinUI 3 together as part of single SDK-style modern project.
  • Re-work XAML Pre-render pipeline to better leverage XmlParser. This has been a WIP, but needs improvement still.
    • Want this to be more defined with parser and tests vs. string manipulation
    • Ensuring mapping or retaining of line numbers pre/post output is critical for error display, maybe an actual mapping system is needed to make it easier to work with, in general.
    • Folder + Resources needs this, we need to directly copy/interleave the complete resource dictionary (which is kind of what XAML does anyway) to get actual resource keys to be referenceable. (The current implementation of parsing separately and setting the resources only works for styles, as otherwise too late for XAML Parser to understand lookups for resource keys.)
      • Bonus if this supports nested references of resource dictionaries...
  • #5 (Needs more type specific widgets and document sync)
  • #11 (Needs more type specific adorners)

These will get converted to sub-issues soon, but wanted to have a general outline and tracking issue here to get started.

This'll be updated in-place as things progress.

You can also track smaller issues in the 2.0-beta milestone and 2.0 milestone. The goal when hitting 2.0-beta would be to potentially flight via the store, or at least produce downloaded MSIX packages at that point.

Lingua principale
C#
Stelle
454
Fork
48
Nessuna PR unita negli ultimi 30g

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 dotnet/XAMLStudio

Tutte le issue di dotnet/XAMLStudio

Issue simili

Altre issue su C#

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.