Mark Experimental API Surfaces

[AMollis]

This issue has been migrated a new MRTK repository, and the status of this issue will now be tracked at the following location:

• Mark Experimental API Surfaces MixedRealityToolkit/MixedRealityToolkit-Unity#100

---

Overview

There are numerous APIs we should mark as experimental. We should consider marking these with a "experimental" attribute, similar to how MRTK2 behaved.

Also, for each experimental class, add a "remarks" comment section:

/// <remarks>
/// This is an experimental feature. This class is early in the cycle, it has 
/// been labeled as experimental to indicate that it is still evolving, and 
/// subject to change over time. Parts of the MRTK, such as this class, appear 
/// to have a lot of value even if the details haven’t fully been fleshed out. 
/// For these types of features, we want the community to see them and get 
/// value out of them early enough so to provide feedback. 
/// </remarks>

Parent Task

• [GA Blocker] API Review for General Availability #11078

Tasks

• Add experimental attribute and drawer
• Add experimental remarks and attribute to DataBinding types.
  • IDataBindable
  • IDataBindingConfigurator
  • ClassDataBindingProfile
  • DataBindingProfile
  • DataRetrievalMethod
  • ButtonTheme
  • UXThemeProfile
  • CommonTheme
  • HandMenuTheme
  • ListMenuTheme
  • ObjectBarTheme
  • SlateTheme
  • SliderTheme
  • SpriteSetTheme
  • ToggleTheme
  • ect (Search for classes that end in "Theme".... to make sure we get them all)
• Add experimental remarks and attribute to NonNativeKeyboard.
• Add experimental remarks and attribute to VirtualizedScrollRectList

[marlenaklein-msft]

Closed with #11630.