Tag Archives: Linux

Why every AutoCAD CAD Manager should have a copy of BricsCAD – part 5, LISP

This is the fifth post in this series where I explain why this statement holds true:

As a CAD Manager looking after AutoCAD users, or a power user looking after yourself, it’s worth your while to have a copy of BricsCAD handy.

This post is about BricsCAD being better than AutoCAD at the one thing that made AutoCAD win the race against its competitors back in the 80s – LISP. That is, AutoLISP (added fully to AutoCAD in Version 2.18) and Visual LISP (fully integrated with AutoCAD 2000).

If you’re a good AutoCAD CAD Manager, you’ll already know the reasons LISP is an extremely important tool, so I won’t cover them here. I may explain those reasons in a later post, but that would distract us from the main point. Why is having a copy of BricsCAD useful to a CAD Manager?

  • BLADE. I’ve covered the BricsCAD LISP Advanced Development Environment in various posts already, and I intend to go into greater detail in future posts. There are enough advantages over VLIDE to warrant an entire series of posts. This is simply the biggest advance for CAD LISP in 20 years; if you’re doing any reasonably complex development in LISP and you’re not BLADE, you’re wasting time and money.
  • Performance. Because BricsCAD’s LISP engine is much more modern than AutoCAD’s, the performance is much greater. In my experience, it’s about three times as fast. Some function calls are as much as 30 times as fast. If you have a user who’s complaining that your routine is taking an age to process in AutoCAD, try it in BricsCAD instead. I once saved a user half an hour in processing time for one polyline by using BricsCAD. Another aspect that will benefit you when programming and testing is BricsCAD’s generally superior performance. Got nothing running and want to get programming in the next 5 seconds? Fire up BricsCAD. Want to do a complex process on a big drawing that makes AutoCAD run out of RAM? Try it in BricsCAD.
  • Licensing. While you’re developing in BricsCAD, you’re not using up an expensive AutoCAD license. You’re using a cheaper (or even free, while you’re evaluating it) BricsCAD license. Also, it’s a perpetual license so if you ever stop paying, you can keep developing as long as you like. Oh, and it’s not going to flake out on you on those days where Autodesk’s subscription licensing server has a meltdown.
  • Extra functionality. BricsCAD’s LISP has the AutoLISP and Visual LISP functions and then some. Some of the DOSLib functions are available without even needing DOSLib, but if you need the full set of DOSLib functions they can be loaded, as per AutoCAD. A range of extended functions are available with the vle- prefix, and the LISP Developer Support Package documents these and provides the source code so you can also use them in AutoCAD.
  • Platform independence. AutoCAD for Mac has severely restricted LISP capabilities, making it unsuitable for use in a professional, efficient custom environment. BricsCAD for Mac and BricsCAD for Linux both provide practically identical functionality to the Windows version. Yes, BricsCAD for Mac really is significantly more AutoCAD-compatible than AutoCAD for Mac.

I do my LISP development in BricsCAD these days, and can attest that it’s well worth the investment in time to get the hang of BLADE.

It will cost you a few minutes to download and install of an evaluation BricsCAD and check out the LISP situation for yourself.

Edit: it’s not just LISP. See James Maeding’s comment below about .NET, too.

The big Bricsys interview 10 – platforms

This is one of a series of posts covering an extensive interview with Bricsys CEO Erik De Keyser and COO Mark Van Den Bergh.

In this post, R.K. McSwain asks about BricsCAD running on three different platforms. Erik explains why BricsCAD for Mac (and Linux) is so much more complete than AutoCAD for Mac, which has more holes than a block of Swiss cheese.


R.K.: Do all three platforms (Windows, Linux, Mac) contain the same functionality?

Erik: Yes. Sometimes it’s a bit hard with the Mac to bring it along but so far, so good. The only problem sometimes is in the APIs.

We are using wxWidgets and not the Microsoft classes. This gives us the ability, with the same source code more or less, to serve Mac, Linux and Windows. By far Windows is the most important one. By history, all the applications are on Windows, because AutoCAD was only Windows. What we have as APIs, and the most important ones are BRX and .NET. If you want to port an application to Mac, it means our API must support that as well. BRX is doing that for 90 to 95%; there are a couple of functions that only work on Windows. For most of the applications, they can port their application to Linux or the Mac without any problems.

Steve: And you support the Visual LISP COM functions as well, right?

Mark: Yes, we cover them and they are also available on Mac and Linux.

Steve: You have a solution there that Autodesk doesn’t, which gives us the strange situation that BricsCAD for Mac is more AutoCAD-compatible than AutoCAD for Mac.

R.K.: AutoCAD for Mac leaves a lot of holes.

Erik: That’s because they rewrote the whole interface for Cocoa, and we didn’t. We are using one code base. You can be more Catholic than the Pope, yeah? If you rewrite AutoCAD completely for the Mac, the result is many holes, no applications possible, it doesn’t help anybody. We’re better off being pragmatic and doing it the way we did it.

Still, we must say that applications availability for Mac and Linux is not much. That has to do with 95% of our sales being on Windows. We expect that might change for BIM, because more architects are Mac users, partly because the first version of ArchiCAD was on Mac, Vectorworks is, so it’s really an Architect’s machine. We expect that maybe for BIM, it might change and we might sell more versions on the Mac.

Steve: Autodesk doesn’t have a competitor there, does it?

Erik: No, absolutely not.

Mark: I should mention that all of our keys are cross-platform. So when you buy a key, you can run them all. So every time you on decide to run on Mac and later on you decide to switch it to Windows, we don’t have any problem. You can switch whenever you want, from one to the other, on to Linux if you want.

Erik: Again, choice. It’s up to the users.


This is the complete set of links to this interview series:

Automated anti-telemarketer script – brilliant!

Annoyed by telemarketers? Too polite to abuse them or just hang up? Can’t be bothered wasting their time in person? Then you need AstyCrapper. If you’re using the open-source Asterisk PBX, it will crap on for ages on your behalf. It works by detecting responses from the telemarketer and silence gaps and responding with a series of recorded samples. It’s pretty convincing!

OK, maybe that doesn’t apply to you, but you can still have a good laugh at the example calls.

AutoCAD on Linux – Video

Lots of people get excited at the prospect of AutoCAD running under Linux. I’m not one of those people, but for those of you that are, here’s a video from a Linux enthusiast that shows AutoCAD running in an environment that’s doing all kinds of cool geeky stuff. It’s not mine and it’s from October 2006:

YouTube Link

Cool if you like that kind of thing, that is. I think the effects would drive me mad after a short period of dorkoid enthusiasm, but of course being Linux it would all be under complete user control.

Before you get too excited, I should point out that this is AutoCAD 2000, that is, software from last century. It’s running on Ubuntu Dapper with XGL installed and it required the copying of DLLs around from a Windows installation. It’s not supported (of course), and there’s no way of seeing what the real-world drafting performance and reliability is like. It’s a cool fun exercise for somebody with far more nerdish street cred than myself, but it’s not an environment I would use to earn a living.