Difference between revisions of "Ribbon Commander Framework Features"

Revision as of 16:45, 30 September 2013

Main Features

• Full object model for the Ribbon and Backstage (2010+).

• Full support for VBA (with advanced features like static function simulation).

• Full support for .NET (customized interop assemblies + native .NET libraries).

• Support for COM-savvy languages like VC++ and VB6. VB6 actually enjoys the same first-class support as VBA and C++-only headers (wrappers around COM interfaces with automatic translation of HRESULTs to std::exception-derived exceptions) may be provided based on customer feedback.

• Not dependent on specific document types when programming in VBA. For example, it works just as well with .xls and .xlsb documents.

• Not dependent on specific project types when programming in .NET/C++/VB6. Non-COM projects (like xll projects) can use the libraries.

• Productivity add-ons. A suite of add-ons for VBA and Visual Studio that we will keep expanding as necessary based on customer feedback. Currently:

  VBA add-on with an 'Mso Image Browser' and delegate insertion functionality.

• Redistributable runtime. The runtime is available both as a merge module (msm) and a minimal installer package (msi) for easy redistribution with your products/within your organization.

• Dynamic manipulation of the ribbon. Up to 1000 contexts (or virtual add-ins) are supported per session, which can be created/destroyed at runtime. Moreover dynamic manipulation of each context is fully supported, so the ribbon UI can be tightly integrated with your applications. The customization capabilities of the Office Ribbon are extended to include all controls/properties and are simplified since there is little need to manage callbacks. At the same time callbacks are fully supported and extended to include events (for all languages) and delegates for .NET.

• 100% compatibility with existing Office UI XML code. All Ribbon Commander control objects are serializable to XML and instantiatable from XML. In practice that means that existing code can be used out-of-the-box while still taking advantage of all framework features.

• The Ribbon Commander object model follows closely the object model defined in the Custom UI XML Markup Specification. Existing experience programming the Office UI using XML can be leveraged when using the framework and vice versa.

• At IlydaUK we are committed to providing great documentation for our products. Ribbon Commander comes with a dedicated wiki with a growing collection of how-tos and samples to help you hit the ground running.