View a project's Ribbon/CustomUI XML in a ToolWindow

[ThunderFrame]

Probably only good for the modern Office file formats, but being able to display the CustomUI (2007) and/or CustomUI (2010+) XML files, with markup, would be useful. The XML would need to be loaded from the last-saved copy of the host document using the Packaging API.

XML can be syntax highlighted with AvalonEdit.

Nice to have would be navigation links from XML-defined callbacks, straight to the VBA callback implementation, and or showing callbacks without implementations.

[pgeerkens]

If there were an XLAM loaded that linked to Rubberduck, how about actually editing the CustomUI.xml for another workbook. Or related, copying images in for use by the Customized Fluent Ribbon?

[ThunderFrame]

sure, you could edit the XML for any document, then have RD save and close the document, update the CustomUI parts in the document, and then reopen the document.

If the document was being referred to by other projects, you'd have to close all of those projects first, before you could close and update the target document, but it's still feasible.

[ThunderFrame]

With AvalonEdit coming, the Ribbon XML files can be displayed as source-code pages (instead of as dedicated ToolWindows). I've added CustomUI and CustomUI14 properties to IVBProject in my branch, so the ribbon content is nearly available. We'll just need to be able to have AvalonEdit be able to render XML source, and select nodes where there's a callback method defined.

I've also added a list of callbacks by control and callback signature, so hopefully find usages will be able to resolve them to Declarations or QMNs once we finalize how those will behave under 3.0.