Adam Hathcock
3227d09958
* Rename utils to common * fix namespaces * Rhino kind of works * Fix converter registration * Fixed circular referece with lazy resolving * Fixed Rhino8 * Revit 2022 builds * revit 2023 compiles * working on revit * use speckle app for info instead of statics * lazy init bindings * Rhino compiles * Revit compiles * Autocad 2022 builds * Autocad/Civil builds * ArcGIS compiles * Remove Autofac completely * format * React to SDK renames * fixes for merge * Update nuget and official sln * Remove extra projects * AutoActivate IBrowserBridge and rename it * add extra null check * Merge fixes * Fix convertermanager problem and add tests * Add new test project to local sln * Use recursion * formatting * resolve circular dep with lazy get
24 lines
915 B
C#
24 lines
915 B
C#
using Speckle.Connectors.DUI.Bridge;
|
|
|
|
namespace Speckle.Connectors.DUI.Bindings;
|
|
|
|
/// <summary>
|
|
/// Describes the most basic binding.
|
|
/// </summary>
|
|
public interface IBinding
|
|
{
|
|
/// <summary>
|
|
/// This will be the name under which it will be available in the Frontend, e.g.
|
|
/// window.superBinding, or window.mapperBinding. Please use camelCase even if
|
|
/// it hurts.
|
|
/// </summary>
|
|
public string Name { get; }
|
|
|
|
/// <summary>
|
|
/// Bindings will be wrapped by a browser specific bridge, and they will need
|
|
/// to use that bridge to send events to the Frontend, via <see cref="IBrowserBridge.Send">SendToBrowser(IHostAppEvent)</see>.
|
|
/// TODO: we'll probably need a factory class of sorts to handle the proper wrapping. Currently, on bridge instantiation the parent is set in the bindings class that has been wrapped around. Not vvv elegant.
|
|
/// </summary>
|
|
public IBrowserBridge Parent { get; }
|
|
}
|