TheSwamp

CAD Forums => CAD General => BricsCAD Users => Topic started by: MP on February 15, 2018, 08:36:49 PM

Title: OMG
Post by: MP on February 15, 2018, 08:36:49 PM
(http://cdn.imza.com/indir/logo/128/bricscad.png) (http://wiki.mcneel.com/_media/doslib/doslib.png)

Just downloaded and installed the latest versions of BricsCAD (http://www.bricsys.com/en-intl/bricscad) (18.1.09) and DOSLIB (https://wiki.mcneel.com/doslib/home) (9.03) for same.

Ran a few tests. Absolute speed demon. Generally smokes its rival. The bulk of my utilities work straight out of the can -- and fast! A couple need rework, e.g. MOE (deep dives into the object model), but overall I am seriously impressed with the LISP implementation. VBA based utilities also work (with some re-work to address the lack of the VBASTMT command [or equivalent] so parameter passing from LISP to VBA currently has to be performed via kludgy slight of hand tricks). Anyway ... I'm grinning despite a crushing headache.

Well done Bricsys & partners, kudos!
Title: Re: OMG
Post by: kdub_nz on February 15, 2018, 09:21:53 PM
... and OpenDCL just keeps ticking along

:)

and the dotNET API works generally as expected.
 

added:
and the developers are responsive.
Title: Re: OMG
Post by: MP on February 15, 2018, 09:24:54 PM
I have some serious dev planned for BC, leveraging OpenDCL / Owen's great work is a no brainer!
Title: Re: OMG
Post by: MickD on February 16, 2018, 07:30:53 PM
...

and the dotNET API works generally as expected.
 
..

better than expected I think, it's when you port it to work with acad that you find the 'strange' things with the acad api that don't work 'as expected'. :)
Title: Re: OMG
Post by: CADbloke on May 23, 2018, 12:42:48 AM
added:
and the developers are responsive.
The CTO is responsive! I enquired about porting https://www.CADreplace.com to BricsCAD and the reply with all sort of offers of assistance came from their CTO. I don't recall getting an email from the A...k CTO lately.

and the dotNET API works generally as expected.
better than expected I think, it's when you port it to work with acad that you find the 'strange' things with the acad api that don't work 'as expected'. :)

That's good news and encouraging. I'll let you know how I go. I don't anticipate any major dramas. Famous last words, I know.