You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If we manage to add back the API some day, it would be great if the TemplateParts could be added to the controls pages. Moreover it would be great to add links to the original Fluent and Simple styles for faster copy & paste if needed.
I imagine that information could probably be auto generated based on the attributes in the control class and then dumped onto the docs site somewhere so people can at least see it exists. The only control I can see there that has it at all is the colour picker
Obviously it would be nice if it was automatically kept in sync with what ever the latest release version is. I am however not sure how the doc site/doc build system works. In any case, it should be fairly easy to generate a bunch of markup for all controls in a specific namespace based on the attribute values. I am guessing some github action could possibly do that. But it would likely mean adding a bunch of C# code to the build system.
On a side note, AvaloniaUI/Avalonia#14180 should actually solve some of my problems with the template part system. But having the list would still be nice.
If we manage to add back the API some day, it would be great if the TemplateParts could be added to the controls pages. Moreover it would be great to add links to the original Fluent and Simple styles for faster copy & paste if needed.
Obviously it would be nice if it was automatically kept in sync with what ever the latest release version is. I am however not sure how the doc site/doc build system works. In any case, it should be fairly easy to generate a bunch of markup for all controls in a specific namespace based on the attribute values. I am guessing some github action could possibly do that. But it would likely mean adding a bunch of C# code to the build system.
Originally posted by @thevortexcloud in AvaloniaUI/Avalonia#14131 (reply in thread)
The text was updated successfully, but these errors were encountered: