| Re: IDL licensing question [message #48546] |
Tue, 02 May 2006 07:26 |
![Paul[2] is currently offline](theme/default/images/xoffline.png.pagespeed.ic.XRkd1fkXye.png "Paul[2] is currently offline")
Paul[2]
Messages: 13
Registered: January 2006
|
Junior Member |
|
|
JB wrote:
> Hello,
>
> Can someone explain me what an IDL developper license allows ? Let me
> explain my problem: I have developped a medical images viewer with a
> developper license of IDL 6.2. I have exported my app as a .sav compiled
> file, and can be run with IDL VM. I would like to distribute a
> self-installing package containing this sav file and the IDL 6.2
> environment exported from IDL dev studio. When you run my tool, user's
> got a splashscreen showing IDL VM logo, what seems to be OK.
> Since my tool is executed without license by the virtual machine, I
> believed that I needn't a redistributable license. But now I think I'am
> wrong, and online doc is not clear for me. Can someone help me, because
> RSINC does not seem to answer my questions...
>
> Thanx,
>
> JB
>
> PS: more info on my tool on my web site: http://jboivin.free.fr
Hi JB,
I think the confusion is due to the fact that you are also using DICOM
features in your application. For example, RSI is required to pay a
royalty for the underlying functionality exposed via the
read/write/query IDLffDOCOMEx interface and therefore, can not freely
distribute under the VM.
However, if you are simply reading images embedded in a DICOM Part 10
file, you could use the freely distributable IDLffDICOM object, or
READ_DICOM procedural interface and freely distribute under the VM.
Lastly, some who need DICOM read/write/query and also want to
distribute under the VM can do so by adding a DICOM Runtime license to
the distribution you build. This way, IDL is free to the end-user,
while the DICOM royalty is covered via a Runtime license agreement. If
you still have questions, please let me know.
Thanks,
-Paul
psommer@rsinc.com
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
