Skip to main content

I'm alive and so is BIM

So I haven't had the chance to post a lot, lately. That is not because I had nothing to say, but because I was busy. As anybody else, I guess. In fact, most of the people I meet are more than busy and getting eaten up by work, responsibilities...

Well, this isn't a post about complaining, beware. I thought I'd share a little thing, which might appeal to some of you. I'm working quite a lot with IFC files lately and while I clearly recommend to at least use a good viewer to check what you are exporting from your BIM software of choice or when checking an IFC you get from somebody else.

But from time to time, you need to dig inside the raw IFC data. The well-structured but otherwise not-meant-to-be-read IFC text code.

So you load up Notepad (on Windows) or TextEdit (on Mac) and open an IFC file... Well, better stop at this point. For one, notepad is nowhere up to any serious text editing task and secondly, well, it'll frustrate you. You need at least a decent code-editor that supports syntax hightlighting and line numbering, at the very least.

I have been using Crimson editor (discontinued since 2008) and more recently Notepad++ on Windows with good success and on OSX TextWrangler, which has been free for quite a while yet still with sufficient functionality for most text editing efforts (writing php, editing source code file, checking cmakelists.txt, reading "readme's", adjusting system settings files).

When loading an IFC file, non of the default Textwrangler language modules properly formats the IFC STEP-formatted file, so I created a language module for IFC.

So instead of looking at this unformatted spelling-checked raw text inside Textedit (or Notepad):

you can at least look at this inside TextWrangler:

While I assume that some dedicated IFC-editors (that is, looking at the rough text) probably exist, I'm quite pleased with a decent, constantly updated and well supported editor such as TextWrangler. It's inside the Appstore for free, it supports the new Retina display, it has powerful find and replace functionality, syntax highlighting, some macro's for text editing. The only thing bothering me is that I cannot indent text using the Tab key, like I used to do in other code-editors and that I haven't figured out how to 'run' a script from here, e.g. cmake a cmakelists.txt file or python a py file.

The actual Language Module for IFC that I created, which might be incomplete, but is far better than none, can be downloaded from my dropbox. It's very small (26 kB) and you need to copy it into the (hidden) Library subfolder on your Mac:

Go to your hidden Library folder underneath your used profile (in Finder: Command-Shift-G and enter the path ~/Library) and then to Application Support > TextWrangler > Language Modules and copy the file ifc.plist (an XML-formatted property list).

If any of you makes an improvement, please be so kind to share it.

Comments

Popular posts from this blog

Improve usage of BIM during early design phases

When I was collecting ideas for a book chapter on BIM (that seemed to never have emerged after that), I collected 10 ideas, which I believe still reflect good recommendations to improve the usage of BIM during the early design phases. These ideas are related to BIM software, but you can apply them in any flavor, as long as you can model with Building Elements, Spaces and have control over representation. Introduction This article gives an overview of several recommendations and tips, to better apply BIM applications and BIM methodologies, in the context of the early design phases. Many of these tips are applicable in any BIM application and they are based on experience gathered from teaching, researching and using BIM software. Sometimes they could help software developers to improve the workflow of their particular BIM implementation. Tip 1 : Gradually increase the amount of information In the early design phases, the architect makes assumptions and lays out the main design in...

Getting BIM data into Unity (Part 0 - Introduction)

This post reflects on work that I carried out, elaborated during my guidance of a few Master thesis students, to better integrate BIM models into Unity. This will be a multi-part post. This makes each article a bit shorter to read, but allows more in-depth information overall. Hope you like it. Please comment with feedback and further improvements. Basic methodology Unity can import geometry from FBX and Collada (DAE) files primarily. There are a few other formats, but these are the preferred ones. When integrating CAD or BIM files into a realtime environment, you have to convert the geometry. During my Unity teaching and the writing of the book Unity for Architectural Visualization ( buy from Packt ), I’ve come up with a basic diagram explaining geometry exchange between CAD and BIM software and Unity. Throughout these posts, we’ll go more into detail. We start with ArchiCAD, but will tackle Revit in a follow-up post. Promised!

PythonOCC : Open Source interactive CAD shell (and how to run it on OSX)

What is PythonOCC? PythonOCC is an Open Source (LGPL) Python-wrapper for OpenCASCADE. So what is OpenCASCADE (OCC)? This is an advanced Open Source (custom license) modeling kernel, comparable to commercial engines, such as ACIS or Parasolid, which are used in quite some commercial CAD programs. When you want to develop CAD software, you could use OCC and write programs in C++. And why using Python? With this wrapper, you can create CAD and geometry scripts in Python, which is an interpreted Object-oriented scripting language. You can write almost "on-the-fly" and seriously reduce the implementation effort, by skipping the compiling-phase. You can even interact with a running program in the Python interpreter. Want to read more about this? The OpenCASCADE official website  (currently Linux and Windows are officially supported) The PythonOCC website/blog  (beware that the core of the actions happen in the development repositories). So far so good. Now the nasty, techn...