If an application were already developed using ACIS 6 do you have any idea of the difficulty level of converting the application to run on OpenCascade.
Thanks,
-jscott
Andras Tue, 06/01/2004 - 23:51
Have you succeded with the translation? Sorry for not responding earlier but I had (have) a lot a work. Basically we are porting our sw from ACIS 6.3.1 to OCC 5.1. I think we could share our succeses and failures:)
Actually there were many reasons but there are two major issues:
First of all a commercial one(no or less cost), however the implementation cost is not negligible:(
And second the available sorce code for the toolkit :). Here is another fact the ACIS source code is also available but...
Well the truth of the matter is the application is not mine nor am I involved in its development. A software that alot of users rely on (including myself) has been recently discontinued because the software company could not come to an agreement over continuing to license the ACIS kernel.
I came here doing a little research on my own to see if OpenCascade may be an option to save our beloved application. The company has other products so I was thinking if I could show them a way out we may see the return of our app.
Since you are working on a port can you give me any insite as to the difficulty level of the porting process. Are you just matching up ACIS functions to corresponding OCC functions or is this basically a re-write? Maybe it's somewhere inbetween?
Any insite you could provide would be much appreciated.
Sorry for the late but I just lost my harddisk's MBR. So I was unable to boot my computer for the last three days. Finally I found a tiny little sw what resolved my problems. Regarding you last post, yes it is somewhere between. ACIS and OCC topology is somehow similar but not totally. For us its a big "problem" the missing coedge from OCC which we use frequently in ACIS. But once you have understood one geometrical toolkit it's "very" easy to understand another. Beside you have the advantage that you know what you have to/should search in the new toolkit, like similarities in the function names, etc. etc. So in my oppinion it's not so hopeless the transcription to OCC, but we are in lack of time. Basically we have started from a simply OCC Viewer wizard generated skeleton and we are transposing the actual features from the ACIS based sw. But, and here comes the beauty, we developed a simplified geometrical toolkit which is more than enough for us, which seats in the back. We perform all the geometrical and topological operations on "our" toolkit and through a bidirectional mapping we are using OCC only for importing geometry and for visualise the result.
Tue, 06/01/2004 - 23:51
Have you succeded with the translation? Sorry for not responding earlier but I had (have) a lot a work. Basically we are porting our sw from ACIS 6.3.1 to OCC 5.1. I think we could share our succeses and failures:)
Wed, 06/02/2004 - 09:42
Why do you migrate from ACIS to OCC?
Is there any reason to do that?
We are choosing our kernel and want to know about your decision...
Thank you in advance...
Wed, 06/02/2004 - 18:24
Hi
Actually there were many reasons but there are two major issues:
First of all a commercial one(no or less cost), however the implementation cost is not negligible:(
And second the available sorce code for the toolkit :). Here is another fact the ACIS source code is also available but...
Best regards,
Andras
Fri, 06/04/2004 - 07:23
Well the truth of the matter is the application is not mine nor am I involved in its development. A software that alot of users rely on (including myself) has been recently discontinued because the software company could not come to an agreement over continuing to license the ACIS kernel.
I came here doing a little research on my own to see if OpenCascade may be an option to save our beloved application. The company has other products so I was thinking if I could show them a way out we may see the return of our app.
Since you are working on a port can you give me any insite as to the difficulty level of the porting process. Are you just matching up ACIS functions to corresponding OCC functions or is this basically a re-write? Maybe it's somewhere inbetween?
Any insite you could provide would be much appreciated.
Kind Regards,
-jscott
Wed, 06/09/2004 - 00:32
Sorry for the late but I just lost my harddisk's MBR. So I was unable to boot my computer for the last three days. Finally I found a tiny little sw what resolved my problems. Regarding you last post, yes it is somewhere between. ACIS and OCC topology is somehow similar but not totally. For us its a big "problem" the missing coedge from OCC which we use frequently in ACIS. But once you have understood one geometrical toolkit it's "very" easy to understand another. Beside you have the advantage that you know what you have to/should search in the new toolkit, like similarities in the function names, etc. etc. So in my oppinion it's not so hopeless the transcription to OCC, but we are in lack of time. Basically we have started from a simply OCC Viewer wizard generated skeleton and we are transposing the actual features from the ACIS based sw. But, and here comes the beauty, we developed a simplified geometrical toolkit which is more than enough for us, which seats in the back. We perform all the geometrical and topological operations on "our" toolkit and through a bidirectional mapping we are using OCC only for importing geometry and for visualise the result.
Thu, 06/10/2004 - 21:06
Thank you for responding....Much appreciated.
-jscott
Fri, 06/11/2004 - 00:26
Please do not hesitate to contact me if you are going into trouble:)
Andras