text stringlengths 34 4.22k | embeddings listlengths 768 768 |
|---|---|
A Speckle kit is, essentially, the definition of a common language: a schema. Moreover, a Speckle kit also contains the translation routines to and from an application's native object model to the kit's schema. Kits are "hot-swappable": Speckle comes with one by default which delivers the core of our interoperability c... | [
-0.5456897616386414,
-0.25332772731781006,
0.08109235018491745,
0.580932080745697,
-0.48136842250823975,
0.6572257876396179,
-0.06912574917078018,
-0.6673596501350403,
0.6399868726730347,
0.8012625575065613,
-0.1030806452035904,
-0.1596628576517105,
-0.3663776218891144,
-0.1321573108434677... |
Existing authoring applications, such as Rhino, Revit, Autocad, send and receive data from and to Speckle by passing it through the conversion routines of a given kit. This is handled through **connectors.** Connectors are plugins that integrate within these host applications (e.g., the Rhino Connector) and allow end-u... | [
-0.9229546785354614,
-0.31293216347694397,
0.46330663561820984,
0.4036637842655182,
-0.3685610890388489,
0.11919917911291122,
0.5905069708824158,
-0.7525932788848877,
0.4716663658618927,
0.8991637229919434,
-0.6033204197883606,
-0.1301257461309433,
-0.09646257013082504,
-0.1030006930232048... |
Read more about **kits** [here](/dev/kits). If curious, you can also follow up with the discussion on [our forum](https://speckle.community/t/introducing-kits-2-0/710). | [
-0.8078263401985168,
-0.3259517252445221,
0.39963647723197937,
0.4722355604171753,
-0.3014301359653473,
0.6369276642799377,
0.36697307229042053,
-0.6833000183105469,
0.9935943484306335,
0.40966325998306274,
-0.6575406789779663,
-0.24904616177082062,
0.05202614888548851,
-0.1746387779712677... |
We also have a guide on how to write your own **connector** - [check it out](/dev/connectors-dev.html)! | [
-1.203342318534851,
-0.7704387307167053,
0.5872389674186707,
0.3059118092060089,
-0.4850676953792572,
-0.030094722285866737,
0.3784453570842743,
0.04214438796043396,
1.0094447135925293,
0.4276708960533142,
-0.8172473311424255,
-0.6358429193496704,
0.34389811754226685,
-0.03475791588425636,... |
Other applications do not necessarily need to do so: they can directly use a kit's schema - or simply use objects that respect the few low-level constraints that Speckle needs to serve its purpose. These aspects are described below in [Serialisation & Structure](#serialisation-structure). Next, we're going to discuss h... | [
-0.4204607605934143,
-0.1319279968738556,
0.49611228704452515,
0.39393824338912964,
-0.3078731298446655,
-0.04878746345639229,
0.45783087611198425,
-0.9498154520988464,
0.3874310851097107,
0.6806738972663879,
-0.2940106987953186,
-0.4108394384384155,
-0.14726552367210388,
-0.22590129077434... |
Once Speckle data is translated or directly created, it needs to be serialised and, lastly, stored. In reverse, data needs to be retrieved from the storage layer and de-serialised to a memory representation that can be used by the application it was received in (either converted back to host application representations... | [
-0.5183001756668091,
-0.22189442813396454,
0.3312687277793884,
0.16182175278663635,
-0.582563579082489,
0.03085312247276306,
0.19677908718585968,
-0.7322308421134949,
0.37197113037109375,
0.9692695140838623,
-0.3340088725090027,
-0.13473545014858246,
-0.3794122338294983,
-0.312651008367538... |
Before we dive deeper into Speckle's decomposition and re-composition procedures, we will first take a look at how the storage layer is handled in Speckle and the flexibility it offers. | [
-0.6592665314674377,
-0.2745555639266968,
0.7243157625198364,
-0.11840181052684784,
-0.19730539619922638,
0.2792533040046692,
0.1059233695268631,
-0.4638276994228363,
0.49544399976730347,
1.0581753253936768,
-0.7252590656280518,
0.06369094550609589,
-0.1503855437040329,
-0.2091277539730072... |
Different storage systems have various characteristics that make them better (or more ill) suited for different scenarios. This is why, rather than employ a unique storage system, Speckle uses an intermediary abstraction layer: transports. A transport defines the way Speckle writes to, and reads from, a given persisten... | [
-0.658779501914978,
-0.08952596038579941,
0.7108051776885986,
0.41286370158195496,
-0.229100301861763,
0.4885547161102295,
0.48639458417892456,
-0.6856441497802734,
0.6784337759017944,
0.43814876675605774,
-0.43117088079452515,
0.15346021950244904,
-0.39433419704437256,
0.04943548887968063... |
One such transport is the Speckle Server Transport. Another transport is an SQLite Transport. Speckle comes with a couple of other transports too: a MongoDB transport, an In-Memory Transport, as well as a Disk Transport. Other transports, such as an S3 transport, a MySQL transport could easily be developed. | [
-0.4180509150028229,
-0.4805369973182678,
0.7121279835700989,
0.0381741002202034,
-0.1076790988445282,
0.44848886132240295,
0.38375619053840637,
-0.5261736512184143,
0.8873549699783325,
0.9892598390579224,
-0.9593194127082825,
0.5315719842910767,
0.20094256103038788,
-0.21065664291381836,
... |
The Disk Transport writes and reads your Speckle data from files in a location you specify, while the SQLite Transport does the same, but backed by a SQLite database. For example, the latter is used extensively throughout our connectors as a local cache so as to reduce the dependency on a high-latency transport, namely... | [
-0.35876089334487915,
-0.41686496138572693,
0.6955952048301697,
0.004669164307415485,
-0.2963778078556061,
0.32454338669776917,
0.35632237792015076,
-0.5867376327514648,
0.8485332131385803,
0.9198852181434631,
-0.8210237622261047,
0.07924092561006546,
0.21714892983436584,
0.065753221511840... |
Transports offer developers low-level flexibility in developing, essentially, their own custom back-ends to Speckle, or pushing data to other systems that can do different things - even a whole new Speckle Server. | [
-0.760774552822113,
-0.25710999965667725,
0.6476569771766663,
0.3206867277622223,
-0.3566931486129761,
0.25992411375045776,
0.33668217062950134,
-0.852556586265564,
0.8252546787261963,
0.887531042098999,
-0.6843653321266174,
0.06724463403224945,
-0.24636763334274292,
0.09157352149486542,
... |
Moreover, send operations are no longer restricted to one single location: Speckle allows you to send data, in parallel, to multiple transports. For example, data can be sent to two different Server Transports at the same time, one being an internal server and one being an external one - a different stakeholder involve... | [
-0.6513628363609314,
-0.4472595155239105,
0.5693650245666504,
0.7472387552261353,
-0.41884365677833557,
0.40018603205680847,
0.09987685084342957,
-0.8490293025970459,
0.7444563508033752,
0.8503977656364441,
-0.5307371616363525,
0.024968428537249565,
-0.5528412461280823,
-0.0688896104693412... |
Alternatively, a plugin based on Speckle could be developed that acts much more like git, writing data to a local folder that resides right next to the source file itself. This enables, in whatever configuration you see fit, a local only usage of Speckle, with pushing to remotes being a secondary, optional operation. | [
-0.3840562701225281,
-0.202106311917305,
0.33688634634017944,
-0.04992327839136124,
-0.2979620695114136,
0.38265663385391235,
-0.031137248501181602,
-0.3247170150279999,
1.1428085565567017,
0.9370104670524597,
-0.7762826085090637,
-0.37459301948547363,
0.10502029210329056,
-0.2309575974941... |
A work-in-progress guide on how to write your own transport can be found [here](transports-dev). | [
-0.5033119320869446,
-0.34554317593574524,
0.7945374846458435,
0.4927609860897064,
-0.0933600664138794,
-0.060760583728551865,
0.4444834291934967,
-0.11277962476015091,
0.8704618811607361,
1.2045115232467651,
-1.0044687986373901,
-0.14649544656276703,
0.06413471698760986,
-0.08682399243116... |
Before data can be persisted to a storage system, it needs to be serialised. Serialisation is the process by which an object is converted into a state that can be stored or transmitted, and be reconstructed later from (deserialisation). | [
-0.404511958360672,
-0.6394637823104858,
0.2811989486217499,
-0.07924647629261017,
-0.34359896183013916,
0.20216292142868042,
0.2289177030324936,
-0.2066541463136673,
0.5156259536743164,
0.6263383626937866,
-0.30928847193717957,
-0.1997297704219818,
-0.5675746202468872,
0.06728129088878632... |
Objects are, by their nature, structured data. The object graph and, implicitly, its structure, gives it meaning. Serialising a whole object graph in a naive way would result into a large blob which would be difficult to work with, and exclude certain workflows - such as reading just subsets of the graph, or individual... | [
-0.20604565739631653,
-1.09346604347229,
0.4322968125343323,
-0.10454803705215454,
-0.4841983914375305,
0.24058637022972107,
0.4376581609249115,
-0.7177636027336121,
0.1624128669500351,
0.4148983359336853,
-0.3589731752872467,
-0.5997585654258728,
-0.40641921758651733,
0.34866002202033997,... |
Speckle solves this structural impedance mismatch by deconstructing an object into its individual constituent parts during the process of serialisation. These individual objects are then sent for storage to any given transports. | [
-0.46733835339546204,
-0.14391247928142548,
0.3816148638725281,
0.1194133311510086,
-0.5084362030029297,
0.4212586581707001,
0.7369661927223206,
-0.5821166634559631,
0.26294898986816406,
0.5749433636665344,
-0.5581280589103699,
0.19019567966461182,
0.027516821399331093,
-0.1715342998504638... |
Each object, when serialised, gets a unique id which is generated by hashing its value. This means that all objects are immutable: if they change throughout their lifecycle, they get a new hash. | [
-0.02661644108593464,
-0.6018253564834595,
0.5147374868392944,
-0.1982347071170807,
-0.5888199806213379,
0.33891579508781433,
0.4373238682746887,
-0.7018171548843384,
0.1847531497478485,
0.3332689106464386,
-0.42193976044654846,
-0.2826620042324066,
-0.6542225480079651,
0.10910914093255997... |
These object hashes are also used to assemble, for each individual object, its internal graph references. What this means, essentially, is that each Speckle object contains the information needed for reconstructing its full graph of descendants - alongside its own data. | [
-0.40562817454338074,
-0.04495320841670036,
0.542108416557312,
-0.2470359057188034,
-0.5739538669586182,
0.6379203200340271,
0.42827707529067993,
-0.6176859736442566,
0.313347190618515,
0.5748511552810669,
-0.3009249269962311,
-0.2687145471572876,
-0.3450852930545807,
-0.09466050565242767,... |
At the heart of `git` there are two types of objects: trees and blobs. Blobs represent the files themselves, and trees represent the file structure. **Objects in Speckle are, essentially, both a tree and a blob at the same time** - the "blob" being the value of the object itself, and the tree representing its object gr... | [
-0.14963622391223907,
-0.9034383296966553,
0.40913283824920654,
-0.22557680308818817,
-0.5360636711120605,
1.102604627609253,
0.22177733480930328,
-0.5749787092208862,
0.6570068597793579,
0.334393173456192,
-0.47921767830848694,
-0.062177810817956924,
-0.8334012627601624,
-0.34688967466354... |
When deserialising data, Speckle reconstructs it at the same time. This means that data can reside and make use of the upsides of storage systems such as relational databases, while at the same time, developers are not constrained as to how they structure it and can continue working with it freely inside their applicat... | [
-0.4803341329097748,
-0.4236752986907959,
0.3285520374774933,
0.2755928039550781,
-0.51693195104599,
0.7270223498344421,
0.2267531454563141,
-0.7475266456604004,
0.5644871592521667,
0.6367127895355225,
-0.4022549092769623,
-0.14270442724227905,
-0.24557562172412872,
0.18635058403015137,
... |
Another important note is that Speckle uses JSON as the native serialisation format for the object "blobs". JSON is a format that is widely used and has plenty of tooling in various languages, and, most importantly, it is both **machine and human readable.** | [
-0.26978546380996704,
-0.36325803399086,
0.24944834411144257,
0.43483272194862366,
-0.4640253186225891,
0.699986457824707,
-0.07234843820333481,
-0.9252065420150757,
0.48993468284606934,
0.7146878838539124,
0.08733969181776047,
-0.48514628410339355,
-0.4982253313064575,
0.24999916553497314... |
This post covered the low level building blocks of Speckle and how they work together. The key points and concepts that we've covered are: | [
-0.5870599150657654,
-0.4433322846889496,
0.8923289179801941,
0.05062260851264,
-0.285839706659317,
0.6314787268638611,
0.4539986252784729,
-0.8204550743103027,
0.532412052154541,
0.7342549562454224,
-0.13514740765094757,
-0.43499356508255005,
-0.38518357276916504,
-0.4574912488460541,
-... |
- How apps interact with Speckle, and how data can be translated between them: either directly, or through Speckle kits.
- How data gets serialised, and subsequently stored & how these two layers interact.
- How Speckle treats objects and decomposes them into their constituent parts.
- What Transports are, and why t... | [
-0.6416298747062683,
-0.3554127514362335,
0.49026715755462646,
0.3628218173980713,
0.023687103763222694,
0.43981853127479553,
0.20501366257667542,
-1.1689174175262451,
0.47820988297462463,
0.7693778276443481,
-0.5135151147842407,
-0.29905906319618225,
-0.1660008728504181,
-0.39154323935508... |
This post was originally part of the Making Speckle 2.0 series of posts on the community forum, it's been adapted as part of our dev docs. Check out [the original on our forum](https://speckle.community/t/core-2-0-the-base-object/782)! | [
-0.2834632992744446,
-0.4187021255493164,
0.36108070611953735,
0.18776124715805054,
-0.6917431354522705,
0.00990348681807518,
0.013496944680809975,
-0.6068990230560303,
0.7198204398155212,
1.0082896947860718,
-0.3595264256000519,
-0.3994298279285431,
-0.45486292243003845,
-0.50590717792510... |
The Base object is one of the smallest, yet most critical parts of our SDKs as it influences the serialisation & deserialisation process, hashing speed & correctness, overall performance, and how elements are defined in the Speckleverse. It's the building block of Speckle. | [
-0.7480957508087158,
-0.5442013144493103,
0.2969292402267456,
-0.20677708089351654,
-0.6403803825378418,
0.2995073199272156,
0.24437600374221802,
-0.4512441158294678,
-0.05548661947250366,
0.6908453106880188,
-0.302615225315094,
-0.17108525335788727,
-0.3359690010547638,
-0.109837986528873... |
In this page we'll describe what it is and how to use it in more detail. Please note that currently examples are only in C#, equivalent implementations are available in our other SDKs. | [
-0.5044956207275391,
-0.5113763809204102,
0.34927308559417725,
0.19530577957630157,
-0.39259248971939087,
0.18409503996372223,
0.4318206012248993,
-0.22870667278766632,
0.5192793011665344,
0.5925852656364441,
-0.8316376209259033,
-0.9180339574813843,
0.07169383764266968,
-0.454831033945083... |
The base object class (actually called `Base`) is the foundation of all data being transferred with Speckle. Any custom data structure that you want to transfer via Speckle should inherit from it. You can read more on creating your own schemas in the [kits section](/dev/kits) | [
-0.5947811603546143,
-0.4555947184562683,
0.12317337840795517,
-0.1331927329301834,
-0.28147855401039124,
0.49929821491241455,
0.23763485252857208,
-0.511804461479187,
0.29937803745269775,
0.8421241641044617,
-0.2053772211074829,
-0.37345582246780396,
-0.49066436290740967,
-0.3267135620117... |
`Base` inherits from a C# dynamic object. This allows us to be strongly typed when needed, but as well fall back elegantly on dynamic properties when we want to, or need to. Imagine a crossover between a JavaScript object and a strongly defined C# class. It's quite cool! Furthermore, this removes some of the friction i... | [
-0.3261924386024475,
-0.6998232007026672,
0.15620067715644836,
0.09313186258077621,
0.06767016649246216,
1.002002477645874,
-0.06613469868898392,
-0.7396832704544067,
-0.10167048871517181,
0.2693604826927185,
-0.04874780774116516,
-0.293712317943573,
-0.29642254114151,
-0.44556039571762085... |
```csharp
// Simplified class definition:
public class Base {
public string id { get; set; } // this is the unique hash, generated from the serialized object
public string applicationId { get; set; } // a secondary (optional) identity value, for example the host application object id
public string speckle_t... | [
-0.3239556849002838,
-0.10324109345674515,
0.04157138988375664,
0.10857687145471573,
-0.28357744216918945,
0.6535009741783142,
0.21604938805103302,
-0.4716452956199646,
0.11297453194856644,
0.3468071222305298,
-0.1822015643119812,
-0.7077551484107971,
-0.34712639451026917,
-0.4593134224414... |
Here's how you would use a "raw" `Base` object as a custom data structure. It's essentially just a dynamic object at heart. | [
-0.23783902823925018,
-1.0743926763534546,
0.0959445908665657,
-0.287699431180954,
-0.38573402166366577,
0.5785919427871704,
0.026432793587446213,
-0.12002693861722946,
0.4491683542728424,
0.49650001525878906,
-0.6966366767883301,
-0.671795129776001,
0.2762172222137451,
-0.0379576832056045... |
// setting properties using dot notation requires cast to dynamic
((dynamic)myObject).myNewProperty = "foo"; | [
-0.20091542601585388,
-0.7841256856918335,
0.0028629284352064133,
0.21585480868816376,
-0.31693586707115173,
0.6751978397369385,
0.3224385678768158,
-0.2832421660423279,
0.4325995147228241,
0.34180763363838196,
-0.15337014198303223,
-0.17445111274719238,
-0.6928649544715881,
-0.33004015684... |
You can define singular objects like this - like something representing a built element; alternatively you can define your own object collection types based on the source application you're working from. | [
-0.33536455035209656,
-0.4164242744445801,
0.3917810022830963,
0.16552232205867767,
-0.14583353698253632,
0.35330936312675476,
0.2959015965461731,
-0.21207332611083984,
0.3378435969352722,
0.6987162232398987,
-0.6454768776893616,
-0.6071904897689819,
-0.110353983938694,
-0.0287660136818885... |
```csharp
var myCommit = new Base();
myCommit["RhinoLayer-A"] = new List<Base>() { ... };
myCommit["RhinoLayer-B"] = new List<Point>() { ... };
myCommit["RhinoLayer-A:RhinoLayer-C"] = new List<String>() { ... };
``` | [
-0.16639947891235352,
-0.1576629877090454,
-0.0033452080097049475,
0.17156918346881866,
-0.1889866292476654,
0.5461118221282959,
-0.1140669584274292,
-0.5380643010139465,
0.3925859332084656,
0.8244230151176453,
-0.3394543528556824,
-0.48549342155456543,
-0.8768635988235474,
-0.642917156219... |
:raised_hand: All property names will need to be serializable and some characters prevent this. With dot notation this is more obvious, but using the dictionary method, invalid prop names will only show up at serialization time. There is a helper function `IsPropNameValid` within `DynamicBase` that you could use to che... | [
-0.30998432636260986,
-1.1076765060424805,
0.11972558498382568,
0.2720308303833008,
-0.2608993351459503,
0.3682805895805359,
0.07476125657558441,
-0.31015896797180176,
0.3250080943107605,
0.5428875684738159,
-0.4825453758239746,
-0.5300760269165039,
-0.695894181728363,
0.008671018294990063... |
Of course, you can define custom classes that inherit from `Base` and define strongly typed properties in there, which can then be accessed as usual; these can easily coexist alongside dynamic ones. | [
-0.8153537511825562,
-0.792434573173523,
0.27012914419174194,
0.06405876576900482,
0.03025047481060028,
0.8971238136291504,
-0.14626047015190125,
-0.7960731983184814,
0.486344575881958,
0.6236105561256409,
-0.22186674177646637,
-0.4530835747718811,
-0.35076814889907837,
-0.2847210168838501... |
```csharp
public class Point : Base {
// define a set of strongly typed properties
public double x { get; set; }
public double y { get; set; }
public double z { get; set; }
} | [
-0.16281184554100037,
0.040815602988004684,
-0.13975492119789124,
0.46842724084854126,
-0.07530546933412552,
0.5351768136024475,
0.0884200856089592,
-0.3756188750267029,
0.07231690734624863,
0.3984137177467346,
0.360942542552948,
-0.8463053703308105,
-0.4364147186279297,
-0.984962940216064... |
// Strongly typed props behave as you would expect them to:
var myPt = new Point();
myPt.x = 10;
var whatIsX = myPt.x; | [
-0.10493753105401993,
-0.674170732498169,
0.5416404604911804,
0.40883535146713257,
-0.276806116104126,
-0.044358719140291214,
0.38658764958381653,
-0.3649355471134186,
0.5636504888534546,
0.3694944977760315,
-0.1338159441947937,
-0.5777847766876221,
-0.5185961127281189,
-0.2043581753969192... |
// With a dynamic property, things are a bit more verbose, but still manageable:
((dynamic)myPt).bar = "baz";
var whatIsBar = ((dynamic)myPt).bar as string; // "baz" | [
-0.1953330934047699,
-0.9961114525794983,
0.08941952884197235,
0.07118534296751022,
-0.20399732887744904,
0.9292113184928894,
-0.28947076201438904,
-0.3214688301086426,
0.6830490231513977,
0.3074394166469574,
-0.5564931035041809,
-0.6723542809486389,
-0.3697909712791443,
-0.270037353038787... |
// Alternative syntax, if you actually pass the property name at runtime:
var whatIsBar = myPt["bar"] as string; // "baz" | [
-0.34124696254730225,
-0.7080695033073425,
0.09620039165019989,
-0.19187773764133453,
-0.3000805675983429,
0.5061537623405457,
-0.15813980996608734,
0.11133746802806854,
0.32570764422416687,
0.8176321387290955,
-0.3419851064682007,
-0.7223286628723145,
-0.17899583280086517,
-0.585402786731... |
::: tip NOTE
Setting a dynamic property that overlaps with a strongly typed one will actually just set the strongly typed one 🙂
::: | [
-0.13372191786766052,
-0.6620796322822571,
-0.000755798420868814,
0.5618242025375366,
-0.424081951379776,
0.8869503736495972,
0.04383797198534012,
-0.9754711389541626,
0.694047749042511,
0.4327305853366852,
0.09000255167484283,
-0.23541320860385895,
-0.48225900530815125,
-0.949192523956298... |
All kit object models are inheriting from the `Base` object class for their object definitions. This ensures that Speckle will be able to transport them! | [
-0.35076937079429626,
-0.07185742259025574,
0.31720370054244995,
0.11434917896986008,
-0.3275538384914398,
0.511501669883728,
0.4259394705295563,
-0.770699679851532,
0.013713942840695381,
0.7864428162574768,
-0.3847181797027588,
-0.0633135512471199,
-0.5339137315750122,
-0.0784625932574272... |
When defining your dynamic `Base` object properties, you can detach them by prepending an `@` to your property name like so: | [
-0.4730566143989563,
-0.900892436504364,
-0.17532062530517578,
-0.4141649603843689,
-0.6729370951652527,
1.061851978302002,
0.06140740588307381,
-0.4489515423774719,
0.2564036250114441,
0.3675217926502228,
-0.5992114543914795,
-0.4090003967285156,
-0.5954998135566711,
-0.37411555647850037,... |
```csharp
public class Foo : Base { }
public class Bar : Base { } | [
-0.23957476019859314,
0.2558157742023468,
-0.26228418946266174,
0.0993981808423996,
-0.6740736365318298,
0.8042047023773193,
-0.025023078545928,
-0.26761314272880554,
-0.18680690228939056,
0.45833685994148254,
0.2719229757785797,
-0.6072493195533752,
-0.3909948170185089,
-0.780364632606506... |
Detaching a property stores that property value as a reference to another object. Why do this? Since it's possible to nest your `Base` inherited class objects, detaching any properties that may be assigned an object used by other objects keeps your data squeaky clean. Since detached objects are only serialized once dur... | [
-0.5529276728630066,
-0.6206911206245422,
-0.257553368806839,
-0.23735088109970093,
-0.566988468170166,
0.34356674551963806,
0.1556248515844345,
-1.0057880878448486,
0.00439393799751997,
0.3296862840652466,
-0.3991048038005829,
0.04455796256661415,
-0.434427410364151,
-0.16142047941684723,... |
For a more in depth rundown of detachables and examples, check out the [decomposition API section](/dev/decomposition). | [
-0.7047024965286255,
-0.7680463194847107,
0.44264307618141174,
-0.0433545857667923,
-0.31636154651641846,
0.7960093021392822,
0.5139353275299072,
-0.04993646591901779,
0.5001927614212036,
0.343919575214386,
-1.058796763420105,
-0.6273090243339539,
-0.27300477027893066,
-0.04882293194532394... |
As you may or may not know, objects in Speckle are immutable. That means that if you change a property of one, it essentially gets a whole new identity; it's a whole new object (as far as the storage layer is concerned). This immutability is enforced through unique hashes that are dependent on the object's properties. | [
-0.22966410219669342,
-0.45821818709373474,
0.26953911781311035,
0.11818351596593857,
-0.52199387550354,
0.7252442836761475,
0.21878071129322052,
-1.0084123611450195,
0.5536954998970032,
0.7877190113067627,
-0.1999179720878601,
0.12214356660842896,
-0.7858712077140808,
-0.23836396634578705... |
As a developer, you don't need to care about all this 🙌. Our SDKs takes care of correctly setting the hash of an object, at the correct time: at the end of the serialisation process. There's another purely cosmetic change that we made: the hash is now stored in an field called `id`. Why? Mostly so it's clear that it's... | [
-0.30190515518188477,
-0.18819479644298553,
0.468067467212677,
-0.027836520224809647,
-0.5619504451751709,
-0.01016855239868164,
0.2585408091545105,
-0.5816366672515869,
0.12241386622190475,
0.41953402757644653,
-0.43089649081230164,
-0.8008276224136353,
-0.18134017288684845,
-0.0312485080... |
What about operations that are dependent on hashes? From our analysis of existing programmatic usage, you rarely really need the hash of an object before serialising (and, implicitly, storing it somewhere). When retrieving objects from "somewhere" (more on this in another post), the hash already exists, so you can chec... | [
-0.41495952010154724,
-0.4369792342185974,
0.6796942949295044,
-0.02332422137260437,
-0.2411261349916458,
-0.15458746254444122,
0.09758218377828598,
-0.7435590028762817,
0.18771493434906006,
0.5681424140930176,
-0.253242552280426,
-0.48548340797424316,
-0.6729320287704468,
-0.1930968016386... |
```csharp
var x = myObject.id; // will be populated only if this object has been previously serialised!
``` | [
0.21814684569835663,
0.10136250406503677,
0.2391529381275177,
0.20705148577690125,
-0.5081349015235901,
0.6034431457519531,
0.16046574711799622,
-0.17876946926116943,
0.07877061516046524,
0.5896172523498535,
-0.20532798767089844,
-0.7153725028038025,
-0.18389227986335754,
-0.64350199699401... |
If you really need the hash (id!) before serialising it, don't panic! You can still generate it - nevertheless we've put that behind an explicit function call so you, as a developer, are aware of the extra cost that you will be incurring. Here's how the signature of that function looks like: | [
-0.5667665600776672,
-0.22426632046699524,
0.537221372127533,
0.17877547442913055,
-0.7591252326965332,
-0.02949291467666626,
0.34727048873901367,
-0.7451820373535156,
0.2665961682796478,
0.4281507730484009,
-0.5943318009376526,
-0.5090436935424805,
-0.31654438376426697,
-0.123150348663330... |
```csharp
/// <summary>
/// Gets the id (a unique hash) of this object. ⚠️ This method fully serializes the object, which in the case of large objects (with many sub-objects), has a tangible cost.
/// <para><b>Hint:</b> Objects that are retrieved/pulled from a server/local cache do have an id (hash) property pre-pop... | [
-0.257682740688324,
-0.5496441721916199,
0.17086774110794067,
-0.03181662783026695,
-0.5240547060966492,
0.39859792590141296,
-0.03508825972676277,
-0.6121385097503662,
0.08643695712089539,
0.30888667702674866,
-0.051409877836704254,
-0.67401522397995,
-0.20582184195518494,
-0.570878267288... |
Noticed that `decompose` flag? You're sharp - check out the [decomposition API section](/dev/decomposition) for more. | [
-1.1029654741287231,
-0.8391562104225159,
0.5905325412750244,
-0.22530634701251984,
-0.6756895780563354,
0.47939029335975647,
0.2202501893043518,
0.06117580085992813,
0.7505786418914795,
0.7887112498283386,
-1.0075442790985107,
-1.0721379518508911,
-0.32008448243141174,
0.12366997450590134... |
Our SDKs come with our in-house Objects Kit comprised of `Base` inherited classes for your standard AEC needs. The core geometry kit contains all your basic elements like Points, Lines, Curves, and Breps, which are then used as properties for our more extensively defined BIM, Structural, and Civil elements. Read more i... | [
-0.8213223218917847,
-0.6290078163146973,
0.4309181869029999,
-0.029936768114566803,
-0.029842577874660492,
0.5683661699295044,
0.5951045751571655,
-0.6405357718467712,
0.10748960077762604,
0.7827918529510498,
-0.5661858320236206,
-0.9246147871017456,
0.025537215173244476,
-0.1519207656383... |
In addition to the `Base` properties in our model above, you may also encounter certain common properties when exploring your data in our web viewer. The objects in our Objects Kit come with properties that we use to display them in our frontend: | [
-0.7824417352676392,
-0.5820881128311157,
0.15151263773441315,
-0.22232432663440704,
-0.1771593987941742,
-0.00291669019497931,
0.19170120358467102,
-0.6660728454589844,
0.23735396564006805,
0.7129166722297668,
-0.6062572002410889,
-0.7555548548698425,
-0.21138989925384521,
-0.389549642801... |
```csharp
// Class definition with additional display properties
public class Foo : Base {
[DetachProperty]
public List<Mesh> displayValue { get; set; } // Mesh objects that represent the geometry of this Base object, e.g. used to render surfaces, or solid objects in our viewer
// or
[DetachProperty]
public... | [
-0.6041550636291504,
-0.14374300837516785,
-0.016877666115760803,
-0.22796690464019775,
-0.1370617151260376,
0.47639000415802,
0.17211882770061493,
-0.3369201123714447,
0.009081246331334114,
0.26574984192848206,
-0.018163371831178665,
-0.17741021513938904,
-0.24687722325325012,
-0.60930699... |
The `displayValue` property is a **special property** within the Objects kit. It is common for classes inheriting `Base` to represent complex, conceptual, or domain specific objects.
The `displayValue` property can be used to provide a **geometric representation** to help display the object in applications that don't ... | [
-0.6792758703231812,
-0.27891993522644043,
0.013990762643516064,
-0.014881196431815624,
-0.2783341109752655,
0.43678468465805054,
0.5177541971206665,
-0.4252253770828247,
0.4074481427669525,
0.172519713640213,
-0.23799216747283936,
-0.1373864859342575,
-0.5747848749160767,
-0.6175990104675... |
For example, When receiving **BIM types** like `Wall`, `Floor`, `Beam`, etc into a **non-BIM application** like Rhino, Unity, or our web viewer, these applications **have no way of rendering these elements natively**. The `displayValue` property represents **fallback** geometry, that will automatically be used by appli... | [
-0.6531229019165039,
-0.3460073173046112,
0.07330724596977234,
0.03330289199948311,
-0.30513736605644226,
0.38851797580718994,
0.6311231255531311,
-0.3476453721523285,
0.3084873855113983,
0.550349235534668,
-0.3183850646018982,
-0.5684288144111633,
-0.5142655968666077,
-0.334856778383255,
... |
The `displayValue` property is expected to be either an **object inheriting `Base`** or a **`List` of objects inheriting `Base`**.
Ideally, these types **should be simple geometry types** like `Mesh` or `Polyline` as these can be converted in all (or almost all) receiving applications (However, this rule isn't enforce... | [
-0.6515859961509705,
-0.36394795775413513,
0.06836340576410294,
-0.0006326702423393726,
-0.37923839688301086,
0.14095956087112427,
0.4179007411003113,
-0.40766555070877075,
0.18469414114952087,
0.530004620552063,
-0.3335117697715759,
-0.4202687442302704,
-0.863115668296814,
-0.417596518993... |
Whether to represent Layers, Categories, Tags, Collections, Groups, or hierarchical containers,
it is common to see a natural grouping of objects within a 3D model.
The `Collection` type provides a unified way to represent hierarchical collections of Speckle objects
in a queryable, filterable way and is useful for i... | [
-0.8298238515853882,
-0.20833981037139893,
0.016707496717572212,
0.017875779420137405,
-0.5756237506866455,
0.5622035264968872,
0.6256227493286133,
-0.6167758703231812,
0.3399801552295685,
0.6833478808403015,
-0.1762576550245285,
-0.44365134835243225,
-0.49552154541015625,
0.16316632926464... |
A collection object only has three properties (in addition to those inherited from the `Base` Speckle object)
and is completely kit/domain agnostic. | [
-0.6450402736663818,
-0.3216460347175598,
-0.0031178195495158434,
0.08190853148698807,
-0.43168017268180847,
0.5723332762718201,
0.16874448955059052,
-0.805659294128418,
0.5564360618591309,
0.842024028301239,
-0.47862714529037476,
-0.21749262511730194,
-0.5687991380691528,
-0.2070244848728... |
> `name` - Any (non-empty) human-readable `string` name, one not necessarily unique.
>
> `collectionType` - Any `string` value describing the type of collection, used for convenience, and specific interop.
>
> `elements` - A `List<Base>` representing child objects, may include nested `Collection` objects. | [
-0.6467355489730835,
-0.4587422311306,
-0.12717491388320923,
-0.36382073163986206,
-0.4528730809688568,
0.7344223260879517,
0.2260475605726242,
-0.363892138004303,
0.20373694598674774,
0.47927388548851013,
-0.7229044437408447,
-0.29508817195892334,
-0.8529338836669922,
0.19914838671684265,... |
Our new front-end (fe2) is designed to display `Collection` in the scene explorer. | [
-0.829314112663269,
-0.07239421457052231,
0.27179768681526184,
0.029012421146035194,
-0.40576210618019104,
0.545056164264679,
0.7603814601898193,
-0.5732518434524536,
0.6345839500427246,
0.23309661448001862,
-1.2453696727752686,
-0.2894185185432434,
-0.4205862879753113,
0.17744196951389313... |
Suppose we look at how Collection objects are used inside Speckle versions.
We see within the Collection’s `elements` property; we can expect any objects to be nested, including sub-collections. | [
-0.5409582853317261,
0.3001144528388977,
0.08271551877260208,
-0.548815906047821,
-0.8047541975975037,
0.6368455290794373,
0.30956774950027466,
-0.8607518672943115,
0.27684301137924194,
0.5392588376998901,
-0.6448506712913513,
-0.15086673200130463,
-0.5899202823638916,
0.08367384970188141,... |
Importantly, however, we only see `Collection` objects nested under other `Collections`.
Unlike other speckle objects which may form any [directed acyclic graph](https://en.wikipedia.org/wiki/Directed_acyclic_graph) structure,
Collections must be in a true directed tree structure. | [
-0.3042641878128052,
-0.3272049129009247,
0.47365841269493103,
-0.17019274830818176,
-0.6251386404037476,
0.7091717720031738,
0.43739208579063416,
-0.8235053420066833,
0.48312848806381226,
0.6932202577590942,
-0.8922447562217712,
-0.5356872081756592,
-0.4447663128376007,
0.1222002729773521... |
> 
>
> Diagram of collections within a Speckle commit, illustrating collections can contain both sub-collections and other objects under the `elements` property. While the `elements` property of geometry objects do not contain Collections | [
-0.49168068170547485,
-0.2758844196796417,
0.127642422914505,
-0.31694772839546204,
-0.7370632290840149,
0.818220853805542,
0.41415533423423767,
-0.6057823896408081,
0.8318020701408386,
0.46343329548835754,
-1.0213563442230225,
-0.6259166598320007,
-0.5302408337593079,
-0.05478968843817711... |
With the exception of the Revit connector, connectors will send `Collection`s from the layer/tag/collection structure. | [
-0.6769348978996277,
-0.22939017415046692,
0.24369773268699646,
-0.10847504436969757,
-0.45848867297172546,
0.18163399398326874,
0.6889811754226685,
-0.48275551199913025,
0.31952592730522156,
0.9890183210372925,
-1.1518596410751343,
0.044550832360982895,
-0.29142245650291443,
-0.1516546458... |
| Rhino | Blender | Sketchup |
| -- | -- | -- |
|  |  | |# Writing your own connector (... | [
-1.0842418670654297,
-0.191038116812706,
0.38441088795661926,
0.2951992154121399,
-0.6497846841812134,
0.425841748714447,
0.6744709610939026,
-0.1879672259092331,
0.655373752117157,
0.9452905654907227,
-0.6079891324043274,
-0.1602630764245987,
-0.5383342504501343,
0.0331786572933197,
-0.... |
Have a dream for a connector that doesn't yet exist? We have all the tools ready for you to start developing your own! | [
-1.1455706357955933,
-0.5232608914375305,
0.8178910613059998,
0.15747764706611633,
-0.4657492935657501,
0.24300460517406464,
0.6800345778465271,
-0.1648806631565094,
0.9164217114448547,
0.2682197690010071,
-1.493245244026184,
-0.2278377115726471,
-0.14277806878089905,
-0.23965007066726685,... |
We are very enthusiastic about community connectors and would love to help you bring them to life. To get started, check out the guide below. Feel free to reach out with any questions or calls for more contributors to the project on our [forum](https://speckle.community/). | [
-0.9047045707702637,
-0.1875273585319519,
0.7481250762939453,
0.31081026792526245,
-0.43149352073669434,
0.3282797932624817,
0.17075815796852112,
-0.23592431843280792,
0.9703778028488159,
0.392821729183197,
-0.5257757902145386,
-0.5070133209228516,
-0.5199605226516724,
-0.04385363310575485... |
Before you begin writing your own connector, we encourage you to follow the steps below: | [
-0.8563722372055054,
-0.2370125651359558,
1.0552905797958374,
0.3940349519252777,
-0.20192308723926544,
-0.23433919250965118,
0.5534780621528625,
-0.09463817626237869,
0.4751455783843994,
0.8938277363777161,
-1.0884968042373657,
-0.4076192378997803,
-0.04528592899441719,
0.2028965204954147... |
1. **make sure you are comfortable** writing plugins for the host application you are planning to target, otherwise the guide below will not be of great help 😅
3. **post on the [community forum](https://speckle.community/)** announcing what you are planning to develop and how
4. **consider** that if you make your co... | [
-1.019704818725586,
-0.07012207806110382,
0.4431731104850769,
0.5317444205284119,
-0.4971209168434143,
-0.03058244287967682,
0.18444086611270905,
-0.4611186683177948,
0.5891772508621216,
0.3937320411205292,
-0.5620843768119812,
-0.5111707448959351,
-0.25838589668273926,
0.09603150188922882... |
- **a User Interface**
- **bindings** between the host application and the UI
- **custom logic** specific to the host application (for selecting elements, saving senders and receivers in the project file etc)
- **a converter** to convert between the host application and Speckle geometry and BIM elements | [
-0.9910890460014343,
-0.43626198172569275,
0.27895036339759827,
0.15680770576000214,
0.09321262687444687,
0.033613141626119614,
0.6826372742652893,
-0.09860117733478546,
0.39898258447647095,
1.028177261352539,
-0.3312976062297821,
-0.17510324716567993,
0.08212791383266449,
-0.3746947348117... |
For the purpose of this tutorial, we'll be using a user interface called [DesktopUI](/user/ui) currently in use by our Revit, Rhino, AutoCAD and Civil 3D connectors. But you can of course create your own or use whatever the host application you are integrating with provides - that's the case of visual programming softw... | [
-1.1035943031311035,
-0.58549565076828,
0.37099748849868774,
0.05036182329058647,
-0.05646902322769165,
0.11309672892093658,
0.7827908396720886,
-0.07454326003789902,
0.2881803810596466,
0.7154000401496887,
-0.6053382754325867,
-0.35172927379608154,
0.14238189160823822,
0.23223255574703217... |
To get started, create a C# project in your IDE of choice by following the conventions and requirements for writing plugins for the host application you are targeting. In most cases you'll be creating a .NET Framework class library project. | [
-0.8363339900970459,
0.00675464142113924,
0.22789236903190613,
0.16559718549251556,
0.10875401645898819,
0.5188422203063965,
0.5171104073524475,
-0.19193921983242035,
0.5300498008728027,
0.3617282807826996,
-0.2695424258708954,
-0.5145618915557861,
0.0415942445397377,
-0.08751123398542404,... |
To be consistent with other Speckle connectors you should name your project `ConnectorAPP_NAME`, set the Assembly name to `SpeckleConnectorAPP_NAME` and the namespace to `Speckle.ConnectorAPP_NAME` where `APP_NAME` is the name of your host application (eg Tekla, Etabs...). | [
-0.582213282585144,
0.10156030207872391,
0.21152882277965546,
0.6972275972366333,
-0.5351820588111877,
0.42761436104774475,
0.5572320222854614,
-0.38641175627708435,
0.7945261001586914,
0.3884541094303131,
-0.47701919078826904,
-0.23549968004226685,
-0.7455694675445557,
0.08264891058206558... |
The minimum supported .NET Framework for using our .NET SDK is **4.6.1** | [
-0.9196064472198486,
0.49069175124168396,
-0.28250017762184143,
0.6895506381988525,
-0.40950721502304077,
-0.3933156728744507,
0.9076579213142395,
-0.5631102323532104,
0.31617271900177,
0.9434467554092407,
-0.734600305557251,
-0.6765747666358948,
-0.08390261977910995,
0.34874993562698364,
... |
Then you can proceed to add the following packages from NuGet: | [
-0.7817565202713013,
0.3559727370738983,
0.22533054649829865,
0.9397364258766174,
-0.319052517414093,
0.43329256772994995,
0.09330573678016663,
-0.32272082567214966,
0.35432136058807373,
0.9878711104393005,
-0.23703567683696747,
-0.2934589385986328,
-0.1933886706829071,
-0.0582910887897014... |
By installing these packages,`Speckle.Core` and other packages will be also added automatically. | [
-0.8014182448387146,
0.213469460606575,
0.25700852274894714,
0.6219797730445862,
-0.42632153630256653,
0.4006822407245636,
0.07715354859828949,
-0.680084764957428,
0.7404775023460388,
0.8664880990982056,
-0.5151615738868713,
-0.18416525423526764,
-0.5764642357826233,
-0.1996717005968094,
... |
Our DesktopUI is written using [Avalonia](https://avaloniaui.net/), a .NET open source framework for cross-platform UIs.
You can play around with a standalone version of it by opening the solution in `speckle-sharp/DesktopUI2/DesktopUI2.sln`.
Assuming the host application you are integrating with provides a way to la... | [
-0.5830376148223877,
-0.3988920748233795,
0.516341507434845,
0.36306172609329224,
0.06493733078241348,
0.17579784989356995,
0.19121301174163818,
-0.2390935719013214,
0.8191579580307007,
0.45196810364723206,
-0.7099931240081787,
-0.4892512261867523,
0.11377525329589844,
-0.2361009567975998,... |
public static AppBuilder BuildAvaloniaApp() => AppBuilder.Configure<DesktopUI2.App>()
.UsePlatformDetect()
.With(new SkiaOptions { MaxGpuResourceSizeBytes = 8096000 })
.With(new Win32PlatformOptions { AllowEglInitialization = true, EnableMultitouch = false })
.LogToTrace()
.UseReactiveUI(); | [
-0.6364403963088989,
-0.467402845621109,
0.007640189956873655,
0.5884577631950378,
-0.31620991230010986,
0.07392917573451996,
-0.06867492944002151,
-0.31527283787727356,
0.0516241118311882,
0.41877803206443787,
-0.17563307285308838,
-0.09292449057102203,
-0.23906445503234863,
-0.2111863046... |
public static void CreateOrFocusSpeckle()
{
if (MainWindow == null)
{
BuildAvaloniaApp().Start(AppMain, null);
} | [
-0.7250089049339294,
-0.6156322360038757,
0.4007440507411957,
0.48489969968795776,
-0.3289564549922943,
0.1844363659620285,
0.1613769382238388,
-0.3124072253704071,
0.537803590297699,
0.6994038224220276,
-0.6558197736740112,
-0.5258323550224304,
-0.42077869176864624,
-0.5069008469581604,
... |
private static void AppMain(Application app, string[] args)
{
var viewModel = new MainWindowViewModel();
MainWindow = new MainWindow
{
DataContext = viewModel
}; | [
-0.2135029286146164,
-0.5569981932640076,
0.27891409397125244,
0.19141826033592224,
-0.37142297625541687,
0.27672725915908813,
0.2853825092315674,
-0.03475324064493179,
-0.224328875541687,
0.9139701724052429,
-0.23762473464012146,
-0.5177772641181946,
-0.2795809805393219,
-0.45116147398948... |
You can see how it's been implemented in [Rhino](https://github.com/specklesystems/speckle-sharp/tree/c413671748d72b236c99177f8f4994ad015da6ba/ConnectorRhino/ConnectorRhino/ConnectorRhinoShared/ConnectorRhinoCommand2.cs) and [Revit](https://github.com/specklesystems/speckle-sharp/tree/c413671748d72b236c99177f8f4994ad01... | [
-0.840821385383606,
-0.3671850264072418,
0.4026961028575897,
0.22628232836723328,
-0.6628468036651611,
0.13231508433818817,
0.30716198682785034,
-0.7574836015701294,
0.3474251925945282,
0.16825278103351593,
-0.9048998355865479,
-0.573490560054779,
-0.16913458704948425,
0.041370123624801636... |
Now, in your host application, after launching the Speckle plugin you should see this window pop up: | [
-0.7880690693855286,
-0.16037225723266602,
0.47804197669029236,
0.45315054059028625,
-0.5195903182029724,
0.7661001682281494,
0.20543527603149414,
-0.14181844890117645,
1.1425777673721313,
0.9027345776557922,
-0.5837072730064392,
-0.42036935687065125,
-0.4809291362762451,
-0.24689643085002... |
The UI we just launched is quite sleek, but also a bit useless for the time being, as it doesn't have any connection to the host application; so it wouldn't know what to do when the _Send_ button is clicked, when the user wants to change selection or where to load saved streams from etc... | [
-0.5361917018890381,
-0.6340457201004028,
0.5705920457839966,
-0.08836829662322998,
-0.2937973141670227,
-0.007035107351839542,
0.30433565378189087,
-0.24564753472805023,
0.6746091246604919,
0.5698640942573547,
-1.2024486064910889,
-0.20708177983760834,
0.24315109848976135,
-0.028897060081... |
DesktopUI comes with some [DummyBindings](https://github.com/specklesystems/speckle-sharp/tree/c413671748d72b236c99177f8f4994ad015da6ba/DesktopUI2/DesktopUI2/DummyBindings.cs) so that you can test it, but let's go ahead and write our own. | [
-0.5112849473953247,
-0.739204466342926,
0.4022904932498932,
0.08711019903421402,
-0.1307319849729538,
0.11571864783763885,
0.13173136115074158,
-0.2829667627811432,
0.7290425300598145,
0.2727154791355133,
-1.0228735208511353,
-0.518523633480072,
0.13366374373435974,
-0.11191286146640778,
... |
Create a class named something like `ConnectorBindingsAPP_NAME.cs` and have it implement the abstract class `ConnectorBindings.cs`. It'll look something like the code below: | [
-0.4228290617465973,
-0.2101982980966568,
0.14898988604545593,
0.7525536417961121,
0.022761182859539986,
0.28128060698509216,
0.14302946627140045,
-0.37795335054397583,
0.7765253782272339,
0.10735579580068588,
-0.5281792283058167,
-0.34947824478149414,
-0.1999344527721405,
-0.0905647799372... |
```csharp
public class ConnectorBindingsAECApp : ConnectorBindings
{
public override string GetActiveViewName()
{
throw new NotImplementedException();
} | [
-0.04749608039855957,
-0.21338148415088654,
0.0760166123509407,
0.24623464047908783,
-0.1755397468805313,
0.12978994846343994,
0.5083729028701782,
-0.1046145036816597,
0.522502601146698,
0.7177767753601074,
-0.06199900433421135,
-0.1647430956363678,
-0.3995323181152344,
-0.4215478897094726... |
public override List<MenuItem> GetCustomStreamMenuItems()
{
throw new NotImplementedException();
} | [
-0.5581064224243164,
-0.08899325132369995,
-0.204539954662323,
-0.8017385601997375,
-0.4755708873271942,
0.14924684166908264,
0.13917116820812225,
-0.11019769310951233,
0.4296311140060425,
1.1196218729019165,
-0.6355651617050171,
-0.22356559336185455,
-0.8712329864501953,
0.011007930152118... |
public override string GetDocumentId()
{
throw new NotImplementedException();
} | [
-0.4271823763847351,
-0.5527400970458984,
0.17478515207767487,
-0.31168174743652344,
-0.5726155638694763,
0.1272549331188202,
0.271348237991333,
-0.31473663449287415,
0.1687401384115219,
0.7373125553131104,
-0.06500763446092606,
-0.6929730772972107,
-0.8160091042518616,
-0.3056601881980896... |
public override string GetDocumentLocation()
{
throw new NotImplementedException();
} | [
-0.3828001916408539,
-0.5938065648078918,
0.2598007023334503,
-0.3050924837589264,
-0.4528413414955139,
0.08560062944889069,
0.08142118901014328,
-0.5441673398017883,
0.2747841775417328,
0.9183130860328674,
-0.1026691347360611,
-0.7009876370429993,
-0.8567776083946228,
-0.41920939087867737... |
public override string GetFileName()
{
throw new NotImplementedException();
} | [
-0.34358710050582886,
-0.5937718749046326,
0.14948278665542603,
-0.2207929790019989,
-0.4612200856208801,
0.2369183748960495,
0.18866394460201263,
-0.40867745876312256,
0.19423183798789978,
0.8078617453575134,
-0.13125719130039215,
-0.4486353099346161,
-0.944218099117279,
-0.21919530630111... |
public override string GetHostAppName()
{
throw new NotImplementedException();
} | [
-0.4360026717185974,
-0.4969792664051056,
0.02594742737710476,
-0.11201787739992142,
-0.5438306331634521,
0.16769368946552277,
0.15567411482334137,
-0.3910907804965973,
0.49252545833587646,
0.9487805962562561,
0.08018036931753159,
-0.24004501104354858,
-0.889963686466217,
-0.26096621155738... |
public override List<string> GetObjectsInView()
{
throw new NotImplementedException();
} | [
-0.5679126381874084,
-0.32966774702072144,
-0.19667479395866394,
-0.4192500114440918,
-0.5476470589637756,
0.08610837906599045,
0.296253502368927,
-0.2901557683944702,
0.26148512959480286,
1.028329849243164,
-0.0394875593483448,
-0.23646345734596252,
-0.9274824261665344,
-0.335091799497604... |
public override List<string> GetSelectedObjects()
{
throw new NotImplementedException();
} | [
-0.5864838361740112,
-0.2509816884994507,
-0.16796977818012238,
-0.5463467240333557,
-0.4466150999069214,
0.3213657736778259,
0.19868795573711395,
-0.45711272954940796,
0.07422342896461487,
0.9045652747154236,
-0.17095690965652466,
-0.2627995014190674,
-0.7851460576057434,
-0.1046386659145... |
public override List<ISelectionFilter> GetSelectionFilters()
{
throw new NotImplementedException();
} | [
-0.815648078918457,
-0.16130346059799194,
-0.005030833650380373,
-0.4826650321483612,
-0.48263636231422424,
0.028526486828923225,
0.2870699465274811,
-0.30245858430862427,
0.35577628016471863,
1.1608372926712036,
-0.5437095761299133,
-0.2074717879295349,
-0.750645637512207,
-0.232829198241... |
public override List<StreamState> GetStreamsInFile()
{
throw new NotImplementedException();
} | [
-0.3785065710544586,
-0.2283916175365448,
-0.11576489359140396,
-0.6765947937965393,
-0.7153146862983704,
0.19452205300331116,
0.0014702312182635069,
-0.22486786544322968,
0.6502217650413513,
0.9594435095787048,
-0.24264630675315857,
-0.12683798372745514,
-1.044708490371704,
-0.08734031021... |
public override Task<StreamState> ReceiveStream(StreamState state, ProgressViewModel progress)
{
throw new NotImplementedException();
} | [
0.18506477773189545,
-0.2191234827041626,
0.35947248339653015,
-0.0677860900759697,
-0.4153035283088684,
0.21009162068367004,
0.3564431071281433,
-0.21799293160438538,
0.4214278757572174,
1.163291573524475,
-0.48281726241111755,
-0.032604023814201355,
-1.2038264274597168,
-0.21051128208637... |
public override void SelectClientObjects(string args)
{
throw new NotImplementedException();
} | [
-0.7389432191848755,
-0.26307713985443115,
0.01122983731329441,
-0.2699702978134155,
-0.5507020354270935,
0.08553493767976761,
0.22722914814949036,
-0.49884259700775146,
0.10270895063877106,
1.1125614643096924,
-0.11287645995616913,
-0.25316593050956726,
-0.6805788278579712,
-0.16387215256... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.