Patrik Meijer

That would be [commit-objects](https://editor.webgme.org/api/projects/demo/FiniteStateMachine/commits?n=1) and [core data-blobs](https://editor.webgme.org/api/projects/demo/FiniteStateMachine/branches/master/tree/) There's nothing inherent that restricts the REST API from exposing such end-points though.

[Project.makeCommit](https://editor.webgme.org/docs/source/Project.html#makeCommit__anchor). The commit-object is created (and later inserted) as part of invoking makeCommit. The core-data-blobs are generated at [Core.persist](https://editor.webgme.org/docs/source/Core.html#persist__anchor). In later versions these objects are actually diffs generated based on...

@brollb Can you specify what you mean by "project load" event?

To have a common language when we interact, can we agree on calling these connections?

This seems a bit specific, couldn't you implement this with a simple plugin that you invoke from one of your UI-pieces?

Andy, glad to hear you're interested in webgme. Curious to hear about the problems you're trying to solve. About the server performance benchmark - there currently is no existing work...

It's meant to use the browsers printing feature and not render the html itself. The print is just a short-cut (and also ensures that all css classes are visible for...

It's not related. However have you tried `gmeConfig.storage.autoMerge.enable = true;`? With that every otherwise forked commit will be attempted to be merged.. If there are conflicts it will be considered...

Yogesh, we will propose this as class project in the MIC-class. We'll keep this issue open and will come with updates here. Thanks for the link.

https://sentry.io/vanderbilt-university/webgme/issues/199718443/