Dave Cowden a écrit :
> Hey, everyone:
Hi Dave,
>
> I have been working on getting more people to use my slicer
> application ( and thus OCC).
>
> One of the most common reasons people have cited for not using it is
> the installation of OpenCascade.
>
> There are three things that turn people off:
>
> (1) they have to register to get anything
> (2) the downloads are quite large
> (3) the installation process is hard.
>
> Have there been any thoughts/ideas to avoid this with pythonOCC by
> distributing a version of OpenCascade with it? I'm thinking perhaps a
> version with just the runtime libraries ( no docs, source, toolkits,
> etc )?
>
> Could this be incorporated into the PythonOCC installer? This could
> dramatically improve the number of takers on pythonOCC.
This could easily be done under Windows, but not under Linux (or
MacOSX). Here is then my suggestion for the packaging of the next release:
- Windows:
* pythonOCC only (about 30Mb),
* pythonOCC with OpenCascade (100Mb total).
- Linux: as it is now, a 'source' only distribution
- MacOSX: as it is now, a binary package for pythonOCC and a binary
package for OpenCascade 6.3.0.
>
> My additional hope would be that I could include my slicer app as a
> pythonOCC sample. This would mean people could use it with only one
> download, while it would allow me to avoid setting up another
> repository and ensure that my application is available as a sample.
Of course, no problem. It could come in the 'Tools' folder. I can give
you an svn write access if you want.
>
> Thoughts? thanks
>
> Dave
Bets Regards,
Thomas
_______________________________________________
Pythonocc-users mailing list
Pythonocc-users@gna.org
https://mail.gna.org/listinfo/pythonocc-users
