Convert Honeybee+ Surface to Environment objects (Panels/Openings)

[FraserGreenroyd]

Issues addressed by this PR

Fixes #4

Test files

Available here

Changelog

Additional comments

[FraserGreenroyd]

/azp run LadybugTools_Toolkit.CheckCompliance

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[FraserGreenroyd]

/azp run LadybugTools_Toolkit.CheckCompliance

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[tg359]

Just jumping in here. Are we focusing on HB-Legacy solely, or including HB+ objects? There is quite a big difference between the workflows and data stored in them. I prefer the HB+ stuff as it's a bit more neat, but most workflows currently use the HB-Legacy objects. The HB+ components would more easily convert to/from BHoM directly.

[FraserGreenroyd]

@tg359 currently doing HB+ objects in this PR. Long term I think it would be good to do both.

I was speaking with Antoine this morning about this further and the LB team are developing up workflows to take LB models into JSON and a C# schema (which we're using as a nuget in this PR ready) to read that JSON and convert to C# objects which will make some of the workflows easier (as you can see from the code, this is basically taking an IronPython dynamic object and converting it to the BHoM object.

I'm not sure how well this PR would work with the legacy surface, but might be good to try out.

Long term it would be good to plan out the full workflows for this toolkit (in addition to getting something up for installer use and discussion), I'll probably suggest a workshop as we get to the end of the milestone to plan out tasks with @MarthaVoul @michaelhoehn @charliebrookerBH etc. 😄

[MajaLindroth]

Ran test script and it worked for me

[FraserGreenroyd]

/azp run LadybugTools_Toolkit.CheckInstaller

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).