TT Core Studio hosted their annual AEC Hackathon, the last weekend of September, and I was invited to join them as one of the Hackathon Leaders to help the participants with their new AEC app creations. Two days of hacking, pizza and red bull happened, delivering successful creation from the participants. I had a chance to show the LMV technology that Autodesk is promoting to make your web site 3D enabled, which also allows you to extract the valuable meta-data from your 3D models, and also, to partially join a team, while I helped others.
I will share with you a small summary of three apps that caught my eye and since I had a chance to help them or just heard their plan, I felt more identified with.
The first one will be the one I got to spend more time with, Augmented Reality BIM, the idea came out from the IKEA IPad app to place your new furniture with AR in your house, so together with a group of TT Core well known developers the hacking started. We even got that excited that we decided to trademark the idea and get the domain name for our project, check it out AugmentedBIM.com. It was definitely a fun experience to code along new awesome friends
The second one, who also won the Hackathon was the app called DOCQR using the Open Source Spectacles viewer and Revit API. The idea is to generate an open source QR code generator, that takes care of creating the URL to link to in order to view the model, and display it with Spectacles. Curious about it? you can read more about it here.
And the third one (secretly my favorite) was a set of plugins developed for Revit and Rhino that enable them to communicate with team members via Slack. This allows the model to alert users if something goes awry and giving a programmable interface for model management and maintenance. It is already available for you to play with and here is also more description about it and the link to their Github Repo.
Definitely it was a great weekend, You can check out the rest of the project’s here.
Back to Revit API, this week we hosted Revit Answer Days, which was a total success with over 900’ish posts, the only downside for us ADN is that we only had around 10 API questions, but I guess it was ok for being the first one. Again, congratulations on delivering great work from the entire Revit Team.
A post that I want to share with all of you today, came in the forum a couple of days ago, it is regarding the use of the New Workset API methods that became available not too long ago. The question came from user marcosmateo, here it is.
Question:Hi every one, I developed my addin Revit using c# 2012, this app creates a document Revit in a default route with a my custom template. I need create a new document with worksets included. In the window (app) the user must select the specialty, select path save file, write workset name and press "create file" button. the app will create a document with worksets. this is possible?, there are some example of how to do it? Thanks
Answer: Hi Marcos,Yes it is possible now to create a workset from the API, the method got introduced in Revit 2015 UR2 and is now available in Revit 2016.Here I'm providing you a small snippet of code that you can use in order to create a workset. If you want to know a bit more about Worksets and the API check this link.
public Workset CreateWorkset(Document document)
Workset newWorkset = null;
// Worksets can only be created in a document with worksharing enabled
string worksetName = "New Workset";
// Workset name must not be in use by another workset
if (WorksetTable.IsWorksetNameUnique(document, worksetName))
using (Transaction worksetTransaction = new Transaction(document, "Set preview view id"))
newWorkset = Workset.Create(document, worksetName);
Hope this helps you. Please let me know how it goes.
Even though Marcos didn’t reply, He accepted the answer as the solution so I will take that , he even gave me a Kudo, sounds like a win win for me.
Thank you for reading and until next time.