Doc WinAppSDK's WinRT registration choice #2359
Conversation
DrusTheAxe
added
documentation
DrusTheAxe
requested review from
dhoehna,
jeffstall,
BenJKuhn,
Scottj1s,
MikeHillberg,
jonwis,
cwruss and
EHO-makai
ghost
added
the
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
| While some might call this "non-ideal layout" (implying projections' manifest-free resolution is | ||
| ideal), that's not true. The manifest-free option is *simple*, but not necessarily best. As in | ||
| WinAppSDK's case. |
There was a problem hiding this comment.
Well it depends. It's non-ideal for some projection authors (me). It's very ideal for WinAppSdk for reasons below. Maybe consider striking this as the next paragraph does a good job at preparing the reader for The Big Why™️ after it.
There was a problem hiding this comment.
Just delete and assert what we do and why. No need to defend it. If you are so motivated, you could write an appendix on how projection-based lookup doesn't meet our current needs w.r.t. naming of components.
| While some might call this "non-ideal layout" (implying projections' manifest-free resolution is | ||
| ideal), that's not true. The manifest-free option is *simple*, but not necessarily best. As in | ||
| WinAppSDK's case. |
There was a problem hiding this comment.
Just delete and assert what we do and why. No need to defend it. If you are so motivated, you could write an appendix on how projection-based lookup doesn't meet our current needs w.r.t. naming of components.
|
@DrusTheAxe I can open a separate issue on this if needed, but the embedded fusion manifest requirement appears to deviate from documented expectations, in that a manifest can be embedded as a resource or be on disk, as a fallback. The embedded-only approach that WAS has implemented is a pain for Rust that has no native tooling to embed a manifest. Was this just deemed unnecessary at the time? |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
This is a polished form of the information in issue #2352 WinAppSdk is difficult to use with reg-free WinRT due to class/file naming, pairs
and particularly in this comment.