search

logant / Lyrebird

Interoperability for Grasshopper and Revit
22 stars 10 forks source link

Lyrebird #5

Open ksobon opened 9 years ago

ksobon commented 9 years ago

Timothy,

Instead of reporting an issue I would like to offer you help. I am by no means an expert in Grasshopper Kernel, Rhino Common or Revit API, but I have been using your tool for a while now and I love it. I want to help keep the development going forward. I prefer writing in Python so I am not sure how that fits with your C# set up but let me know if there is anything that I can do to make Lyrebird better.

logant commented 9 years ago

Hey Konrad,

I'm certainly not opposed to anyone else jumping in to help. I wound up changing jobs and have had less time to work on side projects like this over the last year. As for the Python help specifically, i'm not really sure how that would work. Unless I'm mistaken Python can't be compiled into a library, so there would either need to be some kind of Python interpreter for Lyrebird or the Python would need to be created as an executable that Lyrebird can launch and acquire data from. I'm somewhat new to python so I may be mistaken on some of that.

Did you have anything in mind that you'd like to see implemented?

ksobon commented 9 years ago

Well, nothing really specific that I need ASAP, but from the conversations on the Grasshopper forum I have seen a few outstanding items that would be helpful to have. For once I think that I made a suggestion that it would make sense to create another component that would query information from the Revit model. Some parameters require that you feed them ElementId or an object (Materials for example) so to allow Lyrebird to set those you might need another component to query that information up from Revit model. I thought of something exactly like the current Lyrebird component when you double click you can pick a family/type and it can output its elementId in the model. Output of that node could be used to set parameters in LyrebirdOut component. I am just thinking that it would be easier for people to set parameters this way rather than relaying on them to know how to get a family type element Id...that's tricky even with Revit Lookup tool. Yes, you cannot "easily" compile a Python file into a DLL. Since its an open source project I dont see this as an issue though and like you said there are EXE compilers for Python so at the end of the day we can just wrap whatever I create into an executable and fire it from your library, or I can start learning C# :-)