About the Author

September 2014

Sun Mon Tue Wed Thu Fri Sat
  1 2 3 4 5 6
7 8 9 10 11 12 13
14 15 16 17 18 19 20
21 22 23 24 25 26 27
28 29 30        

« Autodesk Homestyler New Year, New Room Sweepstakes | Main | Scan to BIM »

January 24, 2011

Comments

Feed You can follow this conversation by subscribing to the comment feed for this post.

Steve Germano

I agree, thats why its so important that 3rd party developers are not just comprised of software engineers, they are AEC background professionals with a passion in programming. Just look at most of the Autodesk employees, most of them come from a AEC background.

Phillip Miller

HI. Great post and I totally Agree with Steve as well. Both of us at Kiwi Codes are still in the Architecture Profession. I have my own Architectural Design business and Chris is an Architect. The main focus for us is how do we speed things up for the end user. I think we have achieved that pretty seamlessly with our latest release of Family Browser for Revit.
http://www.youtube.com/watch?v=TDVcydmz1Yw&hd=1

Keep up the great posts.

Cheers

Phillip

Emile Kfouri (Blog Author)

Hacking into our UI and subverting (read: extending) our interaction paradigms. Very interesting stuff. Philip and Chris I am interested to know if you were aware of the resources I mentioned above and if you made any use of them?

BTW - I already have you on my list of future posts. I see some very interesting tools coming out of ANZ and I want to cover as many of them as I can.

While I am talking about posts - I will also share with all of you the results of the survey (from my first post) in the next few weeks so fill it out already if you have not done so.

Phillip Miller

LOL. Yeh I was aware of those resources but chose to ignore them :). Seriously we have been so busy developing our tool that, those resources have taken a back seat. I do think we have integrated FB in to Revit pretty well though. I would love to be able to dock our tool Pallete to the Revit interface though ;)

Tim Waldock

Hi Emile,
You closed the comments on Siteworks, so I will comment here:
Your blogs states "Siteworks integrates well into the Revit user interface and uses native Revit families, components and toposurfaces" - it is my understanding that some of the elements it creates are not well integrated, like using Mass elements for retaining walls (I am going on hearsay on this, so please correct if wrong). We would love to see it properly integrated into Revit - well, to be honest this functionality should be part of core Revit, not an expensive add-on. Almost every architect needs to add a few basic roads and grades to their site model.

Having seen the video of Kiwicodes Family Browser, it looks fantastic, but again it should be how Revit works, not an add-on. Autodesk needs to pay royalties to Kiwicodes and integrate it to the Revit UI. That would free them up to produce some other great Apps for Revit.

Another good New Zealand App is Revit TV Drawing Manager - now that needs to remain as an App because it does something partly outside of core functionality (links external SQL database to Revit).

Emile Kfouri (Blog Author)

Tim - I am sorry the comments are closed for the other post. It must be done automatically :(

Sitework Integration: There is always room for improvement both on the developers part to integrate better and on Revit's part to open up more of the API. (As I mentioned in my post above). In short I agree that we can and should do more.

Core Functionality v. add-in: This has been an ongoing discussion with any product that has an API. This discussion is brought up around AutoCAD all the time. For example think of Softdesk and its contribution to AutoCAD. Without an API we all had to wait for the product team to deliver features to the market. With the API there are a lot more options. Having said that, I completely agree that what Kiwi has is cool and has raised a lot of interest in the Revit team. We will continue to invest in improving usability and access through the API.

RevitTV: This is also on my ever expanding list of products to highlight on the blog. Apart from having a cool name and logo they are also developing some very interesting solutions. They were the first developers to use the Revit Print API to build a compelling product that solved a clear user need. Kudos to them!

The comments to this entry are closed.