Sunday, August 8, 2010

The Revit API, the next Frontier for BIM, Part 2

I agree with "Lindsay and Parley" assessment in part 1. Where my "wishful thinking" is aiming its sights on is best describe by your comment, " I don't think however that the BIM group is large or organized enough to create TRUE open source application coding". I believe that getting the open source application coding started sooner rather than later may be more wishful thinking today, but in the near future, well you never know what the future holds. Unless a market is created for it like what Apple/ Android market did with their products where "there's an App for that" created everyday. That is where I would like the "community" (cough-cough AUGI, cough-cough Autodesk, lol) to start focusing some of their efforts towards. So yes get attention with a "paid version" (yeeaa for Capitalism), but please also release a simplified free version & or a niffty little tool along with its Code for the greater good of the "BIM Frontier".
I had to make Part 1 a little provacative so someone could get my juices flowing, and that's why I ended the post with "to be continued", lol. It was on the tip of my tongue, but I was having too many distractions. Maybe there can be a Part 3... Oh yeah, it will be outlined in my journey with the API.
So little ole me will be trying to duplicate some of the feasable "tools" out there along with my own inspirations, which I will gladly share the finer details of my journey.
Just had an idea pop in my head about "creating the market" of sorts. If Autodesk would have an open competition where the best, let's say up to five, get selected to be part of the "for subscription" only downloads. How's that for Capitalism. What say you Autodesk, and if only they would, lol.

The Revit API, the next Frontier for BIM

For the past few months I've been methodically researching & thinking (trying not to reinvent the wheel, if it's already out there) of ways to create Addins to increase workflow/productivity. I've ran into a few things from the AU classes that really pop out, which are CP322-1, CP222-2, & CP314-2. I've ran into using programs like C#, VB.Net, & best of all VSTA. The reason I concluded with using VSTA as my primary tool for building "Apps" for Revit is because it's 64bit compatability. The next runner up was VB.Net, but its flaw is that it runs in a 32bit mode & it has to jump through hoops to connect to 64bit, thus making the "Need for Speed" useless. The precursor for both of these tools are programs like C# or C++, basically any program that starts with a "C", LOL. Any Computer Science Majors out there wanting to fill me in on the origins of writing "Code", feel free to do so.
Now earlier I said the word "Apps" that comes from the term used form phone Apps market. Basically my vision for the future in BIM API is that when people begin to say if, "can BIM do this", people will start to say, "I have an App for that", LOL. The only area that I see BIM being "caged" is when it comes to "Intellectual Property" from the "Indedendent Programmers". All "I" have to say about that is, What ever happened to the "I" in the BIM philosiphy. If you're in it for BIM then you're in it to "Share Information". Of course, there are some out there that share like Jeremy Tammik that do so & "I" love seeing that, but others that develop an Addin that's like the next best thing since sliced bread keep it klinched. Now "I" understand this is "Capitalism", but we are talking about BIM here, the next frontier. What would you best be known for a "Pioneer" or just another "Capitalist" for BIM, and that's my rant, LOL.
Now the next best thing since sliced bread is using the Revit VSTA to develop your "App", which if you look at Session ID "CP314-2" it will inform you of its location. If you view "CP322-1", then you'll know the direction I'm wanting to go when it comes to the API Development (productivity) & "I" will joyfully "Share" the "Fruits of my Labor"; to be continued....