> On 5 Dec 2017, at 16:26, Juan Sanchez wrote:
>
> Thanks for doing this.
>
> Will it be possible for commands sent to the API to be serialized to a
> GEO file?
For the most part, yes: with the built-in cad kernel you can serialize to a
.geo file (with gmsh::write("file.geo")); for opencasca
Dnia poniedziałek, 4 grudnia 2017 12:53:06 CET Christophe Geuzaine pisze:
> See demos/api/README.txt : basically, you need to either explicitly build
> the shared Gmsh libraries (cmake -DENABLE_BUILD_SHARED=1 ..; make), or the
> dynamic Gmsh app, which will build the shared libraries (cmake
> -DENA
Thanks for doing this.
Will it be possible for commands sent to the API to be serialized to a
GEO file? This is so the structure can be programmatically defined in
a scripting language, and have the result sent to someone without the
API. In addition, is it possible to view the results debugged
> On 4 Dec 2017, at 09:40, Marek Wojciechowski wrote:
>
> Dnia niedziela, 3 grudnia 2017 09:19:27 CET Christophe Geuzaine pisze:
>> To achieve these goals the API
>>
>> - is purely functional
>> - only uses basic types from the target language (C++, C or Python)
>> - is automatically generated
Dnia niedziela, 3 grudnia 2017 09:19:27 CET Christophe Geuzaine pisze:
> To achieve these goals the API
>
> - is purely functional
> - only uses basic types from the target language (C++, C or Python)
> - is automatically generated from a master API description file
> - is fully documented
Great
Dear all,
One of our main goals for the next versions of Gmsh is the release of a stable
Application Programming Interface (API), allowing users/developers to easily
embed Gmsh (as a library) in their own codes. The design goals for this API are
the following: the API should
- allow to do eve
