I recently receive a beta version of LazJS, a Javascript editor embedded within Revit.
Even if I more fluent with .NET and C#, I find the initiative quite interesting, especially when you have to quickly develop some small routine within Revit.
After installing it, I click on the ParamJS button to start their embedded editor.
As an example, I concatenate various parameters of a sheet in the sheet name in order to have them when I print or export it.
I start by selecting a category in the Categories list. Here, you can select multiple categories, but I will only select “Sheets” here. When I click on “Customize”, LazJS displays every editable parameters of our sheets in the “Parameters” list. Since I want to edit the name of my sheet, I select “Sheet Name” and save.
I can now drag and drop parameters from the “Formulas” list to the “Editor” panel. This creates automatically the correct line of code for calling this parameter. I drag some of my sheet parameters, add some “+” to concatenate them, and hit Run. We can see the result of my concatenation just below. I hit save, and my modification are added to my model.
If this is the quickest way to edit parameters, LazJS have also a fully functional editor, which allows us to create more elaborate routines.
I use it to create the same concatenation tool than in my previous example, everything came pretty easily with the auto-completion.
LazJS also provide a set of already existing scripts for inspiration.
Last but not least, LazJS provides functions for exporting and importing data to Excel. These functions are very easy to use, and can replace any plug-in dedicated to exporting and importing data from Excel.
Even if I will keep my habit with C#, the LazJS plug-in seems quite powerful, and far more easy to use than the Revit macro editor, since you don’t have to handle all the tedious document retrieval and the transaction handling.
The only problem I have to report is an error when I attempt to debug a Revit macro in SharpDevelop after installing LazJS. It is kind of annoying, but I am sure this problem will be addressed when they launch their final version.