Iframe integration
The recommended integration is through iframes, as this allows for isolation:Variables used below which need to be replaced according to your on-premise installation or SaaS:
host
On-premise: the location you make the server available or just localhost when running locally
SaaS: https://app.kudo.graebert.com
port
On-premise: port you specified on setup (see Executable parameters )
SaaS: not required
queryParameters
See Editor parameters for query parameters that needs to be passed
Iframe integration
It is a common approach to integrate with Kudo Server via an iframe: an interested partner company can easily provide a web application that contains an iframe loading Kudo.
<div id="cadviewer" layout="column" layout-fill flex ng-cloak>
<iframe id="cadcontent" src="https://{host}:{port}/editor?auth={auth token}&file={fileId}...{queryParameters}">
</ iframe>
</div>
Widget integration
...
<html>
<head>
<style type="text/css">
.Kudo {
width: 1200px;
height: 800px;
}
</style>
</head>
<body>
<div id="editor" class="Kudo"></div>
<script src="https://{host}:{port}/editor.js?auth={auth token}&file={fileId}...{queryParameters}&target=editor">
</script>
</body>
</html>