Thomas Corrie

- [x] Geometry Display - [x] Container Packing - [x] List - [ ] Math

Referred to this documentation for setting up a migrations file or node name changes: https://github.com/DynamoDS/Dynamo/wiki/Zero-Touch-Plugin-Development#migrations

Others have changed their class names to plural to avoid this https://github.com/DynamoDS/Dynamo/issues/8981#issuecomment-422927809 but if I change List to Lists then I get conflicts with others who have done this, e.g....

I have tried various options and the least troublesome seems to be to rename classes to avoid conflict. In this first example I have focused on the geometry nodes. Instead...

I have completed the review of class names with the following amendments. > CoordinateSystem > Abstract > Plane > Abstract > Vector > Abstract > Functions > Maths > List...

Spoke to Keith Alfaro at the London Dynamo + Generative Design Hackathon 2019 and he confirmed that you need to avoid using the same class names

@Vanman989 that is helpful, thank you, particularly the references to the literature. In the case of the EB-AFIT algorithm for 3D packing, I will have to delve into the sources...

@Vanman989 yes, the node can be used for 2D packing although I don't know off-hand how optimised it is for 2D because EB-AFIT was originally written for 3D. Feeding 0...

One additional thing to note is that EB-AFIT will test all possible orientations, so in its current form it isn't possible to restrict the X and Y dimensions to their...

As well as in this repository, the samples are included in Miscellany when you install from the Dynamo package manager, within the folder `\packages\Miscellany\extra\` An implementation in Python could follow...