Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

XAML Studio v2 Roadmap

Abierto
  • ¿Algo no está bien?
#34 2 comentarios 2 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
20/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Estancado
Stack tecnológico
csharp
Área
desktop, tooling

Línea de trabajo

Esta es una hoja de ruta amplia de seguimiento de v2, no una tarea con un alcance definido; se espera que el trabajo se traslade a sub-issues. Empieza leyendo el issue #4 de XmlSyntaxVisualizerUWP y los issues referenciados #5 y #11, y después revisa las iniciativas WinUIEdit, preview, parser y UWP/WinUI 3. Se considera que está terminada al completar elementos de la hoja de ruta con un alcance individual de cara a los hitos 2.0-beta y 2.0.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
C#
Estrellas
456
Forks
48
Sin PR fusionados en 30 d

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de dotnet/XAMLStudio

Todos los issues de dotnet/XAMLStudio

Issues similares

Más issues de C#

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.