Hello,
I'm currently working on a large scale enterprise solution, which basically is a smart client content and feature provider framework, with a central content server (asp.net) backend server.
The framework makes it possible to add plugins (among other things, such as documents etc.) to the client, by uploading them to the server. The next time the user hits the synchronize-button in the klient, the plugin is transferred to the klient, for immediate use by the user, and thereby also making the content/feature available in offline mode.
Now, the issue rises for a smarter input method in some of the plugins, and I came across your Wizard component, which looks very promising. Currently, we merge several ddl's into one when needed. A bit teadious, yes, but we accept it until we expand the plugin architecture further.
Now, the question is: Are there any legal or technical issues regarding the "inclusion" of your components into one of our plugins as part of a new feature? Please keep in mind, that there's no traditional "point of registration/installation" when expanding the client with new features. I've downloaded the evaluation copy, and have read the section on licensing in the documentation. My questions are partially answered, but I hope you can clarify in the context of the described needs.
I look forward to your answer - thanks in advance!
Kind regards,
Chris
[Modified 2 years ago]
