You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Essentially the "opposite" side of the parser. Once a design has been loaded, and possible modified, write the in-memory data model back out to an ODB++ file archive.
When used as shared library, the consuming application can modify the in-memory data model directly. But for use via the REST API, REST API endpoints would need to be added to POST changes back to the library's in-memory data model. Also need endpoints to tell the library to write the file out.
serialization from memory model
POST/PUT REST endpoints
The text was updated successfully, but these errors were encountered:
nam20485
changed the title
Add ODB++ output writer
Add ODB++ output writer functionality
Feb 28, 2024
Essentially the "opposite" side of the parser. Once a design has been loaded, and possible modified, write the in-memory data model back out to an ODB++ file archive.
When used as shared library, the consuming application can modify the in-memory data model directly. But for use via the REST API, REST API endpoints would need to be added to POST changes back to the library's in-memory data model. Also need endpoints to tell the library to write the file out.
The text was updated successfully, but these errors were encountered: