Editing Speckle
From Wiki.OSArch
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
| Latest revision | Your text | ||
| Line 1: | Line 1: | ||
| − | |||
[[File:Icon speckle 64.png]] | [[File:Icon speckle 64.png]] | ||
[https://speckle.systems/ Speckle] | [https://speckle.systems/ Speckle] | ||
| − | Speckle is an open source<ref>[https://speckle.systems/blog/opensource-aec-speckle ''Open Source in AEC & Speckle'']</ref> cloud-based data platform for AEC. It provides a method of liberating data from one platform to another in a quick, manageable, and efficient way. It works with [[Blender]], ThreeJS | + | Speckle is an open source<ref>[https://speckle.systems/blog/opensource-aec-speckle ''Open Source in AEC & Speckle'']</ref> cloud-based data platform for AEC. It provides a method of liberating data from one platform to another in a quick, manageable, and efficient way. It works with [[Blender]], ThreeJS, Rhino, Grasshopper, Excel, Unity, GSA, [[Revit]], and Dynamo. |
| − | Speckle allows you to transfer data and geometry through | + | =What it does in one line= |
| + | |||
| + | Speckle allows you to transfer data and geometry through network. It defines a common geometry language. | ||
=Use case example= | =Use case example= | ||
| Line 30: | Line 31: | ||
=Definitions/parts= | =Definitions/parts= | ||
| − | + | ==speckle kit== | |
| − | |||
«it's basically a schema and its implementations to and from a given set of software apps».<ref>[https://community.osarch.org/discussion/comment/3845/#Comment_3845 OSArch discussion]</ref> | «it's basically a schema and its implementations to and from a given set of software apps».<ref>[https://community.osarch.org/discussion/comment/3845/#Comment_3845 OSArch discussion]</ref> | ||
Documentation is available in high level version<ref>[https://speckle.systems/blog/schemas-revisited/ Dimitrie Stefanescu, ''Schemas & Standards: The BYO Approach'', Speckle blog]</ref> and more technical one <ref>[https://speckle.systems/docs/developers/object-models/ ''Schemas & Object Models (.NET)'', Speckle wiki documentation]</ref> | Documentation is available in high level version<ref>[https://speckle.systems/blog/schemas-revisited/ Dimitrie Stefanescu, ''Schemas & Standards: The BYO Approach'', Speckle blog]</ref> and more technical one <ref>[https://speckle.systems/docs/developers/object-models/ ''Schemas & Object Models (.NET)'', Speckle wiki documentation]</ref> | ||
| − | + | ==speckle-server<ref>[https://github.com/specklesystems/speckle-server speckle-server repository]</ref>== | |
| − | |||
This is the Speckle Server 2.0. It consists of two distinct parts: | This is the Speckle Server 2.0. It consists of two distinct parts: | ||
* The server application itself, which is a nodejs app exposing a GraphQL API. | * The server application itself, which is a nodejs app exposing a GraphQL API. | ||
* The frontend application, which is a static vuejs app. | * The frontend application, which is a static vuejs app. | ||
| − | + | ==PySpeckle<ref>[https://github.com/speckleworks/PySpeckle PySpeckle repository]</ref>== | |
| − | |||
A Python Speckle Client. It powers SpeckleBlender. | A Python Speckle Client. It powers SpeckleBlender. | ||
| − | + | ==SpeckleBlender<ref>[https://github.com/speckleworks/SpeckleBlender SpeckleBlender repository]</ref>== | |
| + | Speckle add-on for Blender. | ||
| − | + | License: MIT | |
=Resources= | =Resources= | ||
| Line 57: | Line 56: | ||
=References= | =References= | ||
<references /> | <references /> | ||
| − | |||
| − | |||
| − | |||
