Follow up meeting design changes
The latest meeting has given birth to a new path to follow. The new idea is broken into many aspects, the smallest of each being a representation of a shape. Above the shape would be translation (in a fine grained iteration) and above that is a cluster of these shapes and a random form of union between them.
Shape: there are many ways in which this could be tackled, but the idea that in some form there is a programmatic representation of a shape literal, be it in discrete objects or mathematically such as a origin point and number of sides/length. A library in this area could potentially exist, depending on the software
Translation: The next part of the branch would be the transformation of this shape in some form of programmatic representation. For example a function could be represented as shapeRotate (shapeLiteral, x, y) where x and y are just placeholder variables. The principle would be that a shape and some values would be passed in and a new translated shape coordinates or size values would be returned.
Combination: Above this scope is the combination aspect of the loop, whereby shapes are combined, through certain types of joins or unions. The output from this step could potentially be a grotesque amalgamation of shapes, which propagated further up the chain or used in a future iteration, could be used in the genetic components of this program.
Loop: The core of the program would be dedicated loops, or main branch stems, that produce an output of a single set of shapes. Many of these loops would be spurned off with differing values to produce tweaked discrete loops at the end that are stored in a global cache of values or some form or representation.
Storage: The solution to the issue of how these values are represented and what this looks like in a usable programmatic sense is still in the air. The idea of a global list of shapes, coordinates and all other necessary values was discussed. This has the benefit of being an output of the program which can be fed back into the program as a starting point for a genetic growth, or a seed.
Once again I feel drawn to Javascript because of the semi functional nature, being able to pass functions as parameters and the simple nature of declaration of objects tends itself to a quick prototyping phase. The large user base leads me to believe there will be some form of simple shape library, plus the representation within a web page canvas gives strict confines with a highly distributed form.
