An especially interesting Forge accelerator is coming up, and how to handle Revit add-in language resources:
We currently have two upcoming Forge accelerators scheduled:
Joining a Forge accelerator is the most effective way to get up to speed on Forge in general and also to answer any and all BIM360 related questions you may be pondering.
As a knowledgeable and architecturally interested person might guess, the February event is AEC oriented.
An AEC focused online Forge accelerator is coming up February 22-26.
It is named "Waldspirale" in honour of the Austrian artist, environmentalist and architect Friedensreich Hundertwasser and his 105-apartment building of the same name in Darmstadt, Germany.
We are hence looking for proposals that aim to solve problems in design, construction and building life cycle management.
We very much look forward to discussing and supporting your many creative ideas and helping you to jump start your development with Forge during the week-long event.
In addition to the APIs that are already publicly available, we are also expecting to have some new sets of BIM 360 APIs to play with by then (*1):
If you are interested in using these new APIs, this event will be a great opportunity to learn and develop while "sitting" with development teams.
If you would like to know what will be possible with the Assets feature and its API, please check out the recordings of the recent Autodesk University presentations:
In addition, the Data Connector feature enables you to extract data at an account level with Executive privilege. This API will allow you to schedule extraction jobs and access extracted data.
In case of interest, here are more full articles and video recordings of the Forge classes at AU classes.
Please submit your proposal to forge.autodesk.com/accelerator-program.
If you would like to find out more about the new APIs in order to detail your proposal, feel free to indicate so in your proposal. We will get back to you and discuss further in your specific context.
(*1) Disclaimer: until we actually see the API officially released, the public release date might change.
Before closing for today, let's quickly also address a desktop Revit API issue.
Lukáš Kohout, Czech Architect and Revit Developer, very kindly solved a Revit API discussion forum thread about internationalisation or I18n on how to convert a Revit plugin from English to other languages:
Question: I have been developing Revit plugins for the past two years in English language.
Now, I intend to convert them into other languages to make them useful for people all around the world.
I would appreciate if anybody could help me with the procedure for doing so.
Answer: You can use Resources with string tables as described in the StockOverflow discussion on how to use localisation in C#.
Many thanks to Lukáš for the very helpful pointer.