in your license agreement in section 5.2 it is specified that it is not allowed to develop toolkits, APIs, libraries or components.
But in case I decide in favor of GdPicture, it will be part of a bigger solution. Therefore it will be included in its own component, which is a library that has an API defined in an interface, like it is supposed to be in a modern object oriented software project.
Now the question: is section 5.2 only meant for components, libraries, etc. that are made public individually or does it mean, that I have to basically reference the GdPicture dll from my main executable, because I’m not allowed to put it behind some kind of seam?
To make things clear for everyone here is the full 5.2 section:
That said I do not understand your question "that are made public individually or does it mean, that I have to basically reference the GdPicture dll from my main executable, because I’m not allowed to put it behind some kind of seam?"GdPicture.NET may not be used to develop software toolkits, API, libraries, components, command line software or any kind of third party software, except as authorized in writing by a duly authorized officer of ORPALIS.
Basically the main purpose of this section is to prevent the development of competitive Imaging SDK based on GdPicture SDK. It also prevent company to acquire only one developer license that will be used by X other developers in the same company (or in customer offices) using a simple wrapper...
What I can suggest is to contact our sales team through our quick contact form: http://www.gdpicture.com/contact/contact-form.php
With best regards,
Who is online
Users browsing this forum: No registered users and 1 guest