- It can "contain" other simulation objects
- It exposes one or more sequences of frequencies
- It maintains a clock with an update() method called once per tick, and sent to each of its contained simulations.
- the contained simulations must run their clocks in synch with the containing object's clock
A goal is to be able to populate a program with objects by declaring/initializing them, and then have the objects freely interact. But what is a "freely interact" supposed to be like when the classes do not know about each other and the programmer (me or you) does not have access to the header file definitions of the classes in use.
So what is a universal language of interaction? The only answer I can come up with is that when exposed frequencies "match" (in the clock of a containing parent class) energy can be exchanged and some kind of communication can occur between interactors. According to yesterday's post, such a "red-shift event"/interaction would need to generate a new class instance (a new "particle") with the frequency difference of the interactors - spun off as an offspring of the harmony.
I guess I don't want you to think I am another crazed mathematician. But I believe there is almost enough here to start creating prototype simulation class definitions, working programs, and some kind of approach to theoretical physics.
No comments:
Post a Comment